An administrator has been tasked with mitigating datastore capacity issues without datastore expansion. Which vSphere Storage vMotion migration option would achieve this mitigation? (Choose the best…

The correct answer is B. Thin-provisioned. Thin provisioning is the correct choice for conserving datastore capacity. A thin-provisioned virtual disk only consumes space on the datastore equal to the data actually written inside the VM - not the full configured disk size. For example, a 100 GB thin disk might only use…

Administrative and Operational Tasks

Question

An administrator has been tasked with mitigating datastore capacity issues without datastore expansion. Which vSphere Storage vMotion migration option would achieve this mitigation? (Choose the best answer.)

Options

ALazy-zeroed thick-provisioned
BThin-provisioned
CEager-zeroed thick-provisioned
DSame as format source

How the community answered

(33 responses)

A
9% (3)
B
70% (23)
C
3% (1)
D
18% (6)

Explanation

Thin provisioning is the correct choice for conserving datastore capacity. A thin-provisioned virtual disk only consumes space on the datastore equal to the data actually written inside the VM - not the full configured disk size. For example, a 100 GB thin disk might only use 20 GB on the datastore if the VM has only written 20 GB of data. This directly addresses capacity constraints without requiring datastore expansion. Lazy-zeroed thick (A) and eager-zeroed thick (C) both pre-allocate the full disk size on the datastore immediately, consuming maximum space. 'Same as format source' (D) preserves the existing disk format rather than converting to thin, so it would not help if the source disks are already thick-provisioned.

Topics

#Storage vMotion#thin provisioning#datastore capacity#disk format

Community Discussion

No community discussion yet for this question.

Full 2V0-21.20 Practice