DOP-C02 Resilient Cloud Solutions Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Use AWS CloudEndure Disaster Recovery (now AWS DRS) with periodic replication every hour.

  Why it's wrong here

  AWS CloudEndure Disaster Recovery (now AWS DRS) achieves sub-second RPO only when running in its default continuous replication mode; selecting a periodic replication schedule of every hour creates recovery points at one-hour intervals. On failover, you can restore only to the last hourly snapshot, risking up to 60 minutes of data loss, which far exceeds the required 1-minute RPO. This option would be operationally incorrect because DRS' value proposition is continuous, near-synchronous replication, not hourly batch processing.

• ✗

  Use AWS Backup to take snapshots every 5 minutes and restore in the target region.

  Why it's wrong here

  AWS Backup schedules snapshots on a recurring basis, and with a 5-minute interval, the newest available recovery point is at most 5 minutes old. A failure immediately after the last snapshot causes at least 5 minutes of data loss, violating the 1-minute RPO. Furthermore, cross-region snapshot copying adds propagation delay, and snapshots themselves are not a continuous replication stream; the RPO is inherently bounded by the snapshot frequency, so this design cannot meet the stated objective.

• ✗

  Use RDS cross-region automated backups with a 5-minute backup window.

  Why it's wrong here

  RDS cross-region automated backups are copied to the destination Region on a periodic basis—typically every 30 minutes—and the backup window simply defines the daily time period during which the source automated backup may be initiated, not a replication interval. Even with a 5-minute backup window, the recovery point in the destination Region is not 5 minutes behind; the cross-Region copy runs on a coarser schedule and can be tens of minutes old. This yields an RPO far above the needed 1 minute, so the option is incorrect.

• ✓

  Configure AWS DRS to continuously replicate data to a staging area in AWS, and launch instances in the target region on failover.

  Why this is correct

  AWS DRS provides continuous block-level replication from source servers to a low-cost staging area in the AWS target Region, capturing every data change and maintaining a nearly synchronous copy. On failover, DRS automatically launches EC2 instances from the most recent consistent recovery point, achieving an RPO of seconds (well under the required 1 minute) and an RTO that can be measured in minutes. This directly meets the stated DR requirements, making it the correct choice.

Go deeper

Related to this question