Fundamental Concepts of Operational Resilience
What this domain tests
The exam checks whether you can distinguish operational resilience from adjacent disciplines and apply its core vocabulary precisely: important business services (IBS), impact tolerances, severe but plausible scenarios, mapping, and outcome-based governance. Expect questions that ask you to choose the correct definition or identify a flawed tolerance.
Core rules
- Resilience is defined by outcomes: the firm continues to deliver its IBS within impact tolerance when disruption occurs. It is not the same as avoiding risk or holding more capital.
- An IBS is a service whose disruption would cause intolerable harm to consumers, market integrity, or other firms. Define it from the customer and market perspective, not from the org chart.
- An impact tolerance is the maximum tolerable level of disruption, expressed as a measurable outcome (for example, “no more than two hours of failed payments for 95% of customers”). It is not an RTO, which is an internal recovery target for a resource.
- Severe but plausible scenarios test the tolerance. They should be plausible enough to justify investment and severe enough to expose fragility.
- Mapping links each IBS to people, processes, technology, data, facilities, and third parties. Mapping must show interdependence, not just a list.
Worked example
A retail bank sets an impact tolerance for domestic instant payments: no more than two hours of failed authorisation for 95% of attempts. Its core payment switch has an RTO of four hours. The tolerance is breached at two hours, so the RTO is inadequate. The fix is not to rewrite the tolerance; it is to redesign recovery, add a standby route, or reduce dependency on the switch.
Traps
- Treating RTO, RPO, or BIA recovery time as the impact tolerance.
- Defining IBS by department or system rather than customer outcome.
- Setting tolerances that cannot be measured or evidenced.
- Listing dependencies without showing which ones drive the tolerance.