Which are two features of VMware Virtual Volumes? (Select 2)

Question

Options

• AStored in storage containers that are created in the storage system
• BRequire vSphere 5.0 at a minimum to run
• CStorage objects that the storage administrator creates manually
• DSupports snapshots at the VM level

• A
  88% (50)
• B
  7% (4)
• C
  4% (2)
• D
  2% (1)

Explanation

The question likely has two correct answers: A and D. Option A is correct because vVols are stored in Storage Containers - logical capacity pools defined directly on the storage array by the vendor, accessed by vSphere through Protocol Endpoints. Option D is also correct because a defining advantage of vVols is VM-level snapshot granularity, shifting storage operations from the traditional LUN level down to individual VM or VMDK level.

Why the distractors are wrong:

• B is wrong because vVols were introduced in vSphere 6.0, not 5.0 - selecting 5.0 is a common trap based on confusing vVols with older vSphere features.
• C is wrong because individual vVols are created automatically by vSphere during VM provisioning - the storage administrator creates the Storage Container, not each vVol object manually.

Memory tip: Think of vVols as "VM-centric storage" - everything shifts from the array's perspective (LUNs) to the VM's perspective (objects in containers). The two hallmarks to remember are containers on the array (where they live) and VM-level operations like snapshots (what they enable). If an answer sounds like "old LUN-based storage thinking" or cites vSphere 5.x, it's almost certainly wrong.

No community discussion yet for this question.