Answer-first summary for fast verification
Answer: Create a Network Connectivity Center hub with a mesh topology. Add a VPC spoke for each of the five VPCs and configure an export exclude filter for 240.0.0.0/4. Add Cloud network firewall policy rules to allow traffic.
The requirement is to enable high-throughput connectivity between five VPCs while avoiding conflicts due to overlapping subnets in the 240.0.0.0/4 (Class E) range, which do not require inter-VPC connectivity. - **Option A** and **D** (VPC peering) are invalid because VPC peering automatically exchanges all subnet routes, including the overlapping 240.0.0.0/16 and 240.128.0.0/24. There is no native way to exclude specific private subnet routes like 240.0.0.0/4 in peering configurations, leading to route conflicts. - **Option C** proposes using multi-NIC VMs and load balancers, which technically works but introduces complexity and manual routing management, making it less optimal. - **Option B** uses Network Connectivity Center (NCC) with an export filter to exclude 240.0.0.0/4. This ensures the overlapping subnets are not advertised, while allowing other subnets to communicate via the hub-and-spoke mesh. NCC provides a managed, scalable solution without manual infrastructure, aligning best with the requirements.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
Your organization has five VPCs across multiple projects in Google Cloud that require high-throughput connectivity. An IP address audit revealed two VPCs have overlapping subnets: 240.0.0.0/16 and 240.128.0.0/24. No Class E subnets (240.0.0.0/4) will need inter-VPC connectivity, but all other subnets must remain connected. How should you design a Google Cloud routing solution to fulfill these requirements?
A
Create a full mesh of VPC Network Peering connections between all five VPCs. Make sure not to import or export subnet routes with public IP addresses. Add Cloud network firewall policy rules to allow traffic.
B
Create a Network Connectivity Center hub with a mesh topology. Add a VPC spoke for each of the five VPCs and configure an export exclude filter for 240.0.0.0/4. Add Cloud network firewall policy rules to allow traffic.
C
Create a series of multiple network interface VMs with an interface in each VPPlace the VMs in an instance group. Create an internal passthrough Network Load Balancer in each VPC with the backend of the instance group. Configure custom static routes in each VPC with the next hop of the respective load balancer. Add Cloud network firewall policy rules to allow traffic.
D
Create a full mesh of VPC Network Peering connections between all five VPCs with an export exclude filter for 240.0.0.0/4 on every side. Add Cloud network firewall policy rules to allow traffic.