Your organization has five different VPCs across different projects in y our Google Cloud organization that need high-throughput connectivity. You have performed an audit of the IP address…

Question

Options

• ACreate a full mesh of VPC Network Peering connections between all five VPCs. Make sure not to
• BCreate a Network Connectivity Center hub with a mesh topology. Add a VPC spoke for each of
• CCreate a series of multiple network interface VMs with an interface in each VPC. Place the VMs in
• DCreate a full mesh of VPC Network Peering connections between all five VPCs with an export

• A
  10% (4)
• B
  66% (27)
• C
  20% (8)
• D
  5% (2)

Explanation

The key constraint is that two VPCs have overlapping Class E subnets (240.0.0.0/16 and 240.128.0.0/24), but the organization confirmed that no Class E traffic needs inter-VPC routing. Network Connectivity Center with a mesh topology allows you to add each VPC as a spoke and selectively exclude specific subnet ranges from being advertised - meaning you can suppress the Class E subnets while still enabling connectivity for all other subnets. Option A and D (VPC Network Peering full mesh) cannot work when any subnets overlap, even if only some VPCs are affected - peering requires completely non-overlapping CIDR ranges across the entire peered pair. Option C (multi-NIC VMs) is operationally complex, does not scale well, and is not a Google-recommended routing solution for this scenario.

No community discussion yet for this question.