You have defined subnets in a VPC within Google Cloud Platform. You need multiple projects to create Compute Engine instances with IP addresses from these subnets. What should you do?

Question

Options

• AConfigure Cloud VPN between the projects.
• BSet up VPC peering between all related projects.
• CChange the VPC subnets to enable private Google access.
• DUse Shared VPC to share the subnets with the other projects.

• A
  5% (1)
• B
  14% (3)
• C
  5% (1)
• D
  77% (17)

Explanation

A is not correct as Cloud VPN between projects does not provide you the functionality to share a subnet to host resources on. B is not correct because peering two VPCs does allow traffic between the two shared networks, but it's only bi-directional. Peered VPC networks remain administratively separate. C is not correct because private Google access allows you to access APIs from a private IP, but it does not have any impact on creating Compute instances on a specific subnet. D is correct because s Shared VPC allows you to share a VPC into multiple projects, keep administrative oversight in the host project, while restricting the other projects to only create VMs on IPs in the shared VPC. https://cloud.google.com/vpc/docs/shared-vpc https://cloud.google.com/vpc/docs/vpc-peering

No community discussion yet for this question.