Which two datastore types store the components of a virtual machine as a set of objects? (Choose two.)

VMware vSAN and vSphere Virtual Volumes (vVols) are both object-based storage architectures. vSAN is a software-defined, object-based storage solution that stores virtual machine components, such as the VM home namespace, VMDKs, and snapshots, as individual objects. These objects are then distributed across the vSAN cluster according to storage policies. vVols is a storage framework that enables storage arrays to become VM-aware. It maps virtual disks and other VM files directly to objects, called virtual volumes, on the storage system. This shifts VM storage management from the LUN/volume level to the individual virtual machine level, treating each component as a distinct object.

A. VMware Virtual Machine File System (VMFS) is a block-based clustered file system that stores VM components as files within a directory structure on a LUN, not as native storage objects.
C. Network File System (NFS) 3 is a file-based protocol. It presents a network share where VM components are stored as a collection of files in a directory.
E. Network File System (NFS) 4.1, while offering enhancements over version 3, remains a file-based protocol that stores VM components as files on a network share.

1. VMware vSphere Documentation

"vSphere Storage

" Chapter 1: vSphere Storage

Section: Storage Types.

This section explicitly contrasts the different storage types. It describes vSAN as an "object-based storage solution" and vVols as a technology where "Virtual volumes are objects exported by the storage array." In contrast

it describes VMFS as a "clustered file system" and NFS as a "file-sharing protocol."

2. VMware vSphere Documentation

"Administering VMware vSAN

" Chapter 1: vSAN Concepts

Section: Objects and Components.

"vSAN stores and manages data in the form of flexible data containers called objects... When you provision a virtual machine on a vSAN datastore

vSAN creates a set of objects for each virtual disk (VMDK)

the VM home namespace

and the VM swap object."

3. VMware vSphere Documentation

"vSphere Storage

" Chapter 11: Working with vSphere Virtual Volumes

Section: vSphere Virtual Volumes Concepts.

"Virtual Volumes are objects exported by the storage array... They are managed on the storage hardware through VASA (vSphere APIs for Storage Awareness) provider." This confirms that vVols represent VM components as objects on the array itself.