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.
Server2 hosts a virtual machine named VM1.
You need to ensure that you can start VM1 on Server1 if Server2 fails. The solution must
minimize hardware costs.
What should you do?
A.
From the Hyper-V Settings of Server2, modify the Replication Configuration settings.
Enable replication for VM1.
B.
On Server1, install the Multipath I/O (MPIO) feature. Modify the storage location of the
VHDs 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–Server1 –by going to the server
and modifying the “Replication Configuration” settings under Hyper-V settings. You then go
to VM1 –which presides on Server2– and run the “Enable Replication” wizard on VM1.
D Enable replication on Server 1, modify the VM from server2
I disagree. First of all, you need to configure server-level replication settings for *both* physical Hyper-V hosts. Then configure the VM for replication on the *primary* Hyper-V server, i.e. the server that is currently hosting the VM.
“Server2 hosts a virtual machine named VM1.”
So the correct, although incomplete, answer is A.
ideally you would enable replication on both servers for 2 way replication but option D would work where as option A would not because you cannot replicate to server 1 as it has not been configured so D is the right answer