Private consumers must reach a service across VPCs, without exposing it publicly. What fits?
Why D is the answer
Private Service Connect
Private Service Connect lets consumers reach a service across VPCs with no public exposure.
In detail
- Private Service Connect gives private access across VPCs.
- The service is not exposed publicly.
Use case
An illustrative scenario, not a real incident.
A data team's service in one VPC is consumed privately from another, through Private Service Connect.
See it in different ways
flowchart TD A["Host project: Shared VPC"] --> B["Service project A"] A --> C["Service project B"] A --> D["Central firewall rules"]
mindmap
root((Connectivity))
Hybrid
Cloud Interconnect
Cloud VPN
Shared
Shared VPC
Private access
Private Service Connect
Identity-Aware Proxy
APIs
ApigeesequenceDiagram participant P0 as Consumer VPC participant P1 as Private Service Connect participant P2 as Producer service P0->>P1: Private request P1->>P2: Forward P2-->>P0: Response
Key point: Private Service Connect links services privately.
Why the other options are wrong
- A. A public load balancer with open firewall rules
- That exposes the service.
- B. A VM with an external IP for each consumer
- That exposes the service.
- C. A shared password for the service
- A password is not connectivity.