Understanding RPO vs RTO in Disaster Recovery

N10-009 By islever Editorial Last updated

Explain disaster recovery (DR) concepts.

Short answer

A RPO (Recovery Point Objective) defines the maximum acceptable amount of data loss measured in time.

Question

As part of a recovery strategy, a network administrator needs to make sure no more than eight hours of data loss occurs. Which of the following DR metrics describes this requirement?
  1. RPO Correct Answer
  2. MTTR
  3. RTO
  4. MTBF

Key Takeaways

The trap is confusing RTO (downtime duration) with RPO (data loss window); focus on whether the constraint is about service availability or data integrity.

This question tests your ability to distinguish between RPO and RTO by identifying which metric governs acceptable data loss limits in a DR strategy.

Common mistake: Choosing RTO because it sounds like 'time,' but RTO measures operational downtime, whereas the scenario explicitly limits data loss, which is RPO's domain.

Expert Analysis

The scenario specifies a limit on data loss measured in time (no more than eight hours). This is the precise definition of the Recovery Point Objective (RPO). RPO determines the maximum age of files that must be recovered from backup storage for normal operations to resume after a disaster, effectively quantifying acceptable data loss.

Recovery Time Objective (RTO) measures the duration of downtime allowed before services must be restored. It addresses how quickly systems come back online, not how much data is lost. Comments suggesting RTO confuse the speed of recovery with the volume of data retention.

MTTR (Mean Time To Repair) and MTBF (Mean Time Between Failures) are reliability metrics unrelated to specific disaster recovery point-in-time constraints. The key distinction lies between 'how long we can be down' (RTO) versus 'how much data can we afford to lose' (RPO).

Official Reference

https://www.comptia.org/contentguides/network-plus-content-guide

This link opens the official vendor documentation in a new tab.

Exam Strategy

When encountering DR scenarios, isolate the noun being constrained: if it is 'data' or 'backups,' select RPO; if it is 'service,' 'uptime,' or 'hours of downtime,' select RTO. Memorize 'RPO = Point' (data state) and 'RTO = Time' (duration).

Frequently Asked Questions

What is the difference between RPO and RTO?

RPO (Recovery Point Objective) is the maximum acceptable data loss measured in time. RTO (Recovery Time Objective) is the maximum acceptable downtime before services must be restored.

How does RPO affect backup frequency?

A shorter RPO requires more frequent backups to ensure less data is lost. For example, an 8-hour RPO means backups must occur at least every 8 hours.

More N10-009 FAQ →

Discussion 3 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 3

  1. Hanamin9896 👍 2 Answered A
    RPO (Recovery Point Objective) = Maximum acceptable amount of data loss measured in time.
  2. ERB14 👍 1 Answered A
    RPO (Recovery Point Objective): Refers to the maximum acceptable amount of data loss measured in time (e.g., eight hours). It determines how frequently backups must be performed to limit lost data during an outage.
  3. Skri113xX 👍 1 Answered C
    C seems like the most plausible answer, though [Other Option] is a clever distractor.

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Practice All N10-009 Questions

Access 100 questions with complete answers and detailed explanations.

View Full N10-009 Practice Test →

← Back to N10-009 Study Guide