Which migration strategy moves an existing on-premises application to AWS virtual servers almost as-is, with little code change? It is commonly called "lift and shift".
Choosing the name of the migration strategy that moves to AWS without changes (lift and shift).
Refactoring (Refactor)
Refactoring is a migration strategy that rebuilds the app into a cloud-native architecture, which involves large code changes.
This question is about a migration with 'almost no change', so a rebuild-heavy refactor does not apply and is incorrect.
Rehosting (Rehost)
Correct. Rehosting (lift and shift) is a strategy that moves an existing app almost as-is to AWS virtual servers (such as EC2). With little change, it migrates quickly, so it is often used in the early stages when you want to move many servers fast.
Replatforming (Replatform)
Replatforming is a strategy that replaces just a part with managed services to optimize it during the move (for example, changing a self-managed DB to Amazon RDS).
This question moves the app almost as-is with little code change, so a replatform that adds optimizations does not apply and is incorrect.
Repurchasing (Repurchase)
Repurchasing is a strategy that switches an existing app to a different product (often SaaS).
This question moves the same app as-is, which is different from buying a different product, so it is incorrect.
The migration R's: Rehost (no change = lift & shift) / Replatform (slight optimization) / Refactor (rebuild) / Repurchase (different product = SaaS) / Relocate (move as-is). 'No change' and 'lift & shift' mean rehost.