Question

Your company operates four production VPCs (vpc-app, vpc-data, vpc-web, vpc-shared) in different projects that must all communicate with each other with full mesh connectivity. Currently they are connected using VPC Network Peering, but the team is frustrated because peering is non-transitive, requiring many individual peering connections that are hard to manage as VPCs are added. You need a managed solution that provides transitive full-mesh connectivity between all VPCs while minimizing operational overhead. What should you do?

Accepted Answer

Create a Network Connectivity Center hub and attach each of the four VPCs as VPC spokes so they exchange routes transitively.

Answer

Configure a hub-and-spoke topology by designating vpc-shared as a transit VPC and creating custom static routes in each VPC pointing to it.

Answer

Migrate all workloads into a single Shared VPC host project so no inter-VPC connectivity is required.

Answer

Deploy HA VPN tunnels between every pair of VPCs and enable BGP on Cloud Routers to exchange dynamic routes.