Question

Difficulty: HardAzure Virtual Machine Recovery and Restore

An organization has an Azure virtual machine named VM-Sales-01 located in the East US region. The virtual machine is backed up to a Recovery Services vault named Vault-Sales with Cross-Region Restore (CRR) enabled. The secondary region is West US. Due to an outage in the East US region, you must recover the workload in the West US region using Azure Backup. Which restore options are available in the secondary region when configuring the restore in the Azure portal? (Select two.)

  1. Create a new virtual machine in the secondary regionAnswer
  2. Restore the virtual machine's disks to a storage account in the secondary regionAnswer
  3. C
    Replace the existing virtual machine in the secondary region
  4. D
    Replace the existing virtual machine in the primary region using Cross-Region Restore

Answer

The correct options are creating a new virtual machine in the secondary region and restoring the virtual machine's disks to a storage account in the secondary region.
When performing a Cross-Region Restore (CRR) for an Azure virtual machine, Azure Backup allows you to either create a new virtual machine in the secondary region or restore the disks to a storage account in the secondary region. The replace option is unavailable because the target virtual machine is in the primary region and does not exist in the secondary region.

Step-by-Step Solution

1
Identify the recovery target region and service configuration.
The target region is the secondary region (West US) utilizing Cross-Region Restore (CRR).
Determining the target region dictates the available restore workflows.
2
Evaluate the supported recovery types for Cross-Region Restore (CRR).
Azure Backup supports 'Create Virtual Machine' and 'Restore Disks' in the secondary region.
Replacing an existing virtual machine requires the original virtual machine to reside in the target recovery region, which is not true for the secondary region.

Key Concept

Cross-Region Restore (CRR) capabilities and limitations for Azure Virtual Machines
Rate this question