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 online retail organization is preparing for a global flash sale that will generate massive, sudden spikes in HTTPS web traffic from users worldwide. The application frontend is deployed across Compute Engine Managed Instance Groups (MIGs) located in North America, Europe, and Asia.
The architecture must satisfy the following technical requirements:
Which Cloud Load Balancing architecture should you implement?
An External passthrough Network Load Balancer is a regional Layer 4 load balancer built on Google Maglev. It routes raw TCP/UDP packets directly to backend VM instances without terminating connections or modifying IP headers, relying on Direct Server Return (DSR).
The application required preserving client source IP addresses directly at the OS level, handling non-HTTP IP protocols (such as UDP, ESP, or GRE), or implementing Direct Server Return (DSR).
This architecture deploys isolated Regional external Application Load Balancers within specific Google Cloud regions using Standard Network Service Tier, using Cloud DNS geolocation routing policies to direct users to specific regional IP addresses based on client geographic IP resolution.
Workloads have strict data sovereignty or jurisdictional compliance requirements mandating that TLS termination and network data stay confined within a single geographic territory.
A Global external Application Load Balancer is a proxy-based Layer 7 system implemented across distributed Google Front Ends (GFEs) at Google's global edge Points of Presence (PoPs). Operating in the Premium Network Service Tier, it exposes a single global Anycast IP address and routes incoming HTTP(S) traffic over Google's private fiber backbone directly to multi-region backends.
UTILIZATION or RPS) on the global backend service, the load balancer automatically overflows excess traffic to the next closest region with available capacity when a region hits its threshold.Unlike regional load balancers or DNS-based failover, the global external Application Load Balancer in Premium Tier actively calculates latency and backend capacity per request, providing seamless global scalability and automated traffic overflow without client interruption.
A Cross-region internal Application Load Balancer provides Layer 7 reverse-proxy load balancing for internal VPC clients across multiple regions using internal RFC 1918 private IP addresses.
You were building an internal, multi-tier corporate microservices architecture where backend services located in different regions need private, cross-regional Layer 7 routing from internal client VMs.
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