Which solution meets these requirements?
Use Amazon Aurora MySQL with Multi-AZ Aurora Replicas for production. Populate the staging database by implementing a backup and restore process that uses the mysqldump utility.
Use Amazon Aurora MySQL with Multi-AZ Aurora Replicas for production. Use database cloning to create the staging database on-demand.
Use Amazon RDS for MySQL with a Multi-AZ deployment and read replicas for production. Use the standby instance for the staging database.
Use Amazon RDS for MySQL with a Multi-AZ deployment and read replicas for production. Populate the staging database by implementing a backup and restore process that uses the mysqldump utility.
Explanations:
While Amazon Aurora MySQL with Multi-AZ Aurora Replicas would improve availability, using the mysqldump utility for backup and restore would still cause delays and high latency, as it is a time-consuming process.
Amazon Aurora MySQL with Multi-AZ Aurora Replicas provides high availability, and using database cloning allows the development team to create a staging database quickly and without impacting the production workload.
Although Amazon RDS for MySQL with Multi-AZ and read replicas would improve availability, using the standby instance for staging is not feasible since the standby instance is not accessible and is meant for failover only.
Amazon RDS for MySQL with Multi-AZ and read replicas would improve availability, but using mysqldump for backup and restore would still cause delays and high latency, affecting the production environment.