AWS Migration Strategy for Unchanged Legacy Workloads
A company runs a legacy workload in an on-premises data center. The company wants to migrate the workload to AWS. The company does not want to make any changes to the workload. Which migration strategy should the company use?
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests knowledge of the 6 Rs of migration; the trap is assuming 'Replatform' allows zero changes, whereas only 'Rehost' strictly prohibits application code or architecture adjustments.
This page explains the AWS cloud migration strategies, specifically identifying Rehost as the correct approach when no workload modifications are permitted. It clarifies why options like Refactor and Replatform are incorrect in this context.
Learners often confuse Replatform with Rehost, thinking that minor infrastructure tweaks (like switching DB engines) constitute a 'change' to the workload itself, leading them to reject Rehost incorrectly.
Community Discussion (4 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Rehosting, commonly known as 'lift and shift,' involves moving an existing on-premises application to AWS without any modification to the application code or architecture. Since the requirement explicitly states that the company does not want to make any changes to the workload, Rehosting is the only strategy that fits this constraint perfectly. This method typically uses services like AWS Application Migration Service or EC2 to replicate the environment.Why the Other Options Are Wrong
Refactoring (or Re-architecting) requires rewriting and re-optimizing code for cloud-native features, which directly violates the 'no changes' rule. Replatforming involves making minor changes to leverage cloud capabilities, such as changing a database engine from Oracle to Amazon RDS, which constitutes a change. Repurchasing involves buying a different product (like SaaS), which is not migrating the existing legacy workload.Community Comment Notes
The community consensus strongly supports option C. As user alokdixit2006 noted, "Rehosting (lift and shift) is the process of migrating your on-premises application to the cloud without modifying it." Another user, Yomijohnson, emphasized that this strategy is suitable when "the company does not want to modify the workload but needs to move it to the cloud." The votes were unanimous, reflecting clear understanding of the definition.Exam Strategy
Always look for keywords like 'no changes', 'without modification', or 'lift and shift' to identify Rehosting. If the question mentions optimizing for performance or using managed services, consider Replatforming or Refactoring instead.
Frequently Asked Questions
What is the difference between Rehost and Replatform?
Rehost moves the app as-is ('lift and shift'), while Replatform makes minor changes to use cloud-native features like managed databases.
When should I choose Refactoring over Rehosting?
Choose Refactoring when you need to fully leverage cloud benefits like scalability and cost-efficiency by rewriting the application code.
Related Analysis
Practice All CLF-C02 Questions
Access 120 questions with complete answers and detailed explanations.
View Full CLF-C02 Practice Test →