Which metrics are commonly tracked to evaluate the effectiveness of a DR test?

Which metrics are commonly tracked to evaluate the effectiveness of a DR test?

• A. Office network uptime.
• B. Color of server racks.
• C. Test success rate, recovery time, data consistency, failover duration, and post-test remediation items.
• D. Number of emails sent during test.

Answer: (C)

The main concept being tested is how to measure the effectiveness of a disaster recovery (DR) test. In a DR exercise, you want concrete indicators that show whether critical services can be restored, how quickly, and with acceptable data integrity. The metrics that capture this are the test success rate (did the planned steps execute as intended?), recovery time (how long it takes to bring systems back), data consistency (is restored data in sync with the source within the allowed window), failover duration (how long it takes to switch over to the DR environment), and post-test remediation items (a documented set of actions to fix gaps and improve the plan). Together, these metrics assess operational performance, timing against objectives, data protection, and actionable improvements, which is exactly what helps organizations gauge DR readiness. Other options don’t fit because they don’t measure DR effectiveness: office network uptime is a broad, ongoing metric not specific to a DR test's success or timing; the color of server racks has no bearing on recovery capabilities; and the number of emails sent during the test doesn’t reflect recovery success, data integrity, or identified gaps and corrective actions.

The main concept being tested is how to measure the effectiveness of a disaster recovery (DR) test. In a DR exercise, you want concrete indicators that show whether critical services can be restored, how quickly, and with acceptable data integrity. The metrics that capture this are the test success rate (did the planned steps execute as intended?), recovery time (how long it takes to bring systems back), data consistency (is restored data in sync with the source within the allowed window), failover duration (how long it takes to switch over to the DR environment), and post-test remediation items (a documented set of actions to fix gaps and improve the plan). Together, these metrics assess operational performance, timing against objectives, data protection, and actionable improvements, which is exactly what helps organizations gauge DR readiness.

Other options don’t fit because they don’t measure DR effectiveness: office network uptime is a broad, ongoing metric not specific to a DR test's success or timing; the color of server racks has no bearing on recovery capabilities; and the number of emails sent during the test doesn’t reflect recovery success, data integrity, or identified gaps and corrective actions.