Quick Note — Recommend a Recovery Solution for Azure and Hybrid Workloads
AZ-305 › Unit 3 › Design business continuity solutions › Recommend a recovery solution for Azure and hybrid workloads that meets recovery objectives
Quick Note — Recommend a Recovery Solution for Azure and Hybrid Workloads
A recovery architecture begins with business impact, not a product name. “Use Azure Backup” is incomplete until the architect knows how much data loss is acceptable, how quickly the workload must return, which failure scopes matter, and which dependencies must recover together. “Use Azure Site Recovery” is equally incomplete if the application is mostly managed PaaS services that require service-native replication rather than virtual-machine failover.
Retrieval target
- Recommend a Recovery Solution for Azure and Hybrid Workloads
- Closed-book recall
- 5 minutes
- Open the full lesson after a miss
Decision anchors
| Prompt | Compact answer |
|---|---|
Recovery Point Objective (RPO) | The maximum data loss your business can tolerate in a disaster, measured in time. If your RPO is 4 hours and a failure happens at 13:00, you must be able to restore data as it was no earlier than 09:00. Drives backup frequency — the more aggressive the RPO, the more often (or continuously) you must take backups / replicate. |
Recovery Time Objective (RTO) | The maximum time the service can be down before business harm becomes unacceptable. If RTO is 4 hours, the recovery process — from disaster detection through full restoration — must complete inside that window. Drives recovery architecture: hot standby, warm standby, or restore-from-backup each fit different RTO budgets. |
Azure Site Recovery (ASR) | A DR-orchestration service that replicates Windows / Linux VMs, VMware, Hyper-V, and physical servers to Azure (or to another datacenter). Provides near-real-time replication with RPO as low as 30 seconds, app-consistent snapshots, single-click recovery plans, network mapping, and integration with Traffic Manager for DNS cutover. Used for full-VM / full-app failover. |
Azure Backup | Microsoft's first-party backup service for files, VMs, databases, file shares, and blobs. Stores recovery points in vaults (Recovery Services Vault or Backup Vault) with policy-driven schedule + retention. Encrypted in transit and at rest. Soft-delete is on by default (default 14 days). Complements ASR — ASR for full-app failover, Backup for file/VM/db restore. |
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.