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.
A SaaS provider hosts a multi-tenant HTTP API in its own VPC network across us-central1 and us-east1. Multiple enterprise consumers—some using overlapping 10.0.0.0/8 RFC 1918 ranges—require private access to the API.
The architecture must satisfy these requirements:
Which producer and consumer architecture should you implement?
PRIVATE_SERVICE_CONNECT NAT subnets and publish each via a service attachment using an ACCEPT_MANUAL consumer accept list. Consumer: Deploy a load balancer with a global backend service referencing regional Private Service Connect NEGs for each service attachment.Private Service Connect (PSC) enables service-oriented, private connectivity between separate VPC networks without network-level peering. Producers expose services through regional service attachments backed by dedicated PRIVATE_SERVICE_CONNECT NAT subnets, while consumers use PSC backends—load balancers configured with Private Service Connect network endpoint groups (NEGs)—when they need advanced Layer 7 control, custom certificates, and multi-region failover.
PRIVATE_SERVICE_CONNECT NAT subnet. Because consumer and producer routing tables remain completely independent, multiple consumers with overlapping 10.0.0.0/8 ranges can connect simultaneously without Cloud NAT or network virtual appliances.ACCEPT_MANUAL and a consumer accept list restricts access exclusively to specified consumer project IDs and enforces per-project connection limits.us-central1 and us-east1) lets the consumer terminate TLS using customer-owned certificates, enforce Google Cloud Armor security policies, and automatically fail over traffic to the healthy region if an instance becomes unhealthy.pscConnectionId values.Unlike VPC Network Peering, PSC prevents broad network exposure and resolves IP overlap natively. Unlike standalone PSC endpoints, PSC backends give the consumer full Layer 7 load balancer control—including custom domains, Cloud Armor, and automated cross-region failover across regional service attachments.
PRIVATE_SERVICE_CONNECT NAT subnets and publish each via a service attachment using an ACCEPT_MANUAL consumer accept list. Consumer: Deploy regional Private Service Connect endpoints with global access enabled and attach custom TLS certificates and Cloud Armor policies directly to the forwarding rules.A Private Service Connect (PSC) endpoint is an internal IP address provisioned in a consumer VPC via a forwarding rule that maps directly to a producer's service attachment. Endpoints provide Layer 4 connectivity, allowing consumer VMs and GKE nodes to send traffic directly to a regional published service.
The consumer only needed simple, private Layer 4 internal IP access to a single regional service attachment and was willing to rely on the producer's TLS certificates, authentication, and availability without Cloud Armor or cross-region failover.
When a consumer needs load balancer features—such as custom domains, TLS termination, Cloud Armor, or cross-region failover—in front of a published service, the consumer must use PSC backends (a consumer load balancer backed by PSC NEGs) rather than standalone PSC endpoints.
Private Service Connect (PSC) interfaces are specialized virtual or dynamic network interfaces placed on producer VM instances that connect to network attachments inside a consumer VPC. When accepted, the producer VM receives an internal IP address from the consumer's network attachment subnet, enabling the producer to initiate outbound connections into the consumer VPC.
10.0.0.0/8 consumer IP ranges create routing ambiguity.nic0 in the producer VPC and a PSC interface in the consumer attachment subnet).A managed service producer (such as an analytics platform or data replication service) needed to initiate outbound connections into a consumer's private VPC or on-premises databases via Cloud Interconnect.
10.0.0.0/8 addresses and VPC firewall rules to restrict access. Consumer: Deploy a global load balancer pointing to the peered producer load balancer VIPs across both regions.VPC Network Peering connects two VPC networks internally over Google's software-defined network (SDN) so workloads can communicate using internal IP addresses. It merges control-plane route exchange between the peered VPCs, allowing direct reachability across subnets and internal forwarding rules.
10.0.0.0/8 space, peering connections will fail to establish or exchange routes.Both VPCs were within a single organization with strictly non-overlapping IP ranges, required full bidirectional network-level connectivity, and needed to insert network virtual appliances (NVAs) or inspect traffic across peered subnets.
When migrating away from legacy peering-based services to avoid IP overlap and reduce administrative overhead, Private Service Connect replaces broad VPC peering with granular, NAT-isolated service attachments and consumer endpoints or backends.
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