AZ-305 Design business continuity solutions Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  A Recovery Services vault in the target Azure region.

  Why this is correct

  The Recovery Services vault in the target Azure region is the central management and storage container for all Azure Site Recovery (ASR) data. It stores the replication configuration, recovery points, and journaled data that are needed to bring up virtual machines on Azure during failover. Without it, there is no logical destination for the replicated Hyper-V VMs and no coordination point for the replication workflow. Its placement in the target region is critical because replication data always flows from on-premises to that region, and failover must be able to occur there.

• ✓

  A replication policy that defines retention and recovery points.

  Why this is correct

  A replication policy defines the recovery point objective (RPO) threshold, the retention window for recovery points (typically from a few hours to 15 days), and the frequency of application-consistent snapshots. In Hyper-V Site Recovery, this policy is assigned to every Hyper-V host or protection container so that ASR knows how often to replicate changes and how many historical recovery points to keep. Without this policy, the service would not know how to schedule replication cycles or how long to preserve failover options. It is a required component because it directly controls the service-level agreement (SLA) for how quickly and how far back workloads can be restored.

• ✓

  The Azure Site Recovery Provider installed on each Hyper-V host.

  Why this is correct

  The Azure Site Recovery Provider is a lightweight agent that must be installed on every Hyper-V server that will replicate virtual machines to Azure. Its role is to securely communicate with the Azure Site Recovery service over HTTPS (port 443), enabling discovery of Hyper-V hosts, registration of the site, and transmission of management commands that control replication. The Provider also forwards replication health status and coordinates automatic updates to the replication engine. It is required in both VMM and non-VMM deployments, and without it the Hyper-V host cannot participate in any ASR replication workflow.

• ✗

  Azure Backup Server installed on-premises.

  Why it's wrong here

  Azure Backup Server (MABS) is an on-premises backup product that is used to protect files, folders, virtual machines, SQL Server, and other workloads by copying them to a Recovery Services vault. This is fundamentally different from Azure Site Recovery, which performs continuous block-level replication and provides orchestrated failover and failback capabilities. MABS does not maintain a continuous replica of the VM state, nor does it support the automatic failover required by a disaster recovery plan. Therefore, it is not a required component for ASR replication and installing it on-premises would not enable or enhance the Site Recovery process.

• ✗

  An ExpressRoute connection from on-premises to Azure.

  Why it's wrong here

  An ExpressRoute connection is not a mandatory component for Azure Site Recovery of Hyper-V VMs because ASR can operate over the public internet using encrypted HTTPS (TLS) communications, or over a site-to-site VPN connection. The replication traffic from the Hyper-V host flows to an Azure storage account, and the Provider communicates with the ASR service endpoints; all of this works with standard internet connectivity as long as the required IP ranges and FQDNs are allowed. ExpressRoute may be used to achieve lower latency, higher bandwidth, and a more predictable private path, but it is purely an optional optimization. Requiring it would incorrectly exclude environments that rely on VPN or internet only, which are fully supported by Azure Site Recovery.

Go deeper

Related to this question