Server1 is running Windows Server with the Hyper-V role. You have a Hyper-V failover cluster named Cluster1 and all machines are in the same domain. You want to replicate VMs from Cluster1 to Server1 using Hyper-V Replica with Kerberos authentication on the default port. What change should you make on Server1?

The correct answer is to enable the Hyper-V Replica HTTP Listener (TCP-In) rule. Hyper-V Replica uses HTTP (port 80) for replication by default when Kerberos authentication is configured. Enabling this firewall rule allows incoming replication traffic on Server1. The other options are incorrect because: Adding primary servers to the Hyper-V Replica Broker configuration is not relevant for a standalone Hyper-V host receiving replication from a cluster; the broker manages replication within the cluster. Enabling incoming and outgoing live migrations is for VM mobility, not for Hyper-V Replica. Turning on the Hyper-V Replica HTTPS Listener (TCP-In) rule would be necessary if certificate-based authentication was used, as HTTPS uses port 443. However, the question specifies Kerberos authentication, which defaults to HTTP.