Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
An organization is designing a disaster recovery (DR) strategy for a non-critical reporting database and needs to align its architecture with the following business requirements:
Which disaster recovery strategy should the organization implement?
A pre-provisioned standby database with continuous asynchronous replication represents a warm standby disaster recovery pattern. In this model, a secondary database instance runs continuously in a recovery region and receives ongoing data updates from the primary database, while web and application tier Compute Engine VMs remain stopped or stored as snapshots until a disaster occurs.
This approach does not meet the strict budget requirement to minimize ongoing infrastructure and licensing costs. Keeping a pre-provisioned database instance running 24/7 in a secondary region continuously consumes compute, memory, and licensing resources. Because the business can tolerate up to 12 hours of downtime (RTO) and 8 hours of data loss (RPO), paying for an always-on secondary database server is over-provisioning.
snapshots to save money, the continuously running database instance still generates substantial operating expenses.This option would be appropriate if the organization needed a warm standby solution for an important business application requiring a low RPO (minutes) and an RTO of less than an hour, while trying to save money on the web and application tiers by launching VMs from snapshots during a failover.
Warm standby architectures bridge the gap between cold backups and hot active-active clusters. However, when a workload's RPO is 8 hours or more and its RTO is several hours, cold backups in Cloud Storage are much more cost-effective.
A multi-zone availability group within a single region is a high availability (HA) architecture that distributes database nodes across separate zones inside the same geographic region, paired with Compute Engine snapshots to capture point-in-time disk states.
This option fails two critical requirements:
Compute Engine instant snapshots captures multi-disk backups in under a second, but requires multi-regional storage placement if regional disaster recovery is needed.OpEx).This strategy would be correct if the organization needed to protect a production database strictly against hardware, instance, or zonal failures within a single region while achieving fast local failover.
It is vital to distinguish between High Availability (HA) across zones and Disaster Recovery (DR) across regions. While multi-zone deployments handle localized infrastructure failures seamlessly, true business continuity during a regional outage requires cross-region replication or multi-region backups.
Backing up a database directly to a multi-region Cloud Storage bucket is a foundational cold disaster recovery (DR) strategy. In this approach, database backups and transaction logs are periodically written to object storage that automatically replicates data across multiple geographic regions within a defined multi-region boundary, without maintaining active standby database servers.

BACKUP TO URL) without requiring intermediate local disk storage.When designing for business continuity, architects must balance the trade-offs between cost, RPO, and RTO. For less critical systems that can tolerate several hours of downtime and data loss, an off-site backup strategy using multi-region Cloud Storage delivers the required geographic resilience at a fraction of the cost of warm or hot standby clusters.
An availability group with synchronous replication is a high availability (HA) and hot standby disaster recovery architecture. In this setup, every transaction committed to the primary database is simultaneously written to one or more active secondary database nodes before the transaction is confirmed as complete.
While synchronous replication across regions provides exceptional resilience, it directly violates the budget requirement to minimize ongoing infrastructure and licensing expenses. Maintaining active, continuously running database clusters across multiple regions requires redundant compute capacity, high-bandwidth networking, and duplicate software licenses, which is unnecessary when an 8-hour RPO and 12-hour RTO are acceptable.
RTO < 1 minute) by keeping standby database nodes online and ready to accept traffic.This strategy would be the right choice if the scenario involved a mission-critical transactional application (such as a core banking system) that required near-zero data loss (RPO < 1 minute) and immediate failover (RTO < 1 minute) regardless of infrastructure cost.
A common misconception in disaster recovery planning is assuming that the fastest recovery strategy is always the best choice. Effective cloud architecture aligns system expenditure with business criticality, avoiding expensive hot-standby architectures when simple off-site backups meet the business impact objectives.
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