Which solution meets these requirements?

Explanations:

While this option provides high availability with Multi-AZ and a read replica, configuring the application to reference the replica instance endpoint for reports can lead to data inconsistency during failover and is not optimal for handling read queries efficiently.

This option incorrectly suggests using the primary DB instance endpoint for the application and the replica endpoint for reporting queries. This could lead to performance issues, as the primary instance will be overloaded with report processing, negating the benefits of having a read replica.

This option uses Amazon Aurora, which offers superior performance and scalability. By configuring the application to use the cluster endpoint for writes and the reader endpoint for reports, it efficiently balances the load and minimizes downtime in disaster recovery situations. Aurora’s design ensures better availability and lower failover times compared to RDS for MySQL.

Similar to option B, this option suggests that the application reference the primary DB instance endpoint for operations while using the replica for reports. This does not utilize the capabilities of Aurora effectively, as it can lead to an imbalanced load on the primary instance, impacting overall performance and not leveraging the benefits of the reader endpoint properly.