Migrating Self-Managed MySQL to AWS Managed Service
A company runs MySQL database workloads on self-managed servers in an on-premises data center. The company wants to migrate the database workloads to an AWS managed service. 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 question tests the distinction between Rehost and Replatform, with the common trap being the assumption that any move to AWS is simply 'lifting' the server without modification.
This question evaluates the correct AWS migration strategy for moving a self-managed on-premises database to a managed cloud service. It establishes that Replatform is the appropriate choice when leveraging managed services without changing the application's core architecture.
Candidates often choose Rehost (A) because they view it as the simplest 'lift-and-shift' method, failing to recognize that switching to a fully managed service like RDS constitutes a 'tweak' or optimization typical of Replatforming.
Community Discussion (6 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Replatform (D) is the correct answer because the scenario involves migrating from a self-managed database to an AWS managed service (such as Amazon RDS). This strategy, often called 'Lift and Tinker' or 'Lift and Reshape,' allows you to migrate the workload while making minor optimizations to leverage cloud benefits, such as automated backups and patching, without rewriting the application code.Why the Other Options Are Wrong
Rehost (A) implies a pure 'lift-and-shift' where the infrastructure is moved exactly as-is, which doesn't fit the switch to a managed service model. Refactor (C) would require significant code changes to adopt native cloud services like DynamoDB, which is not indicated here. Repurchase (B) involves replacing the current software with a new version or platform, which is not the case for migrating standard MySQL workloads.Community Comment Notes
Community consensus strongly supports Replatform. As user ahadh7621 noted, this strategy is also known as 'lift, tinker, and shift.' User Nikmah highlighted that migrating to RDS is a classic example of Replatforming because it leverages cloud optimizations without changing core architecture. Users like ShaiTay pointed out that adjustments are required, distinguishing it from a simple rehost.Official Reference
Exam Strategy
Focus on the keywords 'managed service' and 'self-managed'. If the destination is a managed offering (RDS, Elastic Beanstalk) but the source logic remains similar, choose Replatform. If the source and destination are identical infrastructure, choose Rehost.
Frequently Asked Questions
Why is Rehost incorrect for moving to RDS?
Rehost is a pure lift-and-shift. Moving to RDS involves adopting a managed service with different operational characteristics, which classifies it as Replatforming.
What distinguishes Replatform from Refactoring?
Refactoring requires significant code changes to leverage cloud-native features. Replatform involves minor tweaks to optimize for the cloud without altering the core application structure.
Related Analysis
Practice All CLF-C02 Questions
Access 120 questions with complete answers and detailed explanations.
View Full CLF-C02 Practice Test →