Which of the following will meet the requirements?
Use AWS SCT to generate the schema scripts and apply them on the target prior to migration. Use AWS DMS to analyze the current schema and provide a recommendation for the optimal database engine. Then, use AWS DMS to migrate to the recommended engine. Use AWS SCT to identify what embedded SQL code in the application can be converted and what has to be done manually.
Use AWS SCT to generate the schema scripts and apply them on the target prior to migration. Use AWS DMS to begin moving data from the on-premises database to AWS. After the initial copy, continue to use AWS DMS to keep the databases in sync until cutting over to the new database. Use AWS SCT to identify what embedded SQL code in the application can be converted and what has to be done manually.
Use AWS DMS to help identify the best target deployment between installing the database engine on Amazon EC2 directly or moving to Amazon RDS. Then, use AWS DMS to migrate to the platform. Use AWS Application Discovery Service to identify what embedded SQL code in the application can be converted and what has to be done manually.
Use AWS DMS to begin moving data from the on-premises database to AWS. After the initial copy, continue to use AWS DMS to keep the databases in sync until cutting over to the new database. Use AWS Application Discovery Service to identify what embedded SQL code in the application can be converted and what has to be done manually.
Explanations:
While AWS SCT (Schema Conversion Tool) can generate schema scripts and help convert embedded SQL code, AWS DMS (Database Migration Service) is primarily for data migration and does not provide recommendations for the optimal database engine. Additionally, DMS is not intended for initial schema analysis, making this option inadequate for minimizing downtime.
This option effectively uses AWS SCT to generate and apply schema scripts before migration. It also employs AWS DMS for an initial data copy and ongoing synchronization, ensuring minimal downtime during the switch. It includes the use of AWS SCT for identifying SQL code conversion needs, making it a comprehensive and effective migration strategy.
This option suggests using AWS DMS to identify the best deployment between EC2 and RDS, but DMS does not analyze deployment architectures. It incorrectly implies that DMS can determine the best target deployment. Furthermore, it does not utilize AWS SCT appropriately for schema migration, making it less effective for the given requirements.
While this option starts with moving data using AWS DMS and keeping it in sync, it incorrectly suggests using AWS Application Discovery Service, which is not intended for identifying embedded SQL code conversion. This misapplication of services does not align with the goal of minimizing work and time required for migration.
I assess that the answer is:
Use AWS SCT to generate the schema scripts and apply them on the target prior to migration. Use AWS DMS to begin moving data from the on-premises database to AWS. After the initial copy, continue to use AWS DMS to keep the databases in sync until cutting over to the new database. Use AWS SCT to identify what embedded SQL code in the application can be converted and what has to be done manually.