D-UN-OE-23 · Question #7
Which two vVol object types can have a snapshot? (Select 2)
The correct answer is B. Data C. Mem. Data (B) and Mem (C) vVols can have snapshots because they represent the VM's persistent disk data and in-memory state, respectively - both of which are meaningful to capture at a point in time. When a snapshot is taken, a delta vVol is created for the Data vVol to track…
Question
Which two vVol object types can have a snapshot? (Select 2)
Options
- AConfig
- BData
- CMem
- DSwap
How the community answered
(35 responses)- A3% (1)
- B89% (31)
- D9% (3)
Explanation
Data (B) and Mem (C) vVols can have snapshots because they represent the VM's persistent disk data and in-memory state, respectively - both of which are meaningful to capture at a point in time. When a snapshot is taken, a delta vVol is created for the Data vVol to track changes, and a Mem vVol captures the RAM contents if the "snapshot the virtual machine's memory" option is selected.
Config (A) is wrong because the Config vVol holds metadata files like the VMX configuration and logs - these aren't snapshot targets since they don't represent a point-in-time workload state. Swap (D) is wrong because swap space is ephemeral; its contents are meaningless across power cycles or snapshots and are simply discarded.
Memory tip: Think "D for Disk, M for Memory" - the two things you'd actually want to freeze in time when snapshotting a running VM. Config and Swap are infrastructure plumbing, not stateful workload data.
Topics
Community Discussion
No community discussion yet for this question.