Question

Difficulty: MediumUnderstand the benefits of and strategies for migration to the AWS Cloud

Aegis Health is migrating its patient scheduling database to AWS. The database currently runs on an on-premises Microsoft SQL Server. The IT team wants to reduce database administration overhead, such as patching and backups, but does not want to change the database schema or write new application code. Which migration strategy should Aegis Health select to meet these requirements?

  1. ReplatformingAnswer
  2. B
    Rehosting
  3. C
    Refactoring
  4. D
    Retaining

Answer

Replatforming
Replatforming (sometimes called lift-tinker-and-shift) is correct because it involves making minor optimizations to achieve tangible benefits—such as migrating an on-premises database to a managed database service like Amazon RDS—without altering the core application architecture or changing the database schema.

Step-by-Step Solution

1
Analyze the business and technical constraints of the migration scenario.
The target workload is an on-premises Microsoft SQL Server database. The goal is to migrate to AWS, reduce administrative tasks (patching/backups), and avoid code or schema changes.
Understanding these constraints is necessary to differentiate between simple migration (Rehosting), managed platform optimization (Replatforming), and deep architectural changes (Refactoring).
2
Evaluate which migration strategy aligns with shifting to a managed service without code modifications.
Moving an on-premises database to a managed database service like Amazon RDS without modifying the application code is a classic example of Replatforming.
This strategy allows the organization to optimize the platform (leveraging AWS automation for backups and patching) while leaving the core application architecture untouched.

Key Concept

Identifying AWS migration strategies (the 6 Rs), specifically distinguishing Replatforming from Rehosting and Refactoring.
Rate this question