During a migration assessment, under what circumstances is the retain strategy the right choice?
Show answer and explanation
Answer: A
Retain keeps a workload exactly where it is today — on premises or as-is — which is appropriate when the workload is not yet ready to move, carries a hard dependency or constraint, or is earmarked for a later wave. It is the strategy for deferral, not for abandonment or redesign.
The other options map cleanly onto retire, repurchase, and refactor respectively, which are separate strategies entirely.
Why the other options are wrong
- B. Removing an unused application forever is the retire strategy.
- C. Replacing an application with a different, usually SaaS, product is repurchase.
- D. Redesigning an application's architecture toward cloud-native microservices is refactor.