Question

Difficulty: MediumAssess and Select Migration Strategy (7 Rs)

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 22 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 7 Rs7\text{ Rs} migration framework? (Select TWO.)

  1. Retain the legacy billing tool on-premises.Answer
  2. Replatform the SQL Server database by migrating it to Amazon RDS for SQL Server.Answer
  3. C
    Refactor the SQL Server database by migrating it to Amazon RDS for SQL Server.
  4. D
    Rehost the legacy billing tool by migrating it using AWS Application Migration Service (AWS MGN).
  5. E
    Refactor the Java web application by containerizing it for Amazon ECS on AWS Fargate.

Answer

Retaining the legacy billing tool on-premises and replatforming the SQL Server database to Amazon RDS for SQL Server are the correct strategies.
Retaining the legacy billing tool on-premises is correct because the hardware constraints prevent virtualization or cloud migration. Replatforming the database to Amazon RDS for SQL Server is correct because it adopts a managed service to optimize operations without modifying database engine features or code.

Step-by-Step Solution

1
Analyze the legacy billing tool's constraints.
Because of physical hardware integrations and compliance requirements, the tool cannot be virtualized or migrated. It must remain on-premises, mapping to a Retain strategy.
Identify the migration constraint for the mainframe tool.
2
Analyze the SQL Server database requirements.
Moving SQL Server to Amazon RDS for SQL Server reduces administration overhead without changing the engine or code, which represents Replatforming (lift-tinker-and-shift).
Determine the database migration strategy based on operational goals.
3
Analyze the Java web application requirements.
Containerizing the application for Amazon ECS on AWS Fargate without modifying application code maps to Replatforming, not Refactoring.
Determine the application tier migration strategy based on containerization without code changes.

Key Concept

AWS 7 Rs Migration Framework
Rate this question