Your organization uses separate Google Cloud projects for shared services, development, testing, and production. - The shared services project hosts your private CI/CD runners and a central Artifact…

Question

Options

• ACreate a separate VPC in each of the four projects. Connect each environment's VPC to the
• BExpose the resources in the shared services project using an external load balancer. Implement a
• CCreate a separate VPC in each project. Use VPC Network Peering to create a full mesh,
• DConfigure the shared services project as a Shared VPC host. Create a single VPC in this host

• A
  63% (24)
• B
  11% (4)
• C
  5% (2)
• D
  21% (8)

Explanation

Creating separate VPCs for shared services, development, testing, and production, and then peering only each environment VPC with the shared services VPC forms a hub-and-spoke design. This allows: - CI/CD runners (in shared services VPC) to reach each GKE cluster over private IP. - GKE clusters (in env VPCs) to pull images privately from Artifact Registry (via Private Service Connect / VPC-SC aware patterns). - No direct connectivity between dev, test, and prod, because VPC Network Peering is non- transitive and you do not peer the environment VPCs with each other, thus enforcing strong isolation by design.

No community discussion yet for this question.