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 s

Question

Options

• ARehost
• BRepurchase
• CRefactor
• DReplatform

• A
  2% (1)
• B
  11% (5)
• C
  4% (2)
• D
  82% (37)

Explanation

Replatform is correct because the company is moving its MySQL database to an AWS managed service (such as Amazon RDS for MySQL), which involves lifting and shifting the workload while making a targeted optimization - swapping self-managed infrastructure for a managed cloud service - without changing the core database engine or application architecture.

• Rehost (A) is wrong because it means "lift and shift" to the cloud with no changes - simply moving the workload to EC2 instances, still self-managed, which defeats the purpose of using a managed service.
• Repurchase (B) is wrong because it involves replacing the existing application with a different commercial product or SaaS solution (e.g., moving from a custom CRM to Salesforce), which isn't happening here.
• Refactor (C) is wrong because it means re-architecting the application from the ground up to take full advantage of cloud-native features, which is a far more extensive change than simply migrating to a managed database service.

Memory Tip: Think of Replatform = "Lift, Tinker, and Shift" - you're keeping the same technology (MySQL) but swapping the platform it runs on (from self-managed servers to AWS RDS). If there's a managed service involved with minimal code/architecture changes, think Replatform.

No community discussion yet for this question.