An e-commerce platform hosted on Google Cloud experiences periodic flash-sale traffic surges that can exhaust Compute Engine regional vCPU quotas and cause capacity constraints in the primary region (us-central1). The Site Reliability Engineering (SRE) team needs to implement an automated multi-region capacity scaling and rapid failover strategy. The solution must: Ensure client requests automatically overflow to a secondary region (us-east4) as soon as the primary region reaches backend capacity or quota limits. Avoid client-side DNS caching delays during localized saturation incidents. Maintain high availability and automated traffic distribution based on real-time backend capacity. Which architectural strategy should the SRE team implement?

Deploy backends across multiple regions using Network Service Tiers Premium Tier with a global external load balancer and configured backend capacity limits.: ### What Network Service Tiers Premium Tier with Global Load Balancing is **Network Service Tiers Premium Tier** routes global traffic over Google's high-performance, low-latency private backbone network using a single **global anycast IP address**. When combined with an **external Application Load Balancer** and multi-region backend services, Google Cloud monitors backend utilization in real time. ### How it meets the requirements - **Automatic overflow on capacity exhaustion**: SREs configure maximum backend capacities (such as max CPU utilization or max request rate per instance/endpoint). When backends in `us-central1` hit capacity limits or cannot autoscale further due to regional quota exhaustion, the global load balancer automatically spills over excess requests to the nearest healthy region (`us-east4`) with available capacity. - **Eliminating DNS caching delays**: Because a single global anycast VIP serves all traffic, failover and capacity overflow occur at the network layer without modifying DNS records or waiting for client **Time to Live (TTL)** caches to expire. - **High availability and real-time distribution**: Health checks continuously monitor backend health. If a zone or region suffers severe degradation, traffic shifts dynamically to remaining operational backends. ### Key advantages - **Automated overflow handling**: Prevents dropped requests when localized quotas are reached. - **Sub-second failover routing**: Eliminates DNS propagation latency during critical incidents. - **Capacity-aware load balancing**: Distributes load based on actual backend capability. - **Optimized user latency**: Delivers requests via the closest Google Cloud edge Point of Presence (PoP). ### Why this is optimal This approach provides true active-active multi-region resilience. It seamlessly absorbs regional capacity constraints without administrative intervention or complex client-side failover logic.

Multi Region Capacity Overflow Failover Architecture | Professional Cloud DevOps Engineer

Multi Region Capacity Overflow Failover Architecture

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 e-commerce platform hosted on Google Cloud experiences periodic flash-sale traffic surges that can exhaust Compute Engine regional vCPU quotas and cause capacity constraints in the primary region (us-central1).

The Site Reliability Engineering (SRE) team needs to implement an automated multi-region capacity scaling and rapid failover strategy. The solution must:

Ensure client requests automatically overflow to a secondary region (us-east4) as soon as the primary region reaches backend capacity or quota limits.
Avoid client-side DNS caching delays during localized saturation incidents.
Maintain high availability and automated traffic distribution based on real-time backend capacity.

Which architectural strategy should the SRE team implement?

Deploy backends across multiple regions using Network Service Tiers Premium Tier with a global external load balancer and configured backend capacity limits.

Consolidate workloads into a single large regional GKE cluster spanning all zones in us-central1 and configure Horizontal Pod Autoscaling (HPA).

Deploy backends in each region using Network Service Tiers Standard Tier with Cloud DNS geolocation routing policies and health checks.

Configure Cloud Monitoring to trigger a Cloud Function that executes manual capacity draining on us-central1 and updates Cloud DNS records.

Professional Cloud DevOps Engineer

Multi Region Capacity Overflow Failover Architecture

Related questions