What is a key consideration when designing solutions to meet specific RTO and RPO requirements?

Question

Options

• AFocusing exclusively on RTO, as RPO is generally less important
• BFocusing exclusively on RTO, as RPO is generally less important
• CAssuming that cloud providers will automatically meet all RTO and RPO targets without additional
• DIgnoring RPO in regions with high reliability ratings

• A
  7% (2)
• B
  71% (20)
• C
  18% (5)
• D
  4% (1)

Explanation

Note: Options A and B appear to be identical in this question - this is likely a formatting/copy error. Option B (the correct answer) probably should read something like: "Designing solutions that balance both RTO and RPO requirements based on business priorities and cost constraints."

Assuming that's the intended correct answer: both RTO (Recovery Time Objective - how fast you recover) and RPO (Recovery Point Objective - how much data loss is acceptable) must be actively designed for, since they drive different architectural decisions such as replication frequency, failover automation, and backup retention.

Why the distractors are wrong:

• A (as written, same as B): Either a duplicate error or represents the incorrect stance that RTO alone matters - RPO is equally critical for data-sensitive workloads like finance or healthcare.
• C is wrong because cloud providers offer shared-responsibility models; RTO/RPO targets require explicit configuration (e.g., multi-region replication, automated failover) - nothing is automatic.
• D is wrong because high regional reliability reduces the probability of failure, not the impact - you still need defined recovery point targets.

Memory tip: Think of RTO as a clock (time to recover) and RPO as a calendar (how far back you can afford to go). You can't ignore either one - exam questions that say "only focus on X" are almost always wrong.

No community discussion yet for this question.