Examkin

Question

Difficulty: HardAssess and Select Migration Strategy (7 Rs)

An enterprise is planning to migrate a business-critical inventory management and dispatch system to AWS. The system consists of three distinct application components:

1. Order Processing Core: A monolithic Java application running on Red Hat Enterprise Linux (RHEL). It relies on a proprietary local message queuing middleware. The business wants to break down this monolith into microservices, containerize it using AWS Fargate, and replace the proprietary middleware with Amazon Simple Queue Service (SQS) to improve scalability and eliminate licensing costs. The company has assigned a dedicated team with a 6-month timeline for this work.
2. Inventory Database: An Oracle Database 19c Enterprise Edition instance running on-premises, using advanced PL/SQL stored procedures. To avoid high migration risk and schema conversion complexity, the database engine must remain unchanged, but the business wants to eliminate hardware provisioning, backups, and OS patching overhead.
3. Legacy Shipping Label Generator: A legacy 32-bit application running on an old Windows Server 2008 R2 server. The source code is lost, and the software vendor is out of business, but the utility must be kept running as-is. It has no external dependencies. The enterprise plans to use AWS Application Migration Service (MGN) to copy the server block-by-block to an Amazon EC2 instance with minimal downtime and no software changes.

Which of the following migration strategies represent the correct alignment with the AWS 7 Rs framework for these components? (Select TWO)

  1. Classify the Order Processing Core migration as Refactor (Re-architect), because the application architecture is being modified to adopt microservices, containers, and cloud-native messaging services like Amazon SQS.Answer
  2. Classify the Inventory Database migration as Replatform (Re-platform), because it is moving to a managed service (Amazon RDS for Oracle) to optimize operational tasks without altering the underlying database engine or schema.Answer
  3. C
    Classify the Inventory Database migration as Refactor (Re-architect), because migrating to Amazon RDS for Oracle constitutes a Refactoring strategy due to the architectural changes in database high availability and automated backups.
  4. D
    Classify the Legacy Shipping Label Generator migration as Replatform (Re-platform), because utilizing AWS Application Migration Service (MGN) to migrate the virtual machine to Amazon EC2 is defined as a replatforming activity.
  5. E
    Classify the Order Processing Core migration as Replatform (Re-platform), because containerizing the application onto AWS Fargate and shifting to Amazon SQS represents a platform optimization that does not alter the core business logic.

Answer

The Order Processing Core should be migrated using the Refactor (Re-architect) strategy because it involves architectural changes to adopt microservices, containers, and Amazon SQS, and the Inventory Database should be migrated using the Replatform (Re-platform) strategy because it moves the workload to Amazon RDS for Oracle without changing the database engine or schema.
The migration of the Order Processing Core involves changing the application architecture from a monolith to microservices and replacing proprietary middleware with Amazon SQS, which is classified as a Refactor (Re-architect) strategy. The migration of the Inventory Database to Amazon RDS for Oracle moves the workload to a managed database service without changing the engine or code, which is classified as a Replatform strategy.

Step-by-Step Solution

1
Analyze the migration strategy for the Order Processing Core.
The core is being decomposed into microservices, containerized on ECS Fargate, and its middleware is being replaced with Amazon SQS.
This level of architectural and code change represents a Refactor (Re-architect) migration strategy because it shifts the system design toward cloud-native capabilities.
2
Analyze the migration strategy for the Inventory Database.
The database is moving to Amazon RDS for Oracle to offload administration without modifying the DB engine or schema.
Moving a database to a managed service with the same engine is a Replatform (Re-platform) strategy because the platform is optimized while keeping the application code/database interface intact.
3
Analyze the migration strategy for the Legacy Shipping Label Generator.
The server is being copied block-by-block to AWS EC2 using AWS MGN with no configuration or application changes.
This lift-and-shift pattern is a Rehost migration strategy because the server is migrated without any optimizations or architectural alterations.
4
Identify the correct options based on the analysis.
The options identifying the Order Processing Core as Refactor and the Inventory Database as Replatform are correct.
These options accurately match the 7 Rs definitions based on the requirements and constraints given.

Key Concept

Distinguishing between Rehost, Replatform, and Refactor (Re-architect) migration strategies within the AWS 7 Rs framework based on architecture modifications, managed service adoption, and code rewrite requirements.
Estimated Time:3m 0s
Rate this question

Topics

Assess and Select Migration Strategy (7 Rs)

More questions from this topic