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 organization hosts a sensitive internal administrative web application on Google Kubernetes Engine (GKE) behind an External HTTP(S) Load Balancer, along with private Compute Engine virtual machines (VMs) that administrators manage using SSH.
Your security team mandates the following requirements:
Which architecture should you implement?
Identity-Aware Proxy (IAP) provides a zero-trust application and administrative access layer by establishing identity-centric controls instead of traditional network-level perimeters. In conjunction with Access Context Manager and Chrome Enterprise Premium, IAP evaluates contextual signals—such as identity, geographic location, and device security posture—before proxying any traffic to backend services.
nic0), removing the need for external IPs on Compute Engine instances.request.auth.access_levels), ensures only compliant corporate devices from authorized regions gain access.This approach directly satisfies all zero-trust criteria without introducing complex network routing, custom reverse proxies, or dedicated jump hosts.
This configuration implements a traditional Cloud VPN tunnel to extend the corporate private network into the Google Cloud Virtual Private Cloud (VPC), enabling clients to access internal IP addresses over an encrypted IPSec overlay network.
The architecture mandated private RFC 1918 line-of-sight between non-HTTP legacy enterprise software and cloud databases across an entire corporate office branch.
Google Cloud Armor provides Layer 7 edge defense against web application attacks, DDoS attempts, and enables IP/geo-based filtering on external load balancers. Assigning the roles/compute.osAdminLogin role grants administrative OS-level access to Compute Engine VMs.
roles/compute.osAdminLogin role alone does not allow administrators to reach private VMs without either a public IP, a VPN, or IAP TCP forwarding.The goal was primarily to block layer 7 injection attacks and restrict general public access to specific countries at the network edge.
This architecture relies on traditional network-based perimeter security using a public-facing bastion host (jump box), network firewall rules restricted by source IP CIDR ranges, and OS Login with 2-step verification to govern SSH access to private instances.
The scenario required legacy jump host infrastructure where client endpoints do not support endpoint verification extensions and rely exclusively on static office 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