AZ-305 - Design Business Continuity Solutions (13% of the exam) - Section 3.1
Design solutions for backup and disaster recovery using Azure Backup and Azure Site Recovery.
Design a backup strategy using Azure Backup, Recovery Services vaults, and backup policies that satisfies defined RPO targets for virtual machines, databases, and file workloads. Use Azure Site Recovery to replicate on-premises and Azure workloads so that RTO targets can be met after a regional failure.
Azure BackupRecovery Services vaultbackup policiesAzure Site RecoveryRTO and RPO targets
Practice question for this objective
lock_openFree sampleDesign Business Continuity Solutionsmedium
Your AZ-305 design must protect Azure VMs, on-premises file servers via the MARS agent, and Azure Blob containers, with a single RPO target of 24 hours and an RTO of 4 hours. A WAF Reliability pillar review asks which vault choice aligns with the workloads documented for each service.
APut Azure VM and MARS-agent workloads in a Recovery Services vault and Azure Blob operational backup in a Backup vault.check_circle Correct
BPut every workload into a single Backup vault to consolidate RBAC and monitoring across the design.
CPut every workload into a single Recovery Services vault so MARS, Azure VM, and Blob share one redundancy setting.
DSplit MARS-agent backups into a Backup vault and keep Azure VM and Blob backups in a Recovery Services vault.
MARS and Azure VM extension backups go in Recovery Services vault; Azure Blob backup lives in Backup vault. Azure Backup documents two vault families: Recovery Services vault hosts Azure VM extension backups and MARS-agent backups; Backup vault hosts newer datasource types such as Azure Blob operational/vaulted backup. Aligning each workload to the supported vault keeps the RPO 24h / RTO 4h targets achievable using Microsoft-supported flows.
Why A is correct: Correct. Azure Backup documents two vault families: Recovery Services vault hosts Azure VM extension backups and MARS-agent backups; Backup vault hosts newer datasource types such as Azure Blob operational/vaulted backup.
Why B is wrong: Backup vault does not cover MARS-agent file/folder/system-state backup or the classic Azure VM backup extension flow; those workloads are bound to Recovery Services vault.
Why C is wrong: Azure Blob operational and vaulted backup are protected through Backup vault, not Recovery Services vault, so a single-RSV design omits the blob workload.
Why D is wrong: Backup vault does not host MARS-agent backups, and Azure Blob backup is configured through Backup vault, so the split is inverted.
Exam traps in Design Business Continuity Solutions
Answers that look right on this material and are not. Each one is a distractor from a different question in the AZ-305 bank for this domain.
Configure active geo-replication; RTO is typically less than 30 seconds and RPO is 0.
errorWhy it is wrong: Active geo-replication targets cross-region DR with RTO typically under 60 seconds and an RPO of 0 or greater, not an in-region 30-second guarantee.
Create all 600 Recovery Services vaults inside one subscription; the per-subscription cap is documented as 1,000 vaults.
errorWhy it is wrong: The documented limit is 500 vaults per subscription, not 1,000, so 600 cannot fit in a single subscription.
RTO typically less than 60 seconds; RPO equal to or greater than 0 depending on cross-region replication lag.
errorWhy it is wrong: Less than 60-second RTO is the failover-group target, not geo-restore; geo-restore is documented as minutes to hours.