FRM Part II · FRM Exam Part II · Case Study: Cyberthreats and Information Security Risks
A payments firm sets a recovery time objective (RTO) of 4 hours and a recovery point objective (RPO) of 15 minutes for its card authorization system. Backups are replicated every 30 minutes, and failover takes 3 hours. Which statement is correct?
The RTO is met but the RPO is not. Failover takes 3 hours, within the 4-hour recovery time objective, but replication every 30 minutes means up to 30 minutes of data could be lost, which exceeds the 15-minute recovery point objective.
- AThe RTO is met but the RPO is not, because up to 30 minutes of data could be lostCorrect
- BBoth objectives are met
- CThe RPO is met but the RTO is not, because failover takes 3 hours
- DNeither objective is met
Explanation
RPO measures tolerable data loss. With replication every 30 minutes, up to 30 minutes of transactions could be lost, exceeding the 15-minute RPO. Failover of 3 hours is within the 4-hour RTO, so the RTO is met.
Did you get it right without looking?
One question tells you little. A timed set on Case Study: Cyberthreats and Information Security Risks shows your real accuracy, how long you take and where you lose marks.
More Case Study: Cyberthreats and Information Security Risks questions
- After a breach, a review finds that the bank's security tools generated alerts about unusual data transfers for several weeks, but the alert…
- A bank estimates that a phishing-led breach occurs with annual frequency 0.4 and an average loss of USD 5 million per event. A proposed cont…
- A bank's security team discovers that attackers entered through a third-party vendor's stolen credentials, then moved across internal system…
- When a bank builds a cyber loss distribution using a loss distribution approach, which statement about combining frequency and severity is m…
- An insider at an investment firm emails a spreadsheet of client portfolios to a personal account, but the spreadsheet remains unchanged and …
- A firm's business continuity plan relies on a single cloud provider for both production and backup data. Which weakness does this most clear…