Examkin

Question

Difficulty: HardAssess and Select Migration Strategy (7 Rs)

A financial services company is planning to migrate a three-tier customer portfolio management system to AWS. The project must be completed within 6 months due to datacenter decommissioning. An assessment of the application components reveals the following:

* Reporting Component: A legacy reporting system runs on a proprietary AIX environment. The source code is unavailable, and the vendor no longer supports the product. The historical reports must remain accessible for regulatory compliance, but there is no budget to migrate or rewrite this system. The company decides to keep this component running in the on-premises datacenter with a dedicated network connection to AWS.
* Web Dashboard: An administration dashboard runs on Apache Tomcat on Linux. The development team wants to avoid managing OS patching and scaling configurations. They plan to package the application as a Docker container and deploy it to AWS Fargate using Amazon Elastic Container Service (Amazon ECS) without modifying the application code.
* Core Processing Engine: A transaction processing application relies on an on-premises Oracle Database. To eliminate expensive software licensing fees and support a 10-fold increase in transactional volume, the team wants to migrate to a serverless architecture. They plan to rewrite the application code to use AWS Lambda and convert the relational schema to a NoSQL model using Amazon DynamoDB.

Which combination of migration strategies represents the most appropriate 7 Rs classification for each component?

  1. Retain the Reporting Component; Replatform the Web Dashboard; Refactor the Core Processing Engine.Answer
  2. B
    Retain the Reporting Component; Refactor the Web Dashboard; Replatform the Core Processing Engine.
  3. C
    Retire the Reporting Component; Replatform the Web Dashboard; Refactor the Core Processing Engine.
  4. D
    Retain the Reporting Component; Rehost the Web Dashboard; Replatform the Core Processing Engine.

Answer

Retain the Reporting Component; Replatform the Web Dashboard; Refactor the Core Processing Engine.
The Reporting Component is kept in the source environment, which represents Retain. The Web Dashboard is packaged into containers and moved to a managed platform (AWS Fargate) without changing its core application code, representing Replatform. The Core Processing Engine requires rewriting code for AWS Lambda and a complete schema conversion to Amazon DynamoDB, representing Refactor.

Step-by-Step Solution

1
Analyze the migration plan for the Reporting Component.
The component will remain on-premises due to OS constraints and lack of rewrite budget.
Keeping a system in its source environment is classified as Retain.
2
Analyze the migration plan for the Web Dashboard.
The dashboard will be containerized and run on AWS Fargate without changing application code.
Optimizing the runtime platform (moving to containers and Fargate) without code changes is classified as Replatform.
3
Analyze the migration plan for the Core Processing Engine.
The engine will be rewritten for AWS Lambda and its schema converted to DynamoDB.
Rewriting application code to use cloud-native services (Lambda, DynamoDB) is classified as Refactor/Re-architect.

Key Concept

Applying the AWS 7 Rs migration strategies (Retain, Replatform, Refactor) based on constraints like OS compatibility, licensing, and code modification capability.
Estimated Time:2m 30s
Rate this question

Topics

Assess and Select Migration Strategy (7 Rs)

More questions from this topic