Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Network Engineer practice bank has an additional 2,437 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
You manage a custom-mode Shared VPC host network (prod-host-vpc) that contains a subnet named gke-nodes-subnet in us-central1 with a primary IPv4 range of 10.40.10.0/24. This subnet hosts Compute Engine VMs and a VPC-native Google Kubernetes Engine (GKE) cluster configured with control plane authorized networks.
The Shared VPC is interconnected with two external environments:
analytics-vpc): Connected via VPC Network Peering, containing a subnet with a primary range of 10.40.12.0/23.10.40.8.0/24 into prod-host-vpc.Your team needs to scale the GKE cluster to support 450 nodes total without interrupting active traffic or migrating workloads. An engineer proposes expanding the primary IPv4 range of gke-nodes-subnet by reducing its prefix length to /22.
How should you evaluate this proposal and proceed?
/22 expansion because it spans 10.40.10.0 through 10.40.13.255 and overlaps with the peered VPC subnet 10.40.12.0/23; instead, create a new /23 subnet at 10.40.14.0/23 in the Shared VPC and migrate all existing nodes.This option assumes that reducing the prefix length of 10.40.10.0/24 to /22 expands strictly upward from .10 to .13 (10.40.10.0–10.40.13.255) and therefore collides with analytics-vpc (10.40.12.0/23), forcing a full workload migration to a brand-new subnet.
10.40.10.0 is not a valid network address for a /22 mask. The third octet 10 (00001010 in binary) aligns under a /22 mask to 8 (00001000), creating 10.40.8.0/22 (10.40.8.0–10.40.11.255). It does not touch 10.40.12.0/23 at all.10.40.14.0/23) and migrating all existing VMs and GKE nodes violates the requirement to scale without migrating workloads./22 expansion actually collides with the on-premises 10.40.8.0/24 route rather than the peered VPC./23 expansion (10.40.10.0/23) is valid and avoids migrating nodes.The existing subnet had been 10.40.12.0/24 or 10.40.14.0/24 and even a /23 expansion collided with neighboring peered and on-premises subnets, leaving no contiguous in-place expansion path and forcing a migration to a new subnet.
/22 expansion because it resolves to 10.40.8.0/22 and overlaps with the on-premises 10.40.8.0/24 range; instead, expand the primary range in place to /23 (10.40.10.0/23), and add the expanded range to the GKE control plane authorized networks list.Expanding a subnet's primary IPv4 range in Google Cloud works by reducing the CIDR prefix length so that the new, broader CIDR block strictly aligns on binary boundaries and fully encompasses the original allocation. Because 10 in binary (00001010) clears its last two bits when masked to /22, expanding 10.40.10.0/24 to /22 yields 10.40.8.0/22 (10.40.8.0–10.40.11.255), which directly collides with the on-premises 10.40.8.0/24 route.
/23 Meets Every Requirement10.40.10.0/24 to /23 produces 10.40.10.0/23 (10.40.10.0–10.40.11.255). This avoids both the on-premises 10.40.8.0/24 prefix over Dedicated Interconnect and the peered analytics-vpc subnet at 10.40.12.0/23./23 primary range provides 512 - 4 = 508 usable IP addresses (accounting for the four Google Cloud reserved addresses per primary range), comfortably accommodating 450 nodes.10.40.10.0/23 to the control plane authorized networks list ensures new nodes assigned IPs in 10.40.11.0/24 can communicate with the GKE API server./24 range must be updated to include the newly expanded space.gcloud compute networks subnets expand-ip-range.Unlike creating a new subnet or migrating workloads, expanding to /23 scales capacity in place without downtime, prevents irreversible IP collisions with on-premises infrastructure, and maintains strict routing hygiene across peered and hybrid connections.
10.40.14.0/23 to gke-nodes-subnet in the Shared VPC host project so GKE can allocate additional primary node IPs without altering the /24 primary range.Subnet secondary IPv4 ranges provide additional CIDR blocks attached to an existing subnet exclusively for alias IP ranges. In VPC-native GKE clusters, secondary ranges are used for Pod IP addresses and Service (ClusterIP) IP addresses, not for VM or node interfaces.
10.40.14.0/23 as a secondary range leaves the primary range locked at 10.40.10.0/24 (maximum 252 usable node IPs), preventing the cluster from scaling to 450 nodes.The GKE cluster were running out of Pod IP addresses rather than primary node IP addresses, in which case adding a new secondary range (10.40.14.0/23) and registering it via --additional-pod-ipv4-ranges would expand Pod capacity without touching the primary range.
/22 expansion to 10.40.8.0/22 in the Shared VPC host project, and rely on Cloud Router BGP longest-prefix matching between 10.40.8.0/24 and 10.40.8.0/22 to preserve on-premises routing.This approach expands gke-nodes-subnet to 10.40.8.0/22 and attempts to rely on BGP longest-prefix matching to keep the more specific 10.40.8.0/24 dynamic route directing traffic to the on-premises data center.
gke-nodes-subnet expands to 10.40.8.0/22, Google Cloud treats 10.40.8.0/24 as available local subnet address space and will assign 10.40.8.x IP addresses to new GKE nodes or VMs, colliding with live on-premises hosts.allow-cidr-routes-overlap) with Proxy ARP and /32 custom advertisements are designed strictly for temporary workload migration, not permanent capacity expansion.The on-premises network were not using 10.40.8.0/24 (or any range inside 10.40.8.0/22) and the team explicitly needed up to 1,020 usable node IPs in gke-nodes-subnet.
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