Examkin

Question

Difficulty: HardAssess and Select Migration Strategy (7 Rs)

An enterprise is planning to migrate a legacy three-tier customer service application to AWS within a strict 3-month timeline. The application components and constraints are as follows:

* Presentation Tier: ASP.NET web application hosted on IIS on Windows Server 2012 R2. The company wants to minimize operating system licensing costs and administrative overhead by using containers, but the development team has no capacity to rewrite or modify the application code.
* Licensing Tier: A proprietary Windows service that requires a physical USB licensing dongle connected directly to the server. This service is scheduled to be retired in 12 months.
* Database Tier: A 2-TB2\text{-TB} Oracle Database Enterprise Edition. The business wants to migrate to Amazon Aurora PostgreSQL to eliminate licensing costs. The database contains over 150 PL/SQL packages and stored procedures that the application calls directly. The maximum allowed cutover downtime is 2 hours.

Which of the following migration strategies represent the most optimal alignment to the 7 Rs model for these tiers? (Select TWO.)

  1. Refactor the database tier by using the AWS Schema Conversion Tool (AWS SCT) and AWS Database Migration Service (AWS DMS) to migrate the Oracle database to Amazon Aurora PostgreSQL.Answer
  2. Retain the licensing tier on-premises to support the hardware dependency until the service is decommissioned.Answer
  3. C
    Replatform the database tier by using AWS Database Migration Service (AWS DMS) to perform a direct migration to Amazon Aurora PostgreSQL without modifying application-level calls.
  4. D
    Rehost the licensing tier to Amazon EC2 Dedicated Hosts to maintain compliance with the hardware dongle requirement.
  5. E
    Refactor the presentation tier by rewriting the ASP.NET application to run on AWS Lambda to minimize administrative overhead.

Answer

The correct strategies are to refactor the database tier by using the AWS Schema Conversion Tool and AWS DMS to migrate the Oracle database to Aurora PostgreSQL, and to retain the licensing tier on-premises due to physical hardware dependencies.
The database migration from Oracle to Aurora PostgreSQL is heterogeneous and requires extensive schema and application code adjustments to convert PL/SQL stored procedures, which represents a Refactoring strategy. The licensing service's dependency on a physical USB hardware dongle cannot be accommodated in AWS, and since it will be decommissioned within 12 months, retaining it on-premises is the most efficient and compliant strategy.

Step-by-Step Solution

1
Analyze the Presentation Tier constraints.
The legacy ASP.NET application needs containerization to minimize licensing/overhead, but has zero code modification capacity. This suggests a Replatform strategy (e.g., using AWS App2Container to run on ECS) rather than Refactoring.
Refactoring requires code changes, which violates the developer constraint.
2
Analyze the Licensing Tier constraints.
The licensing service requires a physical USB hardware dongle and will be decommissioned in 12 months. AWS does not support physical hardware dongle attachments.
Keeping the component on-premises (Retain) is the only viable path that respects the physical dependency and avoids wasted migration effort for a system nearing retirement.
3
Analyze the Database Tier constraints.
Migrating from Oracle to Aurora PostgreSQL is a heterogeneous database migration that requires converting 150+ PL/SQL packages/procedures and changing client code.
A database engine change requiring schema and application modifications constitutes a Refactoring migration path, not Replatforming.

Key Concept

Selecting the correct migration strategies (7 Rs) based on code modification limits, database schema conversion requirements, and hardware dependencies.
Estimated Time:3m 0s
Rate this question

Topics

Assess and Select Migration Strategy (7 Rs)

More questions from this topic