A company needs a strategy for failover and disaster recovery of its data and application. The application uses a MySQL database and Amazon EC2 instances. The company requires a maximum RPO of 2 hours

An Amazon Aurora Single-AZ cluster does not provide high availability or disaster recovery across regions without additional complex replication, making it unsuitable for the specified RPO/RTO.

Creating an Amazon Aurora global database across two AWS Regions provides asynchronous, continuous replication with an RPO typically in seconds and RTO in minutes for regional failover, effectively meeting the required 2-hour RPO and 10-minute RTO for data.

The choice is incomplete, but simply having an Aurora cluster in multiple regions without specifying a global database or robust replication/failover mechanism does not inherently meet the strict RPO/RTO requirements.

Setting up the application in two AWS Regions and using Amazon Route 53 failover routing allows for automatic redirection of traffic to the healthy secondary region upon primary region failure, which can achieve an RTO of 10 minutes for the application.

The choice is incomplete, but while AWS Global Accelerator can provide multi-region failover for applications, Route 53 failover routing (Option D) is a common and complete solution that effectively meets the application's RTO requirement.