Exam 5V0-21.19 topic 1 question 22 discussion

B https://blogs.vmware.com/virtualblocks/2018/09/10/vmware-vsan-6-7u1-storage-reclamation-trim-unmap/

I also think B should be the answer, but always thinking if it is a tricky question. I found such an article but not completely the same scenario with the question. I want to encourage people to think in a different manner :) https://globalvirtualdiary.wordpress.com/2021/02/20/vsan-6-7-reclaim-disk-space-by-converting-thick-provisioned-vms-to-thin-on-vsan/

Is correct as per my notes

For sure B..No way D as even if you thin provision, once the OS grows it doesnt reclaim space because it is Thin provisioned, actually its current size remains same even if you delete files/directories and Hence B is correct

Yes, B is correct. TRIM/UNMAP can also be enabled using PowerCLI. Query TRIM/UNMAP status: Get-Cluster | Where-Object {$_.VsanEnabled -eq $true} | Get-VsanClusterConfiguration | Select-Object Name,GuestTrimUnmap | Format-Table -AutoSize Enable TRIM/UNMAP: Get-Cluster | Where-Object {$_.VsanEnabled -eq $true} | Set-VsanClusterConfiguration -GuestTrimUnmap:$true

The correct answer is B vSAN 6.7 U1 and later support guest operating system initiated ATA Trim and SCSI Unmap requests for data included in the VM virtual disks. The ESXi host issues Trim and Unmap requests to the storage devices for VM swap files and directories mapped to vSAN objects on thin- provisioned virtual disks. Performance details about Trim/Unmap can be viewed in the Trim/Unmap throughput or latency Performance graphs for each host belonging to a vSAN cluster. To view these charts, click the Monitor tab for the host and click vSAN > Performance > BACKEND. The Trim/Unmap feature is not enabled by default. You enable Trim/Unmap using the RVC Console. Trim/Unmap is supported but disabled by default in vSAN 6.7 U1. The following performance details are available for Trim/Unmap: • Recovery Unmap Throughput • Unmap Throughput • Latency • Disable

The correct answer is B vSAN 6.7 U1 and later support guest operating system initiated ATA Trim and SCSI Unmap requests for data included in the VM virtual disks. The ESXi host issues Trim and Unmap requests to the storage devices for VM swap files and directories mapped to vSAN objects on thin- provisioned virtual disks. Performance details about Trim/Unmap can be viewed in the Trim/Unmap throughput or latency Performance graphs for each host belonging to a vSAN cluster. To view these charts, click the Monitor tab for the host and click vSAN > Performance > BACKEND. The Trim/Unmap feature is not enabled by default. You enable Trim/Unmap using the RVC Console. Taken from vSAN 6.7 Deploy and Manage Lecture Manual

I would go with B. Even if you "assign a storage policy with thin provisioning" (vSAN default policy) the space won't be reclaimed if the TRIM/UNMAP feature is not enabled for the vSAN cluster (even though it should be initially enabled, but it could be disabled). This feature is enabled initially globally for the cluster: https://blogs.vmware.com/virtualblocks/2018/09/10/vmware-vsan-6-7u1-storage-reclamation-trim-unmap TRIM/UNMAP is enabled per vSAN cluster using the RVC Console: https://storagehub.vmware.com/t/vsan-space-efficiency-technologies/unmap-trim-space-reclamation-on-vsan-1/

B trim / unmap

By default it is thin disk why need to assign storage policy with thin ?

B is correct