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.
Your organization runs a hub-and-spoke topology where application spoke VPCs connect to a central transit VPC via VPC Network Peering. On-premises and multi-cloud networks connect to the transit VPC over Cloud Interconnect. A vendor publishes a managed service via a Private Service Connect (PSC) service attachment.
You need centralized private access meeting these requirements:
Which architecture should you implement?
A Private Service Connect (PSC) endpoint is a consumer-side forwarding rule assigned an internal IP address from a consumer VPC subnet that maps directly to a producer's service attachment. When the producer configures a service domain name, Service Directory can automatically populate a private DNS zone (NAMESPACE--REGION) in the consumer VPC.
The spoke VPCs were connected to the transit VPC as NCC VPC spokes (which support transitive reachability to PSC endpoints) or if you were willing to deploy individual PSC endpoints inside every spoke VPC rather than centralizing access in the transit VPC.
A Private Service Connect (PSC) interface is a resource created by a service producer that attaches to a consumer-managed network attachment inside a dedicated consumer VPC subnet. This places a producer-managed network interface directly inside the consumer's network space.
The managed service needed to initiate outbound connections from the vendor's producer environment into your transit, spoke, or hybrid networks, and you configured Cloud DNS peering zones (rather than forwarding zones) alongside a Cloud DNS private zone and inbound server policy.
A Private Service Connect (PSC) backend uses an internal Google Cloud load balancer configured with a Private Service Connect network endpoint group (NEG) to proxy consumer traffic to a producer's service attachment. Unlike standalone PSC endpoints, an internal load balancer's virtual IP (VIP) resides in a regular VPC subnet and is routable across VPC Network Peering and hybrid Cloud Interconnect links.
Deploying an internal load balancer with a PSC NEG is the standard pattern for extending published services across VPC Network Peering boundaries while keeping service access centralized in a single transit VPC and integrating cleanly with hybrid Cloud DNS.
A Private Service Connect service attachment is a producer-side resource used to publish a service hosted behind an internal load balancer to external consumer VPCs. When paired with a hybrid connectivity network endpoint group (NEG), it allows a service producer to expose workloads running on-premises or in another cloud provider to consumer VPCs in Google Cloud.
IP:port endpoints reachable over Cloud Interconnect or Cloud VPN (such as on-premises or multi-cloud servers), not a third-party vendor's Google Cloud PSC service attachment.35.199.192.0/19), whereas external-to-cloud resolution requires an inbound server policy.Your organization were acting as the service producer publishing an on-premises or multi-cloud service in the transit VPC for consumption by other Google Cloud VPCs, and the transit VPC needed to resolve on-premises domain names.
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