Factors for Calculating Recovery Time Objective
Short answer
AB The importance/priority of systems and the steps needed to recover are the two factors considered when calculating RTO.
Question
Key Takeaways
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.
Common mistake: 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.
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
These links open the official vendor documentation in a new tab.
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?
Does cost of downtime affect RTO calculation?
Community Votes
50% of anonymous learners picked answer BD. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 5 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 5
-
Doobiedoo 👍 5Imagine you're running a bakery. RPO (Recovery Point Objective): How much bread can you afford to lose? This is your RPO. It's about the amount of data (or in this case, baked goods) you're willing to lose. Example: If your RPO is 2 hours, you can afford to lose up to 2 hours worth of baked goods in case of a disaster. RTO (Recovery Time Objective): How long can you be out of business before it's too costly? This is your RTO. It's about the amount of time it takes to get back up and running. Example: If your RTO is 4 hours, you need to be able to reopen your bakery within 4 hours of a disaster. Relating to the options: Options B and D directly relate to RTO because they focus on the time it takes to recover from a disaster (steps to recover and backup restoration time). Option A is about the importance of systems, not the time to recover. Option E is about the amount of data loss (RPO), not the time to recover (RTO). In essence: RPO is about data loss. * RTO is about time to recover.
-
famov66542 👍 2But it talks about A & E: "By understanding what is running and what the value is of all the running systems and applications, it becomes possible to calculate RTO. Keep in mind, however, there can be different RTO requirements based on application priority as determined by the value the application brings to the organization. Calculating RTO requires determining how quickly the recovery process for a given application, service, system or data needs to happen after a major incident based on the loss tolerance the organization has for that application, service, system or data as part of its BIA. Defining the loss tolerance involves how much operational time an organization can afford (or is willing) to lose after an incident before normal business operations must resume." https://www.techtarget.com/whatis/definition/recovery-time-objective-RTO
-
bdp123 👍 2https://www.techtarget.com/whatis/definition/recovery-time-objective-RTO
-
Redrum702 👍 1Answer is CD: When determining the Recovery Time Objective (RTO), several important factors should be considered: Cost of Downtime: Calculate the financial implications of service interruptions. This includes lost revenue, operational costs, and potential penalties for non-compliance with service level agreements (SLAs). Data Backup Frequency: Consider how often backups are performed. More frequent backups can reduce the amount of data loss and help in quicker recovery.
-
kalulosu 👍 1Correct answer is A & B. Backup-related is RPO...
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.