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 organization is architecting a multi-region disaster recovery strategy for an externally accessible, mission-critical web application on Google Cloud. The architecture must satisfy the following business continuity requirements:
StudyCerts
StudyCertsus-east4 region.us-central1 region.How should you configure Cloud DNS and health checking to achieve automated cross-region failover and failback?
Configure a single regional health check in us-east4, attach it directly to the Cloud DNS managed zone, and configure an A record with a 300-second TTL pointing to both forwarding rule IP addresses.
Deploy a Cloud Service Mesh service load balancing policy with the spray-to-world algorithm, and configure Cloud DNS with a Geo routing policy with a 3600-second TTL.
Create a global health check configured with three source regions targeting the primary forwarding rule IP address, configure a Cloud DNS record set with a Failover routing policy referencing the health check, and set the record TTL to 30–60 seconds.
Create an external passthrough Network Load Balancer in each region, set the failover ratio to 0.0, and configure Cloud DNS to use weighted round-robin routing.
Configure a single regional health check in us-east4, attach it directly to the Cloud DNS managed zone, and configure an A record with a 300-second TTL pointing to both forwarding rule IP addresses.
Deploy a Cloud Service Mesh service load balancing policy with the spray-to-world algorithm, and configure Cloud DNS with a Geo routing policy with a 3600-second TTL.
Create a global health check configured with three source regions targeting the primary forwarding rule IP address, configure a Cloud DNS record set with a Failover routing policy referencing the health check, and set the record TTL to 30–60 seconds.
This solution implements automated cross-region failover and failback by pairing Cloud DNS Failover routing policies with Google Cloud distributed health checks targeting regional external Application Load Balancer forwarding rules.
DNS TTL + (Health Check Interval * Unhealthy Threshold). Setting the DNS record TTL to 30–60 seconds ensures client caches expire rapidly, redirecting user traffic to the healthy secondary region with minimal delay.This approach aligns with Google Cloud architectural best practices for cross-region disaster recovery, balancing swift failure detection against protection against transient flap errors.
Create an external passthrough Network Load Balancer in each region, set the failover ratio to 0.0, and configure Cloud DNS to use weighted round-robin routing.