Host1 and Host2 are workgroup servers running Hyper‑V; Host1 hosts three VMs. Each server is in a different site connected by a high‑speed WAN. You need to replicate Host1’s VMs to Host2 for disaster recovery. Which three actions should you take?

To replicate Hyper-V virtual machines between two standalone servers in a workgroup, you must first configure the destination server to receive replicas. Therefore, enabling Host2 to act as a Replica server is a necessary first step. Since the servers are in a workgroup and not part of an Active Directory domain, certificate-based authentication is required for secure communication between the Hyper-V hosts for replication. This also necessitates opening specific TCP firewall exceptions on both hosts to allow the replication traffic. Finally, once the hosts are configured, you must enable Hyper-V replication for each individual virtual machine on Host1 that you wish to replicate to Host2. Enabling live migration is not directly related to Hyper-V replication for disaster recovery; live migration is for moving running VMs between hosts without downtime, not for creating disaster recovery replicas. Using Kerberos authentication is not possible in a workgroup environment as it relies on Active Directory for authentication. Enabling Host1 to act as a Replica server is incorrect because Host1 is the source server, not the destination.