Which components are essential in OT disaster recovery plan considering RTO and RPO?

Which components are essential in OT disaster recovery plan considering RTO and RPO?

• A. RTO and RPO metrics are optional.
• B. RTO should be shorter than the RPO.
• C. Defined maximum downtime (RTO) and data loss tolerance (RPO), with concrete values such as RTO 2 hours and RPO 15 minutes.
• D. RTO and RPO only apply to IT, not OT.

Answer: (C)

In OT disaster recovery planning, you must pin down how long you can be down and how much data you can afford to lose. The Recovery Time Objective (RTO) is the maximum time allowed to restore operations after an outage, while the Recovery Point Objective (RPO) is the maximum amount of data that can be lost since the last good backup. Having concrete values makes the plan actionable: it drives how often you back up, how you replicate data, what kind of failover or redundant systems you deploy, and how you test readiness. For example, aiming for an RTO of two hours and an RPO of fifteen minutes directly informs the choice of hot or warm backups, fast failover capabilities, and the staffing and procedures needed to meet those targets. In OT, these targets are especially critical because outages can affect safety, environmental controls, and regulatory compliance, so the DR plan must be measurable and verifiable. Without defined targets, you can’t design effective recovery steps or validate that the plan actually protects operations. The idea that these metrics are optional is incorrect, and while relationships between RTO and RPO can vary, the key is having concrete, tested values that reflect OT requirements. They apply to OT just as much as to IT.

In OT disaster recovery planning, you must pin down how long you can be down and how much data you can afford to lose. The Recovery Time Objective (RTO) is the maximum time allowed to restore operations after an outage, while the Recovery Point Objective (RPO) is the maximum amount of data that can be lost since the last good backup. Having concrete values makes the plan actionable: it drives how often you back up, how you replicate data, what kind of failover or redundant systems you deploy, and how you test readiness. For example, aiming for an RTO of two hours and an RPO of fifteen minutes directly informs the choice of hot or warm backups, fast failover capabilities, and the staffing and procedures needed to meet those targets. In OT, these targets are especially critical because outages can affect safety, environmental controls, and regulatory compliance, so the DR plan must be measurable and verifiable. Without defined targets, you can’t design effective recovery steps or validate that the plan actually protects operations. The idea that these metrics are optional is incorrect, and while relationships between RTO and RPO can vary, the key is having concrete, tested values that reflect OT requirements. They apply to OT just as much as to IT.