
Private Google Access lets VMs that have no external IP address reach Google APIs and services, such as Cloud Storage, BigQuery, Spanner or the Cloud SQL Admin API, over Google's network. It is a property of each subnet, and it still depends on routing to reach the APIs. Google also publishes two virtual IP ranges for private API access, private.googleapis.com and restricted.googleapis.com, which differ in which APIs they serve. For the Professional Cloud Network Engineer exam, it helps to keep three parts separate: the subnet setting, the routes, and the DNS and routing needed to use a VIP.
Private Google Access has no switch at the VPC network level. It exists only as a setting on each subnet, so it has to be turned on for every subnet where the VMs run.
A Public NAT gateway also gives VMs without external IPs a path to Google APIs, because Google Cloud automatically enables Private Google Access for the subnet ranges a Public NAT gateway covers. Cloud NAT itself does not change route selection, though, and Private Google Access does not send API traffic through it.
Private Google Access still relies on routing. Google APIs use public IP addresses, so API traffic has to follow a route toward the default internet gateway. Any broader custom route that sends egress somewhere else, such as a 0.0.0.0/0 route pointing at a network appliance, catches API traffic as well.
More specific static routes for the Google API ranges, such as 199.36.153.8/30 for private.googleapis.com, with the default internet gateway as the next hop, solve this through longest prefix match. API traffic takes the specific route, and everything else keeps following the broader one.
Private Google Access is specifically about reaching Google APIs from VMs without external IP addresses. It does not cover several nearby needs:
Google publishes two virtual IP ranges for private access to Google APIs:
When compliance requires that workloads reach only APIs that VPC Service Controls supports, restricted.googleapis.com is the VIP to use. The private VIP would still allow access to unsupported APIs, so it does not meet that kind of requirement.
Using either VIP takes two pieces of configuration.
Because a /30 is more specific than 0.0.0.0/0, the VIP route always wins for that range, whatever the default route points to. That holds even when the system-generated default route has been deleted and the default route is one an on-premises router advertises over BGP. The general internet path and the API path can therefore be designed separately. Without the more specific route, API traffic simply follows whatever default route is in place, including one that leads on-premises, where firewalls may drop it.
For Professional Cloud Network Engineer scenarios, a working Private Google Access design answers three questions. Is Private Google Access enabled on every subnet where the VMs run? Does the API traffic have a route to the default internet gateway that beats any broader default route? And if a VIP is used, do API hostnames resolve to it, and is it the restricted VIP when only VPC Service Controls-supported APIs are allowed?
Our Professional Cloud Network Engineer practice exams cover Private Google Access and the Google API VIPs alongside VPC Service Controls and Cloud DNS, with detailed explanations that drill these distinctions.