An enterprise is designing a high-availability architecture on Google Cloud for a stateless web application requiring low latency across multiple regions. The application receives unpredictable traffic spikes and requires continuous availability even if an entire region experiences an outage. Which TWO architectural recommendations should you implement to satisfy these technical and availability requirements?
- Deploy the stateless web backend across multiple Compute Engine Managed Instance Groups (MIGs) located in two different Google Cloud regions.Cevap
- Place a Global External Application Load Balancer in front of the backend instances to route incoming user traffic to the nearest healthy regional instance group.Cevap
- CDeploy Google Kubernetes Engine (GKE) Enterprise clusters in each region with multi-cluster mesh to run the basic stateless HTTP frontend.
- DConfigure an HA VPN connection with maximum tunnel bandwidth as the sole front-end load balancing solution for routing external client traffic.
- EConfigure the Managed Instance Group auto-scaler using strictly a static 80% CPU utilization threshold for I/O-bound web traffic.
Cevap
The correct architecture uses multi-region Compute Engine Managed Instance Groups (MIGs) fronted by a Global External Application Load Balancer.
High availability across regional outages requires deploying application backend instances in multiple Google Cloud regions. Deploying Managed Instance Groups across separate regions combined with a Global External Application Load Balancer allows traffic to automatically route to the closest healthy backend region, satisfying both low latency and seamless failover requirements.
Adım Adım Çözüm
Anahtar Kavram
Designing Multi-Region High Availability with Global Load Balancing