You have two servers named Host1 and Host2 that run Windows Server 2022 and are members of a workgroup named Contoso. Both servers have the Hyper-V…

To establish a disaster recovery solution using Hyper-V Replica between two servers in a workgroup, a specific sequence of configurations is required. First, the destination server, Host2, must be configured to accept incoming replication traffic by enabling it as a Replica server. Second, because the servers are not in an Active Directory domain, Kerberos authentication is not possible. Therefore, certificate-based authentication must be used, and the corresponding firewall rules (TCP exceptions) for HTTPS traffic (port 443) must be enabled on both hosts to allow communication. Finally, after the hosts are configured, replication must be enabled individually for each virtual machine on the source server, Host1, that needs to be protected.

B. Use Kerberos authentication and enable TCP exceptions.

Kerberos authentication requires Active Directory Domain Services for mutual authentication. The servers are in a workgroup, making this option invalid.

E. Enable live migration for Host1 and Host2.

Live migration is a high-availability feature for moving running virtual machines between hosts with no downtime, not a disaster recovery solution like Hyper-V Replica. It is not a prerequisite.

F. Enable Host1 as a Replica server.

Host1 is the primary server containing the source virtual machines. Only the destination server, Host2, needs to be enabled as a Replica server to receive the replicated data.

1. Microsoft Learn

Set up Hyper-V Replica. This document outlines the deployment prerequisites and steps.

Section: "Deployment prerequisites": It states

"If the primary and Replica servers are in a workgroup

or in untrusted domains

you must use certificate-based authentication. Kerberos authentication is only supported for servers in the same trusted domain." This supports option A and invalidates option B.

Section: "Step 2 - Enable the Replica server": This section details the procedure for configuring the destination server. "On the server that will act as the Replica server

in Hyper-V Manager

open Hyper-V Settings > Replication Configuration. In Details

select Enable this computer as a Replica server." This directly supports option D.

Section: "Step 3 - Enable replication for virtual machines": This section explains that after host configuration

you must act on the specific VMs. "On the primary server

right-click a VM > Enable Replication." This supports option C.

Section: "Step 1 - Set up the firewall": This section confirms the need for firewall exceptions. "On the Replica server

open Windows Defender Firewall with Advanced Security... Right-click Hyper-V Replica HTTPS Listener (TCP-In) > Enable Rule." This supports the "enable TCP exceptions" part of option A.

2. Microsoft Learn

Hyper-V Replica Overview. This document distinguishes between different Hyper-V features.

Section: "In-box deployment": It describes Hyper-V Replica as a feature for disaster recovery

which is distinct from high-availability solutions like Failover Clustering and Live Migration. This clarifies why option E is incorrect for this scenario.