A security analyst is reviewing the following company requirements prior to selecting the appropriate technical control configuration and parameter: RTO: 2 days RPO: 36 hours MTTR: 24 hours MTBF: 60…

Question

Options

• ARemote Syslog facility collecting real-time events
• BServer farm behind a load balancer delivering five-nines uptime
• CBackup solution that implements daily snapshots
• DCloud environment distributed across geographic regions

• B
  4% (1)
• C
  93% (25)
• D
  4% (1)

Explanation

Recovery Point Objective (RPO) defines the maximum acceptable amount of data loss measured in time - in this case, 36 hours. This means the organization can tolerate losing at most 36 hours of data. A daily snapshot backup runs every 24 hours, meaning in the worst case (a failure just before the next snapshot), up to 24 hours of data could be lost. 24 hours is well within the 36-hour RPO, so this solution satisfies the requirement. Option A (remote syslog) collects real-time events but is not a recovery mechanism. Option B (load balancer with five-nines uptime) addresses availability/RTO, not data recovery point. Option D (geographic cloud distribution) addresses fault tolerance and uptime, not the specific amount of data that can be recovered. Only Option C directly maps to the RPO definition.

No community discussion yet for this question.