Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
Your organization is establishing shared networking across multiple Google Cloud projects. A producer team has deployed a microservice behind an internal load balancer and exposed it using a Private Service Connect (PSC) service attachment.
Your DevOps team needs to configure connectivity from a consumer VPC network while meeting the following requirements:
Which configuration should the DevOps team implement in the consumer network?
Private Services Access (PSA) is a managed networking mechanism where a consumer allocates a dedicated internal IP address block and establishes a VPC Network Peering connection to the service producer's network (such as Google-managed Cloud SQL or Vertex AI).
You were provisioning traditional Google-managed infrastructure (such as Cloud SQL using legacy private IP) that strictly relies on Private Services Access and VPC peering ranges.
Private Service Connect is Google Cloud's modern replacement for Private Services Access, providing improved security isolation, unidirectional access, and support for overlapping IP addresses.
Service Directory is a managed service registry that stores endpoint definitions (such as IP addresses and ports) and integrates with Cloud DNS private zones to enable service discovery across Google Cloud resources.
The requirement was solely to enable internal DNS resolution and automated discovery of registered service endpoints across teams.
While Service Directory can be integrated with Cloud Service Mesh and PSC to facilitate service discovery, the actual data plane routing, header manipulation, and Cloud Armor inspection require an Application Load Balancer with a PSC backend.
A Private Service Connect (PSC) backend utilizes a specialized PSC network endpoint group (NEG) that targets the producer's service attachment URI. This configuration allows an Application Load Balancer (internal or external regional) in the consumer network to treat the producer's published service as a standard backend service.
A PSC backend with a PSC NEG is the only Google Cloud architectural pattern that combines the private isolation of Private Service Connect with the Layer 7 capabilities, Cloud Armor integration, and fine-grained request decoration of Application Load Balancers.
A Private Service Connect endpoint creates a forwarding rule assigned to an internal IP address in the consumer VPC that connects directly to a producer's service attachment or to Google APIs. This provides Layer 4 private transport into the published service.
The goal was simply to establish basic Layer 4 TCP connectivity to a published service using a private IP address without requiring HTTP header transformation or Cloud Armor security policies.
To gain Layer 7 features and Cloud Armor security controls with Private Service Connect, consumers must deploy PSC backends (NEGs) behind an Application Load Balancer rather than standalone PSC endpoints.
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