HOTSPOT
You have a server that runs Windows Server 2012 R2 and has the iSCSI Target Server role service
installed.
You run the New-IscsiVirtualDisk cmdlet as shown in the New-IscsiVirtualDisk exhibit. (Click the
Exhibit button.)
To answer, complete each statement according to the information presented in the exhibits. Each
correct selection is worth one point.
Answer: 
Explanation:
<map><m x1=”259″ x2=”355″ y1=”112″ y2=”131″ ss=”0″ a=”0″ /><m x1=”269″ x2=”450″
y1=”188″ y2=”209″ ss=”0″ a=”0″ /></map>* From the exhibit we see that the size is 10737418240 bytes. This is roughly 10 GB.
* From the exhibit we also see ‘Status: Not connected’.
Note: Target: It is an object which allows the iSCSI initiator to make a connection. The Target keeps
track of the initiators which are allowed to be connected to it. The Target also keeps track of the
iSCSI virtual disks which are associated with it. Once the initiator establishes the connection to the
Target, all the iSCSI virtual disks associated with the Target will be accessible by the initiator. Introduction of iSCSI Target in Windows Server 2012
http://blogs.technet.com/b/filecab/archive/2012/05/21/introduction-of-iscsi-target-in-windowsserver-2012.aspx
the disk is thin, it should be 4 MB :
http://www.aiotestking.com/microsoft/you-run-the-new-iscsivirtualdisk-cmdlet-as-shown-in-the-new-iscsivirtualdisk-exhibit/
0
0
thin : i mean dynamic…sorry
0
0
https://technet.microsoft.com/en-us/library/jj612821.aspx
Example 1: Create a fixed VHDX
This example creates a fixed VHDX that is 10GB in size.
Windows PowerShell
PS C:\> New-IscsiVirtualDisk –Path “E:\temp\test.vhdx” -Size 10GB
http://www.aiotestking.com/microsoft/you-run-the-new-iscsivirtualdisk-cmdlet-as-shown-in-the-new-iscsivirtualdisk-exhibit/
given answer is correct.
0
0
disk is dynamic not Dynamically expendable. See what Dynamic Disk means: https://msdn.microsoft.com/en-us/library/windows/desktop/aa363785(v=vs.85).aspx
so given answer is correct.
0
0
http://www.altaro.com/hyper-v/hyper-v-guest-design-fixed-vs-dynamic-vhd/
0
0
to all of you 10GB guys: you should really build up a testlab and try out for yourself before posting untrue stuff!!
I just executed the pscmd given in the question in my testlab, and it created a slim 4MB file while showing 10GB of size.
=> the given pscmd created a Dynamically Expanding vhdx!
therefore correct answer should be:
1. 4MB
2. assign to target
so, try out, see how it works, then post, PLEASE!
8
0
Agreed (verified in lab)
Unless you include the -usefixed it will be dynamic (4MB in size, 4194304 bytes).
( -fixed also seems to work though not specified in the TechNet article).
The output in the exhibit doesn’t show the size on disk, just the virtual size of the VHDx. To see the real size, need to do a dir on the directory.
0
0
I agree. I have tested it as well and the size is 4MB
0
0
Thanks Den. It is relatively easy to test in the lab so I went ahead and did this and sure enough, it gave 4mb vhdx.
Thanks again!
0
0
With all respects to all answers, you can test all options in your lab, but during the exam you have to choose from the provided information.
Is the 4GB a STANDARD size that applies to all scenarios, or it applies only to this question scenario. I mean if MS changes the PowerShell script configuration, the answer will be the same.
If you check the very first line and look carefully at the PowerShell ScreenShot, you will see on the top of the ScreenShot the file SizeByte is 10GB. So I believe the correct answer is the provided answer.
0
0
Also in the powershell output it states the size as being 10GB.
0
0