
Private services access and Private Service Connect both give private connectivity to services, but they work in different ways. Private services access connects your VPC network to a Google-managed service producer network through VPC Network Peering, and services such as Cloud SQL and Memorystore place their private IP addresses in that producer network. Private Service Connect follows a consumer and producer model, where a producer exposes a specific service and consumers reach it through endpoints. The similar names make these easy to mix up, and the Professional Cloud Network Engineer exam expects you to know which one a design calls for.
With private services access, the managed service's private IP addresses come from a range you allocate in your VPC network, and your VMs reach them over the peering. Setup takes three steps:
After that, Cloud SQL gives the instance an internal address from the range, and VMs reach it over the peering with no external IPs involved.
A direct connection to a database's private IP is traffic to a peered network, not a call to a Google API. Features built for reaching Google APIs, such as Private Google Access (which covers APIs like the Cloud SQL Admin API) and routes to the Google API VIPs, steer traffic to API endpoints, so they play no part in that connection. Private services access and its peering are what make the private IP reachable.
On-premises access to a service on a private services access range needs two more steps, one for each direction of traffic.
When on-premises clients use RFC 1918 addresses, the Cloud SQL instance needs no authorized network entries once routing works in both directions.
Private services access is not a route to Google APIs such as BigQuery or Cloud Storage. BigQuery is reached through Google API endpoints and is not a VPC network you can peer with. Private Google Access is the feature that lets VMs without external IPs reach Google APIs.
Private Service Connect is built around specific services. A producer publishes a service, and consumers reach it through endpoints. It is not a way to give general IP reachability between networks. Connecting hundreds of networks through it would require a huge and growing number of endpoints and service attachments.
Private Service Connect also appears in a few other places:
The choice follows from what needs to be reached. A Google-managed service such as Cloud SQL or Memorystore that takes a private IP from a range you allocate uses private services access, with the Service Networking API enabled and, for on-premises clients, custom route export and a custom Cloud Router advertisement. A specific service that a producer publishes, or a private address for Google APIs inside your VPC network, uses Private Service Connect. Private services access is not a path to Google APIs such as BigQuery or Cloud Storage, and Private Service Connect is not a tool for broad network-to-network reachability. For the Professional Cloud Network Engineer exam, those boundaries are the basis for choosing between these options.
Our Professional Cloud Network Engineer practice exams cover Private Service Connect and private services access alongside Private Google Access and hybrid connectivity NEGs, with detailed explanations that drill these distinctions.