A business unit proposes adopting a new cloud analytics service whose assessed residual data-confidentiality risk sits clearly within the enterprise risk appetite but slightly above the tolerance band set for that specific objective. How should the risk practitioner advise the decision be guided?
- AApprove the service without change, because residual risk inside the enterprise appetite is automatically acceptable for any objective
- BTreat the residual risk down to the objective tolerance band before approval, because tolerance constrains the specific decision even when appetite is met Correct
- CReject the service outright, because any exposure above a tolerance band represents a breach of the enterprise risk capacity ceiling
- DRaise the tolerance band for this objective to match appetite, because alignment between the two removes the conflict cleanly
Why A is wrong: Sitting within appetite is tempting grounds for approval, but the tighter objective tolerance still governs this particular decision and is exceeded.
Why B is correct: Tolerance is the binding limit for that objective, so the exposure must be reduced into the band even though the broader appetite is satisfied.
Why C is wrong: Outright rejection conflates tolerance with capacity; exceeding a tolerance band is not the same as breaching the survival limit of the enterprise.
Why D is wrong: Lifting tolerance to appetite looks like tidy alignment, yet it discards the deliberate tighter limit set for this sensitive objective.