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!
Prepare and test your skills
Prepare and test your skills
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.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
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:
Which architecture should the enterprise deploy?
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 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 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
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 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 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 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
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
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.
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
StudyCerts