BAR · Business Analysis · 6 practice questions
Risk Tolerance: When to Accept, Revise, or Escalate
Management may accept residual risk only within the applicable tolerance; otherwise, it must revise the response or escalate before proceeding. Below: compare responses to a supplier contract that meets enterprise capacity but exceeds the delivery tolerance.
Try one first
Hint
Separate enterprise risk capacity from objective-level risk tolerance, and ask whether the proposed response actually changes the residual risk that matters.
Answer A. The policy makes objective-level tolerance the decisive trigger for a business unit's authority to accept risk. Because residual risk still exceeds the on-time-delivery tolerance, the division cannot proceed based on attractive economics or unused enterprise risk capacity. The proposal must therefore be revised to bring residual risk within tolerance or escalated for higher-level approval before execution.
Why not B: This distractor appeals to risk-sharing and financial remedies. However, the liquidated-damages clause only compensates some lost profit after a supplier failure; it does not prevent missed deliveries, which is the operational objective whose residual risk remains above tolerance. Financial recovery does not cure the service-level tolerance breach.
Why not C: This is tempting because candidates often treat enterprise risk capacity as the ultimate limit and assume favorable returns justify acceptance. It is incorrect because the policy explicitly states that remaining within enterprise capacity does not authorize exceeding an objective-level tolerance.
Why not D: Monitoring is important but does not eliminate a known tolerance breach at the time of decision. The policy requires that if residual risk remains above tolerance, management must revise the proposal or escalate before executing, enhanced oversight alone does not satisfy that requirement.
What should you do?
The situation
Apex wants a three-year exclusive supply contract. Policy permits management acceptance only within the delivery tolerance: no more than four hours of disruption. After controls, a supplier failure could still interrupt deliveries for six hours. Contract damages reimburse lost profit but cannot prevent delays. The contract improves margin and stays within enterprise risk capacity. Above-tolerance proposals require revision or higher-level approval before signing.
Pause signing; revise the proposal to meet tolerance or obtain higher-level approval.
Best Six residual hours exceed the four-hour limit. This follows the policy while preserving the opportunity to pursue the contract.
Decline the contract and avoid this exposure.
Acceptable Avoidance prevents accepting the excess exposure, but rejection is not required. Revision or higher-level approval could preserve the contract's benefits.
Sign because attractive margins and available enterprise capacity justify accepting the risk.
Wrong Neither favorable returns nor available capacity overrides the delivery tolerance that limits management's acceptance authority.
Sign because contract damages adequately share the supplier-failure risk.
Wrong Damages reimburse profit losses but leave the six-hour interruption unchanged. The delivery exposure remains above tolerance.
Sign now and monitor the supplier more closely.
Wrong Monitoring alone does not bring the assessed interruption within tolerance or provide the required higher-level approval.
Key points
- Remember: Being able to absorb a loss does not authorize management to exceed the delivery tolerance.
- Measure the remaining disruption after controls, not just the reduction controls achieved.
- A payment for lost profit does not shorten a delivery interruption.
- Escalation must occur before signing, not after disruption occurs.
How the exam traps you
- Accepting the contract because enterprise risk capacity remains adequate. Apply the narrower delivery tolerance that governs management's acceptance authority.
- Treating contractual reimbursement as a complete risk transfer. Check whether the arrangement reduces the specific exposure that exceeds tolerance.
- Signing now and relying on enhanced monitoring. Monitoring does not authorize an existing tolerance breach; revise or obtain higher-level approval first.
Question 2
| Item | Amount |
|---|---|
| Risk A (90% probability) | $400,000 operational loss per event |
| Risk B (5% probability) | $4,000,000 reputational loss per event that could threaten key customers and the company's strategic objectives |
| Risk C (40% probability) | $150,000 financial loss per event |
Hint
Think about management's stated tolerances and what would most threaten the firm's core objectives or reputation, not only which loss is largest on average.
Answer B. Prioritization should be governed by whether a risk threatens the organization's ability to achieve its objectives or breaches management's stated tolerances. Quantitative inputs matter, e.g., EVs here are A: 0.9×$400,000 = $360,000, B: 0.05×$4,000,000 = $200,000, C: 0.4×$150,000 = $60,000, but a lower-probability event that could derail strategic objectives or cause severe reputational harm (Risk B) requires primary attention.
Why not A: Tempting because EV gives a clear numeric ranking (A $360,000 > B $200,000 > C $60,000). However, EV can understate low-probability, high-impact events that threaten strategic objectives or fall outside management's tolerances, so it should be an input, not the governing criterion.
Why not C: Tempting because efficient allocation of limited resources is important, mitigate where you get the most reduction per dollar. But cost-effectiveness should not override the need to address risks that could jeopardize core objectives or reputational standing, which management has declared intolerable.
Why not D: Tempting because higher probability increases expected frequency and aggregate loss. However, prioritizing solely by likelihood ignores severity and strategic impact; a lower-probability event that could undermine strategy or reputation may require earlier action.
Question 3
Hint
Decide whether the risk is primarily a compliance/regulatory issue (legal obligations and enforceable remedies) or a discretionary financial exposure subject to trade-offs like EMV or appetite.
Answer A. This exposure arises from potential noncompliance with federal law, so legal and regulatory obligations, and the threat of mandatory enforcement orders or loss of regulatory authorization, are the primary drivers of the response. Management cannot lawfully accept or ignore noncompliance merely because remediation is costly or outside its stated appetite. Therefore Delta's choice should be governed by meeting regulatory requirements rather than by EMV, internal appetite, or short-term earnings impact.
Why not B: Tempting because risk appetite normally guides many treatment choices; but an organization's appetite cannot override legal or regulatory obligations that may require remediation regardless of internal tolerance.
Why not C: Tempting because a remediation cost is given and EMV is useful for prioritizing discretionary financial risks; however, when noncompliance can trigger mandatory enforcement or loss of authorization, a pure cost-benefit calculation cannot justify failing to comply.
Why not D: Tempting because management often prioritizes earnings, but short-term financial considerations are subordinate to compliance obligations when regulatory penalties, mandatory corrective actions, or loss of authorization are possible.
Question 4
Hint
Focus on the governance-level decision that would align scoring, controls, escalation, and resource allocation across business units.
Answer B. The root governance deficiency is the absence of a formal enterprise risk appetite and defined tolerances; without them management lacks consistent criteria to prioritize risks, set escalation thresholds, and allocate resources, which explains the inconsistent scoring and uneven controls. Establishing appetite and tolerances creates the policy framework that guides control expectations and escalation rules. Strengthening controls or audit is important but should follow the governance decision that defines acceptable exposure.
Why not A: This is tempting because the stem cites varying control effectiveness, but inconsistent controls are likely a downstream symptom of lacking enterprise-wide appetite/tolerances and prioritization guidance. Reworking controls is necessary but should be directed by the governance framework that defines expected residual risk and control standards.
Why not C: Candidates may be drawn to audit because it reported the problems, but internal audit is an assurance function that identifies and reports deficiencies, not the authority that sets risk appetite or tolerances. Stronger audit improves detection and reporting but does not establish the enterprise-level decisions needed to align scoring, escalation, and resource allocation.
Why not D: This distractor appeals to those who equate inconsistency with poor identification, but the stem states the company already has a risk register listing major risks and assigned owners. The core issue is inconsistent prioritization and lack of tolerance guidance, not the initial capture of risks.
Question 5
Hint
Calculate each residual as inherent score × (1 − control effectiveness) and compare to the stated appetite bands; prioritize any risk with residual > 12.
Answer C. The data‑breach residual score is 14, which exceeds the organization's 'immediate action' threshold (>12), so additional mitigation to reduce likelihood and impact should be prioritized. The vendor‑outage (residual 9) and regulatory‑change (7.2) fall in the 6-12 band and therefore warrant additional mitigation planning or possible transfer but are lower priority. Transfer mechanisms (insurance) or SLA changes can supplement the response but do not replace immediate technical mitigation for the highest‑priority breach risk.
Why not A: This is incorrect: the data‑breach residual is 14, which exceeds the 'immediate action' band, so it cannot be simply accepted or only monitored.
Why not B: Insurance can address financial loss but does not reduce likelihood or prevent non‑financial consequences (reputational, regulatory). Because the breach residual >12 requires immediate mitigation, transfer alone is insufficient as the primary next step.
Why not D: Although vendor outage is important, its residual (9) is in the 6-12 band and therefore lower priority than the breach (14). Addressing the higher‑priority breach first is the appropriate sequencing. Example mitigations for the breach risk include automated configuration management, stronger change controls, and third-party security testing.
Question 6
Hint
Think about entity-level guidance (risk appetite) versus metrics like probability or expected loss, which determines whether a risk is acceptable, not just how big it is?
Answer B. Enterprise risk management prioritizes protecting the entity's objectives and keeping exposures within management's stated risk appetite. Thus the governing factor when choosing responses is whether a risk threatens strategic objectives or regulatory compliance, not solely its probability, expected monetary loss, or mitigation cost. Quantitative measures and cost considerations inform how to prioritize and implement responses, but they must be applied within the risk appetite framework.
Why not A: Attractive because frequent events can erode operations and demand resources, but probability alone ignores potential severity and whether an event would jeopardize strategic objectives or compliance. Therefore likelihood is an important input but not the governing factor.
Why not C: Expected loss is a useful quantitative comparison, yet a risk with lower expected monetary loss may still be unacceptable if it threatens critical objectives or regulatory standing. Management's risk appetite and objective impact take precedence over dollar-only comparisons.
Why not D: Cost and budget feasibility matter for selecting which controls to implement, but immediate cost should be weighed against whether the risk is acceptable under management's appetite. Management may approve higher costs for risks that would undermine strategic goals or cause regulatory failure.
Common questions
Can management accept residual risk above tolerance?
Not under Apex's policy without higher-level approval. Management must first revise the proposal to meet the delivery tolerance or escalate before signing.
Does staying within enterprise risk capacity mean risk is acceptable?
No. Apex can remain within enterprise capacity while exceeding its specific delivery tolerance, which limits management's authority to accept the contract.
Does sharing financial losses bring residual risk within tolerance?
Only if it addresses the exposure being tested. Contract damages reimburse Apex's lost profit, but the six-hour delivery interruption still exceeds the four-hour tolerance.
Practice BAR like the real exam
The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.
Open the free simulator →More on Risk management
Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.