Google Professional Cloud Network Engineer
Get started today
Ultimate access to all questions.
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?
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?
Exam-Like
Explanation:
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.