CLF-C02 ยท Well-Architected design and cloud migration
The 7 Rs of migration
The 7 Rs of migration (retire, retain, rehost, relocate, repurchase, replatform, refactor) and choosing one for a described workload, including database replication.
Key points
- Retire: decommission apps with no value.
- Retain: keep in source for now.
- Rehost (lift and shift): move unchanged.
- Relocate: cloud version of the same platform, or another VPC, Region or account.
- Repurchase (drop and shop): replace with another product, often SaaS.
- Replatform (lift, tinker and shift): some optimization, e.g. to Amazon RDS.
- Refactor / re-architect: cloud-native redesign; most complex, costly.
Practice questions
Which migration strategy is also known as 'lift and shift'?
- Replatform
- Rehost
- Refactor
- Repurchase
Show answer
Answer: B. Rehost
Rehost moves an application to AWS without changing it, which is why it is called lift and shift. Replatform is 'lift, tinker and shift' because it adds some optimization along the way.
Which situations are common reasons to choose the retain strategy for an application?
- Data residency rules require it to stay where it is
- It has had no inbound connections for 90 days
- It depends on plant hardware with no cloud equivalent
- The vendor will soon release a SaaS version
- Its monolithic design blocks fast feature releases
Show answer
Answer: A. Data residency rules require it to stay where it is, C. It depends on plant hardware with no cloud equivalent, D. The vendor will soon release a SaaS version
Retain fits apps that must stay put for data residency rules, apps that depend on specialized hardware with no cloud equivalent, and apps waiting for a vendor's SaaS release. An app nobody uses is a retire candidate, and a monolith that blocks fast delivery is a refactor candidate.
For a large migration of hundreds of applications, refactoring every application during the move is the recommended approach because it gives the most cloud benefits.
Show answer
Answer: False
False. Refactor is the most complex and costly strategy. For large migrations, the usual advice is to rehost, relocate or replatform first and modernize after the migration is complete.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
