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.
Your organization is deploying new Google Kubernetes Engine (GKE) 1.30 clusters in a Shared VPC environment connected to on-premises data centers over Cloud Interconnect and to external partner VPCs via VPC Network Peering. Previous GKE 1.28 clusters deployed with --master-ipv4-cidr encountered CIDR overlap errors with active peers and required proxy VMs for access from peered networks.
Your new architecture must meet these requirements:
/28 peering CIDR conflicts: Eliminate dedicated /28 control plane peering routes across the VPC peering group.Which control plane endpoint and networking configuration should you implement?
In GKE 1.29 and later, clusters use Private Service Connect (PSC) by default to connect worker nodes in your VPC to the Google-managed control plane tenant project, replacing legacy VPC Network Peering. Enabling the DNS-based endpoint (--enable-dns-access) provides each cluster with a unique, immutable fully qualified domain name (FQDN) under *.gke.goog hosted by the Google Front End (GFE) rather than relying on IP-based access.
container.googleapis.com and kubernetesmetadata.googleapis.com to the restricted services list of a VPC Service Controls perimeter enforces context-aware security boundaries across all Kubernetes API operations sent to the DNS-based endpoint.*.gke.goog is reachable over Google Cloud API paths, administrators in on-premises networks and peered VPCs can run kubectl directly through Private Google Access or a Private Service Connect endpoint for Google APIs (with gke.goog DNS records) without proxy VMs or bastion hosts./28 peering CIDR conflicts: Omitting --master-ipv4-cidr allows PSC to allocate an internal endpoint from the cluster's primary subnet (or --private-endpoint-subnetwork), eliminating imported /28 peering routes that conflict across Shared VPC peering groups.--no-enable-ip-access or --enable-private-endpoint disables client access via any external IP-based endpoint.Unlike IP-based endpoints—which cannot integrate directly with VPC Service Controls and, when paired with --master-ipv4-cidr peering, fail across non-transitive peering links—combining the DNS-based endpoint with Private Service Connect delivers seamless cross-network reachability, clean subnet IP management, and full VPC-SC protection.
This approach uses Private Service Connect with --private-endpoint-subnetwork to place the internal control plane endpoint in a chosen VPC subnet while keeping both the external and internal IP-based endpoints active. Access is filtered at the IP layer using --enable-master-authorized-networks to allowlist corporate public NAT addresses.
container.googleapis.com to a service perimeter does not govern kubectl requests sent to an external or internal IP-based endpoint; VPC-SC protection for Kubernetes API traffic requires accessing the cluster through the DNS-based endpoint (*.gke.goog) alongside kubernetesmetadata.googleapis.com.--private-endpoint-subnetwork avoids /28 peering route conflicts, omitting --enable-dns-access leaves the cluster without policy-based IAM and VPC-SC endpoint security.Your security policy permitted restricted public IP endpoint exposure via static corporate NAT allowlists and did not require VPC Service Controls perimeter enforcement over Kubernetes API operations.
--master-ipv4-cidr isThis legacy topology disables the external IP endpoint (--enable-private-endpoint) and allocates a dedicated /28 RFC 1918 block via --master-ipv4-cidr to connect the cluster VPC to the Google-managed control plane VPC over VPC Network Peering. Enabling --enable-master-global-access and --export-custom-routes extends routing for the internal passthrough Network Load Balancer to hybrid connections.
container.googleapis.com and kubernetesmetadata.googleapis.com), not arbitrary /28 IP CIDR ranges./28 peering CIDR conflicts: Specifying --master-ipv4-cidr creates a dedicated peering subnet route that is imported into the cluster VPC, reintroducing route overlap risks in Shared VPC peering groups where GKE cannot detect all peer overlaps.You were deploying legacy GKE 1.28 clusters (or required private IP-based webhooks incompatible with PSC), only needed hybrid reachability from on-premises rather than peered VPCs, and did not require VPC Service Controls enforcement.
--master-ipv4-cidr and authorized networks doesThis configuration activates the DNS-based endpoint (--enable-dns-access) while also defining a /28 --master-ipv4-cidr range, disabling the external IP endpoint (--enable-private-endpoint), and enabling --enable-authorized-networks-on-private-endpoint and --enable-master-global-access.
--enable-authorized-networks-on-private-endpoint flag only enforces source-IP CIDR allowlists on the IP-based internal endpoint. It does not enforce VPC Service Controls, which require adding container.googleapis.com and kubernetesmetadata.googleapis.com to a VPC-SC perimeter's restricted services list./28 CIDR allocation overhead: Specifying --master-ipv4-cidr instructs GKE to provision a separate subnet range for the control plane rather than allowing Private Service Connect to use the cluster's existing subnet, failing the requirement to eliminate dedicated /28 control plane CIDR blocks.*.gke.goog DNS records) to reach the DNS-based endpoint. Meanwhile, --enable-master-global-access only enables cross-region access to the IP-based internal passthrough Network Load Balancer.--master-ipv4-cidr is deprecated in the Google Cloud console for GKE 1.29+ and cannot be specified unless --enable-private-nodes is also set.You intended to secure an IP-based private endpoint across regions using IP allowlists rather than VPC Service Controls, and specifically needed a dedicated /28 CIDR instead of default Private Service Connect subnet allocation.
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