Correct D. You cannot convert RDS MySQL to Aurora MySQL natively, but you can create an Aurora read replica of the RDS MySQL DB instance and then promote it to a standalone Aurora MySQL DB clusterhttps://aws.amazon.com/getting-started/hands-on/migrate-rdsmysql-to-auroramysql/https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.RDSMySQL.html. This is the first step of option A in the question. However, this option also requires pausing application writes and reconfiguring the application, which can cause downtime and data inconsistency. Therefore, option A is not the best solution for the given requirements. Option D is still the correct answer because it does not require pausing writes or reconfiguring the application, and it enables cross-Region replication and write forwarding for the database.

A for me

This approach leverages Amazon Aurora's Global Database capability, which allows for a single database to span multiple AWS regions, thus enabling low-latency reads and writes in multiple regions and providing data replication across regions with minimal latency. By converting the RDS for MySQL DB instance to an Amazon Aurora MySQL DB cluster and enabling write forwarding, the solution supports writes in multiple regions and ensures that the data is synchronized across the regions in real time. This setup allows customers in both the US and Europe to see updates from each other as they happen, meeting the requirement for real-time data consistency and low application latency.

Galera + ProxySQL ftw

D said 'Convert' but not 'Mirgrate'. You cannot convert RDS MySQL to Aurora MySQL natively.

D CORRECT D. Aurora Global Database with Write Forwarding: This solution addresses all requirements: Real-time data access and updates: Aurora provides global secondary databases in the chosen region (eu-west-1) for low latency and consistent data. Minimal downtime: Aurora automatically handles failovers and data synchronization between regions. Write forwarding: Both regions can perform write operations, ensuring real-time updates for all users. High availability: Aurora offers automatic backups and failover capabilities. Therefore, D. Converting the RDS for MySQL DB instance to an Amazon Aurora MySQL DB cluster with a secondary Region in eu-west-1 and enabling write forwarding is the most suitable solution. It meets all requirements for data availability, minimal latency, real-time updates, and high availability for both US and European customers.

Option A

yes, migration is done through the replica promotion

RDS MySQL to aurora replica, then promote the replica as aurora cluster.

You cannot natively convert the RDS for MySQL DB instance to an Amazon Aurora MySQL DB cluster. Instead, you can create an Amazon Aurora MySQL replica of the RDS MySQL RDS DB instance: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.RDSMySQL.Replica.html https://aws.amazon.com/getting-started/hands-on/migrate-rdsmysql-to-auroramysql/

A is ans:

Write forwarding is a feature of Aurora that allows writes to be directed to the primary cluster while maintaining read access to the replica cluster, ensuring data consistency and low latency.

It's clearly A , not any other option

A, ‘cause of the conversion which is not possible

The reason you create an Amazon Aurora MySQL Replica is because "replication lag between source DB instance and Aurora Read Replica approaches zero" , and here are the steps recommended and isntructed as part of an AWS Workshop https://aws.amazon.com/getting-started/hands-on/migrate-rdsmysql-to-auroramysql/#:~:text=2.1%20-%20Open%20the%20Amazon%20RDS,choose%20Create%20Aurora%20read%20replica.

Answer A

A - https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.RDSMySQL.Replica.html