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: Minimize round-trip latency and TCP/TLS handshake time for users worldwide. Automatically direct traffic to the nearest geographic backend with available capacity. Seamlessly overflow excess traffic to the next closest healthy region if a primary regional instance group reaches its maximum capacity limits. Which Cloud Load Balancing architecture should you implement?

Deploy a Global external Application Load Balancer in Premium Tier with a global backend service referencing the multi-region instance groups configured with utilization or rate capacity limits.: ### What the Global External Application Load Balancer Is 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. ### How It Meets the Requirements - **Low-Latency Edge Termination:** The load balancer terminates client TCP and TLS sessions at the closest edge PoP using **Google Front Ends (GFEs)**. This eliminates multiple long-haul transoceanic round-trips for handshakes, drastically reducing Time to First Byte (TTFB). - **Proximity-Based Steering:** It automatically steers user requests to the geographically closest backend Managed Instance Group (MIG) that passes health checks and has available capacity. - **Automatic Capacity Overflow Handling:** By defining capacity limits (such as `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. ### Key Advantages and Capabilities - **Single Anycast Virtual IP (VIP):** Eliminates complex DNS-based load balancing and geo-routing propagation delays. - **Intelligent Traffic Spreading:** Re-routes traffic away from unhealthy or saturated backend instances seamlessly. - **Advanced Layer 7 Management:** Enables URL mapping, header-based routing, traffic splitting, and deep integration with **Google Cloud Armor** and **Cloud CDN**. - **High Availability:** Fully resilient to zonal and regional service outages. ### Why This Is Optimal 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.

StudyCerts

Global External Alb Capacity Overflow Traffic | Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam! | StudyCerts

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Global External Alb Capacity Overflow Traffic

Section: Scalability to meet growth requirements

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

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:

Minimize round-trip latency and TCP/TLS handshake time for users worldwide.
Automatically direct traffic to the nearest geographic backend with available capacity.
Seamlessly overflow excess traffic to the next closest healthy region if a primary regional instance group reaches its maximum capacity limits.

Which Cloud Load Balancing architecture should you implement?

Deploy a Global external Application Load Balancer in Premium Tier with a global backend service referencing the multi-region instance groups configured with utilization or rate capacity limits.

Deploy a Cross-region internal Application Load Balancer with global access enabled and fronted by regional Cloud NAT gateways.

Deploy an External passthrough Network Load Balancer in Premium Tier using a regional target pool across multiple zones.

Deploy individual Regional external Application Load Balancers in Standard Tier in each region, and configure Cloud DNS geolocation routing policies with health checking.

Professional Cloud Architect

Global External Alb Capacity Overflow Traffic

Related questions