GCP Associate Cloud Engineer Practice Question 24: Shared VPC Host Project
Google Cloud Associate Cloud Engineer · Test 3 · question 4 of 10
A central network team must own the subnets, routes, and firewall rules for the whole organization. Application teams work in their own projects, and want to create VMs that use internal IP addresses from those centrally managed subnets, without each team running its own network.
What should you set up?
Show answer and explanation
Answer:
Shared VPC lets an organization connect resources from multiple service projects to one VPC network in a host project. The network team administers the network centrally, and service project users, granted the Compute Network User role on the shared subnets, create VMs whose internal IP addresses come from those subnets.
Option A gives every team its own VPC network to manage, and peering only exchanges routes between networks that stay separate and are still administered by each team. Option C puts every team in a single project, which removes the resource and billing separation and requires giving broad rights. Option D uses tunnels for hybrid connectivity, which adds cost and management overhead and does not centralise administration.
Reference: Shared VPC