You have a server named Server1 that runs Windows Server 2012 R2. Server1 has the Hyper-V server
role installed.

An iSCSI SAN is available on the network.
Server1 hosts four virtual machines named VM1, VM2, VM3, VM4.
You create a LUN on the SAN.
You need to provide VM1 with access to the LUN. The solution must prevent other virtual machines
from accessing the LUN.
What should you configure?

A.
A fixed-size VHDX

B.
A dynamically expanding VHDX

C.
A fixed-size VHD

D.
A pass-through disk

E.
A dynamically expanding VHD

Explanation:
You can use physical disks that are directly attached to a virtual machine as a storage option on the
management operating system. This allows virtual machines to access storage that is mapped
directly to the server running Hyper-V without first configuring the volume. The storage can be
either a physical disk which is internal to the server, or a SAN logical unit number (LUN) that is
mapped to the server (a LUN is a logical reference to a portion of a storage subsystem). The virtual
machine must have exclusive access to the storage, so the storage must be set in an Offline state in
Disk Management. The storage is not limited in size, so it can be a multi-terabyte LUN. When using
physical disks that are directly attached to a virtual machine, you should be aware of the following:
This type of disk cannot be dynamically expanded.
You cannot use differencing disks with them.
You cannot take virtual hard disk snapshots.
Att:
If you are installing an operating system on the physical disk and it is in an Online state before the
virtual machine is started, the virtual machine will fail to start. You must store the virtual machine
configuration file in an alternate location because the physical disk is used by the operating system
installation. For example, locate the configuration file on another internal drive on the server
running Hyper-V.