Your organization is deploying a single project for 3 separate departments. Two of these departments require network connectivity between each other, but the third department should remain in…

Question

Options

• ACreate a Shared VPC Host Project and the respective Service Projects for each of the 3 separate
• BCreate 3 separate VPCs, and use Cloud VPN to establish connectivity between the two
• CCreate 3 separate VPCs, and use VPC peering to establish connectivity between the two
• DCreate a single project, and deploy specific firewall rules. Use network tags to isolate access

• A
  18% (5)
• B
  4% (1)
• C
  71% (20)
• D
  7% (2)

Explanation

The requirement for 'separate network administrative domains' means each department needs its own VPC - ruling out option D (single project/VPC). VPC Peering (C) is the right choice because it allows direct, low-overhead private connectivity between exactly the two departments that need it, while the third VPC remains fully isolated with no peering relationship. Compared to Cloud VPN (B), VPC peering is simpler to operate: no tunnels, no encryption overhead, no IKE/IPsec configuration, and no need to manage gateway VMs. Shared VPC (A) shares a single host network across all projects, which contradicts the requirement for separate administrative domains.

No community discussion yet for this question.