Examkin

Question

Difficulty: MediumPlanning Virtual Private Cloud (VPC) Networks and Subnets

An organization is planning a Google Cloud Virtual Private Cloud (VPC) design for a multi-region enterprise workload. The deployment requires Google Kubernetes Engine (GKE) clusters in `us-central1` and `europe-west1`, and the entire cloud footprint must connect to an on-premises network via Cloud VPN. Which TWO subnet and network planning decisions should the architect implement to ensure seamless connectivity without IP routing conflicts?

  1. Create a custom-mode VPC network to manually define primary and secondary subnet IP ranges for each region.Answer
  2. B
    Deploy an auto-mode VPC network so that subnets and secondary IP ranges automatically expand into reserved regional blocks.
  3. Allocate dedicated, non-overlapping secondary IP ranges within each subnet for GKE Pod and Service IP address assignments.Answer
  4. D
    Configure primary subnet ranges to automatically expand into non-contiguous IP blocks whenever instance scaling occurs.

Answer

Create a custom-mode VPC network to manually define primary and secondary subnet IP ranges for each region, and allocate dedicated, non-overlapping secondary IP ranges within each subnet for GKE Pod and Service IP address assignments.
Enterprise hybrid architectures connecting GCP to on-premises environments via Cloud VPN require custom-mode VPC networks to maintain strict control over IP allocation and prevent overlap. Furthermore, GKE VPC-native clusters require secondary IP ranges within subnets to handle Pod and Service IP addressing without conflicting with on-premises routing tables.

Step-by-Step Solution

1
Evaluate network creation mode requirements for enterprise hybrid environments.
Select custom-mode VPC because auto-mode uses predefined CIDRs within 10.128.0.0/910.128.0.0/9 that often overlap with corporate on-premises networks.
Custom-mode VPC allows strict specification of subnet CIDR blocks to prevent IP collision across hybrid Cloud VPN tunnels.
2
Plan IP address allocations for Kubernetes cluster workloads.
Assign dedicated secondary IP ranges for GKE Pods and Services in each regional subnet.
VPC-native GKE clusters rely on secondary IP ranges for Pod and Service networking, which must be routable and non-overlapping across the network.

Key Concept

Planning custom-mode VPC networks and secondary IP ranges for multi-region GKE hybrid deployments
Estimated Time:2m 0s
Rate this question

Topics

Planning Virtual Private Cloud (VPC) Networks and Subnets

More questions from this topic