Question #1199
A company operates a monolithic application in an on-premises environment. The company plans to migrate the application to AWS without altering its architecture, dependencies, or codebase. Which migration strategy aligns with these requirements?
Repurchase
Replatform
Rehost
Refactor
Explanation
The Rehost (lift-and-shift) strategy is the best fit because the company explicitly stated they do not want to alter the application's architecture, dependencies, or codebase. Rehosting involves migrating the monolithic application to AWS infrastructure (e.g., EC2 instances) with minimal changes, ensuring compatibility and reducing migration complexity.
Other options are incorrect because:
- A. Repurchase: Involves switching to a different product (e.g., SaaS), which would require abandoning the existing application.
- B. Replatform: Requires minor optimizations (e.g., moving to managed services like RDS), which may involve dependency changes.
- D. Refactor: Involves re-architecting the application (e.g., breaking a monolith into microservices), which contradicts the requirement of no codebase changes.
Key Takeaway: Rehost is the go-to strategy for lift-and-shift migrations where no application modifications are allowed.
Answer
The correct answer is: C