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 runs a VPC-native Google Kubernetes Engine (GKE) cluster in a Shared VPC service project that connects to an on-premises data center over Cloud Interconnect. Currently, the cluster uses public nodes with ephemeral external IP addresses, which causes external SaaS partners to block node traffic after node upgrades and causes security audits to flag unrestricted access to non-VPC Service Controls Google APIs.
You need to redesign the GKE node configuration and Shared VPC networking to meet the following requirements:
*.pkg.dev) and only VPC Service Controls-supported Google APIs without traversing the public internet.Which architecture should you implement?
This configuration retains public GKE nodes that have ephemeral external IP addresses, attempts to place a Cloud NAT gateway inside a Shared VPC service project targeting only the Pod secondary range, and uses the private.googleapis.com VIP (199.36.153.8/30) for Google API and Artifact Registry name resolution.
*.googleapis.com to private.googleapis.com (199.36.153.8/30) allows access to all Google APIs, including those not supported by VPC Service Controls, violating the security audit requirement.199.36.153.8/30 VIP grants broad Google API reachability, whereas 199.36.153.4/30 enforces the VPC Service Controls restricted API surface.There is no valid scenario where this exact combination works in Shared VPC, because Cloud NAT must always reside in the host project, GKE NAT must cover both primary and secondary ranges, and VPC Service Controls compliance requires restricted.googleapis.com.
This approach uses private GKE nodes but assumes GKE automatically configures Private Google Access in a Shared VPC, advertises a 0.0.0.0/0 default route over Cloud Interconnect to send outbound traffic on-premises, and relies on Linux http_proxy and https_proxy environment variables alongside a host-project Cloud NAT gateway.
restricted.googleapis.com or Artifact Registry.0.0.0.0/0 dynamic route over Cloud Interconnect overrides the default route and renders Cloud NAT inoperable—preventing internet failover—and also disrupts Private Google Access unless explicit routes for Google API VIPs pointing to the default internet gateway are configured.http_proxy and https_proxy environment variables operates strictly on a best-effort basis; workloads or libraries that ignore these variables bypass the proxy completely.199.36.153.4/30, traffic is not restricted to VPC Service Controls-supported APIs.0.0.0.0/0 route directed to a VLAN attachment, Cloud VPN tunnel, or network virtual appliance.Private Google Access were manually enabled on the Shared VPC subnet with explicit routes to the default internet gateway for Google APIs, restricted.googleapis.com DNS zones were configured, and all external SaaS traffic were intentionally inspected on-premises without relying on Public Cloud NAT or best-effort Pod proxy variables.
A private GKE node pool removes external IP addresses from worker node VMs so that nodes only use internal RFC 1918 addresses, while Shared VPC centralizes subnet, DNS, and NAT management in the host project. Combining Private Google Access with the restricted Virtual IP (VIP) range (199.36.153.4/30) and Cloud NAT provides isolated, deterministic egress paths for both Google-managed services and external internet endpoints.
--enable-private-nodes provisions all GKE nodes with internal IP addresses only, removing direct internet exposure and ephemeral IP churn during autoscaling or upgrades.*.googleapis.com and *.pkg.dev to restricted.googleapis.com (199.36.153.4/30) keeps all registry pulls and API calls on Google's private network while blocking non-VPC Service Controls APIs.--disable-default-snat prevents nodes from performing IP masquerading on Pod traffic before it reaches the VPC network, offloading all SNAT tracking directly to Cloud NAT across both the primary node range and secondary Pod range.199.36.153.4/30 restricts access exclusively to APIs supported by VPC Service Controls.Unlike public node pools or service-project NAT attempts, this design enforces strict perimeter isolation on Shared VPC subnets, guarantees static egress IPs for third-party allowlisting, and eliminates redundant node-level SNAT.
This design mixes a private application node pool with a public egress gateway node pool running Cloud Service Mesh, keeps default node-level SNAT active, attempts to keep Private Google Access disabled so Artifact Registry pulls traverse Cloud NAT, and relies on legacy network tags for VPC firewall targeting.
Both the application and egress gateway node pools used private nodes with --disable-default-snat, Private Google Access and restricted.googleapis.com DNS were enabled for Artifact Registry, and Cloud NAT with manual static IPs served the gateway node pool using service accounts or IAM-governed Tags in firewall 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