Configure Tamperproof Snapshots CERTIFIED-CYBER-RESILIENCY-EXPERT Practice Questions (Page 6)

Questions 26–30

1. 26foundation · easy

   Which characteristic is essential for a snapshot to be considered 'tamperproof' in a NetApp environment?

   • AIt is encrypted at rest using a customer-managed key
   • BIt is stored on a different storage system than the source volume
   • CIt is created automatically on a daily schedule
   • DIt cannot be modified or deleted until its retention period expires
   Reveal Solution Discussion Select an answer first
2. 27application · medium

   A security team needs to be alerted if any tamperproof snapshot on a critical volume is deleted or modified. Which monitoring approach is most appropriate?

   • AReview the volume's performance metrics for unusual I/O.
   • BCheck the SnapMirror relationship status daily.
   • CConfigure an event alert for snapshot deletion and modification events in the cluster.
   • DMonitor the volume's used space to detect changes in snapshot size.
   Reveal Solution Discussion Select an answer first
4. 28application · medium

   After configuring tamperproof snapshots, an administrator wants to confirm that a specific snapshot is protected and will be retained for the full 30-day period. Which single command provides the most direct confirmation?

   • A'snapshot show -fields snaplock-expiry-time' for the specific snapshot.
   • B'snapmirror show' for the volume.
   • C'snapshot policy show' for the volume's policy.
   • D'volume show -fields snaplock-type' for the volume.
   Reveal Solution Discussion Select an answer first
5. 29expert · hard

   An administrator enabled SnapLock on a volume and created a snapshot policy with a 14-day retention. After 10 days, the administrator notices that the snapshots are not showing a 'snaplock-expiry-time' value. What is the most likely cause?

   • AThe snapshot policy was not applied to the volume after creation.
   • BThe SnapLock license is not installed on the cluster.
   • CThe volume is in enterprise mode, which does not display an expiry time until the retention period is about to end.
   • DThe SnapLock retention period was not configured in the snapshot policy, so the snapshots are not locked.
   Reveal Solution Discussion Select an answer first
6. 30expert · hard

   An administrator configured SnapLock compliance mode on a volume and applied a snapshot policy with a 10-day retention. After 5 days, the administrator attempts to delete a snapshot and receives an error. The administrator also notices that the 'snaplock-expiry-time' is 5 days in the future. What is the most likely reason for the error?

   • AThe SnapLock license is not activated on the cluster.
   • BThe snapshot policy was changed after the snapshot was created.
   • CThe snapshot is locked and cannot be deleted before the expiry time.
   • DThe volume is out of space, preventing snapshot deletion.
   Reveal Solution Discussion Select an answer first