Examkin

Question

Difficulty: HardAssess and Select Migration Strategy (7 Rs)

An enterprise is planning to migrate a three-tier customer portal to AWS as part of a datacenter exit project that must be completed within a strict 6-month window. The architecture and business requirements are as follows:

* Presentation Layer: A stateless Java application running on Apache Tomcat. The operations team wants to eliminate operating system patching and VM management overhead without modifying the application code.
* Database Layer: A Microsoft SQL Server database with high licensing costs. The enterprise wants to migrate to Amazon Aurora PostgreSQL. A preliminary assessment shows that converting the database schema and rewriting complex T-SQL stored procedures will take at least 9 months. The migration must limit the database downtime window to less than 2 hours during the final cutover.
* Reporting Tier: A legacy third-party reporting tool running on Solaris that cannot be virtualized on x86-64 hardware, but must remain available for regulatory compliance audits for another year.

Which combination of migration strategies is the most appropriate to meet the timeline, satisfy the technical constraints, and align with the 7 Rs framework?

  1. A
    Presentation Layer: Replatform to Amazon ECS on AWS Fargate.
    Database Layer: Replatform to Amazon Aurora PostgreSQL using AWS Schema Conversion Tool (AWS SCT) and AWS Database Migration Service (AWS DMS) within the 6-month window.
    Reporting Tier: Retain the legacy tool on-premises or in a co-location facility.
  2. B
    Presentation Layer: Rehost on Amazon EC2 instances.
    Database Layer: Refactor to Amazon Aurora PostgreSQL immediately using AWS Schema Conversion Tool (AWS SCT) to eliminate license costs.
    Reporting Tier: Rehost the legacy tool on Amazon EC2 instances.
  3. Presentation Layer: Replatform to Amazon ECS on AWS Fargate.
    Database Layer: Replatform to Amazon RDS for SQL Server, deferring the Refactor to Amazon Aurora PostgreSQL to a post-migration phase.
    Reporting Tier: Retain the legacy tool on-premises or in a co-location facility.    Answer
  4. D
    Presentation Layer: Replatform to Amazon ECS on AWS Fargate.
    Database Layer: Replatform to Amazon RDS for SQL Server, deferring the Refactor to Amazon Aurora PostgreSQL.
    Reporting Tier: Replatform the legacy tool to Amazon RDS.

Answer

Presentation Layer: Replatform to Amazon ECS on AWS Fargate. Database Layer: Replatform to Amazon RDS for SQL Server, deferring the Refactor to Amazon Aurora PostgreSQL to a post-migration phase. Reporting Tier: Retain the legacy tool on-premises or in a co-location facility.
Replatforming the presentation layer to Amazon ECS on AWS Fargate satisfies the requirement to eliminate operating system patching and VM management overhead without changing application code. For the database layer, moving from Microsoft SQL Server to Amazon Aurora PostgreSQL is a heterogeneous database migration, which is classified as Refactoring (Re-architecting). Since this refactoring effort is estimated to take 9 months, it cannot be completed within the 6-month migration window. Replatforming the database to Amazon RDS for SQL Server allows the enterprise to meet the 6-month timeline, while deferring the Refactoring phase to a later time. The legacy reporting tool runs on Solaris and cannot be virtualized on standard x86-64 cloud hardware, making Retain the correct strategy.

Step-by-Step Solution

1
Analyze the database migration requirements and timeline constraints.
Identify that moving from Microsoft SQL Server to Amazon Aurora PostgreSQL is a heterogeneous database migration, which represents a Refactoring (Re-architecting) strategy. Since it takes 9 months, it cannot fit into the 6-month datacenter exit window. Therefore, the database must be Replatformed to Amazon RDS for SQL Server initially, deferring the Refactor phase.
To ensure the migration meets the strict datacenter exit timeline.
2
Evaluate the presentation layer operational and code requirements.
Determine that the presentation layer can be containerized and run on Amazon ECS on AWS Fargate. This aligns with the Replatforming strategy.
Fargate removes the server management and OS patching overhead without requiring application code changes.
3
Assess the compatibility of the legacy reporting tool.
Determine that the tool runs on Solaris and has no x86-64 equivalent, meaning it cannot be hosted directly on standard Amazon EC2 instances. Thus, it must be Retained on-premises or in a co-location facility.
To keep the historical compliance data accessible without unsupported platform emulation.

Key Concept

Distinguishing between Replatforming and Refactoring within the 7 Rs framework under strict timeline and platform compatibility constraints.
Rate this question

Topics

Assess and Select Migration Strategy (7 Rs)

More questions from this topic