Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Developer practice bank has an additional 608 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your development team is deploying a Cloud Run service in vpc-consumer that needs to send requests to a partner-managed API hosted in vpc-producer within a separate Google Cloud organization. You have the following requirements:
Which networking configuration should you deploy?
A Serverless VPC Access connector deploys a managed pool of Compute Engine VM instances in a dedicated /28 subnet to bridge outbound traffic from serverless environments—such as Cloud Run, App Engine, or Cloud Run functions—into a VPC network.
/28 subnet with a PRIVATE purpose that cannot be shared with other resources.Your workload required an older serverless environment without Direct VPC egress support, or if you were routing heavy Cloud NAT traffic where Direct VPC egress cold-start delays with Cloud NAT must be avoided.
While pairing a connector with a Private Service Connect endpoint successfully handles private cross-organization traffic and overlapping IP ranges, Direct VPC egress is the recommended replacement for Cloud Run because it removes connector VM overhead and supports revision-level network tags.
VPC Network Peering connects two VPC networks directly over Google's internal network so that workloads in both VPCs can communicate using internal IP addresses without traversing the public internet, even across different projects or organizations.
vpc-consumer and vpc-producer have overlapping IP ranges, peering cannot be established.Both VPC networks had guaranteed non-overlapping IP ranges, belonged to trusted environments where full subnet-to-subnet reachability was desired, or required inserting network virtual appliances (NVAs) in the traffic path.
For consuming managed or partner services across organizational boundaries, Private Service Connect is preferred over VPC Network Peering because it uses NAT to resolve IP conflicts and enforces a service-oriented security boundary.
Direct VPC egress enables Cloud Run services to send outbound traffic directly into a VPC network using internal IP addresses allocated from a specified subnet, eliminating the need for an intermediary connector VM. Private Service Connect is a service-centric networking capability that publishes a service from a producer VPC into a consumer VPC via a single internal IP address endpoint.
vpc-consumer, and the Private Service Connect endpoint forwards requests privately over Google's internal network to vpc-producer.Combining Direct VPC egress with a Private Service Connect endpoint is the recommended pattern for Cloud Run workloads calling services in external or non-peered VPCs. It satisfies all performance, cost, security, and IP-overlap constraints simultaneously.
Private Google Access allows Compute Engine VM instances that do not have external IP addresses to reach Google APIs and Google Cloud services (such as Cloud Storage, BigQuery, or Cloud Run run.app endpoints) using internal routing inside Google's network.
vpc-consumer.You were configuring a Compute Engine VM without a public IP inside vpc-consumer to call Google Cloud APIs (or an internal Cloud Run service's run.app URL) privately.
To reach a Private Service Connect endpoint inside vpc-consumer, the Cloud Run service must first be connected to vpc-consumer for outbound traffic using Direct VPC egress.
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