NS0-528 · Question #74
A customer wants to enable tamper-proof Snapshot copies on volume LockingVolume, which is hosted on SVM LockingSVM. They have created the Snapshot policy, including the required retention set…
The correct answer is D. snaplock compliance-clock initialize -node *. To enable tamper-proof (locked) Snapshot copies using SnapLock, the SnapLock Compliance Clock must be initialized on all nodes in the cluster. Without initializing this clock, locked Snapshots cannot be created, even if the policy and retention settings are configured.
Question
A customer wants to enable tamper-proof Snapshot copies on volume LockingVolume, which is hosted on SVM LockingSVM. They have created the Snapshot policy, including the required retention set. However, when they apply the policy to a volume, the Snapshot copies are not locked. Which command must the customer issue before tamper-proof Snapshot copies can be enabled?
Options
- Avolume modify -volume LockingVolume -anti-ransomware-state enable
- Bvolume modify -volume LockingVolume -snapdir-access false
- Csnaplock event-retention apply -vserver LockingSVM
- Dsnaplock compliance-clock initialize -node *
How the community answered
(51 responses)- A12% (6)
- B8% (4)
- C4% (2)
- D76% (39)
Explanation
To enable tamper-proof (locked) Snapshot copies using SnapLock, the SnapLock Compliance Clock must be initialized on all nodes in the cluster. Without initializing this clock, locked Snapshots cannot be created, even if the policy and retention settings are configured.
Topics
Community Discussion
No community discussion yet for this question.