A web application runs in a single AWS Region on microservices hosted on AWS Fargate (Amazon ECS) and uses an Amazon RDS for MySQL instance for data. Route 53 handles DNS. A CloudWatch alarm triggers an EventBridge rule when the application fails. Design a disaster recovery solution that provides recovery in a second Region and minimizes recovery time. Which approach meets the requirement?

The correct approach provisions a warm standby in the secondary Region, minimizing recovery time. A second ECS cluster and Fargate service are pre-provisioned, meaning the compute layer is ready. A cross-Region RDS read replica ensures data is continuously replicated with minimal lag. When a disaster occurs, the Lambda function promotes the read replica to a standalone primary database, making it immediately available for writes, and updates Route 53 to direct traffic to the secondary Region. This strategy offers a low Recovery Time Objective (RTO) and Recovery Point Objective (RPO). Incorrect options involve creating resources on demand or relying on snapshots for the database, which significantly increases RTO due to the time required for provisioning and data restoration. Converting RDS data to DynamoDB is a data migration and schema change, not a disaster recovery strategy for an existing relational database.