Google Associate Cloud Engineer

Get started today

Ultimate access to all questions.

Explanation:

Option A is correct because shared VPC enables an organization to securely connect resources from multiple projects to a common VPC network, allowing them to communicate efficiently using internal IPs. This requires both projects to be within the same GCP organization. Sharing a VPC from one project to another facilitates communication between VMs across different projects and VPCs. Options B, C, and D are incorrect as they either suggest unnecessary creation of new VPCs or fail to address the prerequisite of projects belonging to the same GCP organization, which is essential for shared VPC functionality. For more details, refer to Google Cloud's documentation on shared VPC.

Explanation:

Comments (0)

No comments yet.

Your fantasy sports app consists of multiple backend microservices hosted on Compute Engine across different GCP projects. To enable communication between two groups of Compute Engine VMs located in different projects and separate VPCs, what is the recommended approach?

Real Exam

Ensure both projects are part of the same GCP organization. 2. Share the VPC from one project and configure the Compute Engine instances in the other project to use this shared VPC.

66.7%

Confirm you are the Project Administrator for both projects. 2. Establish a new VPC and migrate all instances into it.

11.1%

Verify both projects are under the same GCP organization. 2. Create a new VPC and include all instances within it.

14.8%

Ensure you have Project Administrator rights for both projects. 2. Create two new VPCs and distribute all instances between them.

7.4%