An enterprise runs a mission-critical web application on Google Cloud Compute Engine and needs to implement an automated disaster recovery (DR) and traffic management strategy. The design must meet the following operational requirements: Route global user traffic automatically to the closest healthy backend compute region during normal operations. Automatically shift traffic to a secondary region if all backend instances in the primary region become unhealthy, without requiring manual DNS changes or client reconnections. Automatically steer client traffic to a standby static maintenance website hosted in Cloud Storage if all compute backends in both regions experience an outage. Which architecture should the enterprise deploy?

Deploy a Global External Application Load Balancer in Premium Tier with regional backend Managed Instance Groups (MIGs) in both regions, and configure a Cloud DNS failover routing policy with health checking pointing to the load balancer VIP as primary and the Cloud Storage bucket as backup: ### What Global External Application Load Balancing and Cloud DNS Failover Are A **Global External Application Load Balancer** operating in **Premium Tier** provides a single Anycast IP address that terminates connections at Google Points of Presence (PoPs) closest to clients. Combined with **Cloud DNS failover routing policies**, organizations can achieve multi-tiered resilience by combining Layer 7 multi-region proximity routing with automated DNS-level fallback. ### How It Meets the Requirements - **Proximity-Based Routing & Automated Cross-Region Failover**: The global load balancer automatically distributes incoming client traffic to the nearest healthy **Managed Instance Group (MIG)** based on capacity and health check status. If all instances in the primary region become unhealthy, the global load balancer automatically redirects incoming requests to the secondary region without changing IP addresses or updating DNS records. - **Static Site Failover via Cloud DNS**: By configuring a **Cloud DNS failover routing policy** with automated health checks targeting the primary load balancer VIP, Cloud DNS continuously monitors load balancer availability. If backends across all regions fail and the load balancer fails health checks, Cloud DNS automatically updates DNS resolution to route clients to the standby **Cloud Storage static website**. ### Key Advantages and Capabilities - **Single Anycast VIP**: Avoids client-side DNS caching delays during regional failover between primary and secondary compute clusters. - **Health Check Integration**: Native HTTP/HTTPS health checks detect instance, zonal, and regional compute failures rapidly. - **Low RTO Maintenance Mode**: Provides immediate graceful degradation to a static site during comprehensive system failures. - **Automated Failback**: Traffic automatically returns to primary compute backends once regional health checks recover. ### Why This Is Optimal This architecture combines automated infrastructure-level traffic distribution with DNS-based disaster recovery steering. It eliminates manual intervention during regional disasters and delivers predictable business continuity within defined **Recovery Time Objectives (RTO)**.

StudyCerts

Automated Dr Traffic Management Load Balancing Cloud Dns | 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

Automated Dr Traffic Management Load Balancing Cloud Dns

Section: Disaster recovery

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 runs a mission-critical web application on Google Cloud Compute Engine and needs to implement an automated disaster recovery (DR) and traffic management strategy.

The design must meet the following operational requirements:

Route global user traffic automatically to the closest healthy backend compute region during normal operations.
Automatically shift traffic to a secondary region if all backend instances in the primary region become unhealthy, without requiring manual DNS changes or client reconnections.
Automatically steer client traffic to a standby static maintenance website hosted in Cloud Storage if all compute backends in both regions experience an outage.

Which architecture should the enterprise deploy?

Deploy a Global External Application Load Balancer in Premium Tier with regional backend Managed Instance Groups (MIGs) in both regions, and configure a Cloud DNS failover routing policy with health checking pointing to the load balancer VIP as primary and the Cloud Storage bucket as backup

Deploy independent Regional External Application Load Balancers in each region and configure a standard round-robin Cloud DNS routing policy pointing equally to both regional IP addresses

Deploy a single Regional External Application Load Balancer in the primary region, configure Persistent Disk Asynchronous Replication, and use an automated Cloud Function to modify Cloud DNS records to point to Cloud Storage during an outage

Deploy an Internal Passthrough Network Load Balancer in each region with a failover backend service and configure Cloud DNS private routing policies to steer external user traffic

Professional Cloud Architect

Automated Dr Traffic Management Load Balancing Cloud Dns

Related questions