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 Compute Engine VMs without external IP addresses in us-central1 and us-east1 subnets of a custom-mode VPC (prod-vpc). An on-premises data center connects to prod-vpc via Cloud Interconnect in us-central1. The default 0.0.0.0/0 route to default-internet-gateway was replaced with a route to a network virtual appliance (NVA).
A VPC Service Controls perimeter protects prod-vpc and your Cloud Storage project. Requirements:
Which configuration should you implement?
us-central1 and us-east1 subnets, map *.googleapis.com to restricted.googleapis.com (199.36.153.4/30) in Cloud DNS and on-premises DNS, add a custom static route for 199.36.153.4/30 targeting default-internet-gateway, and configure Cloud Router to advertise 199.36.153.4/30 over BGP.restricted.googleapis.com isPrivate Google Access (PGA) enables Compute Engine VMs with only internal IP addresses to reach Google APIs and services privately, while Private Google Access for on-premises hosts extends that private path across Cloud Interconnect or Cloud VPN. Mapping *.googleapis.com to restricted.googleapis.com (199.36.153.4/30) restricts traffic strictly to Google APIs supported by VPC Service Controls.
us-central1 and us-east1 subnets ensures VMs without external IP addresses in both regions can reach Google APIs.0.0.0.0/0 route to default-internet-gateway breaks PGA unless a more specific route exists. Adding a custom static route for 199.36.153.4/30 with next hop default-internet-gateway keeps API traffic entirely within Google's private network.199.36.153.4/30 as a custom IP range over the Cloud Interconnect BGP sessions directs on-premises API requests through the private interconnect into prod-vpc.*.googleapis.com to 199.36.153.4/30 automatically denies access to Google APIs not supported by VPC Service Controls, preventing data exfiltration.default-internet-gateway as its next hop.prod-vpc inherits the VPC Service Controls perimeter protection for Cloud Storage and BigQuery.0.0.0.0/0 traffic continues flowing to the NVA while 199.36.153.4/30 takes the more specific /30 route.This architecture satisfies multi-region VM connectivity, hybrid on-premises access over Cloud Interconnect, NVA coexistence, and strict VPC Service Controls API restriction using native, zero-proxy routing.
us-central1 and us-east1 subnets, map *.googleapis.com to private.googleapis.com (199.36.153.8/30) in Cloud DNS and on-premises DNS, add a custom static route for 199.36.153.8/30 targeting default-internet-gateway, and configure Cloud Router to advertise 199.36.153.8/30 over BGP.private.googleapis.com doesThe private.googleapis.com domain resolves to the 199.36.153.8/30 virtual IP (VIP) range and provides private connectivity over Google's internal network to a broad set of Google APIs and services. It allows both VPC VMs without external IP addresses (when Private Google Access is enabled on their subnet) and connected on-premises hosts to reach Google APIs without traversing the public internet.
private.googleapis.com allows access to Google APIs and services that are not supported by VPC Service Controls, creating a potential data exfiltration path unless additional service patterns are configured.199.36.153.8/30, unsupported APIs remain reachable through the same VIP path, violating the security requirement.private.googleapis.com (199.36.153.8/30) includes APIs outside the VPC Service Controls boundary, making it less restrictive than restricted.googleapis.com.private.googleapis.com without explicit VPC Service Controls service patterns exposes organizations to unintended API usage.private.googleapis.com and restricted.googleapis.com require subnet-level Private Google Access, proper DNS CNAME/A records, a custom static route to default-internet-gateway (when the default route is overridden), and Cloud Router custom IP advertisements for hybrid access.The organization explicitly needed access to Google APIs that are not supported by VPC Service Controls and either did not enforce strict API blocking or paired private.googleapis.com with VPC Service Controls service patterns to restrict specific unsupported APIs.
us-central1 and us-east1 subnets, map *.googleapis.com to restricted.googleapis.com (199.36.153.4/30) in Cloud DNS and on-premises DNS, set the prod-vpc dynamic routing mode to global so Cloud Router automatically advertises the restricted VIPs, and retain the 0.0.0.0/0 route to the NVA without adding a route to default-internet-gateway.Global dynamic routing mode allows a Cloud Router in one region (us-central1) to advertise VPC subnet ranges from all other regions (us-east1) to on-premises peers and propagate learned hybrid routes globally across the VPC. Meanwhile, a custom 0.0.0.0/0 static route pointing to an NVA directs all unmatched outbound traffic toward the virtual appliance.
199.36.153.4/30), so on-premises routers will lack a BGP route into prod-vpc.default-internet-gateway route: Private Google Access requires a route in the VPC whose next hop is default-internet-gateway covering the destination VIP (199.36.153.4/30). Without this specific route, VMs send 199.36.153.4/30 traffic to the NVA via 0.0.0.0/0 rather than directly to Google's internal API frontends.199.36.153.4/30 (or 199.36.153.8/30) to on-premises networks over Cloud Interconnect or Cloud VPN.0.0.0.0/0 with an NVA next hop breaks native Private Google Access unless an explicit /30 static route targeting default-internet-gateway is added.Cloud Router were explicitly configured with a custom advertised IP range for 199.36.153.4/30, and a custom static route for 199.36.153.4/30 with next hop default-internet-gateway were added to prod-vpc.
us-central1 subnet, set the prod-vpc dynamic routing mode to global so us-east1 VMs inherit Private Google Access across regions, map *.googleapis.com to restricted.googleapis.com (199.36.153.4/30), add a static route for 199.36.153.4/30 targeting default-internet-gateway, and advertise 199.36.153.4/30 via Cloud Router.Private Google Access (PGA) is strictly a regional, subnet-level property that allows VM instances without external IP addresses residing in that specific subnet to reach Google APIs. Global dynamic routing mode, by contrast, is a VPC-level BGP setting governing how Cloud Router exchanges subnet and custom routes between regions and hybrid peers.
us-east1 remain blocked: Because Private Google Access is not global or VPC-wide, enabling PGA only on the us-central1 subnet does not grant API access to VMs in us-east1. Without PGA enabled on the us-east1 subnet itself, traffic from us-east1 VMs without external IPs to 199.36.153.4/30 is dropped.restricted.googleapis.com (199.36.153.4/30) and VPC routes are global constructs, the Private Google Access flag itself is configured per regional subnet.199.36.153.4/30 via Cloud Interconnect do not depend on subnet PGA flags, whereas every VPC VM without a public IP does.All VMs requiring private API access were deployed exclusively in the us-central1 subnet, or if Private Google Access were enabled on both the us-central1 and us-east1 subnets.
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