Question

Difficulty: MediumResilience, High Availability, and Redundancy

A security architect is evaluating resilience specifications for an enterprise infrastructure redesign. Match each business availability metric on the left with its corresponding definition on the right.

  • Recovery Time Objective (RTO)The target duration of time within which a system or process must be restored after a disruption.
  • Recovery Point Objective (RPO)The maximum acceptable amount of data loss measured in time prior to an outage.
  • Mean Time Between Failures (MTBF)The predicted elapsed operational time between inherent failures of a system during normal operation.
  • Mean Time To Repair (MTTR)The average time required to troubleshoot, fix, and restore a failed component to full operation.

Answer

Recovery Time Objective (RTO) matches the target duration of time within which a system must be restored. Recovery Point Objective (RPO) matches the maximum acceptable amount of data loss measured in time. Mean Time Between Failures (MTBF) matches the predicted elapsed operational time between failures. Mean Time To Repair (MTTR) matches the average time required to troubleshoot, fix, and restore a failed component.
Each availability metric directly matches its standard security architecture definition: RTO specifies target restoration duration, RPO specifies maximum allowable data loss window, MTBF calculates expected operational lifespan between failures, and MTTR measures repair turnaround time.

Step-by-Step Solution

1
Differentiate downtime metrics (RTO) from data loss metrics (RPO)
RTO focuses on elapsed time to restore service (downtime duration), whereas RPO focuses on point-in-time data tolerance (data loss window).
Business impact analyses rely on distinguishing system recovery duration from data backup currency.
2
Differentiate component reliability metrics (MTBF) from maintainability metrics (MTTR)
MTBF measures expected operational uptime between failures, while MTTR measures the time required to perform repair actions once a failure occurs.
Hardware resilience planning requires separating failure frequency expectations from maintenance restoration speeds.

Key Concept

High Availability and Resilience Business Metrics
Rate this question