You need to ensure that you can start VM1 on Server2 if…

Your network contains two servers named Server1 and Server2 that run Windows Server 2012 R2.
Both servers have the Hyper-V server role installed. Server1 and Server2 are located in different offices. The
offices connect to each other by using a high-latency WAN link.
Server1 hosts a virtual machine named VM1.
You need to ensure that you can start VM1 on Server2 if Server1 fails. The solution must minimize hardware
costs.What should you do?

Your network contains two servers named Server1 and Server2 that run Windows Server 2012 R2.
Both servers have the Hyper-V server role installed. Server1 and Server2 are located in different offices. The
offices connect to each other by using a high-latency WAN link.
Server1 hosts a virtual machine named VM1.
You need to ensure that you can start VM1 on Server2 if Server1 fails. The solution must minimize hardware
costs.What should you do?

A.
. On Server1, install the Multipath I/O (MPIO) feature. Modify the storage location of the VHDs for VM1.

B.
From the Hyper-V Settings of Server2, modify the Replication Configuration settings. Enable replication for
VM1.

C.
On Server2, install the Multipath I/O (MPIO) feature. Modify the storage location of the VHDs for VM1.

D.
From the Hyper-V Settings of Server1, modify the Replication Configuration settings. Enable replication for
VM1.

Explanation:
You first have to enable replication on the Replica server—Server2–by going to the server and modifying the
“Replication Configuration” settings under Hyper-V settings. You then go to VM1–which presides on Server1–
and run the “Enable Replication” wizard on VM1.



Leave a Reply 1

Your email address will not be published. Required fields are marked *


d

d

This was on the test, server 1 and 2 were reversed, be careful