Two VPC networks are peered: VPC-A and VPC-B. VPC-B is also peered with VPC-C. You need VPC-A to reach VPC-C without creating additional peering relationships. Which design is supported by Google Cloud?

The correct answer is to create a Network Connectivity Center (NCC) hub and attach the three networks as spokes. NCC provides a centralized connectivity management solution that supports transitive routing between spoke VPC networks connected to the same hub. This allows VPC-A to reach VPC-C via the NCC hub, even though they are not directly peered. Enabling transitive routing on VPC peering is incorrect because VPC Network Peering is non-transitive; A cannot reach C through B. Deploying a VM in B with IP forwarding is incorrect because while a VM could route traffic, it introduces a single point of failure and management overhead, and VPC peering itself doesn't automatically forward packets through an intermediate VM in this scenario without complex routing. Configuring custom static routes in B that point to C via VPC peering is incorrect because VPC peering does not support transitive routing, so a static route in B pointing to C via the peering link to C would not enable A to reach C through B.