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?
- ReplatformingAnswer
- BRehosting
- CRefactoring
- DRetaining
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
Key Concept
Identifying AWS migration strategies (the 6 Rs), specifically distinguishing Replatforming from Rehosting and Refactoring.