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 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?
This pattern relies on a single Regional External Application Load Balancer in one location, backing up data using Persistent Disk Asynchronous Replication (Async PD), and relying on reactive automation (such as Cloud Functions) triggered by monitoring alerts to rewrite public DNS records.
The architecture were designed for a cold or warm disaster recovery strategy with a loose RTO allowing tens of minutes to provision compute capacity in the secondary region.
An Internal Passthrough Network Load Balancer distributes non-proxied Layer 4 (TCP/UDP) traffic internally within a Google Cloud Virtual Private Cloud (VPC) network using private RFC 1918 IP addresses.
The workload were an internal multi-tier microservice accessed exclusively by backend services located in the same VPC or across Cloud Interconnect circuits.
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).
A standard round-robin Cloud DNS record distributes DNS resolution equally across multiple static IP addresses without evaluating the operational health of the underlying endpoints.
The requirement called for simple stateless load distribution across two active regions where regional health-checking and automatic failover were handled externally by client-side retry logic.
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 Validated