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 multi-tier, mission-critical web application on Google Cloud that serves users globally over HTTPS. The architecture must satisfy the following reliability and traffic management requirements:
Which architecture should you deploy to meet these requirements?
This design uses independent Regional External Application Load Balancers deployed in separate regions, relying on Cloud DNS routing policies to detect regional outages and point client requests to the active regional IP endpoint.
The workload were subject to strict regulatory or jurisdictional compliance constraints requiring all network configurations, traffic processing, and TLS termination to be strictly confined within specific regional boundaries.
A Global External Application Load Balancer operates at Layer 7 using Google's global Anycast IP infrastructure to terminate connections close to users at edge Points of Presence (PoPs). When paired with regional Managed Instance Groups (MIGs), the architecture provides multi-region redundancy, automated traffic steering, and self-healing infrastructure.

This architecture leverages fully managed Google Cloud native services to automate global routing, high availability, and self-healing infrastructure, meeting all recovery time and availability requirements with zero manual intervention.
A Cross-Region Internal Application Load Balancer is a Layer 7 proxy load balancer designed for internal private traffic originating from within VPC networks, connected on-premises networks, or peered VPCs across multiple regions.
The workload was an internal middleware service or enterprise ERP system accessed exclusively by private VMs or internal client applications distributed across multiple Google Cloud regions.
An External Passthrough Network Load Balancer is a regional Layer 4 load balancer built on Maglev and Andromeda that routes TCP/UDP traffic directly to backend VMs without proxying connections or terminating TLS. It supports primary and failover backend pools within a single region.
The application required non-HTTP protocols (e.g., raw TCP, UDP, or GRE) with direct server return (DSR) and needed to preserve the client's original source IP address without proxy encapsulation.
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