A company is planning a Virtual Private Cloud (VPC) network in Google Cloud to host a multi-tenant Google Kubernetes Engine (GKE) cluster environment. The cloud network will connect directly to an existing on-premises data center using the IPv4 CIDR range . The design requires dedicated primary IP ranges for node instances and secondary IP ranges for Pods and Services, with the ability to expand subnet capacity in the future without network disruption.
Which TWO network planning practices should the cloud architect follow to meet these requirements? (Select TWO.)
- Provision the VPC network in custom mode to explicitly manage subnets and ensure primary and secondary IP ranges do not overlap with .Answer
- Reserve contiguous, unallocated IP address space adjacent to each primary subnet CIDR block to allow seamless subnet expansion in the future.Answer
- CProvision the VPC network in auto mode so Google Cloud automatically creates and resizes subnets across all regions as GKE workloads grow.
- DReuse the on-premises CIDR block for secondary GKE Pod alias ranges and rely on Cloud Router NAT to resolve address collisions.
Answer
The network architect should provision the VPC network in custom mode with non-overlapping ranges relative to the on-premises network, and reserve contiguous adjacent IP address space next to each primary subnet block to facilitate future CIDR expansion.
Custom-mode VPC networks provide complete control over IP range planning, ensuring that primary and secondary ranges do not conflict with connected on-premises networks (such as ). Additionally, reserving contiguous IP space next to existing subnets allows administrators to expand subnet primary ranges in-place without causing CIDR overlap errors.
Step-by-Step Solution
Key Concept
VPC Subnet Planning and Expansion Rules