Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
Your company runs containerized backend workloads on Cloud Run in the us-central1 region. These serverless applications must communicate securely with the following resources:
All traffic between Cloud Run, the internal VMs, and Google APIs must traverse the VPC network without being routed over the public internet.
How should you configure the Cloud Run networking architecture to satisfy these requirements?
us-central1 attached to the VPC network, configure the Cloud Run service to use the connector, and keep the default VPC egress setting to Route only requests to private IPs to the VPC.The default setting, Route only requests to private IPs to the VPC (private-ranges-only), instructs Cloud Run to send traffic through the Serverless VPC Access connector only when destination IP addresses fall strictly within RFC 1918, RFC 6598, or designated Google private access ranges (199.36.153.4/30 and 199.36.153.8/30).
All VPC destinations and PSC endpoints were allocated purely within RFC 1918 subnets, and no other external or custom IP ranges were utilized within the VPC.
Whenever workloads interact with privately used external IP ranges or require comprehensive firewall inspection in the VPC, changing the egress mode to Route all traffic to the VPC is mandatory.
An Internal Application Load Balancer (ALB) with a Private Service Connect NEG is used to direct incoming requests toward published managed services or Google APIs. Setting Cloud Run ingress to internal-and-cloud-load-balancing restricts who can send inbound requests to the Cloud Run service.
The primary goal was to restrict external public callers from accessing Cloud Run and only allow access through an internal enterprise load balancer.
us-central1 attached to the VPC network, configure the Cloud Run service to use the connector, and set the VPC egress setting to Route all traffic to the VPC.Serverless VPC Access allows serverless environments—such as Cloud Run, Cloud Functions, and App Engine—to initiate outbound connections to private resources in a Google Cloud Virtual Private Cloud (VPC) network. When creating a connector, it provisions lightweight connector VM instances inside an allocated subnet or CIDR range within your VPC.
all-traffic). This guarantees that packets destined for non-RFC 1918 internal endpoints pass through the connector and into the VPC routing table rather than escaping directly to the public internet.This approach directly satisfies the need for private VPC connectivity while accommodating the architectural requirement of Private Service Connect endpoints assigned privately used external IP spaces.
Cloud NAT provides outbound internet connectivity for Compute Engine VMs or GKE nodes that do not have public IP addresses. Private Google Access allows VM instances with internal IP addresses in a VPC subnet to access Google APIs and services using default Google public VIPs.
The workloads were Compute Engine VMs hosted directly within a private VPC subnet needing outbound software updates and Google API access without public IP addresses.
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