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.
A financial services organization operates Google Kubernetes Engine (GKE) clusters in a custom VPC network (prod-vpc) and must enforce strict data exfiltration controls over cluster administration. Both private Compute Engine VMs (with no external IP addresses) and on-premises workstations (connected via Cloud Interconnect and Cloud Router) need to administer the GKE control planes while meeting these requirements:
0.0.0.0/0 route to the default internet gateway may exist in prod-vpc.Which configuration should you implement?
container.googleapis.com and kubernetesmetadata.googleapis.com to the VPC Service Controls perimeter's restricted services, deploy a Private Service Connect endpoint targeting the all-apis bundle without creating gke.goog DNS records, remove the 0.0.0.0/0 default route, and advertise the endpoint IP address via Cloud Router custom route advertisements.Private Service Connect (PSC) for Google APIs lets you allocate a custom global internal IPv4 address via a forwarding rule inside your VPC network to reach Google APIs privately. Endpoints can target either the all-apis bundle (most Google APIs, including those unsupported by VPC Service Controls) or the vpc-sc bundle (only APIs supported by VPC Service Controls).
gke.goog DNS configuration: When accessing the GKE DNS-based endpoint through a Private Service Connect endpoint, you must configure private Cloud DNS records for the gke.goog domain so that *.gke.goog queries resolve to the internal IP address of the PSC endpoint. Without these DNS records, clients resolve *.gke.goog to default public Google IP addresses, which are unreachable after removing the 0.0.0.0/0 default internet route.all-apis bundle permits traffic to Google APIs and services that are not supported by VPC Service Controls, violating the requirement to deny access to unsupported APIs.googleapis.com and gke.goog for GKE DNS endpoints) to steer client requests to the consumer's internal forwarding rule IP.vpc-sc bundle behaves equivalently to restricted.googleapis.com by blocking APIs unsupported by VPC Service Controls, whereas all-apis behaves like private.googleapis.com.*.gke.goog and *.googleapis.com to that endpoint IP.The Private Service Connect endpoint targeted the vpc-sc bundle instead of all-apis, and private Cloud DNS records were created for both googleapis.com and gke.goog pointing to the PSC endpoint's internal IP address.
container.googleapis.com and kubernetesmetadata.googleapis.com to the VPC Service Controls perimeter's restricted services, enable Private Google Access on the subnets, configure DNS and a custom static route for 199.36.153.8/30 (private.googleapis.com) pointing to default-internet-gateway after removing the 0.0.0.0/0 default route, and advertise 199.36.153.8/30 via Cloud Router custom route advertisements.private.googleapis.com (199.36.153.8/30) doesThe private.googleapis.com VIP range (199.36.153.8/30) is a Private Google Access virtual IP range that enables private Compute Engine VMs and on-premises hosts (over Cloud Interconnect or Cloud VPN) to reach Google APIs and services privately within Google's network. Unlike restricted.googleapis.com, private.googleapis.com supports virtually all Google APIs and services, including those that do not support VPC Service Controls.
199.36.153.8/30 (private.googleapis.com) without additional VPC Service Controls service patterns permits network reachability to APIs outside VPC Service Controls enforcement, creating a potential data exfiltration path.container.googleapis.com and kubernetesmetadata.googleapis.com are protected by the service perimeter, workloads in prod-vpc or on-premises clients using the 199.36.153.8/30 path could still reach unsupported Google services.private.googleapis.com (199.36.153.8/30): Grants access to both VPC Service Controls-supported APIs and unsupported Google APIs unless paired with VPC accessible services and service patterns.restricted.googleapis.com (199.36.153.4/30): Automatically denies access at the network/VIP level to all Google APIs and services that are not compatible with VPC Service Controls.default-internet-gateway, and neither range is advertised on the public internet.The organization required access to Google APIs not supported by VPC Service Controls alongside GKE, and explicitly mitigated exfiltration risks by configuring VPC Service Controls service patterns on the perimeter rather than blocking all unsupported APIs via restricted.googleapis.com.
container.googleapis.com and kubernetesmetadata.googleapis.com to the VPC Service Controls perimeter's restricted services, enable Private Google Access on the subnets, and configure DNS and routing for 199.36.153.4/30 (restricted.googleapis.com).An IP-based private endpoint exposes the GKE Kubernetes API server via an internal passthrough Network Load Balancer inside the Google-managed control plane VPC, which is connected to the customer's VPC through VPC Network Peering. Access is controlled at Layer 3/Layer 4 by authorized networks (a list of up to 100 CIDR blocks) and optionally control plane global access for cross-region internal clients.
container.googleapis.com and kubernetesmetadata.googleapis.com to the service perimeter governs GKE management API calls (such as cluster creation or get-credentials), but kubectl and Kubernetes API requests sent directly to the cluster's private RFC 1918 endpoint bypass VPC Service Controls perimeter checks.199.36.153.4/30 Private Google Access VIP path.The organization did not require VPC Service Controls protection on Kubernetes API server requests and only needed Layer 3/Layer 4 CIDR-based isolation (authorized networks) within a single VPC and its directly connected hybrid networks.
container.googleapis.com and kubernetesmetadata.googleapis.com to the VPC Service Controls perimeter's restricted services, enable Private Google Access on the subnets, configure DNS and a custom static route for 199.36.153.4/30 (restricted.googleapis.com) pointing to default-internet-gateway after removing the 0.0.0.0/0 default route, and advertise 199.36.153.4/30 via Cloud Router custom route advertisements.Combining the GKE DNS-based control plane endpoint with Private Google Access (PGA) over the restricted.googleapis.com virtual IP (VIP) range (199.36.153.4/30) and a VPC Service Controls perimeter creates an end-to-end private, context-aware control plane access path. The DNS-based endpoint exposes each cluster's Kubernetes API server through Google Cloud's API infrastructure (*.gke.goog) rather than relying solely on raw cluster IP addresses, allowing IAM policies and VPC Service Controls to inspect and enforce perimeter boundaries on control plane operations.
container.googleapis.com and kubernetesmetadata.googleapis.com in the service perimeter's restricted services list enables VPC Service Controls enforcement across all GKE API and DNS-based control plane operations.0.0.0.0/0 default internet route and creating a custom static route for 199.36.153.4/30 with next hop default-internet-gateway keeps all packets inside Google's private backbone. Advertising 199.36.153.4/30 via Cloud Router custom route advertisements extends this private path over Cloud Interconnect to on-premises workstations.restricted.googleapis.com VIP (199.36.153.4/30) explicitly blocks access to any Google APIs and services that are not supported by VPC Service Controls, preventing data exfiltration through unsupported APIs.container.clusters.connect (included in roles/container.developer and roles/container.viewer), avoiding certificate or static token sprawl.199.36.153.4/30 range is not announced to the public internet, ensuring hybrid traffic never leaves Google's network fabric even though the VPC next hop is default-internet-gateway.prod-vpc (which terminates the Cloud Interconnect connection) must reside within the same VPC Service Controls perimeter or be connected via a perimeter bridge.Unlike IP-based private endpoints, which do not integrate with VPC Service Controls and fail across non-transitive VPC peering hops without proxies, and unlike private.googleapis.com (199.36.153.8/30), which exposes unsupported APIs, this architecture enforces strict perimeter boundaries, eliminates internet egress routes, and scales cleanly across hybrid networks.
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