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:
Using 4MB of space as it is dynamic and not fixed. Therefore grows as data is written.
4096KB is the actual size of the VHDX
it should be:
“using 4 MB of” See Screenshot. They are correct
“assign Disk2.vhdx to a target” is correct.
Agree!
I tested this one in Hyper-V. The answer is 4MB. (it is the inital VHDX size on disk)
For Fixed you NEED to use the -UseFixed option.
the mentioned answer is a correct 10G as per the request
That no make any sense. The exam don’t let you go to explore the drive. You should answer what you see in the Exhibit, and the answer is 10G
No, because you just created the new disk with that powershell command, so it’s BRAND NEW and it’s dynamic, so only 4Mb.
The highlighted answer is wrong, Sam is correct.
It’s true. The SizeBytes determines the maximimum disk size, it’s initial size is 4MB, growing up to the max of 10GB.
From the Training Guide 70-410 Installing and Configuring Windows Server 2012 R2, page 358:
Dynamically expanding: This type of virtual hard disk uses only as much physical storage space as it needs to store the actual data that the disk currently contains.
The size of the virtual disk’s image file then grows as additional data is written to it. For example, the image file for a dynamic virtual hard disk of a newly created virtual machine that has no operating system installed on it has a size of only 4 MBs even though its maximum size is configured with the default value of 127 GBs. Once Windows Server 2012 or Windows Server 2012 R2 has been installed as the guest operating system, however, the size of the virtual disk’s image file will grow to more than 8 GBs. See Lesson 3 in this chapter for information on how to expand, compact, or shrink dynamically expanding disks.
kinda subjective, since it mention dynamic, if follow writen theory, then should be 4MB, 10G is just a trick
It says in the exhibit – disktype : DYNAMIC
As from the premium file version 30.0
the answers is
Using 10G
assign Disk2.vhdk to a target
Liron,
Don’t always trust the premium file.
I don’t think Microsoft will put the answer directly in the question, I’ve never seen such thing, the 10 GB is a trick, it should be 4 MB.
agreed it 4mb not 10gb regardless if what displayed “new dynamic disk”
you have to fill it 10 gb to see 10gb on the disk
http://www.windowsnetworking.com/kbase/WindowsTips/WindowsServer2012/AdminTips/VirtualPlatforms/using-powershell-add-virtual-disk-virtual-machine.html
This link is suggesting that it is showing the max value for the file size, so I would have to go with 4 mb.
I also made 2 ISCSI disks in my lab, for both fixed and dynamic, the size shown is the maximal size of the disk
This one is very tough! I’m still unsure.
I made a iscsi disk of 1gb in Server 2012 R2 (previous versions do not support dynamically allocated). I tried this first in 2012 (not R2) and there was no option for dynamic allocation thus the disk showed as 1gb. I then proceeded to install R2 and ran the wizard again and I was able to create a dynamic disk, it showed as only 4mb, not 1gb.
Nutshell: 4mb, assign disk2 to a target
🙂
I’ve tested it my lab. the first answer is wrong and it must be 4mb. i’ve created a Dynamic iscsi vhdx in 10GB space disk. after it’s done, i discovered my new VHDX in my selected hard drive. when you right click on it and select the properties option, you will see “Size 4MB , Size on disk 4MB”. don’t forget the vhdx is Dynamic. if it’s Fix, it will definitely 10GB.
surly the correct answer is 4MB 🙂
I have confirmed 100% that the size is 4MB. Created 2 virtual disks, 1 10GB and 1 100MB, they both show the size as being 4MB. This is because by default it is created as a dynamic disk so the only time it will show as 10GB is when it is full.
The second part of the answer also seems correct, you have to add it to a target before an iscsi initiator can connect.
Also, it shows how bad some of these dumps are, the answer is marked as 10GB but yet the explanation tells you why it is 4MB!
I have a premium file and it says 10GB but I have to agree with most of you that it’s not 10gb if you convert bytes to GB the size it a little over 10GB which tells me that that’s the maximum size that the disk can be expanded but initially it start at about 3-4mb…
From Microsoft Article:
When you create a dynamically expanding virtual hard disk, you specify a maximum file size. This size restricts how large the disk can become. However, the initial size of the .vhd file is only about 3 MB. For example, if you create a 1-GB, dynamically expanding virtual hard disk, the initial size of the .vhd file will be about 3 MB. As a virtual machine uses the virtual hard disk, the size of the .vhd file grows to accommodate the new data. The size of any dynamically expanding disk only grows; it does not shrink, even when you delete data. You may be able to reduce the size of a dynamically expanding disk by compacting it. For more information, see Compacting dynamically expanding virtual hard disks.
Pzhar please send me premium file. I am going to give exam on Tuesday. thanks in advance
[email protected]
Do it in your lab, the answer is correct.
You should check your lab 😀
My dynamic VHDX is using only 4 MB of disk space… – it can take up to 10GB though but it’s not using this disk space at the time of creation!
PS C:\Users\Administrator> New-IscsiVirtualDisk -Path C:\usr\Disk2.vhdx -SizeBytes 10GB
ClusterGroupName :
ComputerName : SRV-ST-PH-10-05
Description :
DiskType : Dynamic
HostVolumeId : {06EDBDCF-50A3-11E5-80B1-806E6F6E6963}
LocalMountDeviceId :
OriginalPath :
ParentPath :
Path : C:\usr\Disk2.vhdx
SerialNumber : 93F4F6FB-7E67-44AF-A7CE-16849969E388
Size : 10737418240
SnapshotIds :
Status : NotConnected
VirtualDiskIndex : 1842107301
PS C:\Users\Administrator> Get-ChildItem C:\usr
Directory: C:\usr
Mode LastWriteTime Length Name
—- ————- —— —-
d—- 08.09.2015 14:07 snmp
-a— 23.09.2016 10:29 4194304 Disk2.vhdx
I think the answer is correct, because it is asking “is using not used”. Maybe we can use “will” instead of ” is using” then will be easy to understand. Thanks.