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 is deploying confidential workloads onto Compute Engine instances within a custom VPC subnet that has no external IP addresses and no default internet gateway route. The security team has defined a VPC Service Controls (VPC-SC) perimeter protecting services such as Cloud Storage and BigQuery.
To enforce strict perimeter boundaries and prevent data exfiltration, the architecture must satisfy these criteria:
Which network and DNS configuration should the security engineer implement?
/28 subnet and configure custom egress firewall rules blocking destination port 443 for default gateway routes.Serverless VPC Access creates a managed connector in a dedicated /28 subnet that enables serverless workloads (such as Cloud Run, Cloud Run functions, or App Engine) to send outbound requests into a VPC network.
restricted.googleapis.com or restrict API access based on VPC Service Controls compatibility.The team needed to allow serverless runtimes (such as Cloud Run or Cloud Run functions) to access internal private resources located inside a customer VPC network.
Private Services Access is a private peering connection between a customer VPC network and a service producer VPC network managed by Google or a third party (such as Cloud SQL, Memorystore, or AlloyDB).
*.googleapis.com).restricted.googleapis.com VIP for API requests.The architecture required internal IP connectivity to managed database instances like Cloud SQL or Memorystore Redis from a consumer VPC.
googleapis.com with a CNAME record directing *.googleapis.com to private.googleapis.com, and map private.googleapis.com to 199.36.153.8/30.The private.googleapis.com VIP range (199.36.153.8/30) provides private network routing to the vast majority of Google APIs and services from instances that do not have external IP addresses.
restricted.googleapis.com, private.googleapis.com allows access to Google APIs and services that are not supported by VPC Service Controls.private.googleapis.com will route and process the request, creating a potential egress channel that bypasses VPC Service Controls boundary policies.199.36.153.8/30 instead of 199.36.153.4/30.The requirement stated that workloads needed to reach all Google APIs and services (including services unsupported by VPC Service Controls) privately from internal IP addresses without perimeter blocking.
googleapis.com with a CNAME record directing *.googleapis.com to restricted.googleapis.com, and map restricted.googleapis.com to 199.36.153.4/30.The restricted.googleapis.com virtual IP (VIP) address range (199.36.153.4/30 for IPv4) is a specialized Google Cloud endpoint designed specifically to integrate with VPC Service Controls. When workloads route API traffic to this VIP, Google Cloud only accepts API calls directed to services that support VPC Service Controls perimeters.
restricted.googleapis.com automatically drops or rejects requests targeting Google services that do not support VPC Service Controls. This prevents workloads from exfiltrating data via unvetted, non-perimeter-protected APIs.googleapis.com with a wildcard CNAME to restricted.googleapis.com ensures that all VM API calls natively resolve to 199.36.153.4/30.Routing to restricted.googleapis.com is the Google Cloud best practice for environments governed by VPC Service Controls. It ensures that traffic cannot bypass perimeter security boundaries while keeping network traffic entirely private.
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