A cloud architect is designing a network topology connecting three distinct Google Cloud Virtual Private Cloud (VPC) networks: VPC-A, VPC-B, and VPC-C. Currently, VPC-A is peered directly with VPC-B, and VPC-B is peered directly with VPC-C. Workloads in VPC-A require highly available, low-latency private connectivity to resources in VPC-C without traversing the public internet. Which configuration fulfills this network requirement?
- Establish a direct VPC Network Peering connection between VPC-A and VPC-C.Answer
- BMaintain the current topology, because VPC Network Peering inherently routes traffic transitively through VPC-B.
- CReplace the VPC-B to VPC-C peering connection with a Dedicated Interconnect connection to enable transit routing.
- DEnclose VPC-A, VPC-B, and VPC-C inside a single VPC Service Controls perimeter to automatically route inter-VPC traffic.
Answer
Establish a direct VPC Network Peering connection between VPC-A and VPC-C.
Google Cloud VPC Network Peering is strictly non-transitive. Even though VPC-A is peered with VPC-B and VPC-B is peered with VPC-C, workloads in VPC-A cannot reach VPC-C through VPC-B. Creating a direct VPC Network Peering connection between VPC-A and VPC-C satisfies the high availability and low latency requirements using internal IP addresses.
Step-by-Step Solution
Key Concept
VPC Network Peering Non-Transitivity