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 is designing a business continuity and disaster recovery (DR) strategy on Google Cloud for a mission-critical web application. The application consists of a stateless web/application tier and a transactional database backend.
The business continuity plan establishes the following operational criteria:
Which architectural pattern should you select to meet these requirements?
A Cold Standby disaster recovery pattern relies on periodic backups, snapshots, and automation scripts (such as Terraform or Cloud Build pipelines) to provision compute and restore databases only after a disaster occurs.
The workload were a non-critical internal service or batch reporting application with an RTO of 4–24 hours and an RPO of 12–24 hours where lowest storage-only cost is the primary objective.
A Warm Standby (often implemented alongside pilot light principles) maintains critical background services and data synchronization continuously running in a secondary geographic region, while keeping compute resources scaled down to a minimum footprint during normal operations.
The warm standby pattern provides the ideal trade-off between the sub-15-minute RTO and sub-1-minute RPO while avoiding the full expense of a dual-region active-active deployment.
A Zonal High Availability (HA) architecture deploys redundant compute instances across two or more zones in the same region, utilizing synchronous replication to a standby database instance located in an alternate zone.
The business requirements strictly focused on high availability (HA) against localized hardware faults without needing geographic disaster recovery (DR) against regional service interruptions.
A Hot Standby / Active-Active multi-region deployment runs fully provisioned, identically sized application clusters in two or more geographically distributed regions simultaneously, sharing the live production traffic load behind global load balancers.
The organization required an RTO of zero downtime (instantaneous failover) and maximum availability with no budget restrictions regarding duplicate compute infrastructure.
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