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 are deploying a VPC-native, private Google Kubernetes Engine (GKE) cluster (version 1.30) in a Shared VPC service project using a subnet shared from the host project. Your architecture must satisfy the following security and networking requirements:
10.20.0.0/24) in a different Google Cloud region while blocking Google Cloud external IP addresses.Which configuration should you implement?
--enable-private-nodes, --enable-private-endpoint, --enable-master-global-access, and a validating webhook configured with the internal IP address of a host-project backend.This approach routes all Google API and container registry traffic through Cloud NAT by disabling Private Google Access, enforces an ultra-restrictive node ingress firewall rule allowing only TCP port 443, and points a Kubernetes admission webhook directly to an internal IP address URL.
443 blocks mandatory control plane-to-node communication—most critically kubelet traffic on TCP port 10250—causing nodes to fail registration and the cluster to stop functioning.Service backed by a manually managed Endpoints or EndpointSlice object.--disable-default-snat) nor enables Pod-level NetworkPolicy enforcement and logging.10250 from the control plane) are required for cluster health and must never be overwritten or blocked.Private Google Access remained enabled, default GKE control plane firewall rules on port 10250 were preserved, webhooks used a headless Service rather than a raw internal IP URL, and Dataplane V2 with --disable-default-snat was configured.
--enable-private-nodes, --enable-private-endpoint, --enable-master-global-access, --no-enable-google-cloud-access, authorized networks restricted to 10.20.0.0/24 on the internal endpoint, --disable-default-snat, and GKE Dataplane V2 enabled for Kubernetes NetworkPolicies.This architecture combines Shared VPC host-project network controls with a Private Service Connect (PSC)-based private GKE cluster, offloading outbound NAT translation to Cloud NAT and enforcing Pod-level microsegmentation through GKE Dataplane V2.
--enable-private-nodes ensures worker nodes receive only internal IP addresses, while --enable-private-endpoint disables the public control plane endpoint. Applying authorized networks to the internal endpoint restricts access exclusively to 10.20.0.0/24, --enable-master-global-access allows that remote region to reach the internal endpoint, and --no-enable-google-cloud-access blocks Google Cloud external IP addresses.--disable-default-snat—offloads SNAT tracking directly to Cloud NAT, eliminating double SNAT.NetworkLogging) at the Pod layer without interfering with node-level control plane traffic.Every network boundary is secured using the exact plane designed for it: Shared VPC host-project infrastructure handles subnet routing, PGA, and Cloud NAT, PSC isolates the control plane, authorized networks with global access enforce L3/L4 access control, and Dataplane V2 enforces Pod-level policies.
10.20.0.0/24 to authorized networks, then disable the external endpoint without enabling control plane global access, and apply VPC egress-deny firewall rules targeting the node network tags to restrict Pod outbound traffic.This configuration places Cloud Router and Cloud NAT in the Shared VPC service project, enables authorized networks before disabling the external control plane endpoint, omits global access, and relies on node-targeted VPC egress-deny firewall rules for Pod isolation.
--enable-master-global-access blocks 10.20.0.0/24 because clients in another Google Cloud region cannot reach the internal endpoint by default.kubectl exec, while failing to provide Pod-level granularity or logging.The cluster ran in a standalone VPC inside the same project, Private Google Access was manually enabled, global access was turned on, and Pod-level NetworkPolicies replaced node-level egress-deny rules.
--master-ipv4-cidr), private nodes, and --enable-private-endpoint with authorized networks set to 10.20.0.0/24. Rely on GKE to automatically enable Private Google Access on the Shared VPC subnet, configure a Cloud NAT gateway in the host project for the primary node IP range only while retaining default node SNAT, and enforce Pod-level traffic rules using VPC firewall rules in the host project.This configuration attempts to deploy a legacy VPC Network Peering-based private GKE cluster in a Shared VPC environment while relying on automatic subnet settings, node-level SNAT, and VPC firewall rules to manage cluster connectivity and Pod security.
iptables on the node, and again from node IP to NAT IP at the Cloud NAT gateway—reducing scalability and connection tracking efficiency.--enable-master-global-access) prevents the operations subnet (10.20.0.0/24) in a different Google Cloud region from reaching the internal passthrough Network Load Balancer backing the control plane endpoint.The architecture were deployed in a standalone VPC (not Shared VPC), required double SNAT for on-premises IP hiding, accessed the control plane only from the same region, and did not require Pod-level network policies.
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