During an annual audit, a systems administrator discovers that the disaster-recovery runbook for the organization's on-premises file server is missing one critical metric. Because of the omission, technicians are unsure how long the business can tolerate the file share being unavailable before they must activate the cold-standby system at a secondary site. Which item should be added to the recovery documentation to eliminate this uncertainty?
Mean time between failures
Uptime percentage specified in the service level agreement
The recovery time objective (RTO) states the maximum acceptable duration that a service may remain offline after an outage. When the RTO is documented, support staff know exactly how long they can spend restoring or failing over the file server before business impact becomes unacceptable. The recovery point objective (RPO) addresses allowable data loss, not service-outage duration. Mean time between failures (MTBF) measures hardware reliability and is unrelated to restoration deadlines. An SLA's uptime percentage is a contractual performance metric but does not specify a precise restoration window for an internal recovery process.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is the difference between RTO and RPO?
Open an interactive chat with Bash
Why is MTBF not applicable for determining file server downtime tolerance?
Open an interactive chat with Bash
How does an SLA's uptime percentage differ from RTO?