Question

Difficulty: MediumAssess and Select Migration Strategy (7 Rs)

A financial services organization is planning to migrate its loan processing system to AWS. The system is composed of three main components:

* A transaction database running on Oracle Database on-premises. To reduce licensing costs, the organization wants to migrate this database to Amazon Aurora PostgreSQL, which will require converting schemas and rewriting database stored procedures.
* A web portal running on JBoss EAP on physical servers. The organization wants to package the portal into a container image and run it on Amazon ECS using AWS Fargate to reduce operational overhead, without making any modifications to the application code.
* A legacy document archival tool that integrates with a physical on-premises Hardware Security Module (HSM) appliance. Due to compliance and physical hardware dependencies, this tool must remain in the on-premises data center and communicate with AWS via AWS Direct Connect.

Which of the following identifies the most appropriate migration strategies for these three components?

  1. Refactor the database, replatform the web portal, and retain the archival tool.Answer
  2. B
    Replatform the database, rehost the web portal, and retain the archival tool.
  3. C
    Refactor the database, refactor the web portal, and relocate the archival tool.
  4. D
    Replatform the database, replatform the web portal, and retire the archival tool.

Answer

Refactor the database, replatform the web portal, and retain the archival tool.
The correct option correctly identifies the migration paths: migrating from Oracle to Aurora PostgreSQL requires schema conversion and rewrite of database code, which is Refactoring. Containerizing the Java portal to run on Amazon ECS/Fargate without code modifications is Replatforming. Keeping the archival tool on-premises due to physical HSM dependencies is Retaining.

Step-by-Step Solution

1
Analyze the database migration requirements.
Migrating from Oracle to Amazon Aurora PostgreSQL requires schema translation and stored procedure rewriting.
Changing the core engine and modifying schemas or code is classified as a Refactor (or Re-architect) migration strategy.
2
Analyze the web portal migration requirements.
Packaging the Java-based portal into a container to run on Amazon ECS on AWS Fargate without changing the application code.
Deploying an existing application to a managed platform or container runtime without altering core application architecture is classified as a Replatform strategy.
3
Analyze the legacy archival tool requirements.
The tool cannot be migrated due to hardware dependency on a physical on-premises HSM and must continue running on-premises.
Keeping a workload in its source environment due to migration barriers or lack of business case for moving is classified as a Retain strategy.

Key Concept

Selecting the correct AWS migration strategy (7 Rs) based on architectural constraints, application changes, and hardware dependencies.
Rate this question