A cloud architect is configuring network connectivity across three independent Google Cloud Virtual Private Cloud (VPC) networks: VPC-1, VPC-2, and VPC-3. Active VPC Network Peering connections exist between VPC-1 and VPC-2, as well as between VPC-2 and VPC-3. Compute instances in VPC-1 are unable to reach instances in VPC-3 using internal IP addresses. Which network topology configuration is required to allow direct private communication between VPC-1 and VPC-3?
- Establish a direct VPC Network Peering connection between VPC-1 and VPC-3.Answer
- BEnable custom route exchange on both existing peering connections to support transitive routing through VPC-2.
- CDeploy a Dedicated Interconnect connection between VPC-1 and VPC-3 to route internal traffic.
- DCreate a VPC Service Controls perimeter encompassing VPC-1, VPC-2, and VPC-3 to enable cross-VPC network routing.
Answer
Establish a direct VPC Network Peering connection between VPC-1 and VPC-3.
VPC Network Peering in Google Cloud is strictly non-transitive. Although VPC-1 is peered with VPC-2 and VPC-2 is peered with VPC-3, resources in VPC-1 cannot communicate with resources in VPC-3 via VPC-2. Establishing a direct peering connection between VPC-1 and VPC-3 is required to exchange internal IP routes between them.
Step-by-Step Solution
Key Concept
VPC Network Peering Non-Transitivity