You create a new virtual disk in a storage pool by using the New Virtual Disk Wizard. You
discover that the new virtual disk has a write-back cache of 1 GB.
You need to ensure that the virtual disk has a write-back cache of 5 GB.
What should you do?
A.
Detach the virtual disk, and then run the Resize-VirtualDisk cmdlet.
B.
Detach the virtual disk, and then run the Set-VirtualDisk cmdlet.
C.
Delete the virtual disk, and then run the New-StorageSubSystemVirtualDisk cmdlet.
D.
Delete the virtual disk, and then run the New-VirtualDisk cmdlet.
http://windowsitpro.com/windows-server-2012-r2/set-windows-server-2012-r2-storage-space-write-back-cache
Very smartly worded answer should be D.
Not C: New-StorageSubsystemVirtualDisk
Allows the creation of a VirtualDisk object on a storage subsystem that does not support creation of storage pools.
https://technet.microsoft.com/en-us/library/hh848705(v=wps.630).aspx
Question says that a virtual disk has been created in a “storage pool” via the “New Virtual Disk Wizard” which means the answer is not C !
It isn’t possible to set a write-back cache custom size by using Server Manager Windows Server 2012 R2. By default, if you create a virtual disk using Server Manager, it will create a 1GB write-back cache if sufficient space exists on solid-state disk (SSD) storage in the pool.
If you want to customize the write-back cache size, use the Windows PowerShell cmdlets and the -WriteCacheSize parameter, for example:
New-VirtualDisk -StoragePoolFriendlyName “My Storage Pool” -FriendlyName TieredSpace -StorageTiers @($ssd_tier, $hdd_tier) -StorageTierSizes @(50GB, 300GB) -ResiliencySettingName Mirror -WriteCacheSize 2GB
Note: After a virtual disk is created, its WriteCacheSize can’t be modified.
After a virtual disk is created, its WriteCacheSize can’t be modified – this means it can’t be A or B.
create a new virtual disk and specify -writecachesize 5GB
Answer is D