An enterprise organization is designing a custom-mode Virtual Private Cloud (VPC) network in Google Cloud to support a multi-region deployment across `us-east4` and `europe-west3`. The VPC will connect to an existing on-premises data center via Cloud VPN with BGP dynamic routing over an on-premises IP block of . Additionally, the team plans to deploy VPC-native Google Kubernetes Engine (GKE) clusters in both regions. Which TWO networking design choices are required to ensure proper IP allocation and prevent routing conflicts?
- Design subnets with primary IP ranges in each region that do not overlap with each other or with the on-premises CIDR block.Answer
- Define separate, non-overlapping secondary IP ranges for GKE pods and services within each regional subnet.Answer
- CCreate the VPC network using auto-mode to ensure all regional subnets are automatically provisioned with globally unique IP addresses that avoid hybrid network collisions.
- DReuse identical secondary CIDR blocks for pod aliases across both subnets to simplify cross-region pod routing within the global VPC network.
Answer
The correct requirements are to design primary IP ranges in each region that do not overlap with each other or on-premises networks, and to define separate, non-overlapping secondary IP ranges for GKE pods and services within each regional subnet.
In custom-mode VPC networks connected to on-premises data centers, primary subnet IP ranges must be non-overlapping across regions and with on-premises CIDR blocks () to enable accurate BGP route propagation over Cloud VPN. Furthermore, VPC-native GKE clusters rely on secondary subnet ranges for pods and services, which must be unique across all subnets to prevent internal IP conflicts within the global VPC network.
Step-by-Step Solution
Key Concept
VPC Subnet & Secondary Range IP Planning for Hybrid GKE Architectures
Estimated Time:2m 0s