Two servers, Server1 and Server2, run Windows Server with the Hyper‑V role. Server1 hosts VM1, VM2, and VM3, and those VMs replicate to Server2. After a hardware failure on Server1, you must bring VM1, VM2, and VM3 online as quickly as possible from Server2’s Hyper‑V Manager. Which action should you run for each VM?

The correct action is Unplanned Failover. This option is specifically designed for disaster recovery scenarios where the primary Hyper-V host (Server1) has failed unexpectedly. Executing an Unplanned Failover on Server2 for each VM will bring the replicated VMs online immediately, using the most recent replica data, without requiring the primary server to be operational. "Start" is incorrect because simply starting the VMs on Server2 would not establish them as the new primary, nor would it properly manage the replication relationship. "Move" is used for migrating live VMs between hosts or storage when both hosts are healthy and connected, which is not the case here. "Planned Failover" is used when the primary server is still operational and you intend to gracefully shut down VMs on the primary and bring them up on the replica, often for maintenance or testing, which is the opposite of an unplanned hardware failure.