nerdexam
Broadcom-VMware

2V0-622D · Question #106

In vSphere 6.5, a virtual machine is thinly-provisioned on a VMFS6 datastore. The administrator deleted a large file within the guest OS. The freed blocks in the datastore are no longer needed by the

The correct answer is C. UNMAP. VAAI UNMAP was introduced in vSphere 5.0 to allow the ESXi host to inform the backing storage that files or VMs had be moved or deleted from a Thin Provisioned VMFS datastore. This allowed the backing storage to reclaim the freed blocks. There was no way of doing this previously,

Section 3 – Configure and Administer vSphere 6.5 Storage

Question

In vSphere 6.5, a virtual machine is thinly-provisioned on a VMFS6 datastore. The administrator deleted a large file within the guest OS. The freed blocks in the datastore are no longer needed by the VM. Which feature in vSphere 6.5 allows the backing storage to automatically reclaim the freed blocks?

Options

  • AATS
  • BDefrag
  • CUNMAP
  • DAuto Reclaim

How the community answered

(48 responses)
  • A
    2% (1)
  • B
    6% (3)
  • C
    90% (43)
  • D
    2% (1)

Explanation

VAAI UNMAP was introduced in vSphere 5.0 to allow the ESXi host to inform the backing storage that files or VMs had be moved or deleted from a Thin Provisioned VMFS datastore. This allowed the backing storage to reclaim the freed blocks. There was no way of doing this previously, resulting in many customers with a considerable amount of stranded space on their Thin Provisioned VMFS datastores.

Topics

#UNMAP#VMFS6#thin provisioning#block reclaim

Community Discussion

No community discussion yet for this question.

Full 2V0-622D Practice