During an outage, IT restores email first because complainers are loudest, while wastewater SCADA dependencies identified in planning are left waiting. What BIA lesson was ignored?
Select an answer to reveal the explanation.
Short Explanation
The squeaky wheel got the grease while the plant that keeps the river clean waited. BIA exists so recovery follows real dependency and harm — not whoever shouts loudest in the war room.
Full Explanation
Recovery priority should follow researched criticality and dependencies, not the loudest stakeholders is the BIA lesson ignored when IT restores email first because complainers are loud while wastewater SCADA dependencies wait. Life-safety and environmental control systems identified in planning outrank noisy but less critical collaboration tools. Civic outage response must honor the BIA, not the loudest inbox.
Claiming email must always restore before any life-safety or environmental control system fails by concept because universal email-first rules contradict dependency-based prioritization. Claiming SCADA systems are excluded from BIA because they are not user-facing fails because impact and dependency—not user-interface popularity—drive BIA scope; non-user-facing systems can be most critical. Claiming stakeholder volume is the official metric for ranking business impact fails because volume measures complaint energy, not mission impact.
Exam caveat: CRMC continuity execution ties recovery order to BIA criticality. Political noise is a recognized failure mode when it overrides planned priorities.
Operational check: During the next city outage or drill, require the incident commander to follow the BIA priority list; document any deviation with risk acceptance by an authorized official—not by help-desk ticket volume.