AWS Migration Strategy for Monolithic to Microservices
A company is planning to migrate a monolithic application to AWS. The company wants to modernize the application by splitting it into microservices. The company will deploy the microservices on AWS. Which migration strategy should the company use?
Community Votes
100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The core concept tested is the definition of the 'Refactor' (Re-architect) strategy, with the common trap being confusion between minor platform adjustments and complete architectural redesigns.
This question examines the AWS Cloud migration strategies, specifically identifying when to use Refactoring versus other approaches like Rehosting or Replatforming. It establishes that splitting a monolith into microservices constitutes a fundamental architectural change.
Candidates often incorrectly choose 'Replatform' (Lift and Reshell), assuming that moving code to EC2 or containers counts as modernization, whereas true microservices decomposition requires refactoring.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The correct strategy is Refactor (also known as Re-architect). This strategy involves significantly changing the application's architecture to take full advantage of cloud-native features. Splitting a monolithic application into microservices is a classic example of refactoring because it alters the underlying structure to improve scalability, maintainability, and resilience.Why the Other Options Are Wrong
Rehost (Lift and Shift) involves moving the application to AWS with no changes, which contradicts the goal of modernization. Replatform (Lift, Tinker, and Shift) implies minor optimizations, such as switching to managed databases, but does not involve breaking apart the monolith. Repurchase means replacing the application with a new SaaS product, which is not the case here as the company is modifying their existing code.Community Comment Notes
The community consensus strongly supports D. As user Yomijohnson noted, "Refactoring... is the process of significantly modifying an application’s architecture." Another commenter, alokdixit2006, reinforced that this option is chosen because the application is being "modifying... to better support the cloud environment" through structural changes.Exam Strategy
Always look for keywords indicating architectural change. If the question mentions 'microservices', 'serverless', or 'cloud-native design patterns', the answer is almost always Refactor/Re-architect.
Frequently Asked Questions
Is Replatform ever used for microservices?
No. Replatform involves minimal changes (e.g., swapping DB engines). Microservices require significant architectural rework, which defines Refactoring.
What is the difference between Rehost and Refactor?
Rehost is 'lift and shift' with zero code changes. Refactor involves rewriting or restructuring code to leverage cloud-native capabilities.
Related Analysis
Practice All CLF-C02 Questions
Access 120 questions with complete answers and detailed explanations.
View Full CLF-C02 Practice Test →