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 a VPC-native Google Kubernetes Engine (GKE) cluster in us-central1 for a platform engineering team. You must design the cluster's networking to satisfy these requirements:
198.51.100.0/28 and 203.0.113.16/28) must run kubectl commands over the internet without Cloud VPN or Cloud Interconnect.Which control plane and cluster networking configuration should you implement?
--enable-private-nodes) and disable the control plane's external endpoint (--enable-private-endpoint), then enable authorized networks on the internal endpoint (--enable-authorized-networks-on-private-endpoint) with 198.51.100.0/28 and 203.0.113.16/28.Setting --enable-private-endpoint disables the control plane's external IP-based endpoint, leaving only the internal IP-based endpoint active inside the cluster's VPC network. Combining this with --enable-authorized-networks-on-private-endpoint restricts which source IP ranges can reach that internal endpoint.
198.51.100.0/28 and 203.0.113.16/28) to the authorized networks list, branch office traffic cannot route to a private VPC endpoint without Cloud VPN, Cloud Interconnect, or a bastion host.kubectl traffic, which directly violates the constraint against bastion hosts.--enable-master-global-access).This architecture would be optimal if the branch offices already had Cloud VPN or Cloud Interconnect connectivity to the cluster's VPC network (using private RFC 1918 source CIDRs), or if the organization required zero internet exposure for the control plane and accepted using a VPC bastion host for administration.
--enable-private-nodes) while keeping the external IP-based endpoint enabled, configure authorized networks for 198.51.100.0/28 and 203.0.113.16/28, and add Google Cloud external IP addresses to the authorized networks list so GKE management services can reach the cluster.This configuration keeps the external control plane endpoint enabled with authorized networks for the two branch offices, while also enabling Google Cloud external IP address access (the opposite of --no-enable-google-cloud-access). It conflates Google Cloud external IP addresses with Google-reserved IP addresses.
/32 external IP of a controlled host if needed.--no-enable-google-cloud-access does not take effect immediately and can take several hours to propagate across firewall rules.This setting would only be acceptable in low-security development or testing environments where broad access from Google-hosted external workloads (such as dynamic Cloud Shell sessions or ephemeral external CI runners on Google Cloud) is acceptable and multi-tenant GCP IP exposure is not a concern.
--enable-private-nodes), disable all IP-based control plane endpoints (--no-enable-ip-access), enable the DNS-based endpoint (--enable-dns-access), and create VPC ingress firewall rules permitting 198.51.100.0/28 and 203.0.113.16/28.This option transitions the cluster completely to a DNS-based control plane endpoint (--enable-dns-access) while turning off both internal and external IP-based endpoints (--no-enable-ip-access), and attempts to enforce source IP restrictions using VPC firewall rules.
--master-authorized-networks) apply exclusively to IP-based endpoints, not to the DNS-based endpoint.container.googleapis.com and kubernetesmetadata.googleapis.com to a VPC Service Controls service perimeter.This configuration (using --enable-dns-access and --no-enable-ip-access) would be the Google Cloud recommended best practice if the organization were permitted to use VPC Service Controls and IAM policies instead of IP-based authorized networks to restrict control plane access.
--enable-private-nodes) while keeping the control plane's external IP-based endpoint enabled, enable control plane authorized networks (--enable-master-authorized-networks) allowing only 198.51.100.0/28 and 203.0.113.16/28, and deny access from Google Cloud external IP addresses (--no-enable-google-cloud-access).This configuration implements a hybrid GKE network isolation model that separates data plane isolation (private worker nodes) from control plane reachability (an external IP-based endpoint protected by authorized networks). By enabling --enable-private-nodes while omitting --enable-private-endpoint, the cluster exposes both an internal and an external IP-based control plane endpoint while ensuring worker nodes receive only internal RFC 1918 IP addresses.
--enable-private-nodes ensures GKE worker nodes have no external IP addresses. Furthermore, regardless of whether the external control plane endpoint is active, GKE nodes always communicate with the control plane exclusively over the internal endpoint via Google's private network.kubectl over TLS without needing Cloud VPN, Cloud Interconnect, or intermediary bastion hosts.--enable-master-authorized-networks enforces an IP-based firewall at the control plane boundary, permitting only the allowlisted branch office CIDRs (198.51.100.0/28 and 203.0.113.16/28), the cluster's own node/Pod ranges, and Google-reserved IP addresses needed for GKE management. Explicitly setting --no-enable-google-cloud-access prevents other Google Cloud customers' external VM or Cloud Run IP addresses from reaching the endpoint.Unlike a private-endpoint-only model, this design supports direct internet administration from known static branch office CIDRs without VPN tunnels or bastion hosts. Unlike allowing all Google Cloud external IPs or switching to a DNS-only endpoint, it enforces strict source IP filtering directly at the control plane firewall without requiring VPC Service Controls.
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