Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
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:
us-east4 region.us-central1 region.How should you configure Cloud DNS and health checking to achieve automated cross-region failover and failback?
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.
This configuration deploys Network Load Balancers (Layer 4 passthrough) with a failover ratio of 0.0 and uses Cloud DNS Weighted Round Robin (WRR) routing policies.
0.0 means failover to backup pools would never trigger based on primary backend health thresholds.You wanted to split static percentages of TCP traffic across multiple functioning regions for canary testing.
This option applies a Cloud Service Mesh service load balancing policy using the spray-to-world algorithm across client proxies, combined with a Geo routing policy in Cloud DNS with a 1-hour (3600 seconds) TTL.
spray-to-world algorithm spreads client requests globally across all instances in all regions simultaneously, defeating active-standby isolation and increasing network transit costs.You were configuring internal service-to-service mesh communication that required uniform request distribution across all global backends.
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.This option attempts to monitor the primary load balancer using a regional health check located inside us-east4 and points a standard multi-value A record with a 5-minute (300 seconds) TTL to both load balancers.
us-east4) may become unreachable or fail to report status, preventing reliable failover coordination.You needed simple round-robin DNS load balancing without automated health-checking failover controls.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated