Treat this syllabus as a decision discipline rather than a formula sheet. For every practice scenario, first identify which risk type is described, then ask what decision the question implies: a threshold, an average tail loss, a capital buffer, a hedge size, or an escalation path. That two-step habit of naming the risk and naming the decision is what this guide trains through worked examples, a decision table, and a self-check rubric you can score against your own practice logs.
VaR or Expected Shortfall? Reading the Question's Tail Language
Value at Risk is a loss threshold at a stated confidence level; expected shortfall is the average loss in scenarios that breach that threshold. Choose VaR for threshold or probability questions and expected shortfall when severity beyond the threshold is asked.
Define both measures precisely before comparing them. A 99% one-day VaR of 50 million means: on 99% of days the loss should not exceed 50 million. Expected shortfall at 99% asks a different question: among the worst 1% of days, what is the average loss? The two numbers answer different sentences, so the cue words in a scenario are decisive. Look for phrases like 'will not exceed' (VaR) versus 'on average, once losses exceed' or 'in the worst cases' (expected shortfall).
Worked example: a desk reports a 99% ten-day VaR of 50 million. A reviewer asks, 'If that VaR is breached, what loss should we expect on average?' A plausible mistake is to restate 50 million, because the number is already on the page. The better response is the expected shortfall, which must be at least 50 million and typically more, since breach days include losses beyond the threshold. Quoting VaR understates tail severity and conflates a threshold with an average. A second cue: if a question asks which measure better respects diversification when two portfolios are combined, expected shortfall's subadditivity points that way, while VaR can fail to satisfy it in some distributions.
Expected Loss vs Unexpected Loss: Which Credit Formula Does the Scenario Want?
Expected loss equals PD times LGD times EAD and is an average absorbed through pricing and provisions. Unexpected loss is the deviation beyond that average, addressed through capital and mitigation. Match the formula to the words 'average' versus 'beyond average.'
Trace each input to its economic meaning. Probability of default is the likelihood a borrower defaults over the horizon; loss given default is the fraction lost after recoveries; exposure at default is the amount outstanding when default occurs. Their product is a long-run annual average. Questions that say 'expected annual credit loss on this book' are asking you to multiply. Questions that say 'worse than expected,' 'stress condition,' or 'capital to absorb losses beyond the average' are pointing at unexpected loss, which requires a distributional view, not just the three inputs.
Also track how mitigation changes which input moves. A collateral pledge reduces LGD because recovery improves; a first-loss guarantee from a stronger obligor substitutes the guarantor's PD for the borrower's PD; a netting agreement can reduce EAD. One trap to watch in a scenario: collateral is posted against a loan and the question asks for the new expected loss. The better decision is to recompute with the reduced LGD rather than to discount the whole EL figure proportionally, because the mitigation acts on one component. Getting the component right matters because the same loan might appear later with a different mitigation type where the affected input, and therefore the calculation, differs.
Duration, DV01, and Convexity: Sizing a Bond Hedge With the Right Base
Modified duration measures percentage price sensitivity to yield; DV01 converts that into currency loss per basis point. Hedge by matching DV01, then check convexity for large yield moves. Never size a hedge off maturity or coupon.
Worked example: a portfolio holds bonds worth 200 million with modified duration 5. DV01 equals 200 million times 5 times 0.0001, which is 100,000 per basis point. If the hedging instrument has a DV01 of 45,000 per contract, the position needs roughly 100,000 divided by 45,000, about 2.2 contracts, rounded to the tradable number. A plausible mistake is using the portfolio's weighted-average maturity or its notional directly to count contracts, which ignores how price sensitivity concentrates in duration. The better decision is to compute both DV01s and take the ratio; it matters because a hedge sized on the wrong base can over- or under-protect by a wide margin even when the direction is correct.
State the assumption behind the linear estimate. The DV01 ratio is accurate for small, parallel yield shifts; for large shifts, convexity enters, because price-yield curvature makes the linear estimate drift. A question that specifies a large move, say 200 basis points, is inviting that second step: acknowledge the linear hedge leaves residual exposure and convexity adjustment improves it. A second check: duration applies to the instrument's own yield, so a portfolio of bonds from different markets is exposed to basis risk if hedged with a single instrument's duration. Naming that residual is part of a complete answer.
Operational Risk Tools: RCSA, KRIs, and Loss Data Do Different Jobs
Risk and control self-assessment looks forward at processes and control weaknesses; key risk indicators monitor conditions against thresholds; loss data records past events. Map each scenario to the tool by its time orientation and purpose.
Distinguish the three by what question each answers. An RCSA workshop asks process owners to identify where controls are weak before an event occurs, so a scenario describing a new product launch or a process review points to RCSA, ideally paired with scenario analysis for severe outcomes. KRIs are measurable signals, such as staffing shortfalls or system downtime counts, with thresholds that trigger escalation, so a scenario describing monitoring and alerting points to KRIs. Internal loss data catalogs actual events and their causes, supporting trend analysis and validation, so a scenario about analyzing past incidents points to loss data.
Practice combining them, because scenarios can chain tools. Example framing: a bank is onboarding a payments product. The forward-looking tool is an RCSA of the onboarding process; the ongoing tool is a set of KRIs such as failed-transaction rates with escalation thresholds; after any incident, loss data entries feed back into the RCSA's control ratings. A plausible mistake is to treat a KRI breach as proof a control failed; the better decision is to investigate whether the indicator's threshold was set too tightly or the underlying control genuinely deteriorated. The distinction matters because the response differs: recalibrating a threshold is a measurement fix, while remediating a control is an operational change.
Funding Liquidity vs Market Liquidity: Two Problems, Two Toolkits
Funding liquidity is the ability to meet cash obligations as they fall due; market liquidity is the ability to sell an asset quickly without a large price concession. Cash-flow ladders address the first; bid-ask spread and depth metrics address the second.
Separate the two because a firm can fail on either while remaining solvent on paper. Funding liquidity is tested by a maturity ladder: project cash inflows and outflows over short horizons and check whether cumulative net outflows can be covered by unencumbered liquid assets and committed facilities. Market liquidity is tested by transaction-cost measures: bid-ask spread, market depth, and the discount suffered if a position must be sold quickly. A scenario describing a payroll or settlement obligation points to funding liquidity; a scenario describing a forced sale of a thinly traded instrument points to market liquidity.
See how the two interact, because a single scenario can describe that linkage directly. A funding gap can force asset sales, and sales into an illiquid market realize fire-sale discounts, converting a cash-flow problem into a trading loss and potentially a solvency one. Worked example: a ladder shows a negative cumulative net cash flow over the next ten days of 40 million; selling 40 million of a bond whose typical sale discount under stress is 8% would realize only 36.8 million. The better decision is to identify the funding action that avoids the distressed sale, such as drawing a committed line or lengthening the liability profile. The point is not the arithmetic but the sequencing: each risk's toolkit addresses the other's failure mode only at a cost.
Appetite, Tolerance, and Limits: Tracing a Breach Through the Governance Chain
Risk appetite is the board's broad statement of acceptable risk; tolerance quantifies acceptable deviation; limits operationalize both at desk and business-unit level. A limit breach is evaluated against tolerance, which is checked against appetite.
Learn the chain by tracing an event through it. Suppose a trading desk breaches its single-name exposure limit. The first question is whether the breach also exhausts the business unit's tolerance, which is a wider quantitative band; the second is whether tolerance, even if respected, is consistent with the board's appetite statement. This ordering matters because the responses differ: a desk-level limit breach may be handled by desk management within tolerance, while a tolerance breach requires escalation to the risk committee, and an appetite inconsistency is a board-level conversation.
Anchor roles using the three lines of defense. The first line owns risk in daily operations, such as a desk monitoring its own exposures. The second line sets frameworks, measures aggregate exposures, and challenges the first line, as a risk management function would when validating limit structures. The third line, internal audit, provides independent assurance that both of the others work as designed. If a scenario assigns a task to a specific line, read the role wording closely: if it asks the risk function to 'own' the recovery of a breached exposure, the better reading is that risk management challenges and monitors, while the business executes the reduction; audit then verifies the process afterward.
A Preparation Sequence, Decision Table, and Self-Check Rubric
Sequence your study from definitions to formula application, then metric-selection drills, then integrated cases, finishing with a timed review against a decision table. Score yourself with observable rubric checks; these are learning milestones, not pass predictions.
A workable sequence: first, define each measure and write one sentence on when it is the right tool. Second, apply formulas in labeled worked examples with full units, like the DV01 hedge above. Third, run metric-selection drills: for each practice item, write the risk type and the decision implied before computing anything. Fourth, practice integrated cases that chain concepts, such as a funding gap forcing a liquidity-stressed sale. Fifth, close with a timed review using the table below as your cue sheet, adding rows for any cue you misread.
Practical exercise and rubric: build a metric-choice log from twenty practice scenarios. For each, record the cue words, the metric you selected, and the reason. Expected observations by the end of the set: you can define expected shortfall and state that it is at least VaR at the same confidence level; you can compute expected loss from PD, LGD, and EAD and say which component mitigation affects; you can size a hedge from two DV01s; you can classify a control activity to its line of defense; you can draft a simple cash-flow ladder and identify a funding gap. Self-check each item as met or not met; unmet items define your review list, and scores here measure learning progress only.
One administrative note: scheduling, eligibility, and current exam-format details belong to the issuer, IFMP, and should be confirmed on their site rather than inferred from third-party material.
| Scenario cue | Risk area | Right tool or measure |
|---|---|---|
| 'Will not exceed' a stated loss at a confidence level | Market risk | Value at Risk |
| 'Average loss once the threshold is breached' or tail severity | Market risk | Expected shortfall |
| 'Expected annual loss' on a credit book | Credit risk | PD x LGD x EAD |
| 'Beyond the average' or stress-condition credit loss | Credit risk | Unexpected loss / distributional view |
| Collateral or guarantee changes the loss profile | Credit risk | Recompute the affected EL component (LGD or PD) |
| Count of hedging contracts for a bond position | Market risk | DV01 ratio; check convexity for large shifts |
| New process or product, control weaknesses before events | Operational risk | RCSA, with scenario analysis |
| Monitoring signal with escalation threshold | Operational risk | Key risk indicators |
| Analysis of past incidents and their causes | Operational risk | Internal loss data |
| Cash obligations falling due | Liquidity risk | Maturity/cash-flow ladder |
| Speed and cost of selling a position | Liquidity risk | Bid-ask spread, depth, sale discount |
| Desk exceeds its exposure threshold | Governance | Evaluate against tolerance, then appetite; escalate per role |
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.
