RTO, RPO and MTD Explained for CISA and CISM

Recovery objectives appear in both exams, usually inside a scenario. Getting them straight earns easy marks.

The three terms

How they fit together

Think of a timeline around a disruption:

Who sets them

The business process owner sets recovery objectives, based on a business impact analysis. IT designs solutions to meet them. On the exam, an option where IT sets the RTO based on what servers can do is a trap.

What drives what

Classic exam scenarios

  1. Nightly backups, one-hour RPO. The issue is potential data loss far beyond tolerance.
  2. Recovery test took eight hours against a four-hour RTO. Analyze causes, then update the plan, resources or — with business approval — the RTO, and retest.
  3. Replication lag of two hours, RPO of 30 minutes. Actual capability does not meet the objective.
  4. Synchronous replication protects everything. No: it replicates corruption and ransomware too. You still need point-in-time backups.

Quick self-test

Related on Auditor Path

Sources

ISACA CISA and CISM exam content outlines (business continuity, disaster recovery and BIA subtopics).