Migrating Self-Managed MySQL to AWS Managed Service
Short answer
D The company should use the Replatform strategy to migrate its self-managed MySQL database to an AWS managed service like Amazon RDS.
Question
Key Takeaways
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.
Common mistake: 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.
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
https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-strategies.html
This link opens the official vendor documentation in a new tab.
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?
What distinguishes Replatform from Refactoring?
Community Votes
100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 6 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 6
-
ahadh7621 👍 2 Answered DThe answer is D, Replatform. https://docs.aws.amazon.com/prescriptive-guidance/latest/large-migration-guide/migration-strategies.html This strategy is also known as lift, tinker, and shift or lift and reshape. Using this migration strategy, you move the application to the cloud, and you introduce some level of optimization in order to operate the application efficiently, to reduce costs, or to take advantage of cloud capabilities. For example, you might replatform a Microsoft SQL Server database to Amazon RDS for SQL Server. Using this strategy, you might make a few or many changes to the application, depending on your business goals and your target platform. The following are common use cases for the replatform migration strategy: You want to save time and reduce cost by moving to a fully managed service or serverless service in the AWS Cloud.
-
red_panda 👍 2Replatform because we are going to from self managed db to fully managed db by aws so it's not sufficient rehost.
-
Nikmah 👍 1 Answered DReplatform “lift and reshape” • Example: migrate your database to RDS • Example: migrate your application to Elastic Beanstalk • Not changing the core architecture, but leverage some Cloud optimizations • Save time and money by moving to a fully managed service or Serverless
-
Zerro 👍 1Why not A, rehost? Is it because Rehost is more used for applications and Replatform is used for databases?
-
ShaiTay 👍 1 Answered DD. Replatform - a few adjustments will have to be made, so replatforming is the right answer vs rehosting.
Show 1 more comment
-
Meow7 👍 1D is correct. please help with discussion on 500 503 ~ 511. Thanks.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All CLF-C02 Questions
Access 120 questions with complete answers and detailed explanations.
View Full CLF-C02 Practice Test →