NS0-528 · Question #8
Your customer wants to use tamper-proof Snapshot copies on a SnapMirror destination volume only. You successfully created a SnapMirror relationship using a SnapMirror policy that contains the…
The correct answer is A. volume modify -snapshot-locking-enabled. Although the SnapMirror policy includes rules for retaining Snapshot copies, the ability to make them tamper-proof (i.e., locked) depends on enabling snapshot locking on the destination volume. You must explicitly run: volume modify -volume <vol_name> -snapshot-locking-enabled…
Question
Your customer wants to use tamper-proof Snapshot copies on a SnapMirror destination volume only. You successfully created a SnapMirror relationship using a SnapMirror policy that contains the following rules:
After initializing, you are able to delete a daily Snapshot copy. Which command did you need to modify to enable the tamper-proof Snapshot copies as specified in the policy?
Exhibit
Options
- Avolume modify -snapshot-locking-enabled
- Bvolume snaplock modify -privileged-delete
- Cvserver modify -snapshot-policy
- Dvolume snapshot modify -expiry-time
How the community answered
(41 responses)- A83% (34)
- B10% (4)
- C2% (1)
- D5% (2)
Explanation
Although the SnapMirror policy includes rules for retaining Snapshot copies, the ability to make them tamper-proof (i.e., locked) depends on enabling snapshot locking on the destination volume. You must explicitly run: volume modify -volume <vol_name> -snapshot-locking-enabled true Without this setting, SnapMirror-created Snapshot copies can still be deleted manually. Enabling snapshot-locking ensures that retention rules (like the 5-day daily rule in your policy) are enforced and Snapshots are immutable.
Topics
Community Discussion
No community discussion yet for this question.