Your company has Azure virtual machines running a critical application. You need to back up these VMs daily and retain backups for 7 years. The solution must be cost-effective and support application-consistent backups. What should you use?
Azure Backup is the native managed backup service for Azure VMs. It installs a backup extension on each VM and coordinates VSS (Volume Shadow Copy) on Windows or file-system-consistent snapshots on Linux, then transfers the VM's disks to a Recovery Services vault. It provides a configurable backup policy (daily or weekly) with long-term retention, and allows application-consistent, crash-consistent point-in-time restores of entire VMs or individual disks. Because it is fully managed and integrated with Azure Policy and monitoring, it is the correct choice for a critical application that needs reliable recoverability.
Why this answer
Azure Backup is the correct choice because it provides a native, cost-effective backup solution for Azure VMs that supports application-consistent backups via the Volume Shadow Copy Service (VSS) for Windows and file-system-consistent backups for Linux. It allows you to configure a backup policy with daily backups and a retention duration of up to 99 years, easily meeting the 7-year requirement. Azure Backup also integrates with Azure Recovery Services vault, offering centralized management and long-term retention at a lower cost than other disaster recovery or snapshot-based approaches.
Exam trap
The trap here is that candidates often confuse Azure Site Recovery (disaster recovery) with Azure Backup (backup), or assume that VM snapshots are sufficient for long-term retention, overlooking the need for application consistency and cost-effective lifecycle management.
How to eliminate wrong answers
Option B is wrong because Azure Files backup is designed to back up Azure file shares, not Azure VMs, and does not provide application-consistent backups for VM workloads. Option C is wrong because Azure Site Recovery is a disaster recovery solution focused on replication and failover for business continuity, not a backup service; it does not support long-term retention policies like 7 years and is more expensive for daily backup needs. Option D is wrong because Azure VM snapshots stored in Azure Storage are crash-consistent by default, not application-consistent, and managing snapshots for daily backups over 7 years would be complex and costly due to manual lifecycle management and lack of native backup policy integration.