VCP550 · Question #66
Which action should an administrator take to increase the size of a VMFS5 datastore from 2TB to 32TB?
The correct answer is B. Dynamically expand the original LUN and increase the size of the VMFS datastore. VMFS5 supports growing a datastore up to 64TB by expanding the underlying LUN on the storage array and then increasing the VMFS volume size to consume the new space.
Question
Which action should an administrator take to increase the size of a VMFS5 datastore from 2TB to 32TB?
Options
- ADynamically expand the original LUN and add a second share for the NFS datastore
- BDynamically expand the original LUN and increase the size of the VMFS datastore
- CDynamically expand the original LUN and add extents to the VMFS datastore
- DDynamically expand the original LUN and add extents to the NFS datastore
How the community answered
(26 responses)- A8% (2)
- B81% (21)
- C12% (3)
Why each option
VMFS5 supports growing a datastore up to 64TB by expanding the underlying LUN on the storage array and then increasing the VMFS volume size to consume the new space.
Adding a second share applies to NFS datastores, not VMFS datastores, and VMFS does not use NFS shares.
VMFS5 supports a single-volume datastore up to 64TB, so expanding from 2TB to 32TB is possible by first dynamically expanding the LUN on the storage array and then using the vSphere Client to increase the VMFS datastore size to use the reclaimed space. This approach is preferred over adding extents because it keeps the datastore as a single contiguous volume, simplifying management and avoiding the limitations of spanned volumes.
Adding extents is an older VMFS3-era approach for spanning multiple LUNs; VMFS5 supports direct LUN expansion and datastore growth without requiring extents.
NFS datastores do not use the VMFS filesystem or extents - mixing NFS terminology with a VMFS scenario is technically incorrect.
Concept tested: VMFS5 datastore expansion via LUN grow
Source: https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-storage/GUID-7601921E-D2F0-4E81-81FA-FB4AD2D7F67C.html
Topics
Community Discussion
No community discussion yet for this question.