An organization is deploying a stateless web application on Compute Engine in Google Cloud. The application must maintain high availability within a single region and automatically tolerate the failure of an individual zone. Which two configuration choices should you implement to meet these high availability requirements?
- Configure a regional Managed Instance Group (MIG) to automatically distribute compute instances across multiple availability zones.Answer
- Deploy a Regional External Application Load Balancer to distribute incoming traffic across instances in all active backend zones.Answer
- CMigrate the stateless application to a multi-cluster Google Kubernetes Engine (GKE) environment with Anthos Service Mesh across multiple regions.
- DConfigure the load balancer HTTP health check to execute complex database queries against the backend relational database.
- EUse single-zone unmanaged instance groups and rely on scheduled disk snapshots to manually recreate instances during an outage.
Answer
To achieve high availability against zonal outages for a stateless Compute Engine application within a single region, you should configure a regional Managed Instance Group (MIG) across multiple zones and front the instances with a Regional External Application Load Balancer.
Regional Managed Instance Groups automatically maintain compute capacity across multiple availability zones within a Google Cloud region. Pairing regional MIGs with a Regional External Application Load Balancer ensures traffic is seamlessly directed to healthy instances across active zones, providing high availability and protection against zonal outages.
Step-by-Step Solution
Key Concept
Designing single-region high availability using regional Managed Instance Groups and Regional Load Balancers