An organization is designing the infrastructure for a critical stateless application hosted on Compute Engine in Google Cloud. The application must remain available even if an entire Availability Zone experiences an outage within a selected region. Which TWO architectural options should the cloud architect implement to achieve regional high availability for this workload?
- Deploy the Compute Engine virtual machines using a Regional Managed Instance Group (MIG) distributed across multiple zones within the region.Answer
- Configure an External HTTP(S) Load Balancer in front of the backend instances to distribute incoming web traffic across healthy instances in all active zones.Answer
- CReplace the stateless application layer with a Cloud Spanner database deployment to handle compute processing across multiple regions.
- DMigrate the simple stateless workload to a multi-region Google Kubernetes Engine (GKE) cluster to provide basic zonal fault tolerance.
- EEstablish VPC Network Peering between zonal subnetworks and rely on transitive routing to forward traffic during a zonal failure.
Answer
Deploying instances across multiple zones using a Regional Managed Instance Group (MIG) combined with an External HTTP(S) Load Balancer provides automated health checking, traffic distribution, and fault tolerance against single-zone outages.
Regional Managed Instance Groups (MIGs) provision and manage Compute Engine instances across multiple Availability Zones in a single region, ensuring compute redundancy. Pairing a Regional MIG with an External HTTP(S) Load Balancer enables automated health checking and seamless traffic routing to operational instances if a specific zone experiences an outage.
Step-by-Step Solution
Key Concept
Regional High Availability with Compute Engine Regional MIGs and Cloud Load Balancing