What should a solutions architect do to meet these requirements?
Deploy the application with the required infrastructure elements in place. Use Amazon Route 53 to configure active-passive failover. Create an Aurora Replica in a second AWS Region.
Host a scaled-down deployment of the application in a second AWS Region. Use Amazon Route 53 to configure active-active failover. Create an Aurora Replica in the second Region.
Replicate the primary infrastructure in a second AWS Region. Use Amazon Route 53 to configure active-active failover. Create an Aurora database that is restored from the latest snapshot.
Back up data with AWS Backup. Use the backup to create the required infrastructure in a second AWS Region. Use Amazon Route 53 to configure active-passive failover. Create an Aurora second primary instance in the second Region.
Explanations:
This option sets up an active-passive failover using Amazon Route 53, which meets the downtime tolerance and allows for potential data loss. An Aurora Replica in a second region provides a means for disaster recovery while minimizing costs when the primary is healthy.
Active-active failover is not required based on the given requirements, and running a scaled-down deployment may complicate the infrastructure without providing necessary disaster recovery benefits. Additionally, using an Aurora Replica instead of a primary instance could lead to data loss.
While it replicates the infrastructure, using active-active failover is not needed and could introduce complexity. Restoring an Aurora database from a snapshot would also result in data loss, which does not align with the tolerance for downtime and data loss stated.
This option suggests creating infrastructure from backups, which does not align with the requirement for near-real-time failover. The use of an Aurora second primary instance is also unnecessary for the requirements given.