FlexClone volumes consume space only when what occurs?

FlexClone volumes consume space only when what occurs?

• A. Equal to their parent volume immediately
• B. Only when modified blocks differ from the parent
• C. Proportionally to the Snapshot age
• D. Based on aggregate deduplication ratio

Answer: (B)

FlexClone volumes use a copy-on-write mechanism. When you create a clone from a parent (via a Snapshot), the clone initially shares the same data blocks as the parent, so no extra space is used up right away. Space is only consumed when you modify data in the clone: the system copies the original block to a new block in the clone and writes your changes there. Therefore, space usage starts and grows with the amount of data you modify in the clone. The other ideas don’t fit because the clone’s space isn’t determined by how old the Snapshot is, nor by a deduplication ratio, and it isn’t allocated immediately equal to the parent’s full size.

FlexClone volumes use a copy-on-write mechanism. When you create a clone from a parent (via a Snapshot), the clone initially shares the same data blocks as the parent, so no extra space is used up right away. Space is only consumed when you modify data in the clone: the system copies the original block to a new block in the clone and writes your changes there. Therefore, space usage starts and grows with the amount of data you modify in the clone.

The other ideas don’t fit because the clone’s space isn’t determined by how old the Snapshot is, nor by a deduplication ratio, and it isn’t allocated immediately equal to the parent’s full size.