An enterprise is planning to migrate a three-tier application to AWS. A solutions architect has compiled the following inventory and migration requirements:
1. A legacy billing tool runs on an old on-premises mainframe system. Due to complex physical hardware integrations, this system cannot be virtualized or migrated to the cloud, but the business must continue using it for compliance reporting for the next years.
2. The main application database runs on an on-premises Microsoft SQL Server. The enterprise wants to reduce database administration overhead, such as patching and backups, but does not want to convert the schema or rewrite any application SQL code. They plan to move this database to Amazon RDS for SQL Server.
3. The web application tier consists of a Java application running on Apache Tomcat. The development team wants to package this application into Docker containers and run it on Amazon ECS on AWS Fargate to simplify scaling and infrastructure management, without modifying the application code.
Which of the following migration strategies represent the correct mappings for these components under the AWS migration framework? (Select TWO.)
- Retain the legacy billing tool on-premises.Cevap
- Replatform the SQL Server database by migrating it to Amazon RDS for SQL Server.Cevap
- CRefactor the SQL Server database by migrating it to Amazon RDS for SQL Server.
- DRehost the legacy billing tool by migrating it using AWS Application Migration Service (AWS MGN).
- ERefactor the Java web application by containerizing it for Amazon ECS on AWS Fargate.