A municipal energy utility provider plans to migrate its legacy customer billing portal to AWS. The portal consists of a Java-based application running on local servers and an on-premises Microsoft SQL Server database. The provider wants to eliminate the administrative burden of patching operating systems, managing database backups, and provisioning hardware, but has strict constraints that prohibit any modifications to the application's core codebase or SQL query structures.
To achieve this, the migration team decides to deploy the Java application code onto AWS Elastic Beanstalk and migrate the database to Amazon RDS for SQL Server.
Which migration strategy is this provider employing?
- ARehosting
- ReplatformingAnswer
- CRefactoring
- DRepurchasing
Answer
The correct strategy is replatforming, as the company is adopting managed cloud platforms to reduce operational overhead without modifying the core application code.
The correct answer is replatforming. Replatforming (often referred to as 'lift-tinker-and-shift') involves moving applications to the cloud while making minor optimizations to take advantage of cloud benefits—such as adopting managed database services (Amazon RDS) or platform-as-a-service solutions (AWS Elastic Beanstalk) to reduce operational overhead—without changing the core application architecture or code. This aligns perfectly with the provider's goal to eliminate administrative tasks like patching and backups while keeping the codebase intact.
Step-by-Step Solution
Key Concept
Identifying AWS Migration Strategies (6 Rs)
Estimated Time:1m 30s