Quick Note — Evaluate a Migration Solution that Leverages the Microsoft Cloud Adoption Framework
AZ-305 › Unit 4: Design infrastructure solutions › Design migrations › Evaluate a migration solution that leverages the Microsoft Cloud Adoption Framework for Azure
Quick Note — Evaluate a Migration Solution that Leverages the Microsoft Cloud Adoption Framework
A retailer's CTO announces a "24-month cloud migration". Eighteen months later the project has burned , migrated a quarter of the planned workloads, and lost two of its three architects. The post-mortem finds the same root cause everywhere: the team picked tools and migrated workloads before there was a strategy, a landing zone, or a governance baseline. Each migrated workload needed its own subscription, its own NSG design, its own logging — and each redesign created drift from the previous one. A neighbouring retailer ran a similar migration two years earlier using the Microsoft Cloud Adoption Framework (CAF).…
Retrieval target
- Evaluate a Migration Solution that Leverages the Microsoft Cloud Adoption Framework
- Closed-book recall
- 5 minutes
- Open the full lesson after a miss
Decision anchors
| Prompt | Compact answer |
|---|---|
Cloud Adoption Framework (CAF) | Microsoft's opinionated playbook for cloud adoption — documentation, tools, templates, and best practices organized around the seven core methodologies of an enterprise cloud journey. Vendor-neutral concepts but tooling targeted at Azure. Pairs with the Well-Architected Framework (WAF) — CAF is what to adopt; WAF is how to build well once adopted. |
| The seven CAF methodologies | 1. Strategy — business justification, outcomes. 2. Plan — actionable plan to drive outcomes. 3. Ready — set up the landing zone. 4. Adopt — Migrate existing workloads, Modernize them onto Azure services, or build cloud-native workloads. 5. Govern — governance disciplines (cost, security, identity, deployment). 6. Secure — protect workloads; security controls applied end to end across every phase. 7. Manage — operations baseline. |
Landing Zone | A pre-configured, opinionated Azure environment ready to receive workloads. Includes governance baselines (Policy, RBAC, network topology, identity, logging, security). CAF publishes enterprise-scale landing zone reference architecture with Bicep / Terraform templates. The 'foundation' you deploy before the first workload — saves teams from re-inventing tenant-level setup. |
| The 8 R's of cloud migration | 1. Retire — decommission a redundant or low-value workload. 2. Rehost (lift-and-shift) — move VM as-is; fastest path, no modernization. 3. Replatform — PaaS with minimal code changes, to offload maintenance (e.g., move to App Service). 4. Refactor — code changes to cut technical debt or optimize for cloud. 5. Rearchitect — restructure into microservices / serverless. 6. Replace — adopt a SaaS / AI solution instead (Salesforce, ServiceNow). 7. Rebuild — discard and rewrite cloud-native. 8. Retain — leave it in place; stable, compliant, no near-term driver to move.… |
Read the answers once, then cover the right-hand column and reconstruct each one from the prompt. A useful answer names the requirement, the recommended control or service boundary, and the nearest alternative it rejects. If you can only recognize the answer after seeing it, retrieval is not yet secure.
Ninety-second explanation
Without notes, explain:
- What requirement signals this learning objective rather than a neighbouring one?
- Which two solution families are most likely to be compared?
- Which hard constraint eliminates the strongest distractor?
- What identity, network, data, or failure boundary must appear in the design?
- Which operational test would prove the recommendation works?
Then compare your explanation with the full lesson. Record the missing decision rule—not merely the missed product name—in your error log.
When to open the full lesson
Open the curriculum-linked lesson when you cannot explain a comparison, when a scenario depends on a numeric limit or SKU feature, or when the service is on a retirement path. Use current Microsoft Learn documentation for availability, limits, pricing, naming, and migration milestones; the quick note is intentionally compact.
Source and freshness
Derived from the linked AZ-305 lesson and retrieval deck, grounded in both attached course sources. Reviewed 2026-08-02. Current Microsoft documentation controls changing product contracts.