An enterprise organization is planning a Google Cloud Virtual Private Cloud (VPC) network architecture to connect an on-premises data center using the IPv4 range to GCP via Cloud VPN. The cloud deployment will span two regions (`us-central1` and `europe-west1`) and will host Google Kubernetes Engine (GKE) clusters. Which TWO network design practices should the cloud engineer follow to prevent IP address collisions and maintain flexible network expansion? (Select TWO.)
- Create a Custom mode VPC network instead of an Auto mode VPC network to manually define non-overlapping subnet CIDR blocks.Cevap
- BUse an Auto mode VPC network so that Google Cloud automatically manages IP range expansion without manual subnetwork routing tables.
- Ensure secondary IP ranges allocated for GKE pods and services do not overlap with any on-premises CIDR ranges.Cevap
- DAssign a primary subnet range of in `us-central1` and rely on Cloud Router BGP to automatically resolve overlapping addresses.
Cevap
The cloud engineer must create a Custom mode VPC network to explicitly control subnet allocation and ensure that GKE secondary IP ranges do not overlap with on-premises CIDRs.
The correct responses identify key VPC planning requirements for hybrid enterprise networks. Using Custom mode VPC networks ensures that subnets are only created where needed with user-defined CIDR blocks, preventing automated creation of overlapping ranges. Additionally, accounting for GKE secondary IP ranges (used for Pods and Services) is necessary because these IP ranges must remain unique across both the GCP VPC and connected on-premises networks to avoid routing collisions.
Adım Adım Çözüm
Anahtar Kavram
VPC Network Planning and Hybrid Subnet Allocation