file-level recovery can retrieve selected files without replacing the live instance. In this case, an administrator sees that nightly backups stopped after authentication or permission changes. “Azure Backup file recovery or an alternate restore target for supported workload” would not satisfy that requirement; the supported action is “Backup job errors, vault access and protected workload permissions”. Backup operations can fail when identities, extensions or resource access no longer satisfy requirements.

recovery-point frequency bounds potential lost changes between protected points. In this case, an administrator sees that nightly backups stopped after authentication or permission changes. “The backup RPO may exceed the allowable data-loss window” would not satisfy that requirement; the supported action is “Backup job errors, vault access and protected workload permissions”. Backup operations can fail when identities, extensions or resource access no longer satisfy requirements.

retention policy specifies which backup recovery points remain for longer periods. In this case, an administrator sees that nightly backups stopped after authentication or permission changes. “Backup retention rules in the protection policy” would not satisfy that requirement; the supported action is “Backup job errors, vault access and protected workload permissions”. Backup operations can fail when identities, extensions or resource access no longer satisfy requirements.

a recovery point supplies the protected state from which Azure Backup can reconstruct supported resources. In this case, a finance service needs recovery from accidental VM disk deletion. “Restore the VM or its disks from an available recovery point” would not satisfy that requirement; the supported action is “Verify a usable VM or disk recovery point and exercise restore”. Configured backups are meaningful only when the required protected data can actually be recovered.

stopping protection and removing retained data are different actions with compliance consequences. In this case, a finance service needs recovery from accidental VM disk deletion. “Retention requirements, recovery-point availability and authorization” would not satisfy that requirement; the supported action is “Verify a usable VM or disk recovery point and exercise restore”. Configured backups are meaningful only when the required protected data can actually be recovered.

file-level recovery can retrieve selected files without replacing the live instance. In this case, a finance service needs recovery from accidental VM disk deletion. “Azure Backup file recovery or an alternate restore target for supported workload” would not satisfy that requirement; the supported action is “Verify a usable VM or disk recovery point and exercise restore”. Configured backups are meaningful only when the required protected data can actually be recovered.

backup policies determine when recovery points are created and how long they are retained. In this case, a long-term retention rule requires monthly or yearly recovery points. “An Azure Backup policy with the required schedule and retention” would not satisfy that requirement; the supported action is “Backup retention rules in the protection policy”. Retention policy specifies which backup recovery points remain for longer periods.

recovery-point frequency bounds potential lost changes between protected points. In this case, a long-term retention rule requires monthly or yearly recovery points. “The backup RPO may exceed the allowable data-loss window” would not satisfy that requirement; the supported action is “Backup retention rules in the protection policy”. Retention policy specifies which backup recovery points remain for longer periods.

backup operations can fail when identities, extensions or resource access no longer satisfy requirements. In this case, a long-term retention rule requires monthly or yearly recovery points. “Backup job errors, vault access and protected workload permissions” would not satisfy that requirement; the supported action is “Backup retention rules in the protection policy”. Retention policy specifies which backup recovery points remain for longer periods.

test failover verifies recovery sequencing and target resources without intentionally interrupting production replication. In this case, a primary-region outage requires application VMs to run in another Azure region. “A non-disruptive Site Recovery test failover where supported” would not satisfy that requirement; the supported action is “Azure Site Recovery configured for the protected workload”. Site Recovery orchestrates supported replication and failover to a target location.

failover brings replicated workloads online at the target site based on their available recovery state. In this case, a primary-region outage requires application VMs to run in another Azure region. “Initiate planned or unplanned failover according to the recovery situation” would not satisfy that requirement; the supported action is “Azure Site Recovery configured for the protected workload”. Site Recovery orchestrates supported replication and failover to a target location.

failover networking settings determine where recovered instances connect in the secondary region. In this case, a primary-region outage requires application VMs to run in another Azure region. “Site Recovery target-network mapping and failover configuration” would not satisfy that requirement; the supported action is “Azure Site Recovery configured for the protected workload”. Site Recovery orchestrates supported replication and failover to a target location.

failover networking settings determine where recovered instances connect in the secondary region. In this case, an application is replicated to a secondary region but failover steps have never been tested. “Site Recovery target-network mapping and failover configuration” would not satisfy that requirement; the supported action is “A non-disruptive Site Recovery test failover where supported”. Test failover verifies recovery sequencing and target resources without intentionally interrupting production replication.

site Recovery orchestrates supported replication and failover to a target location. In this case, an application is replicated to a secondary region but failover steps have never been tested. “Azure Site Recovery configured for the protected workload” would not satisfy that requirement; the supported action is “A non-disruptive Site Recovery test failover where supported”. Test failover verifies recovery sequencing and target resources without intentionally interrupting production replication.

recovery plans can coordinate workload restoration instead of starting every tier arbitrarily. In this case, an application is replicated to a secondary region but failover steps have never been tested. “A recovery plan that groups and sequences failover actions” would not satisfy that requirement; the supported action is “A non-disruptive Site Recovery test failover where supported”. Test failover verifies recovery sequencing and target resources without intentionally interrupting production replication.

recovery plans can coordinate workload restoration instead of starting every tier arbitrarily. In this case, an administrator must recover an application in another region after a disaster. “A recovery plan that groups and sequences failover actions” would not satisfy that requirement; the supported action is “Initiate planned or unplanned failover according to the recovery situation”. Failover brings replicated workloads online at the target site based on their available recovery state.

failover networking settings determine where recovered instances connect in the secondary region. In this case, an administrator must recover an application in another region after a disaster. “Site Recovery target-network mapping and failover configuration” would not satisfy that requirement; the supported action is “Initiate planned or unplanned failover according to the recovery situation”. Failover brings replicated workloads online at the target site based on their available recovery state.

site Recovery orchestrates supported replication and failover to a target location. In this case, an administrator must recover an application in another region after a disaster. “Azure Site Recovery configured for the protected workload” would not satisfy that requirement; the supported action is “Initiate planned or unplanned failover according to the recovery situation”. Failover brings replicated workloads online at the target site based on their available recovery state.

replicated corruption or deletion can propagate, so recovery-point backup serves a different purpose. In this case, a service can tolerate 30 minutes of data loss but not six hours of downtime. “Replication for continuity is different from point-in-time backup retention” would not satisfy that requirement; the supported action is “Recovery point objective and recovery time objective”. RPO describes acceptable lost data while RTO describes acceptable restoration delay.

site Recovery orchestrates supported replication and failover to a target location. In this case, a service can tolerate 30 minutes of data loss but not six hours of downtime. “Azure Site Recovery configured for the protected workload” would not satisfy that requirement; the supported action is “Recovery point objective and recovery time objective”. RPO describes acceptable lost data while RTO describes acceptable restoration delay.

failover networking settings determine where recovered instances connect in the secondary region. In this case, a service can tolerate 30 minutes of data loss but not six hours of downtime. “Site Recovery target-network mapping and failover configuration” would not satisfy that requirement; the supported action is “Recovery point objective and recovery time objective”. RPO describes acceptable lost data while RTO describes acceptable restoration delay.

failover brings replicated workloads online at the target site based on their available recovery state. In this case, a recovery plan contains three dependent application tiers that must start in order. “Initiate planned or unplanned failover according to the recovery situation” would not satisfy that requirement; the supported action is “A recovery plan that groups and sequences failover actions”. Recovery plans can coordinate workload restoration instead of starting every tier arbitrarily.

test failover verifies recovery sequencing and target resources without intentionally interrupting production replication. In this case, a recovery plan contains three dependent application tiers that must start in order. “A non-disruptive Site Recovery test failover where supported” would not satisfy that requirement; the supported action is “A recovery plan that groups and sequences failover actions”. Recovery plans can coordinate workload restoration instead of starting every tier arbitrarily.

failover networking settings determine where recovered instances connect in the secondary region. In this case, a recovery plan contains three dependent application tiers that must start in order. “Site Recovery target-network mapping and failover configuration” would not satisfy that requirement; the supported action is “A recovery plan that groups and sequences failover actions”. Recovery plans can coordinate workload restoration instead of starting every tier arbitrarily.

test failover verifies recovery sequencing and target resources without intentionally interrupting production replication. In this case, a VM is replicated but its disaster-region subnet is wrong after failover. “A non-disruptive Site Recovery test failover where supported” would not satisfy that requirement; the supported action is “Site Recovery target-network mapping and failover configuration”. Failover networking settings determine where recovered instances connect in the secondary region.

failover brings replicated workloads online at the target site based on their available recovery state. In this case, a VM is replicated but its disaster-region subnet is wrong after failover. “Initiate planned or unplanned failover according to the recovery situation” would not satisfy that requirement; the supported action is “Site Recovery target-network mapping and failover configuration”. Failover networking settings determine where recovered instances connect in the secondary region.

rPO describes acceptable lost data while RTO describes acceptable restoration delay. In this case, a VM is replicated but its disaster-region subnet is wrong after failover. “Recovery point objective and recovery time objective” would not satisfy that requirement; the supported action is “Site Recovery target-network mapping and failover configuration”. Failover networking settings determine where recovered instances connect in the secondary region.

rPO describes acceptable lost data while RTO describes acceptable restoration delay. In this case, an administrator assumes Azure Site Recovery replaces all backups. “Recovery point objective and recovery time objective” would not satisfy that requirement; the supported action is “Replication for continuity is different from point-in-time backup retention”. Replicated corruption or deletion can propagate, so recovery-point backup serves a different purpose.

failover brings replicated workloads online at the target site based on their available recovery state. In this case, an administrator assumes Azure Site Recovery replaces all backups. “Initiate planned or unplanned failover according to the recovery situation” would not satisfy that requirement; the supported action is “Replication for continuity is different from point-in-time backup retention”. Replicated corruption or deletion can propagate, so recovery-point backup serves a different purpose.

recovery plans can coordinate workload restoration instead of starting every tier arbitrarily. In this case, an administrator assumes Azure Site Recovery replaces all backups. “A recovery plan that groups and sequences failover actions” would not satisfy that requirement; the supported action is “Replication for continuity is different from point-in-time backup retention”. Replicated corruption or deletion can propagate, so recovery-point backup serves a different purpose.

recovery plans can coordinate workload restoration instead of starting every tier arbitrarily. In this case, a recovery team completes a regional failover successfully. “A recovery plan that groups and sequences failover actions” would not satisfy that requirement; the supported action is “Validate recovered application function and plan failback/reprotection as appropriate”. Connectivity alone does not prove full business-service restoration, and continuing protection must be planned.

replicated corruption or deletion can propagate, so recovery-point backup serves a different purpose. In this case, a recovery team completes a regional failover successfully. “Replication for continuity is different from point-in-time backup retention” would not satisfy that requirement; the supported action is “Validate recovered application function and plan failback/reprotection as appropriate”. Connectivity alone does not prove full business-service restoration, and continuing protection must be planned.

failover brings replicated workloads online at the target site based on their available recovery state. In this case, a recovery team completes a regional failover successfully. “Initiate planned or unplanned failover according to the recovery situation” would not satisfy that requirement; the supported action is “Validate recovered application function and plan failback/reprotection as appropriate”. Connectivity alone does not prove full business-service restoration, and continuing protection must be planned.