Examkin

Question

Difficulty: HardAssess and Select Migration Strategy (7 Rs)

An enterprise is planning to migrate its on-premises customer management and billing systems to AWS. A solutions architect has completed the application discovery phase and identified the following workload components:

* Core Billing Database: A legacy Oracle Database. The business wants to migrate this database to Amazon Aurora PostgreSQL to eliminate licensing fees and leverage cloud-native database features. This migration will require a complete schema rewrite and application-level SQL query changes.
* Web Frontend: A legacy Java application running on Apache Tomcat. The development team wants to avoid managing operating systems and virtual machine patching. They plan to package the existing application into a Docker container and host it on a managed container orchestration platform.
* Legacy Inventory System: A legacy client-server desktop application that relies on a specialized physical USB license key (hardware dongle) plugged directly into the physical host. The vendor is out of business, and the software cannot be virtualized or run without the physical dongle.

Which combination of migration strategies should the solutions architect recommend for these systems? (Select THREE.)

  1. Refactor the Core Billing Database by converting the Oracle schema and rewriting application-level SQL queries to migrate to Amazon Aurora PostgreSQL.Answer
  2. Replatform the Web Frontend by packaging the Java application into a Docker container and deploying it to Amazon ECS with AWS Fargate.Answer
  3. Retain the Legacy Inventory System on-premises because of the physical hardware dongle dependency.Answer
  4. D
    Replatform the Core Billing Database by performing a direct lift-and-shift of the Oracle schema to Amazon Aurora PostgreSQL without application changes.
  5. E
    Rehost the Web Frontend by using AWS Application Migration Service (MGN) to deploy the VM directly into Amazon ECS tasks.
  6. F
    Retire the Legacy Inventory System by decommissioning the application on-premises and hosting the client-server logic on AWS Lambda.

Answer

The correct migration strategies are: Refactoring the Core Billing Database (converting Oracle to Aurora PostgreSQL), Replatforming the Web Frontend (containerizing Tomcat to ECS/Fargate), and Retaining the Legacy Inventory System on-premises due to the hardware dongle dependency.
The correct strategies are Refactoring the database tier, Replatforming the web tier, and Retaining the inventory tier. Migrating from Oracle to Amazon Aurora PostgreSQL is a heterogeneous database migration that requires schema conversion and query changes, which is classified as Refactoring (or Re-architecting). Containerizing the Java application on Tomcat to run on Amazon ECS with AWS Fargate changes the platform configuration without altering the application code, which represents Replatforming. The inventory system has a hard dependency on a physical USB hardware dongle plugged into the host, making it impossible to virtualize or host in the cloud; therefore, this system must be Retained on-premises.

Step-by-Step Solution

1
Analyze the migration requirements for the Core Billing Database.
Identified a heterogeneous migration from Oracle to Amazon Aurora PostgreSQL requiring schema conversion and code modifications.
Determining whether a migration involves changing the database engine is critical, as engine changes require schema conversions (Refactoring/Re-architecting) rather than a simple platform optimization (Replatforming) or block-level copy (Rehosting).
2
Analyze the migration requirements for the Web Frontend.
Identified a shift from VM-based Tomcat to containerized ECS/Fargate without modifying the core application code.
Transitioning to a managed container service without application code modifications aligns with the Replatforming strategy (also known as lift-tinker-and-shift).
3
Analyze the constraints of the Legacy Inventory System.
Identified a hard dependency on a physical USB hardware dongle that cannot be virtualized or migrated to the cloud.
Applications that rely on physical hardware keys, unsupported legacy OS versions, or proprietary hardware that cannot be virtualized must be Retained on-premises.

Key Concept

Selecting the appropriate migration strategy from the 7 Rs framework based on workload constraints, database engine compatibility, containerization goals, and physical hardware dependencies.
Rate this question

Topics

Assess and Select Migration Strategy (7 Rs)

More questions from this topic