A company runs an on-premises application backed by a MySQL database. The company is migrating the application to AWS to improve elasticity and availability. The production database experiences heavy read activity during normal operation. Every 4 hours the development team pulls a full export of the production database to populate a staging database; during this export users experience unacceptable latency and the development team cannot use staging until the export finishes. A solutions architect must recommend a replacement architecture that eliminates the application latency and allows the development team to use the staging environment without delay. Which solution meets these requirements?

The correct solution leverages Amazon Aurora MySQL with Multi-AZ Aurora Replicas for high availability and read scalability in production. Aurora's architecture separates compute and storage, allowing for efficient scaling. Database cloning in Aurora is a near-instantaneous operation that creates a copy of the database, sharing the same underlying storage volume. This eliminates the performance impact on the production database during staging environment creation and allows the development team immediate access to the staging environment. Incorrect options: Using mysqldump for staging database population would still impact the production database's performance and cause latency, similar to the on-premises issue. Using Amazon RDS for MySQL with a Multi-AZ deployment and read replicas is a good solution for production, but using the standby instance for staging is not feasible as the standby is for disaster recovery and cannot be directly accessed for other purposes. Using Amazon RDS for MySQL with mysqldump again introduces the same latency issues as the on-premises solution.