Examkin

Question

Difficulty: HardAssess and Select Migration Strategy (7 Rs)

An enterprise is planning to migrate its core billing and reporting platform to AWS. The platform consists of three main components:

1. A legacy financial reporting application that runs on an on-premises IBM AIX server. The application is licensed via a CPU-ID node-lock mechanism and is scheduled to be decommissioned in 10 months when a new SaaS-based reporting service is launched.
2. A monolithic billing web application written in Java and running on Apache Tomcat on Windows Server 2016. To minimize operating system licensing costs and administrative overhead, the enterprise wants to run this workload on a managed container platform without altering the application's Java source code.
3. A Microsoft SQL Server database containing transactional billing data. The enterprise wants to migrate this database to Amazon Aurora PostgreSQL to avoid database licensing fees. Preliminary analysis with the AWS Schema Conversion Tool (SCT) indicates that all stored procedures must be rewritten to match PostgreSQL syntax. The migration must be completed within a maximum scheduled downtime window of 2 hours.

Which of the following migration paths represent the correct classifications for these components under the 7 Rs migration framework? (Select TWO.)

  1. Retain the legacy financial reporting application on-premises.Answer
  2. Replatform the billing web application by containerizing it to run on Amazon ECS with AWS Fargate.Answer
  3. C
    Replatform the transactional database by migrating Microsoft SQL Server to Amazon Aurora PostgreSQL.
  4. D
    Rehost the legacy financial reporting application on Amazon EC2 Dedicated Hosts.
  5. E
    Refactor the billing web application by rewriting its functionality as AWS Lambda functions.

Answer

The correct strategies are to retain the legacy financial reporting application on-premises and to replatform the billing web application by containerizing it to run on Amazon ECS with AWS Fargate.
Retaining the legacy financial reporting application on-premises is correct because the system is on IBM AIX (which cannot be easily rehosted on EC2) and is being decommissioned in 10 months, making a migration project wasteful. Replatforming the billing web application by containerizing it for Amazon ECS with AWS Fargate is correct because it avoids Windows OS licensing fees and reduces administration through Fargate without requiring Java code modifications.

Step-by-Step Solution

1
Assess the legacy financial reporting application against migration constraints.
Since the application runs on IBM AIX (which is not natively supported on EC2), is locked to CPU-ID licensing, and is scheduled to be retired in 10 months, migrating it is unviable.
This establishes that the correct migration strategy is to Retain the workload on-premises to avoid wasted migration effort.
2
Assess the billing web application against the architectural goals.
The application needs to run on a managed container service to minimize overhead and OS licensing costs, without modifying the source code. Moving from Tomcat/Windows to Tomcat/Linux containers on ECS/Fargate fits this description.
This qualifies as a Replatform strategy, optimizing the environment without modifying core code.
3
Assess the transactional database migration path.
The target engine is Aurora PostgreSQL, which differs from the source SQL Server database and requires stored procedure rewrites.
A database engine migration requiring database-level code and schema modifications is a Refactor strategy, which excludes the option that classifies it as Replatform.

Key Concept

Selecting the correct migration strategy (7 Rs) by aligning application constraints, operating system compatibility, licensing, and retirement timelines with migration costs and effort.
Rate this question

Topics

Assess and Select Migration Strategy (7 Rs)

More questions from this topic