CompTIA Cloud Essentials+ (CLO-002)Business Principles of Cloud EnvironmentsHard
A company is planning to move its monolithic, on-premises enterprise resource planning (ERP) system to a public cloud. The system is highly customized and tightly integrated with several other internal applications. The company wants to leverage cloud-native features and improve agility in the long term, even if it requires significant initial effort. Which migration approach is BEST suited for this scenario?
- ARehosting (Lift-and-Shift)
- BRefactoring (Re-architecting)
- CReplatforming (Lift-and-Reshape)
- DRetire
Show answer & explanationAnswer & explanation
Correct answer: B. Refactoring (Re-architecting)
Refactoring (Re-architecting) involves fundamentally altering the application's code and architecture to take full advantage of cloud-native capabilities. While complex and time-consuming, it provides the most significant long-term benefits in terms of agility, scalability, and cost optimization for highly customized and integrated legacy systems.
Why the other options are wrong
- A. Rehosting would move the monolithic system as-is, failing to leverage cloud-native features or improve agility.
- C. Replatforming makes some optimizations but doesn't fundamentally change the architecture to fully exploit cloud benefits for a highly customized system.
- D. Retiring the application means decommissioning it, which is not a migration approach for an essential ERP system.
Refactoring (Re-architecting)
Modifying an application's code and architecture to be cloud-native, leveraging cloud services for optimal performance, scalability, and agility.
- Highest effort and cost initially.
- Provides maximum long-term benefits of cloud computing.
- Often involves breaking down monoliths into microservices.
Memory trick: Rehost for speed, Refactor for future.