Factors for Calculating Recovery Time Objective
Which two factors must be considered while calculating the RTO? (Choose two.)
Community Votes
50% of anonymous learners picked answer BD. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The exam tests the distinction between RTO (time to restore) and RPO (data loss tolerance), with the common trap being the selection of backup frequency or data loss limits.
This question tests the key factors involved in calculating the Recovery Time Objective (RTO) within a Business Continuity Plan (BCP). It establishes that RTO is driven by business impact analysis (priority) and technical recovery procedures.
Candidates often select D and E because they relate to backups and data loss, which are primary drivers for Recovery Point Objective (RPO), not RTO.
Community Discussion (5 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The Recovery Time Objective (RTO) is defined as the maximum targeted period of time in which a business process must be restored after a disaster. To calculate this, two main categories of information are required: Business Impact Analysis (BIA) and Technical Recovery Strategies. Option A is correct because the 'importance and priority' of systems determines the urgency; critical systems require shorter RTOs. Option B is correct because the 'steps needed to mitigate or recover' represent the technical complexity and duration of the restoration process. The sum of these priorities and procedural steps defines the achievable RTO.Why the Other Options Are Wrong
Option D (backup frequency) and Option E (maximum tolerable data loss) are incorrect because they define the Recovery Point Objective (RPO). RPO measures how much data can be lost, whereas RTO measures how long the system can be down. While backup speed affects RTO, the frequency of backups does not determine the time to restore the service itself. Option C (cost of lost data) is a financial metric used during the Business Impact Analysis to prioritize systems (Option A), but it is not a direct factor in the calculation of the time objective itself.Community Comment Notes
Community comments show significant confusion between RTO and RPO. One user provided an analogy comparing RPO to 'bread you can afford to lose' and RTO to 'time out of business,' highlighting the conceptual difference. Another comment incorrectly argued for AB based on TechTarget definitions, while others mistakenly selected options related to backup frequency (D), confusing the operational mechanics of backups with the strategic definition of RTO.Official Reference
- https://www.techtarget.com/whatis/definition/recovery-time-objective-RTO
- NIST SP 800-34 Rev. 1
- Cisco Data Center Unified Computing Best Practices Guide
Exam Strategy
Always distinguish between 'Time' (RTO) and 'Data Loss' (RPO) in your head. If an option mentions 'amount of data', 'frequency of backups', or 'tolerable loss', it is describing RPO, not RTO.
Frequently Asked Questions
Why is backup frequency (Option D) not part of RTO?
Backup frequency determines how much data is lost (RPO), not how long it takes to bring the system back online (RTO).
Does cost of downtime affect RTO calculation?
Cost drives the prioritization (Option A), but the actual calculation relies on the technical steps (Option B) required to restore service.