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

Questions 16–20

1. 16foundation · easy

   Why is it important to regularly test SVM DR backup data rather than assuming the replication is working?

   • ABecause testing is the only way to measure replication performance
   • BBecause replication status alone does not guarantee that the data is recoverable and usable
   • CBecause testing helps reduce the cost of the DR solution
   • DBecause testing is required by all regulatory compliance standards
   Reveal Solution Discussion Select an answer first
2. 17expert · hard

   During an SVM DR test failover, the destination SVM's volumes mount successfully, but the application on the destination reports database corruption. The administrator confirms that the source database is healthy. What is the most likely cause of the corruption on the destination?

   • AThe replication schedule was paused, causing the destination to have stale data.
   • BThe destination SVM's volumes were mounted as read-only, preventing the application from writing.
   • CThe SVM DR relationship was in a 'InSync' state, but the last replicated snapshot was taken during an inconsistent database state.
   • DThe test failover was performed on the source SVM instead of the destination SVM.
   Reveal Solution Discussion Select an answer first
4. 18foundation · easy

   Which SVM DR relationship state indicates that the destination SVM is ready to be used for a test failover?

   • AUninitialized
   • BOut-of-Sync
   • CBroken
   • DIn-Sync
   Reveal Solution Discussion Select an answer first
5. 19expert · hard

   An administrator is monitoring an SVM DR relationship and notices that the 'Lag Time' is increasing steadily. The relationship state is 'InSync', but the lag time is now over 24 hours. What is the most appropriate action?

   • AInvestigate the cause of the increasing lag, such as network bandwidth or source SVM performance, and adjust the replication schedule if needed.
   • BBreak the SVM DR relationship and re-create it to reset the lag time.
   • CPerform a test failover to verify that the lag time does not affect data integrity.
   • DIgnore the lag time because the relationship is 'InSync'.
   Reveal Solution Discussion Select an answer first
6. 20application · medium

   A storage administrator needs to validate the disaster recovery readiness of a critical SVM DR relationship without impacting production. The administrator plans to run a test failover during business hours. Which action must be taken to ensure the test does not disrupt production?

   • AInitiate a test failover from the destination SVM; production I/O on the source SVM continues unaffected.
   • BPerform a full failover to the destination SVM, then redirect client traffic back after validation.
   • CBreak the SVM DR relationship and re-create it after testing to avoid any impact.
   • DPause replication and manually copy the latest snapshot to the destination for validation.
   Reveal Solution Discussion Select an answer first