Question

Difficulty: MediumAssess and Select Migration Strategy (7 Rs)

An enterprise is planning to migrate its inventory tracking system to AWS. The system consists of three main components:

1. Web Tier: A Java web application currently running on Apache Tomcat on VMware virtual machines (VMs). The enterprise wants to migrate it to AWS without modifying its code, but aims to eliminate the overhead of managing VMs and operating system patching.
2. Database: A Microsoft SQL Server database. The enterprise wants to migrate this database to Amazon Aurora PostgreSQL to eliminate licensing fees. They have allocated budget and time for schema conversion and application code adjustments.
3. Legacy File Archiver: A legacy tool running on a physical on-premises Windows server. It uses a node-locked license tied to the hardware MAC address of the physical server. The software vendor is out of business, so the license cannot be modified or reissued, and the tool remains business-critical.

Which combination of migration strategies represents the most appropriate alignment with the 7 Rs framework for these components?

  1. A
    Web Tier: Rehost; Database: Replatform; Legacy File Archiver: Retain
  2. B
    Web Tier: Refactor; Database: Refactor; Legacy File Archiver: Retain
  3. Web Tier: Replatform; Database: Refactor; Legacy File Archiver: RetainAnswer
  4. D
    Web Tier: Replatform; Database: Replatform; Legacy File Archiver: Retire

Answer

The correct strategy alignment is Replatform for the Web Tier, Refactor for the Database, and Retain for the Legacy File Archiver.
The correct option is the one specifying Replatform for the Web Tier, Refactor for the Database, and Retain for the Legacy File Archiver. Replatforming the Web Tier to a managed container service (like Amazon ECS on AWS Fargate) or AWS Elastic Beanstalk allows the enterprise to run the Java web application without code changes while eliminating VM and OS management. Migrating a Microsoft SQL Server database to Amazon Aurora PostgreSQL (a heterogeneous database migration) involves schema conversion and application code changes, which corresponds to the Refactor strategy. The Legacy File Archiver cannot be migrated because of physical hardware MAC address node-locking and the vendor being out of business, meaning it must be Retained on-premises.

Step-by-Step Solution

1
Analyze the migration requirements for the Web Tier.
The web application must be migrated without code changes, but the enterprise wants to eliminate VM administration and OS patching. This corresponds to the Replatform strategy, where the application is moved to a managed service like AWS Elastic Beanstalk or Amazon ECS on AWS Fargate.
Replatforming changes the runtime environment to a managed service to reduce operational overhead without modifying the core application code.
2
Analyze the migration requirements for the Database.
The target is to move from Microsoft SQL Server to Amazon Aurora PostgreSQL. Because the source and target database engines are different, this is a heterogeneous migration requiring schema translation (e.g., using AWS SCT) and application SQL query modifications.
A heterogeneous database engine change involves rewriting schema and code components, which classifies it under the Refactor (or Re-architect) strategy rather than a simple Replatform.
3
Analyze the migration requirements for the Legacy File Archiver.
The archiver uses a hardware-locked license tied to the MAC address of a physical server, and the vendor is out of business. Because it cannot be run on AWS and is still needed by the business, it cannot be migrated or retired.
Workloads that cannot be migrated due to hard licensing constraints or physical dependencies must be kept on-premises, which represents the Retain strategy.

Key Concept

Selecting migration strategies using the 7 Rs framework based on organizational and technical constraints.
Estimated Time:1m 30s
Rate this question