Question

Difficulty: Very hardUnderstand the benefits of and strategies for migration to the AWS Cloud

A global maritime cargo shipping firm is evaluating its application portfolio for migration to the AWS Cloud. During the analysis, the migration team identifies two specific workloads:

1. A bespoke legacy port operations scheduler running on an outdated, highly customized IBM AIX Unix operating system that cannot be virtualized in standard x86 environments. The firm plans to keep this scheduler operational on-premises for the next two years.
2. A monolithic core logistics dispatch system. The team plans to migrate the application server as-is, but will migrate its underlying commercial relational database to Amazon Aurora PostgreSQL to reduce licensing costs and management overhead, without modifying the application's core code.

Which two of the following migration strategies represent the correct approach for these workloads?

  1. Retaining for the port operations scheduler, as it will remain on-premises due to platform incompatibility and business requirements.Answer
  2. Replatforming for the logistics dispatch system, as the database is moved to a managed database service (Amazon Aurora) to optimize operations and reduce licensing costs without modifying the core application code.Answer
  3. C
    Rehosting for the logistics dispatch system, as the application and its database are migrated to AWS without any modifications to their configuration or platform components.
  4. D
    Refactoring for the logistics dispatch system, as changing the underlying database engine to Amazon Aurora requires a complete rewrite of the application's architecture to be cloud-native.
  5. E
    Repurchasing for the port operations scheduler, as the unsupported Unix system must be retired and replaced with a modern commercial off-the-shelf software product.

Answer

The correct strategies are Retaining for the port operations scheduler and Replatforming for the logistics dispatch system.
The correct strategies are Retaining and Replatforming. Retaining is appropriate for the port operations scheduler because it runs on unsupported hardware (IBM AIX Unix on non-x86 architecture) and the business has chosen to keep it on-premises. Replatforming is appropriate for the logistics dispatch system because it involves moving the application to the cloud with minor optimizations—specifically, moving the database to a managed service (Amazon Aurora) to save licensing costs—without modifying the core application code.

Step-by-Step Solution

1
Analyze the migration constraints for the port operations scheduler.
The scheduler runs on an outdated, highly customized Unix OS (IBM AIX) that cannot be virtualized on standard x86 cloud environments, and the business plans to keep it operational on-premises.
This identifies that the workload cannot currently move to the cloud without substantial effort, and keeping it on-premises matches the definition of Retaining.
2
Analyze the migration goals and constraints for the logistics dispatch system.
The application server will be migrated as-is, but the database will be changed to a managed service (Amazon Aurora) to optimize costs without changes to the core application code.
Making minimal adjustments (tinkering) to leverage cloud benefits (like migrating to a managed database) without changing the core application architecture defines Replatforming.
3
Match the analyzed strategies to the options.
The option stating Retaining is correct for the scheduler, and the option stating Replatforming is correct for the dispatch system are identified as the correct selections.
This confirms the alignment of the business scenarios with the standard AWS Cloud Adoption Framework (CAF) 6 Rs migration strategies.

Key Concept

Identifying and applying the AWS 6 Rs migration strategies based on technical requirements, operating system dependencies, and business constraints.
Rate this question