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.
An enterprise is designing a secure cloud architecture on Google Cloud across multiple projects. The architecture utilizes a Shared VPC where compute workloads deployed in a service project interact with managed Google Cloud APIs. The security team establishes the following requirements:
Which solution should you implement?
VPC Service Controls establishes an isolation perimeter around Google Cloud resources to prevent unauthorized access and mitigate data exfiltration risks. Access Context Manager allows administrators to define fine-grained, context-aware access levels based on attributes such as client IP subnets, device policy, and user identity, which can then be bound directly to VPC Service Controls service perimeters.

This solution natively addresses both cross-project networking constraints in Shared VPC deployments and the operational requirement of console management from verified enterprise networks without weakening perimeter isolation.
This approach places the Shared VPC host project and service project into distinct service perimeters, attempts to use Google Cloud Armor on an external load balancer to filter corporate traffic, and leverages Cloud NAT with Private Google Access for console administration.
You were deploying an internet-facing custom web application behind an external HTTPS load balancer that required Layer 7 DDoS and IP filtering rules via Cloud Armor.
This configuration attempts to isolate only the service project within a VPC Service Controls perimeter while leaving the Shared VPC host project outside, using Identity-Aware Proxy (IAP) TCP forwarding to tunnel Google Cloud console traffic.
The requirement were strictly focused on establishing secure administrative shell (SSH/RDP) access to backend Compute Engine VMs without public IP addresses instead of securing Google Cloud API management via the console.
This option places both projects in the service perimeter, configures Private Services Access, and attempts to use internal VPC firewall rules to allow external administrators to connect to the Google Cloud console.
The primary goal was filtering internal network traffic between Compute Engine virtual machines and internal subnets within the Shared VPC network.
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