Azure Disk Backup uses the Backup vault model for protected disks. In this case, a VM was added to a vault without a policy and no regular recovery points appear. “A Backup vault with a compatible Azure Disk Backup policy” would not satisfy that requirement; the supported action is “Enable protection under a valid backup policy”. Vault creation alone does not schedule application data recovery points.

Azure Backup vault types and policy models differ by protected resource. In this case, a VM was added to a vault without a policy and no regular recovery points appear. “Select the correct vault and workload-specific backup product” would not satisfy that requirement; the supported action is “Enable protection under a valid backup policy”. Vault creation alone does not schedule application data recovery points.

Recovery points allow restoration of supported protected VM workloads. In this case, a VM was added to a vault without a policy and no regular recovery points appear. “Restore an available VM backup recovery point according to policy” would not satisfy that requirement; the supported action is “Enable protection under a valid backup policy”. Vault creation alone does not schedule application data recovery points.

Blob object replication does not automatically back up a VM’s OS, disks, deployment relationships and guest application state. The competing choice “Create a Blob Storage object replica and assume it includes VM OS and configuration state” does not meet the specific requirement: An application team needs a recoverable Azure VM with its operating system configuration and application data, rather than only snapshot protection of an individual managed disk. Which backup design is appropriate. The supported action is “Configure a supported Azure VM backup policy in a Recovery Services vault for the protected workload”.

Managed-disk backup is not a blanket replacement for the requested VM-level backup and application-consistency guarantees. The competing choice “Use Azure Disk Backup only and assume it captures every VM guest application consistency requirement” does not meet the specific requirement: An application team needs a recoverable Azure VM with its operating system configuration and application data, rather than only snapshot protection of an individual managed disk. Which backup design is appropriate. The supported action is “Configure a supported Azure VM backup policy in a Recovery Services vault for the protected workload”.

Site Recovery replication addresses availability and failover but can replicate undesired changes; it does not replace retained backup points. The competing choice “Replicate the VM with Azure Site Recovery and use that as the only historic point-in-time backup” does not meet the specific requirement: An application team needs a recoverable Azure VM with its operating system configuration and application data, rather than only snapshot protection of an individual managed disk. Which backup design is appropriate. The supported action is “Configure a supported Azure VM backup policy in a Recovery Services vault for the protected workload”.

Backup policies determine schedule and retention for supported protected workloads. In this case, an operator configures a Recovery Services VM backup policy and assumes it protects every disk snapshot workflow. “An Azure Backup policy linked through an appropriate Recovery Services vault” would not satisfy that requirement; the supported action is “Select the correct vault and workload-specific backup product”. Azure Backup vault types and policy models differ by protected resource.

Vault creation alone does not schedule application data recovery points. In this case, an operator configures a Recovery Services VM backup policy and assumes it protects every disk snapshot workflow. “Enable protection under a valid backup policy” would not satisfy that requirement; the supported action is “Select the correct vault and workload-specific backup product”. Azure Backup vault types and policy models differ by protected resource.

Recovery points allow restoration of supported protected VM workloads. In this case, an operator configures a Recovery Services VM backup policy and assumes it protects every disk snapshot workflow. “Restore an available VM backup recovery point according to policy” would not satisfy that requirement; the supported action is “Select the correct vault and workload-specific backup product”. Azure Backup vault types and policy models differ by protected resource.

Azure Disk Backup uses the Backup vault model for protected disks. In this case, a protected Azure VM is accidentally deleted. “A Backup vault with a compatible Azure Disk Backup policy” would not satisfy that requirement; the supported action is “Restore an available VM backup recovery point according to policy”. Recovery points allow restoration of supported protected VM workloads.

Azure Backup vault types and policy models differ by protected resource. In this case, a protected Azure VM is accidentally deleted. “Select the correct vault and workload-specific backup product” would not satisfy that requirement; the supported action is “Restore an available VM backup recovery point according to policy”. Recovery points allow restoration of supported protected VM workloads.

Retention policy design can reduce cost while meeting recovery requirements. In this case, a protected Azure VM is accidentally deleted. “Use an appropriate long-term retention schedule with monthly points” would not satisfy that requirement; the supported action is “Restore an available VM backup recovery point according to policy”. Recovery points allow restoration of supported protected VM workloads.

Retention policy design can reduce cost while meeting recovery requirements. In this case, an app team needs the state before yesterday's failed migration. “Use an appropriate long-term retention schedule with monthly points” would not satisfy that requirement; the supported action is “Restore a recovery point from before the damaging change”. Restore point selection determines the application data state recovered.

Azure Backup vault types and policy models differ by protected resource. In this case, an app team needs the state before yesterday's failed migration. “Select the correct vault and workload-specific backup product” would not satisfy that requirement; the supported action is “Restore a recovery point from before the damaging change”. Restore point selection determines the application data state recovered.

Daily and monthly retention schedules support different recovery horizons. In this case, an app team needs the state before yesterday's failed migration. “Extend the policy with supported monthly long-term retention” would not satisfy that requirement; the supported action is “Restore a recovery point from before the damaging change”. Restore point selection determines the application data state recovered.

Recovery points allow restoration of supported protected VM workloads. In this case, a backup policy retains daily backups for 30 days but the audit requires one year of monthly points. “Restore an available VM backup recovery point according to policy” would not satisfy that requirement; the supported action is “Extend the policy with supported monthly long-term retention”. Daily and monthly retention schedules support different recovery horizons.

Restore point selection determines the application data state recovered. In this case, a backup policy retains daily backups for 30 days but the audit requires one year of monthly points. “Restore a recovery point from before the damaging change” would not satisfy that requirement; the supported action is “Extend the policy with supported monthly long-term retention”. Daily and monthly retention schedules support different recovery horizons.

Compute management rights do not universally imply backup administrative privileges. In this case, a backup policy retains daily backups for 30 days but the audit requires one year of monthly points. “Backup-specific role assignments and vault protection controls” would not satisfy that requirement; the supported action is “Extend the policy with supported monthly long-term retention”. Daily and monthly retention schedules support different recovery horizons.

Restore point selection determines the application data state recovered. In this case, a team keeps every daily recovery point for years when only monthly historical points are needed. “Restore a recovery point from before the damaging change” would not satisfy that requirement; the supported action is “Use an appropriate long-term retention schedule with monthly points”. Retention policy design can reduce cost while meeting recovery requirements.

Compute management rights do not universally imply backup administrative privileges. In this case, a team keeps every daily recovery point for years when only monthly historical points are needed. “Backup-specific role assignments and vault protection controls” would not satisfy that requirement; the supported action is “Use an appropriate long-term retention schedule with monthly points”. Retention policy design can reduce cost while meeting recovery requirements.

Recovery points allow restoration of supported protected VM workloads. In this case, a team keeps every daily recovery point for years when only monthly historical points are needed. “Restore an available VM backup recovery point according to policy” would not satisfy that requirement; the supported action is “Use an appropriate long-term retention schedule with monthly points”. Retention policy design can reduce cost while meeting recovery requirements.

Soft delete provides a recoverability window for eligible deleted backup data. In this case, an organization wants restore access restricted to authorized backup operators. “Enable supported soft delete and vault security settings” would not satisfy that requirement; the supported action is “Use scoped Azure RBAC and vault security controls for recovery operations”. Recovery activities should be permissioned independently from ordinary VM operations.

Retention policy design can reduce cost while meeting recovery requirements. In this case, an organization wants restore access restricted to authorized backup operators. “Use an appropriate long-term retention schedule with monthly points” would not satisfy that requirement; the supported action is “Use scoped Azure RBAC and vault security controls for recovery operations”. Recovery activities should be permissioned independently from ordinary VM operations.

Soft-delete behavior provides a grace period for recovery after deletion. In this case, an organization wants restore access restricted to authorized backup operators. “Backup soft delete retaining eligible backup data during its safety window” would not satisfy that requirement; the supported action is “Use scoped Azure RBAC and vault security controls for recovery operations”. Recovery activities should be permissioned independently from ordinary VM operations.

Soft delete provides a recoverability window for eligible deleted backup data. In this case, a VM Contributor assumes they can delete every backup recovery point. “Enable supported soft delete and vault security settings” would not satisfy that requirement; the supported action is “Backup-specific role assignments and vault protection controls”. Compute management rights do not universally imply backup administrative privileges.

Soft-delete behavior provides a grace period for recovery after deletion. In this case, a VM Contributor assumes they can delete every backup recovery point. “Backup soft delete retaining eligible backup data during its safety window” would not satisfy that requirement; the supported action is “Backup-specific role assignments and vault protection controls”. Compute management rights do not universally imply backup administrative privileges.

Retention policy design can reduce cost while meeting recovery requirements. In this case, a VM Contributor assumes they can delete every backup recovery point. “Use an appropriate long-term retention schedule with monthly points” would not satisfy that requirement; the supported action is “Backup-specific role assignments and vault protection controls”. Compute management rights do not universally imply backup administrative privileges.

Vault immutability and protected operations reduce malicious deletion risk. In this case, a vault needs protection against accidental deletion of backup items. “Enable available immutable vault settings and multi-user authorization where supported” would not satisfy that requirement; the supported action is “Enable supported soft delete and vault security settings”. Soft delete provides a recoverability window for eligible deleted backup data.

Compute management rights do not universally imply backup administrative privileges. In this case, a vault needs protection against accidental deletion of backup items. “Backup-specific role assignments and vault protection controls” would not satisfy that requirement; the supported action is “Enable supported soft delete and vault security settings”. Soft delete provides a recoverability window for eligible deleted backup data.

Recovery activities should be permissioned independently from ordinary VM operations. In this case, a vault needs protection against accidental deletion of backup items. “Use scoped Azure RBAC and vault security controls for recovery operations” would not satisfy that requirement; the supported action is “Enable supported soft delete and vault security settings”. Soft delete provides a recoverability window for eligible deleted backup data.

Compute management rights do not universally imply backup administrative privileges. In this case, a backup admin deletes a protected item and data remains temporarily recoverable. “Backup-specific role assignments and vault protection controls” would not satisfy that requirement; the supported action is “Backup soft delete retaining eligible backup data during its safety window”. Soft-delete behavior provides a grace period for recovery after deletion.

Vault immutability and protected operations reduce malicious deletion risk. In this case, a backup admin deletes a protected item and data remains temporarily recoverable. “Enable available immutable vault settings and multi-user authorization where supported” would not satisfy that requirement; the supported action is “Backup soft delete retaining eligible backup data during its safety window”. Soft-delete behavior provides a grace period for recovery after deletion.

Recovery activities should be permissioned independently from ordinary VM operations. In this case, a backup admin deletes a protected item and data remains temporarily recoverable. “Use scoped Azure RBAC and vault security controls for recovery operations” would not satisfy that requirement; the supported action is “Backup soft delete retaining eligible backup data during its safety window”. Soft-delete behavior provides a grace period for recovery after deletion.