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.
A financial enterprise is securing communications between its Google Cloud VPC network and Google APIs to prevent data exfiltration. The security architect has established the following requirements:
Which combination of private connectivity architectures should the architect implement?
*.googleapis.com to restricted.googleapis.com (199.36.153.4/30) across the VPC, and configure Serverless VPC Access connectors for the analytics tier.This solution maps *.googleapis.com to restricted.googleapis.com and attempts to use Serverless VPC Access connectors to provide private connectivity for the analytics tier.
/28 connector subnet solely to route egress packets from serverless environments into customer VPC subnets.The analytics tier consisted of serverless Cloud Run services that needed to initiate egress connections into a VPC to reach private databases or on-premises systems.
all-apis for the analytics tier.This proposal relies on standard Private Google Access (which routes requests to default Google public VIPs) and configures an internal Application Load Balancer (ALB) with a Private Service Connect backend configured with the all-apis service bundle.
all-apis allow connections to all Google APIs, including services that fall outside VPC-SC perimeters. This violates the security mandate to block non-supported APIs.vpc-sc bundle) directly satisfies the private IP allocation requirement.restricted.googleapis.com unless explicit DNS overriding is configured.all-apis PSC bundle includes services that are not protected by VPC Service Controls, defeating the requirement for strict data boundary restriction.The enterprise required Layer 7 URL-based routing, traffic management policies, and access to all Google Cloud APIs irrespective of VPC-SC perimeter compatibility.
*.googleapis.com to restricted.googleapis.com (199.36.153.4/30) for VPC-wide egress, and deploy a Private Service Connect (PSC) endpoint for Google APIs with an allocated internal IP in the analytics subnet.This architecture combines Restricted Google Access via the restricted.googleapis.com domain with a Private Service Connect (PSC) endpoint for Google APIs. restricted.googleapis.com maps API domain names to a specific virtual IP range (199.36.153.4/30) that strictly permits communication only with Google services supported by VPC Service Controls (VPC-SC), while Private Service Connect projects Google API services directly into a consumer VPC network using a private RFC 1918 internal IP address.
*.googleapis.com and related domains to restricted.googleapis.com (199.36.153.4/30) ensures that compute workloads can only communicate with services verified to support VPC-SC perimeters. Any API call to a non-supported service (such as consumer web apps or unsupported APIs) is blocked at the network layer.restricted.googleapis.com VIP and PSC internal IP endpoints can be advertised across Cloud Interconnect or Cloud VPN to extend security postures to on-premises hosts.This dual approach applies the exact native mechanism intended for broad VPC-SC enforcement across the VPC (restricted.googleapis.com) while providing the dedicated analytics tier with private, subnet-bound addressing and firewall control via Private Service Connect.
*.googleapis.com to private.googleapis.com (199.36.153.8/30) for the entire VPC, and create a Private Services Access (PSA) connection for the analytics subnet.This configuration uses Private Google Access mapped to the private.googleapis.com domain (199.36.153.8/30) alongside Private Services Access (PSA), which establishes a VPC Network Peering connection with a Google-owned service producer network.
private.googleapis.com resolves to an internal Google Cloud routable IP range that supports most Google APIs and services regardless of whether they support VPC Service Controls (VPC-SC). This fails the requirement to strictly block access to non-VPC-SC supported APIs.private.googleapis.com is recommended only when workloads need to consume services that do not support VPC Service Controls.The scenario required accessing Google APIs that are not supported by VPC-SC and required provisioning private database instances (like Cloud SQL) via internal VPC peering.
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