What DRP objectives (RTO/RPO) does UAP Document 301 specify for document services?

What DRP objectives (RTO/RPO) does UAP Document 301 specify for document services?

• A. No specific targets.
• B. Document services must have defined RTO and RPO objectives and tested recovery plans.
• C. RTO only, no RPO.
• D. Only recovery plan after incident.

Answer: (B)

In DRP for document services, you must have clear recovery objectives and proven ability to meet them. That means defining both Recovery Time Objective (RTO) and Recovery Point Objective (RPO) for the service, and then validating the plan through testing. The RTO sets how quickly the service must be restored after a disruption, while the RPO specifies how much data loss is acceptable. Having both targets defined ensures you know the expected resilience and the acceptable risk, and testing the recovery plans confirms you can actually achieve those targets in practice. This is why the best choice is that document services require defined RTO and RPO objectives and tested recovery plans. It’s not sufficient to claim no targets, to have only RTO without an RPO, or to rely solely on post-incident recovery—UAP Document 301 emphasizes proactive, measurable objectives plus validated readiness.

In DRP for document services, you must have clear recovery objectives and proven ability to meet them. That means defining both Recovery Time Objective (RTO) and Recovery Point Objective (RPO) for the service, and then validating the plan through testing. The RTO sets how quickly the service must be restored after a disruption, while the RPO specifies how much data loss is acceptable. Having both targets defined ensures you know the expected resilience and the acceptable risk, and testing the recovery plans confirms you can actually achieve those targets in practice.

This is why the best choice is that document services require defined RTO and RPO objectives and tested recovery plans. It’s not sufficient to claim no targets, to have only RTO without an RPO, or to rely solely on post-incident recovery—UAP Document 301 emphasizes proactive, measurable objectives plus validated readiness.