Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
An enterprise uses a hub-and-spoke network topology on Google Cloud. The central hub-vpc is connected to multiple departmental spoke VPCs via VPC Network Peering, with custom route exchange enabled to share internal routes across networks.
A security engineer is deploying a private VPC-native Google Kubernetes Engine (GKE) cluster in spoke-vpc-a. The cluster deployment fails during creation with an IP address conflict error, even though the selected /28 control plane IP range does not overlap with any primary or secondary subnet ranges locally configured inside spoke-vpc-a.
What is the root cause of this deployment failure, and how should the engineer resolve it?
In a private VPC-native GKE cluster, Google Cloud manages the Kubernetes control plane within a separate Google-managed tenant project. Google Cloud establishes VPC Network Peering between the tenant project's VPC and the customer's VPC network (spoke-vpc-a) to enable secure, private communication between nodes and the master control plane.
/28 control plane route into the customer's VPC. Because VPC Network Peering enforces strict, global non-overlapping IP rules across the entire peering group, the control plane CIDR cannot conflict with any IP address space in the local VPC or any networks directly peered to it (such as hub-vpc)./28 range is free within spoke-vpc-a, an existing subnet, custom route, or imported route within the peered hub-vpc already occupies that CIDR block, violating peering constraints./28 RFC 1918 CIDR block that is completely distinct across the entire peering group resolves the validation failure./28 block (16 IPv4 addresses) dedicated to control plane replicas and load balancing.VPC Network Peering cannot be established or maintained when subnet ranges or static routes overlap across peered boundaries. Choosing a globally unique CIDR for the control plane satisfies GKE provisioning prerequisites without requiring structural alterations to the existing hub-and-spoke peering topology.
Routes-based clusters in Google Kubernetes Engine use static routes in Google Cloud VPC networks to direct traffic destined for Pods to specific node instances, rather than assigning native alias IP addresses directly from subnet secondary ranges.
A legacy infrastructure design strictly mandated avoiding alias IP configurations and relied entirely on Cloud Router BGP dynamic routing over hybrid interconnects to on-premises data centers without Google-managed private control plane peering.
In a VPC-native cluster, Google Cloud utilizes a primary range for node IP allocation and secondary alias IP ranges for Pods and Services (ClusterIPs) within the designated node subnet.
/28 subnet range inside the Google-managed tenant project; it does not consume IP addresses from the primary node subnet or the Pod secondary alias range./28 range provides 16 IP addresses, which is the exact fixed size required by Google Cloud for private cluster control planes. Allocating a /24 secondary alias range is unnecessary and does not resolve the tenant peering overlap./28 block within RFC 1918 or supported non-RFC 1918 space.The GKE cluster creation failed due to IP exhaustion when provisioning worker nodes or Pods within a depleted local subnet secondary range.
Transitive routing refers to the ability of intermediate networks to route traffic between two disconnected endpoint networks (e.g., Network A communicating with Network C through Network B).
The scenario involved connecting on-premises networks to multiple VPCs through a centralized transit hub using Cloud VPN or Interconnect gateways rather than direct VPC Network Peering.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated