Question 520
A server operations team encounters the following situation: A recovery team confuses a four-hour RTO with four-hour backup frequency and overlooks the time required to rebuild the OS and restore data. Which sustained operational control best reduces the likelihood of this same issue recurring?
Explanation
Correct Answer
This control targets the underlying recurrence risk: Recovery time is a service-restoration deadline, not a backup interval. It builds validation into the affected workflow and supports the expected recovery result: A full drill returns the service within four hours.
Incorrect Answers
This control addresses a different scenario: A security audit cannot locate the current hardening baseline because the only copy is on the server whose access is being investigated. That event's root mechanism was operational documents cannot depend solely on the system they support. The described incident instead arises from: Recovery time is a service-restoration deadline, not a backup interval.
This control addresses a different scenario: A new virtual cluster's configuration diagram lists server names but excludes the VLAN, storage and power dependencies needed for outage response. That event's root mechanism was incomplete infrastructure documentation conceals shared failure points. The described incident instead arises from: Recovery time is a service-restoration deadline, not a backup interval.
This control addresses a different scenario: A business claims five-minute RPO without measuring backup or replication interval, while restore tests reveal 50 minutes of data loss. That event's root mechanism was recovery point objectives describe tolerated data age, not recovery duration. The described incident instead arises for this situation: Recovery time is a service-restoration deadline, not a backup interval.