You need to ensure that VM1 remains available from HV1 …

Your network contains three servers named HV1, HV2, and Server1 that run Windows Server 2012 R2. HV1
and HV2 have the Hyper-V server role installed. Server1 is a file server that contains 3 TB of free disk space.
HV1 hosts a virtual machine named VM1. The virtual machine configuration file for VM1 is stored in D:\\VM and
the virtual hard disk file is stored in E:\\VHD.
You plan to replace drive E with a larger volume.
You need to ensure that VM1 remains available from HV1 while drive E is being replaced. You want to achieve
this goal by using the minimum amount of administrative effort.
What should you do?

Your network contains three servers named HV1, HV2, and Server1 that run Windows Server 2012 R2. HV1
and HV2 have the Hyper-V server role installed. Server1 is a file server that contains 3 TB of free disk space.
HV1 hosts a virtual machine named VM1. The virtual machine configuration file for VM1 is stored in D:\\VM and
the virtual hard disk file is stored in E:\\VHD.
You plan to replace drive E with a larger volume.
You need to ensure that VM1 remains available from HV1 while drive E is being replaced. You want to achieve
this goal by using the minimum amount of administrative effort.
What should you do?

A.
Perform a live migration to HV2.

B.
Add HV1 and HV2 as nodes in a failover cluster. Perform a storage migration to HV2.

C.
Add HV1 and HV2 as nodes in a failover cluster. Perform a live migration to HV2.

D.
Perform a storage migration to Server1.



Leave a Reply 1

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


justbecause

justbecause

Explanation:
‘Using a minimum amount of adminitrative effort’ is the always key for this type of questions.
They will give multiple possible solutions, but with that key in mind, D is the answer.
A,C is not the answer because VM1 has to remain in HV1
B is possible, but it takes lots of effort to set up cluster.
D seems the best answer. You just do storage migration lively to another server, then bring back
when large disk is insert to hot swap bay.