Task 5.2: Implement backup and recovery

• AEnable Cross Region Restore on the West Europe vault

  Incorrect

  Cross Region Restore restores data to the paired region; it doesn't let the vault protect VMs in another region.

• BChange the vault's storage replication to geo-redundant

  Incorrect

  Replication controls where backup data is copied, not which region's VMs the vault can protect.

• CCreate a second Recovery Services vault in North Europe

  Correct

  A vault protects data sources in its own region, so each region with VMs needs its own vault.

• DMove the North Europe VMs into the vault's resource group

  Incorrect

  The resource group doesn't matter; the region of the VM and the vault must match.

A Recovery Services vault must be in the same region as the data sources it protects. Back up VMs in several regions with one vault per region.

• AAzure virtual machines

  Incorrect

  Azure VM backup is orchestrated by a Recovery Services vault.

• BAzure file shares

  Incorrect

  Azure file share backup uses a Recovery Services vault.

• CAzure managed disks

  Correct

  Azure Disk Backup stores its backup instances and policies in a Backup vault.

• DSQL Server in an Azure VM

  Incorrect

  SQL Server in Azure VMs is a Recovery Services vault workload.

• EAzure Blob storage

  Correct

  Blob backup, both operational and vaulted, is configured in a Backup vault.

Recovery Services vaults handle Azure VMs, SQL Server and SAP HANA in VMs, Azure file shares and the MARS agent. Backup vaults hold newer workloads such as Azure Disks, Azure Blobs and Azure Database for PostgreSQL.

• AThe data is gone, because soft delete covers vaults and not backup items

  Incorrect

  Soft delete applies to backup items and recovery points, and to vaults as well.

• BThe data is recoverable, because it's kept for 14 days by default

  Correct

  Deleted backup data stays in a soft-deleted state for 14 days by default, and you can undelete it in that time.

• CThe data is recoverable for 180 days, the default retention

  Incorrect

  180 days is the longest soft-delete retention you can set; the default is 14 days.

• DThe data is recoverable from the secondary region through Cross Region Restore

  Incorrect

  Soft-deleted data stays in the vault; recovering it doesn't depend on Cross Region Restore.

Soft delete keeps deleted backup data for a retention period of 14 days by default, configurable from 14 to 180 days, and the first 14 days cost nothing. Recover the item by undeleting it and then resuming protection.

• ARun a failover to West US, then fail back after the drill

  Incorrect

  A failover moves the workload to the target region, which takes production out of East US.

• BRun a test failover into a nonproduction virtual network

  Correct

  A test failover creates VMs in the network you pick while replication goes on; clean up the test afterward.

• CRun a failover and leave the recovery point uncommitted

  Incorrect

  Even without a commit, a failover brings the VMs up in the target region as a real recovery; it isn't a drill.

• DRestore the VMs from Azure Backup into the West US region

  Incorrect

  A backup restore tests backups, not the Site Recovery replication and failover the auditors want to see.

Test failover runs a drill in an isolated or nonproduction network without data loss or interruption to replication. Afterward, run Cleanup test failover to delete the test VMs.

• AA recovery plan with three groups in that order

  Correct

  A recovery plan gathers machines into groups that fail over in sequence, with optional scripts.

• BAn availability set per tier

  Incorrect

  Availability sets don't control failover order.

• CThree separate test failovers

  Incorrect

  Running separate failovers one by one doesn't define an order for a real failover.

• DA backup policy with three schedules

  Incorrect

  Backup policies have nothing to do with failover order.

Recovery plans define the order, actions and scripts for failing over a set of machines, so applications come up in the right sequence.

• AReprotect the VMs so they replicate from West US to East US

  Correct

  Reprotect starts replication in the reverse direction, which a failback needs.

• BCommit the failover again

  Incorrect

  Commit finalizes the earlier failover; it doesn't start reverse replication.

• CDisable replication and recreate the VMs in East US

  Incorrect

  Disabling replication loses the reverse replication you need.

• DRun a test failover to East US

  Incorrect

  A test failover needs replication toward East US, which reprotect sets up.

After a failover is committed, reprotect the VMs so they replicate back to the original region. When synchronized, fail back and reprotect again.

• AStop protection and retain backup data

  Correct

  This stops future backups and keeps the existing recovery points.

• BChange the policy to retain zero days

  Incorrect

  Retention can't be zero, and shortening it would remove recovery points.

• CStop protection and delete backup data

  Incorrect

  Deleting the data removes the recovery points auditors need.

• DDelete the Recovery Services vault

  Incorrect

  A vault with backup items can't be deleted, and it would remove the data.

Stop protection with retain backup data ends scheduled backups but keeps recovery points, which you can restore later. Charges for the retained data continue.

• AThe vault still has a backup policy assigned

  Incorrect

  Policies don't block deletion; protected and soft-deleted items do.

• BCross Region Restore must be disabled

  Incorrect

  Cross Region Restore doesn't block vault deletion.

• CThe deleted backup items are in the soft-deleted state

  Correct

  A vault with soft-deleted items can't be deleted until they're permanently removed.

• DThe vault must be moved to another resource group first

  Incorrect

  Moving the vault doesn't remove its dependencies.

Before deleting a vault, remove its dependencies: protected items, registered servers and soft-deleted items. Soft-deleted data stays for its retention period unless removed.