An enterprise is designing a multi-tier, mission-critical web application on Google Cloud that serves users globally over HTTPS. The architecture must satisfy the following reliability and traffic management requirements: Automatically route end-users to the geographically closest healthy backend instances to minimize latency. Automatically steer traffic away to another region if the primary region's backend instances become unhealthy or exceed capacity. Automatically detect application software crashes on backend virtual machines (VMs) and self-heal by recreating unhealthy instances without manual intervention. Provide zone-level resilience within each deployed region. Which architecture should you deploy to meet these requirements?

Deploy a Global External Application Load Balancer fronting regional Managed Instance Groups (MIGs) across multiple regions, configure load balancing HTTP health checks on the backend service, and attach an auto-healing health check policy to each regional MIG.: ### What Global External Application Load Balancers and Regional MIGs Provide A **Global External Application Load Balancer** operates at Layer 7 using Google's global Anycast IP infrastructure to terminate connections close to users at edge Points of Presence (PoPs). When paired with **regional Managed Instance Groups (MIGs)**, the architecture provides multi-region redundancy, automated traffic steering, and self-healing infrastructure. ### How It Meets the Requirements - **Proximity-based routing and low latency:** The **Global External Application Load Balancer** in Premium Tier automatically terminates user traffic at the closest edge PoP and routes incoming requests to the nearest backend MIG with available capacity. - **Automated cross-region failover:** The load balancer uses **backend service health checks** to continuously monitor instance health. If all backend instances in the closest region become unhealthy or reach their capacity limits, the load balancer automatically shifts traffic to the next closest healthy region with capacity. - **Application self-healing:** Applying an **auto-healing policy** with an application-level HTTP health check to each MIG allows Compute Engine to monitor application health and automatically recreate instances that fail consecutive health probes. - **Zonal resilience:** **Regional MIGs** automatically distribute VM instances evenly across multiple zones within each region, protecting against single-zone infrastructure failures. ### Key Advantages - **Seamless multi-region failover:** Failover occurs transparently at the Google Front End (GFE) proxy level without relying on client-side DNS cache expiration. - **Separation of concerns:** Enables independent health checking for traffic distribution (load balancer health check) and VM lifecycle management (MIG auto-healing health check). - **High availability in depth:** Provides automated recovery across application, instance, zonal, and regional failure scenarios. - **Capacity-aware load balancing:** Prevents backend overloading by shedding excess traffic to other available regions. ### Why This Is Optimal This architecture leverages fully managed Google Cloud native services to automate global routing, high availability, and self-healing infrastructure, meeting all recovery time and availability requirements with zero manual intervention.

StudyCerts

Global Alb Multi Region Mig Autohealing | 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 Alb Multi Region Mig Autohealing

Section: High availability and fail-over design

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 enterprise is designing a multi-tier, mission-critical web application on Google Cloud that serves users globally over HTTPS. The architecture must satisfy the following reliability and traffic management requirements:

Automatically route end-users to the geographically closest healthy backend instances to minimize latency.
Automatically steer traffic away to another region if the primary region's backend instances become unhealthy or exceed capacity.
Automatically detect application software crashes on backend virtual machines (VMs) and self-heal by recreating unhealthy instances without manual intervention.
Provide zone-level resilience within each deployed region.

Which architecture should you deploy to meet these requirements?

Deploy a Global External Application Load Balancer fronting regional Managed Instance Groups (MIGs) across multiple regions, configure load balancing HTTP health checks on the backend service, and attach an auto-healing health check policy to each regional MIG.

Deploy a Cross-Region Internal Application Load Balancer with regional Managed Instance Groups, and configure global URL map weighted traffic splitting between regions.

Deploy an External Passthrough Network Load Balancer in each region with zonal Managed Instance Groups, and configure primary and failover backend pools with OS-level restart scripts.

Deploy individual Regional External Application Load Balancers in each region with unmanaged instance groups, and configure a Cloud DNS failover routing policy to steer traffic between regions.

Professional Cloud Architect

Global Alb Multi Region Mig Autohealing

Related questions