A cloud administrator creates a VPC Network Peering connection between VPC-A and VPC-B, and another VPC Network Peering connection between VPC-B and VPC-C. A user attempts to ping a Compute Engine virtual machine in VPC-C directly from a virtual machine in VPC-A, but the traffic is dropped. What is the fundamental VPC networking rule causing this behavior?
- VPC Network Peering is non-transitive, so traffic cannot transit through VPC-B to reach VPC-C.Answer
- BInternal communication across separate VPC networks requires Cloud VPN tunnels instead of network peering.
- CVPC Service Controls automatically block internal IP traffic between peered networks unless an egress perimeter rule is configured.
- DPeered VPC networks require control plane authorized network ranges to be registered before Compute Engine instances can exchange traffic.
Answer
VPC Network Peering is non-transitive, so traffic cannot transit through VPC-B to reach VPC-C.
In Google Cloud, VPC Network Peering is non-transitive. Routes established between VPC-A and VPC-B are not passed along to VPC-C through VPC-B's peering connection. As a result, virtual machines in VPC-A cannot communicate directly with virtual machines in VPC-C.
Step-by-Step Solution
Key Concept
VPC Network Peering Transitivity
Estimated Time:1m 0s