You will deploy Hyper‑V Replica between Server1 and Server2 using certificate‑based authentication. What two prerequisite steps must you perform on each server?

To configure Hyper-V Replica with certificate-based authentication, two key prerequisites are needed on both the primary and replica servers. First, you must enable the Hyper-V Replica HTTPS Listener (TCP-In) firewall rule. This rule opens port 443, allowing secure, encrypted communication between the Hyper-V hosts over HTTPS, which is essential for certificate-based authentication. The HTTP Listener rule is for Kerberos authentication, not certificate-based. Second, a trusted computer certificate must be installed on each server. This certificate is used to authenticate the Hyper-V hosts to each other, ensuring secure and verified communication. User certificates are for user authentication, not server-to-server replication. While you could create a self-signed certificate, it's generally recommended to use certificates issued by a trusted Certificate Authority for production environments, but the core requirement is to install a trusted computer certificate, regardless of its origin.