2V0-621 · Question #121
Which datastore type can be extended to span several physical storage extents, including storage Area Network LUNs and local storage devices, in order to create a datastore that fits the needs of…
The correct answer is D. VMFS Datastores. VMFS datastores support spanning across multiple physical storage extents, including SAN LUNs and local disks, allowing flexible capacity expansion for virtual machines.
Question
Which datastore type can be extended to span several physical storage extents, including storage Area Network LUNs and local storage devices, in order to create a datastore that fits the needs of your virtual machines?
Options
- AVirtual SAN
- BNFS
- CiSCSI
- DVMFS Datastores
How the community answered
(42 responses)- B2% (1)
- C5% (2)
- D93% (39)
Why each option
VMFS datastores support spanning across multiple physical storage extents, including SAN LUNs and local disks, allowing flexible capacity expansion for virtual machines.
Virtual SAN (vSAN) is a software-defined storage solution that aggregates local host disks into a shared datastore cluster, but it does not span traditional SAN LUNs and local devices as extents.
NFS is a network file system protocol used to mount remote shares as datastores, and it does not support extent-based spanning across multiple physical storage devices.
iSCSI is a block storage transport protocol used to connect to LUNs over TCP/IP, not a datastore type that can be extended to span multiple physical extents.
VMFS (Virtual Machine File System) datastores can be extended by adding additional extents from different physical storage devices, including SAN LUNs and local storage. This spanning capability allows administrators to create larger logical datastores that exceed the size of a single physical LUN. No other datastore type in vSphere supports this multi-extent spanning behavior.
Concept tested: VMFS datastore extent spanning and expansion
Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-3A1CE585-5A8A-4B65-8B03-A38B35F4A3C2.html
Topics
Community Discussion
No community discussion yet for this question.