Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
An enterprise has deployed a backend microservice on Cloud Run with its ingress setting configured to internal to prevent direct exposure to the public internet. The security team needs to allow a frontend application running in App Engine standard environment within the same Google Cloud project to privately invoke this Cloud Run service.
Which architecture should the security team implement to satisfy these requirements?
Serverless VPC Access bridges Google Cloud serverless runtimes (such as App Engine standard, Cloud Run, and Cloud Functions) to a Virtual Private Cloud (VPC) network. Attaching a serverless service to a dedicated connector enables private egress into the VPC without allocating public IP addresses to individual serverless application instances.
internal only accepts requests that originate from inside an authorized VPC network or arrive via approved private paths. Serverless requests must traverse a VPC network to be recognized as internal traffic.all-traffic through the Serverless VPC Access connector forces all outbound traffic into the VPC subnet.run.app endpoints route privately through Google's internal network infrastructure rather than exiting to the public internet.Routing all-traffic through the connector while enabling Private Google Access on the connector subnet directly fulfills Google Cloud's architectural requirements for serverless-to-serverless internal communication, guaranteeing strict perimeter security without complex reverse proxies.
VPC Network Peering allows internal RFC 1918 connectivity between two distinct Google Cloud Virtual Private Cloud (VPC) networks using Google's internal software-defined network routing.
internal by Cloud Run ingress controls without explicit Private Service Connect or VPC Service Controls configurations.internal-and-cloud-load-balancing does not solve the lack of VPC connectivity from App Engine standard.You had two separate customer-managed VPC networks containing Compute Engine instances or GKE nodes that needed direct private bidirectional IP communication.
Cloud NAT provides outbound Network Address Translation, enabling private VPC instances without external IP addresses to access the public internet using a shared pool of public IP addresses.
internal, it explicitly rejects incoming requests originating from public IP addresses. Routing egress traffic through Cloud NAT translates packets to external NAT IP addresses, causing the destination Cloud Run service to block the requests.*.run.app) bypass the connector entirely unless configured for all-traffic or directed to private VIPs.*.run.app.The destination service was hosted externally on the public internet and required egress from serverless runtimes through a fixed set of static public IP addresses.
Private Service Connect (PSC) network attachments are dedicated networking resources that allow managed service producers (such as Cloud SQL) to initiate outbound connections back into a consumer VPC network through a Private Service Connect interface.
A managed Cloud SQL database needed outbound access into your custom VPC network to perform a database migration from an on-premises replication server.
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