You need to assign VirtualiSCSI2.vhd a logical unit val…

You have a server named LON-DC1 that runs Windows Server 2012 R2. An iSCSI virtual disk named
VirtualiSCSI1.vhd exists on LON-DC1 as shown in the exhibit. (Click the Exhibit button.)

You create a new iSCSI virtual disk named VirtualiSCSI2.vhd by using the existing itgt iSCSI target.
VirtualiSCSIl.vhd is removed from LON-DC1.
You need to assign VirtualiSCSI2.vhd a logical unit value of 0.
What should you do?

You have a server named LON-DC1 that runs Windows Server 2012 R2. An iSCSI virtual disk named
VirtualiSCSI1.vhd exists on LON-DC1 as shown in the exhibit. (Click the Exhibit button.)

You create a new iSCSI virtual disk named VirtualiSCSI2.vhd by using the existing itgt iSCSI target.
VirtualiSCSIl.vhd is removed from LON-DC1.
You need to assign VirtualiSCSI2.vhd a logical unit value of 0.
What should you do?

A.
Modify the properties of the itgt ISCSI target.

B.
Modify the properties of the VirtualiSCSI2.vhd iSCSI virtual disk.

C.
Run the Set-VirtualDisk cmdlet and specify the -Uniqueld parameter.

D.
Run the iscsicli command and specify the reportluns parameter.

Explanation:
The virtual disk has the option to change the lun ID, no other option available in the answers appear to allow
this change.
Note: Logical unit numbers (LUNs) created on an iSCSI disk storage subsystem are not directly assigned to a
server. For iSCSI, LUNs are assigned to logical entities called targets.



Leave a Reply 0

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