In a DR test, which metric indicates how quickly services resume after failover?

In a DR test, which metric indicates how quickly services resume after failover?

• A. Test duration.
• B. Recovery time.
• C. Data integrity.
• D. User satisfaction.

Answer: (B)

Recovery time is about how long it takes to get services back online after failover. In a DR test, you measure the elapsed time from when the disruption starts (or when you trigger the failover) to the moment the critical services are fully restored and usable. This directly shows how quickly the failover process works and lets you gauge whether your recovery targets are met, often framed as the Recovery Time Objective (RTO) or the actual MTTR. The other options don’t capture that speed: test duration is the total time you run the test, data integrity checks data correctness across systems, and user satisfaction reflects how users perceive the experience rather than the technical restoration speed.

Recovery time is about how long it takes to get services back online after failover. In a DR test, you measure the elapsed time from when the disruption starts (or when you trigger the failover) to the moment the critical services are fully restored and usable. This directly shows how quickly the failover process works and lets you gauge whether your recovery targets are met, often framed as the Recovery Time Objective (RTO) or the actual MTTR. The other options don’t capture that speed: test duration is the total time you run the test, data integrity checks data correctness across systems, and user satisfaction reflects how users perceive the experience rather than the technical restoration speed.