What is a characteristic of thin clones?

Question

Options

• AThin clones reflect changes to properties on the Base LUN made by a user.
• BThe source snapshot cannot be deleted after a thin clone is created.
• CData protection is main use case for thin clones.
• DThin Clones are supported for snapshots of thick LUNs.

• A
  2% (1)
• B
  85% (41)
• C
  8% (4)
• D
  4% (2)

Explanation

Option B is correct because a thin clone is built on top of a source snapshot - it uses that snapshot as its baseline, storing only the differences (delta). Since the thin clone depends on the snapshot to reconstruct its full data, the storage system enforces a dependency lock, preventing deletion of the source snapshot as long as the thin clone exists.

Why the distractors are wrong:

• A is false because thin clones are independent, point-in-time copies; property changes on the base LUN do not propagate to the clone after it is created.
• C is false because data protection is the primary use case for snapshots, not thin clones. Thin clones are typically used for dev/test workflows or creating writable copies without consuming full storage.
• D is false because thin clones are only supported for snapshots of thin LUNs, not thick LUNs, since thick LUNs pre-allocate all their storage and don't use the same underlying provisioning model.

Memory tip: Think of the source snapshot as a "foundation slab" - the thin clone is a building sitting on it. You cannot demolish the slab (delete the snapshot) while the building (clone) still stands on top of it.

No community discussion yet for this question.