Which set of actions should the solutions architect implement?
Create an Amazon Aurora DB cluster. Use AWS Database Migration Service (AWS DMS) to do a full load from the on-premises database to Aurora. Update the Route 53 entry for the database to point to the Aurora cluster endpoint, and shut down the on-premises database.
During nonbusiness hours, shut down the on-premises database and create a backup. Restore this backup to an Amazon Aurora DB cluster. When the restoration is complete, update the Route 53 entry for the database to point to the Aurora cluster endpoint, and shut down the on-premises database.
Create an Amazon Aurora DB cluster. Use AWS Database Migration Service (AWS DMS) to do a full load with continuous replication from the on-premises database to Aurora. When the migration is complete, update the Route 53 entry for the database to point to the Aurora cluster endpoint, and shut down the on- premises database.
Create a backup of the database and restore it to an Amazon Aurora multi-master cluster. This Aurora cluster will be in a master-master replication configuration with the on-premises database. Update the Route 53 entry for the database to point to the Aurora cluster endpoint, and shut down the on- premises database.
Explanations:
This option proposes a full load migration followed by updating the Route 53 entry and shutting down the on-premises database. However, it does not account for continuous replication, which could lead to data loss or downtime if any changes occur in the on-premises database after the full load and before the switch.
This approach involves shutting down the on-premises database, creating a backup, and restoring it to an Aurora cluster. This method causes downtime since the database is offline during the backup and restore process, and there’s a risk of data loss for any changes made during this period.
This option uses AWS DMS for a full load with continuous replication, allowing real-time data synchronization between the on-premises database and Aurora. This approach ensures that changes made during the migration process are captured, minimizing the risk of data loss and allowing for a seamless switch over to the Aurora database.
This option suggests creating a multi-master Aurora cluster with master-master replication, which is more complex and not necessary for the migration scenario described. It still requires the on-premises database to be operational during the setup, and the complexity may introduce additional points of failure. Furthermore, this approach does not adequately ensure that all data is replicated before switching, risking data inconsistency.
I categorize that the answer is:
Create an Amazon Aurora DB cluster. Use AWS Database Migration Service (AWS DMS) to do a full load with continuous replication from the on-premises database to Aurora. When the migration is complete, update the Route 53 entry for the database to point to the Aurora cluster endpoint, and shut down the on- premises database.
It appears that the answer is:
Create an Amazon Aurora DB cluster. Use AWS Database Migration Service (AWS DMS) to do a full load with continuous replication from the on-premises database to Aurora. When the migration is complete, update the Route 53 entry for the database to point to the Aurora cluster endpoint, and shut down the on- premises database.