Snapshot copies for SnapLock volumes are deleted automatically according to the retention count set in the Snapshot schedule.

The statement is false. While a Snapshot schedule dictates when Snapshot copies are created and how many are retained for standard volumes, this process is fundamentally altered for SnapLock volumes. A Snapshot copy on a SnapLock volume cannot be deleted, even if it exceeds the retention count in the Snapshot policy, as long as it contains one or more files that are still under a WORM (Write-Once, Read-Many) retention period. The Snapshot copy itself is assigned a retention period that corresponds to the longest retention period of any WORM file it contains. Deletion can only occur after the SnapLock retention period for all contained files has expired.

The "True" option is incorrect because it overlooks the primary function of SnapLock, which is to enforce data immutability for a specified duration. This immutability extends to the Snapshot copies that contain the locked files. The SnapLock retention period takes precedence over the standard, count-based retention settings in a Snapshot policy, preventing automatic deletion until the WORM commitment is fulfilled.

1. NetApp ONTAP 9 Documentation

"SnapLock configuration and management guide": In the section "How SnapLock works with NetApp Snapshot copies

" it is explicitly stated: "A Snapshot copy on a SnapLock volume cannot be deleted if it contains one or more files that are under WORM retention. The Snapshot copy is assigned a retention period that is the same as the longest retention period of the WORM files in the Snapshot copy. The Snapshot copy expires when the retention period ends."

2. NetApp ONTAP 9 Documentation

"Logical storage management guide": The section "How Snapshot copy automatic deletion works" details the conditions for deletion and notes exceptions. It specifies that ONTAP cannot delete a Snapshot copy that is locked by any feature

with SnapLock being a primary example of such a lock.

3. NetApp ONTAP 9 Documentation

"Data protection and disaster recovery overview": In the chapter on "Data protection with SnapLock

" the documentation clarifies that Snapshot copies of SnapLock volumes are also protected by WORM. This implies their lifecycle is tied to the WORM retention dates of the data they contain

not just a simple retention count in a schedule.