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. 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.
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.