In the recovery scenario, how many hours are allocated to database recovery?

• A. 10 hours
• B. 14 hours
• C. 4 hours
• D. 8 hours

Answer: (C)

In a recovery scenario, the time allocated to bring back a system is driven by the recovery time objective (RTO) for that asset. Databases are usually among the most critical components because they hold essential data and support core business processes, so the plan targets a tight window to restore service and minimize downtime and data exposure. Four hours reflects a compressed recovery window that acknowledges the effort required to restore a database while prioritizing quick resumption of operations. Longer windows—such as eight, ten, or fourteen hours—would prolong downtime and are typically not acceptable for a mission-critical database in standard DR planning. That tighter four-hour allocation best aligns with the need to quickly recover the database after a disruption, which is why it’s chosen.