Select and automate disaster recovery strategies (backup and restore, pilot light, warm standby, multi-site active/active) to meet recovery time and recovery point objectives across Regions.

A payments platform requires that a Regional failure cause effectively no downtime and effectively no data loss, and the business has accepted the cost of running production capacity in two Regions at once. The data layer must accept writes in both Regions concurrently. The DevOps team must choose the disaster recovery strategy that satisfies a near-zero recovery time and near-zero recovery point objective. Which strategy fits?

• AMulti-site active/active, serving live traffic from both Regions with a multi-Region database accepting writes in each, so a Regional loss removes one active site while the other keeps serving uninterrupted.check_circle Correct
• BBackup and restore using frequent AWS Backup copies to the second Region, restoring the platform there within the recovery window whenever the primary Region becomes unavailable for an extended period.
• CPilot light, holding replicated data in the second Region while the application tier stays off until a failover starts it, so capacity is summoned on demand when the primary fails.
• DWarm standby, running a scaled-down always-on copy in the second Region that is scaled up and promoted to take writes when the primary Region is declared unavailable during an incident.

Why A is correct: Multi-site active/active runs full production in both Regions with a database that takes writes in each, so losing one Region simply drops a live site while the survivor keeps serving, delivering the near-zero recovery time and recovery point the business has paid for.

Why B is wrong: Backup and restore is the slowest pattern with a recovery point bounded by the backup interval, so it cannot deliver near-zero downtime or near-zero data loss no matter how frequent the copies are.

Why C is wrong: Pilot light keeps the data current but leaves compute off, so the time to launch and scale the application tier produces noticeable downtime, which violates the near-zero recovery time objective.

Why D is wrong: Warm standby recovers in minutes by scaling a smaller fleet and promoting the standby, but that scale-up and promotion still introduces a short outage, so it falls short of the near-zero recovery time the payments platform demands.