Test and Verify Backup Data (SVM:DR) CERTIFIED-CYBER-RESILIENCY-EXPERT Practice Questions (Page 1)

Questions 1–5

1. 1foundation · easy

   During an SVM DR test failover, the destination SVM is not accessible. What is a common cause of this issue?

   • AThe destination SVM has too much storage
   • BThe source SVM is powered off
   • CThe replication relationship is in the 'In-Sync' state
   • DThe destination SVM is not in the In-Sync state
   Reveal Solution Discussion Select an answer first
2. 2expert · hard

   After performing an SVM DR test failover, an administrator discovers that the destination SVM's volumes are mounted but the data appears to be from several days ago, even though the relationship was 'InSync' before the test. What is the most likely explanation?

   • AThe SVM DR relationship was in a 'Test Failover' state, which automatically reverts to the last known good snapshot.
   • BThe destination SVM's volumes were mounted as read-only, preventing the latest data from being written.
   • CThe replication schedule was set to a daily schedule, and the last successful transfer occurred before the most recent data changes.
   • DThe test failover was performed on the source SVM, which caused the destination to use an older snapshot.
   Reveal Solution Discussion Select an answer first
4. 3application · medium

   An administrator is monitoring an SVM DR relationship and sees that the state is 'Broken'. What does this state indicate, and what is the appropriate action?

   • AThe relationship is no longer replicating; the administrator should investigate the cause and re-establish replication.
   • BThe relationship is temporarily paused; the administrator should wait for the next scheduled cycle.
   • CThe relationship is in a test failover; the administrator should clean up the test.
   • DThe relationship is healthy but the destination is temporarily offline.
   Reveal Solution Discussion Select an answer first
5. 4application · medium

   After completing a successful SVM DR test failover, an administrator needs to restore the original relationship state so that replication can resume normally. What is the correct next step?

   • ARun the 'SVM DR test failover cleanup' operation on the destination SVM.
   • BDelete the test SVM and re-create the SVM DR relationship from scratch.
   • CPerform a failover back to the source SVM and then re-synchronize the destination.
   • DLeave the test SVM in place and monitor it for any issues.
   Reveal Solution Discussion Select an answer first
6. 5foundation · easy

   What is the primary purpose of monitoring SVM DR replication?

   • ATo ensure that the backup data is current and reliable
   • BTo reduce the storage capacity used by the destination
   • CTo delete old snapshots automatically
   • DTo increase the speed of the source SVM
   Reveal Solution Discussion Select an answer first