A SaaS application runs on API Gateway (HTTPS), AWS Lambda, and Aurora Serverless v1 deployed across multiple AZs. The deployment used AWS SAM. There is no disaster recovery (DR) plan. The company requires the application to be recoverable in another AWS Region with an RTO of 5 minutes and an RPO of 1 minute. Which DR approach meets these recovery objectives?

The correct answer meets the RTO of 5 minutes and RPO of 1 minute by using an active-passive configuration with Aurora Global Database. Aurora Global Database provides low RPO (typically less than 1 second) and fast recovery (RTO often under 1 minute) by replicating data asynchronously to a secondary region. Launching the application in the target region in an active-passive setup means the infrastructure for Lambda and API Gateway is already provisioned, minimizing recovery time. Incorrect options: Creating a read replica of Aurora Serverless v1 in the target region and promoting it during a disaster would not meet the RPO of 1 minute, as Aurora Serverless v1 read replicas are not designed for cross-region disaster recovery with such low RPO. Also, deploying the application via a SAM runbook during a disaster would likely exceed the 5-minute RTO. Converting to a standard Aurora MySQL global database and using a SAM runbook to deploy the application would meet the RPO but likely fail the RTO, as the application deployment would take too long. Creating an Aurora Serverless v1 DB cluster with multiple writer instances in the target region is not a standard Aurora Serverless v1 feature for cross-region DR, and it doesn't inherently provide the RPO/RTO benefits of Aurora Global Database.