From which storage resources can a thin clone be created?

Question

Options

• AVMFS datastore and vVol datastore
• BFile system and VMFS datastore
• CFile system and thin LUN
• DThin LUN and consistency group

• B
  3% (1)
• C
  94% (30)
• D
  3% (1)

Explanation

Option C is correct because thin clones can only be created from storage resources that natively support thin provisioning at the block or file level - specifically a file system (such as a NetApp FlexVol volume) and a thin LUN. Both resources share their underlying data blocks with the clone, making the operation space-efficient without requiring a full physical copy.

Why the distractors are wrong:

• A (VMFS and vVol): These are VMware-layer constructs built on top of storage resources, not the underlying storage primitives from which thin clones originate.
• B (File system and VMFS): VMFS is a VMware file system that resides on a LUN - it's a guest-layer abstraction, not a base storage resource eligible as a thin clone source.
• D (Thin LUN and consistency group): Consistency groups are a data protection/grouping mechanism used for snapshot coordination, not a storage resource from which a clone can be created.

Memory tip: Think "thin clone, thin source" - a thin LUN is the block-level thin resource, and the file system (volume) is the file-level one. Both are native storage layer objects, which is the key distinction from VMware-layer objects like VMFS or vVols.

No community discussion yet for this question.