A business impact analysis is only useful if its numbers can all be true at once. Each scenario hands you a BIA table with MTD, RTO, WRT, RPO, backups, dependencies and current recovery arrangements, and asks you to find the rows that contradict themselves or each other, set the recovery order, choose the cheapest recovery option that actually meets the targets, and match test requests to the right test.
A dental group's first business impact analysis has five rows and three of them cannot be true. Find the RTO that outlasts its MTD, the RPO a nightly backup cannot deliver and the dependency that recovers too slowly, then set the recovery order and pick the cheapest recovery option that actually works.
An insurance broker's BIA looks tidy until you follow the dependencies and add back the work recovery time. Find the rows that cannot be delivered, order six processes for recovery, and choose a telephony fallback that keeps claims intake inside its targets.
A manufacturer's plant systems need minutes of data loss and hours of downtime, and one of them cannot live in the cloud. Fix a BIA with a hidden dependency chain, order recovery when a low-priority system must come back first, and pick the site that meets the targets at least cost - even when that is the expensive one.
A hospital has to prove its plans work without putting patients at risk. Review a clinical BIA, match five test requests to the right test type - checklist, tabletop, simulation, parallel or full interruption - and choose a recovery site for theatre scheduling.