The statement that SnapLock volumes are supported on the gFiler appliance is not true. A gFiler, also known as a NetApp V-Series or Gateway system, was a product that virtualized third-party storage arrays. This architecture prevented the use of features that required deep integration with the physical disk layer and the WAFL (Write Anywhere File Layout) file system. SnapLock's WORM (Write-Once, Read-Many) functionality is one such feature, as it relies on low-level controls to enforce data immutability, which was not possible on the virtualized LUNs presented by a gFiler.

A: This is false because SnapLock is available in two distinct modes: SnapLock Compliance and SnapLock Enterprise, catering to different regulatory and governance requirements.

B: This is false because SnapLock is fully compatible with SnapMirror, allowing for the replication of WORM-protected data to a disaster recovery site.

C: This is false because setting a retention period on a per-file basis is a fundamental capability of the SnapLock feature, allowing for granular control over data immutability.

1. NetApp TR-4570: SnapLock Best Practices and Implementation Guide. Section 2

"SnapLock Overview

" states

"SnapLock is available in two modes: SnapLock Compliance (SLC) and SnapLock Enterprise (SLE)." This document also confirms in Section 6

"SnapLock and SnapMirror

" that "SnapLock supports SnapMirror technology for disaster recovery." (Supports options A and B being true statements).

2. NetApp ONTAP 9 Documentation

"Manage WORM storage using SnapLock." This documentation describes the process of committing files to WORM

which involves setting a retention period on individual files using commands like touch -t. (Supports option C being a true statement).

3. NetApp TR-3437: V-Series Best Practices and Implementation Guide. In historical versions of this technical report

the "Unsupported Features" section explicitly listed SnapLock. The core reason is that V-Series systems virtualize back-end storage

and features requiring low-level WAFL and disk block manipulation

like SyncMirror

MetroCluster

and SnapLock

were not supported. (Supports option D being a false statement).