A colleague asks how the recovery time objective and the recovery point objective differ in what they measure. Which explanation draws the distinction most accurately?
- ARTO measures how much data may be lost, while RPO measures how long recovery may take
- BRTO caps the tolerable outage duration, while RPO caps the tolerable amount of data loss Correct
- CBoth measure downtime, but RTO applies to hardware and RPO applies to software
- DRTO and RPO are two names for the same downtime target used by different vendors
Why A is wrong: This states the correct pair of ideas but swaps the labels, which is the classic trap; RTO is about time to recover and RPO is about data loss.
Why B is correct: This correctly separates the two axes: RTO is time-to-restore service and RPO is the acceptable data-loss window measured in time.
Why C is wrong: The split by asset type is invented; neither metric is defined by hardware versus software, so this misstates both concepts.
Why D is wrong: Treating them as synonyms is a common beginner error, but they are distinct objectives that can hold very different values for the same system.