This CAIIB Risk Management MCQ set is for bankers preparing for the IIBF CAIIB Risk Management paper. Attempt all 10 questions below—tap an option to see whether you are right, then read the short explanation. These are SimplifyingFin practice questions, not official IIBF questions.
Part of the CAIIB Risk Management MCQ practice series.
CAIIB Risk Management MCQ Day 1 quiz: 10 questions
Show answer
Answer: C — ₹0.40 crore (₹40 lakh).
The idea: Expected loss is the average credit loss the bank should budget for on this loan in a normal year — the cost of lending that is priced into the spread and covered by provisions, not by capital. Here it works out to ₹40 lakh on a ₹40 crore loan, i.e. 1% of the exposure.
- Expected loss = PD × LGD × EAD.
- The stem gives the recovery rate, not LGD. LGD = 1 − recovery rate = 1 − 60% = 40%.
- EAD = ₹40 crore (the amount outstanding if default happens).
- EL = 0.025 × 0.40 × 40 = 0.01 × 40 = ₹0.40 crore.
- Convert: ₹0.40 crore = ₹40 lakh.
- Shortcut: multiply the two percentages first — 2.5% × 40% = 1% — then take 1% of ₹40 crore = ₹0.40 crore.
Why the others are wrong:
- A (₹0.60 crore (₹60 lakh)): ₹0.60 crore is PD × recovery rate × EAD (0.025 × 0.60 × 40): it uses the 60% recovered instead of the 40% lost.
- B (₹1.00 crore): ₹1.00 crore is PD × EAD (0.025 × 40): it assumes the whole loan is lost on default and ignores recoveries (LGD taken as 100%).
- D (₹16.00 crore): ₹16.00 crore is LGD × EAD (0.40 × 40): the loss if default were certain — it leaves out the 2.5% probability of default.
- E (₹24.00 crore): ₹24.00 crore is recovery rate × EAD (0.60 × 40): the amount the bank expects to get back after a default, not a loss.
Check:
| Item | Value |
|---|---|
| EAD | ₹40 crore |
| PD | 2.5% |
| Recovery rate | 60% |
| LGD = 1 − 60% | 40% |
| PD × LGD | 1.0% |
| EL = 1.0% × ₹40 crore | ₹0.40 crore |
If the stem gives a recovery rate, convert it to LGD before multiplying.
Memory tip: EL = PD × LGD × EAD, and LGD = 1 − recovery. Multiply the two percentages first, then apply to the rupee exposure.
Answer: C — ₹0.40 crore (₹40 lakh).
The idea: Expected loss is the average credit loss the bank should budget for on this loan in a normal year — the cost of lending that is priced into the spread and covered by provisions, not by capital. Here it works out to ₹40 lakh on a ₹40 crore loan, i.e. 1% of the exposure.
- Expected loss = PD × LGD × EAD.
- The stem gives the recovery rate, not LGD. LGD = 1 − recovery rate = 1 − 60% = 40%.
- EAD = ₹40 crore (the amount outstanding if default happens).
- EL = 0.025 × 0.40 × 40 = 0.01 × 40 = ₹0.40 crore.
- Convert: ₹0.40 crore = ₹40 lakh.
- Shortcut: multiply the two percentages first — 2.5% × 40% = 1% — then take 1% of ₹40 crore = ₹0.40 crore.
Why the others are wrong:
- A (₹0.60 crore (₹60 lakh)): ₹0.60 crore is PD × recovery rate × EAD (0.025 × 0.60 × 40): it uses the 60% recovered instead of the 40% lost.
- B (₹1.00 crore): ₹1.00 crore is PD × EAD (0.025 × 40): it assumes the whole loan is lost on default and ignores recoveries (LGD taken as 100%).
- D (₹16.00 crore): ₹16.00 crore is LGD × EAD (0.40 × 40): the loss if default were certain — it leaves out the 2.5% probability of default.
- E (₹24.00 crore): ₹24.00 crore is recovery rate × EAD (0.60 × 40): the amount the bank expects to get back after a default, not a loss.
Check:
| Item | Value |
|---|---|
| EAD | ₹40 crore |
| PD | 2.5% |
| Recovery rate | 60% |
| LGD = 1 − 60% | 40% |
| PD × LGD | 1.0% |
| EL = 1.0% × ₹40 crore | ₹0.40 crore |
If the stem gives a recovery rate, convert it to LGD before multiplying.
Memory tip: EL = PD × LGD × EAD, and LGD = 1 − recovery. Multiply the two percentages first, then apply to the rupee exposure.
Show answer
Answer: A — 2.10 years.
The idea: The duration gap tells the ALCO how exposed the bank's net worth (economic value of equity) is to interest rates. A positive gap of 2.1 years means assets are much more rate-sensitive than liabilities, so if rates rise by 1 percentage point, equity value falls by roughly 2.1% of total assets (about ₹21 crore here, before the small 1 + yield adjustment).
- Duration gap = asset duration − (liabilities ÷ assets) × liability duration.
- Leverage weight: liabilities ÷ assets = 900 ÷ 1,000 = 0.90.
- Weighted liability duration = 0.90 × 1.0 = 0.90 year.
- Duration gap = 3.0 − 0.90 = 2.10 years.
- Reading: a positive gap means a rise in rates cuts the economic value of equity, and a fall in rates raises it.
- Shortcut: when the liability duration is 1 year, the weighted liability duration is just the L/A ratio (0.90), so subtract that from the asset duration.
Why the others are wrong:
- B (2.00 years): 2.00 years is asset duration − liability duration (3.0 − 1.0); it leaves out the 0.90 liabilities-to-assets weight.
- C (1.89 years): 1.89 years divides the liability duration by 0.90 (3.0 − 1.0 ÷ 0.90) instead of multiplying by it, which inverts the leverage weight.
- D (3.90 years): 3.90 years adds the weighted liability duration to the asset duration (3.0 + 0.90) instead of subtracting it.
- E (1.70 years): 1.70 years applies the 0.90 weight to the asset duration (0.90 × 3.0 − 1.0) instead of the liability duration.
Check:
| Step | Value |
|---|---|
| Asset duration (D_A) | 3.0 years |
| L ÷ A = 900 ÷ 1,000 | 0.90 |
| Weighted liability duration = 0.90 × 1.0 | 0.90 year |
| Duration gap = 3.0 − 0.90 | 2.10 years |
Approximate change in equity value ≈ −duration gap × assets × change in yield ÷ (1 + yield).
Memory tip: Weight the liability duration by L/A, then subtract. Positive gap → rates up, equity value down.
Answer: A — 2.10 years.
The idea: The duration gap tells the ALCO how exposed the bank's net worth (economic value of equity) is to interest rates. A positive gap of 2.1 years means assets are much more rate-sensitive than liabilities, so if rates rise by 1 percentage point, equity value falls by roughly 2.1% of total assets (about ₹21 crore here, before the small 1 + yield adjustment).
- Duration gap = asset duration − (liabilities ÷ assets) × liability duration.
- Leverage weight: liabilities ÷ assets = 900 ÷ 1,000 = 0.90.
- Weighted liability duration = 0.90 × 1.0 = 0.90 year.
- Duration gap = 3.0 − 0.90 = 2.10 years.
- Reading: a positive gap means a rise in rates cuts the economic value of equity, and a fall in rates raises it.
- Shortcut: when the liability duration is 1 year, the weighted liability duration is just the L/A ratio (0.90), so subtract that from the asset duration.
Why the others are wrong:
- B (2.00 years): 2.00 years is asset duration − liability duration (3.0 − 1.0); it leaves out the 0.90 liabilities-to-assets weight.
- C (1.89 years): 1.89 years divides the liability duration by 0.90 (3.0 − 1.0 ÷ 0.90) instead of multiplying by it, which inverts the leverage weight.
- D (3.90 years): 3.90 years adds the weighted liability duration to the asset duration (3.0 + 0.90) instead of subtracting it.
- E (1.70 years): 1.70 years applies the 0.90 weight to the asset duration (0.90 × 3.0 − 1.0) instead of the liability duration.
Check:
| Step | Value |
|---|---|
| Asset duration (D_A) | 3.0 years |
| L ÷ A = 900 ÷ 1,000 | 0.90 |
| Weighted liability duration = 0.90 × 1.0 | 0.90 year |
| Duration gap = 3.0 − 0.90 | 2.10 years |
Approximate change in equity value ≈ −duration gap × assets × change in yield ÷ (1 + yield).
Memory tip: Weight the liability duration by L/A, then subtract. Positive gap → rates up, equity value down.
Show answer
Answer: D — 11.25%.
The idea: The Tier 1 ratio shows how much going-concern capital — capital that absorbs losses while the bank keeps operating — stands behind every ₹100 of risk-weighted assets. 11.25% means about ₹11.25 of Tier 1 capital for every ₹100 of RWA across credit, market and operational risk.
- Tier 1 capital = CET1 + AT1 = 1,080 + 270 = ₹1,350 crore. Tier 2 is not part of Tier 1.
- Total RWA = credit + market + operational = 10,000 + 800 + 1,200 = ₹12,000 crore.
- Tier 1 ratio = Tier 1 capital ÷ total RWA = 1,350 ÷ 12,000.
- Simplify: 1,350 ÷ 12,000 = 135 ÷ 1,200 = 0.1125 = 11.25%.
- Shortcut: 1% of ₹12,000 crore is ₹120 crore; 1,350 ÷ 120 = 11.25, so the ratio is 11.25%.
Why the others are wrong:
- A (9.00%): 9.00% is the CET1 ratio (1,080 ÷ 12,000): it leaves out the ₹270 crore of AT1 that belongs in Tier 1.
- B (14.25%): 14.25% is the total capital ratio (CRAR): (1,080 + 270 + 360) ÷ 12,000 — it wrongly adds Tier 2.
- C (13.50%): 13.50% is Tier 1 ÷ credit-risk RWA only (1,350 ÷ 10,000): it ignores the market and operational risk RWA.
- E (10.80%): 10.80% is CET1 ÷ credit-risk RWA only (1,080 ÷ 10,000): it both drops AT1 and ignores market and operational RWA.
Check:
| Ratio | Working | Result |
|---|---|---|
| CET1 ratio | 1,080 ÷ 12,000 | 9.00% |
| Tier 1 ratio | 1,350 ÷ 12,000 | 11.25% |
| Total capital ratio (CRAR) | 1,710 ÷ 12,000 | 14.25% |
All three ratios use the same denominator: total RWA for credit + market + operational risk.
Memory tip: Tier 1 = CET1 + AT1; total capital = Tier 1 + Tier 2. The denominator is always total RWA across all three Pillar 1 risks.
Answer: D — 11.25%.
The idea: The Tier 1 ratio shows how much going-concern capital — capital that absorbs losses while the bank keeps operating — stands behind every ₹100 of risk-weighted assets. 11.25% means about ₹11.25 of Tier 1 capital for every ₹100 of RWA across credit, market and operational risk.
- Tier 1 capital = CET1 + AT1 = 1,080 + 270 = ₹1,350 crore. Tier 2 is not part of Tier 1.
- Total RWA = credit + market + operational = 10,000 + 800 + 1,200 = ₹12,000 crore.
- Tier 1 ratio = Tier 1 capital ÷ total RWA = 1,350 ÷ 12,000.
- Simplify: 1,350 ÷ 12,000 = 135 ÷ 1,200 = 0.1125 = 11.25%.
- Shortcut: 1% of ₹12,000 crore is ₹120 crore; 1,350 ÷ 120 = 11.25, so the ratio is 11.25%.
Why the others are wrong:
- A (9.00%): 9.00% is the CET1 ratio (1,080 ÷ 12,000): it leaves out the ₹270 crore of AT1 that belongs in Tier 1.
- B (14.25%): 14.25% is the total capital ratio (CRAR): (1,080 + 270 + 360) ÷ 12,000 — it wrongly adds Tier 2.
- C (13.50%): 13.50% is Tier 1 ÷ credit-risk RWA only (1,350 ÷ 10,000): it ignores the market and operational risk RWA.
- E (10.80%): 10.80% is CET1 ÷ credit-risk RWA only (1,080 ÷ 10,000): it both drops AT1 and ignores market and operational RWA.
Check:
| Ratio | Working | Result |
|---|---|---|
| CET1 ratio | 1,080 ÷ 12,000 | 9.00% |
| Tier 1 ratio | 1,350 ÷ 12,000 | 11.25% |
| Total capital ratio (CRAR) | 1,710 ÷ 12,000 | 14.25% |
All three ratios use the same denominator: total RWA for credit + market + operational risk.
Memory tip: Tier 1 = CET1 + AT1; total capital = Tier 1 + Tier 2. The denominator is always total RWA across all three Pillar 1 risks.
Show answer
Answer: B — Risk appetite.
The idea: Risk appetite is the board's chosen amount and type of risk it is willing to take to meet its objectives. It sits below risk capacity, the most the bank can bear, and above the detailed limits that put it into practice at desk or portfolio level.
- Figure (i) is the most loss the bank can absorb before breaching regulatory capital. That is a hard ceiling, called risk capacity.
- Figure (ii) is a choice the board makes, set below capacity: how much risk it is willing to take for the plan. That is risk appetite.
- Figure (iii) is a granular, monitorable ceiling for one desk. That is a risk limit, one of the tools that turn appetite into day-to-day controls.
- So the ordering is capacity (₹2,400 crore) ≥ appetite (₹1,500 crore) → cascaded into limits (₹40 crore desk VaR).
Why the others are wrong:
- A (Risk capacity): Risk capacity is figure (i), the maximum the bank could bear before breaching its regulatory minimum, not the amount the board chooses to take.
- C (Risk limit): A risk limit is figure (iii), an operational ceiling for a specific desk or portfolio that comes out of the appetite.
- D (Risk profile): Risk profile is the risk the bank actually holds at a point in time; it is measured and compared against appetite, not set by the board.
- E (Inherent risk): Inherent risk is the risk in an activity before any controls or mitigation, a term used in risk and control self-assessment, not a board-approved loss level.
Check:
| Figure | What it is | Term |
|---|---|---|
| (i) ₹2,400 crore | Most the bank can absorb | Risk capacity |
| (ii) ₹1,500 crore | Board-chosen risk for the plan | Risk appetite |
| (iii) ₹40 crore | Desk-level ceiling | Risk limit |
Appetite must stay within capacity; limits put appetite into practice.
Memory tip: Can bear = capacity; choose to bear = appetite; allowed per desk = limit.
Answer: B — Risk appetite.
The idea: Risk appetite is the board's chosen amount and type of risk it is willing to take to meet its objectives. It sits below risk capacity, the most the bank can bear, and above the detailed limits that put it into practice at desk or portfolio level.
- Figure (i) is the most loss the bank can absorb before breaching regulatory capital. That is a hard ceiling, called risk capacity.
- Figure (ii) is a choice the board makes, set below capacity: how much risk it is willing to take for the plan. That is risk appetite.
- Figure (iii) is a granular, monitorable ceiling for one desk. That is a risk limit, one of the tools that turn appetite into day-to-day controls.
- So the ordering is capacity (₹2,400 crore) ≥ appetite (₹1,500 crore) → cascaded into limits (₹40 crore desk VaR).
Why the others are wrong:
- A (Risk capacity): Risk capacity is figure (i), the maximum the bank could bear before breaching its regulatory minimum, not the amount the board chooses to take.
- C (Risk limit): A risk limit is figure (iii), an operational ceiling for a specific desk or portfolio that comes out of the appetite.
- D (Risk profile): Risk profile is the risk the bank actually holds at a point in time; it is measured and compared against appetite, not set by the board.
- E (Inherent risk): Inherent risk is the risk in an activity before any controls or mitigation, a term used in risk and control self-assessment, not a board-approved loss level.
Check:
| Figure | What it is | Term |
|---|---|---|
| (i) ₹2,400 crore | Most the bank can absorb | Risk capacity |
| (ii) ₹1,500 crore | Board-chosen risk for the plan | Risk appetite |
| (iii) ₹40 crore | Desk-level ceiling | Risk limit |
Appetite must stay within capacity; limits put appetite into practice.
Memory tip: Can bear = capacity; choose to bear = appetite; allowed per desk = limit.
Show answer
Answer: E — Countercyclical capital buffer.
The idea: The countercyclical capital buffer is built up in good times and released in bad times. Banks put aside extra CET1 while credit grows too fast, and the regulator releases it in a downturn so that losses do not force banks to stop lending.
- Spot the trigger: the decision is driven by an economy-wide indicator (credit growing faster than GDP, a widening credit-to-GDP gap), not by one bank's own risk.
- Spot the timing: the buffer is built in the boom and can be released in the downturn, so it moves with the credit cycle.
- Spot the form: it is held in CET1 on top of the minimum and the conservation buffer.
- Those three features together describe the countercyclical capital buffer. In India, RBI's 2015 framework uses the credit-to-GDP gap as the main indicator, together with GNPA growth and other supplementary indicators, with the buffer ranging from 0 to 2.5% of RWA.
Why the others are wrong:
- A (Capital conservation buffer): The capital conservation buffer is a fixed CET1 cushion that banks hold at all times; it does not rise and fall with the credit cycle.
- B (Additional CET1 surcharge for domestic systemically important banks): The D-SIB surcharge depends on a bank's systemic importance (size, interconnectedness and similar factors), not on economy-wide credit growth.
- C (Leverage ratio): The leverage ratio is a backstop that compares Tier 1 capital with total exposure without risk weights; it is not a buffer built in booms and released in downturns.
- D (Pillar 2 capital add-on set after reviewing a bank's ICAAP): A Pillar 2 add-on depends on one bank's own risk profile found in the supervisory review of its ICAAP, not on a system-wide credit boom.
Check: Economy-wide credit-to-GDP signal + build in boom + release in bust + held in CET1 = countercyclical capital buffer.
Memory tip: ‘Counter-cyclical’ = goes against the cycle: build when credit runs hot, release when it cools.
Answer: E — Countercyclical capital buffer.
The idea: The countercyclical capital buffer is built up in good times and released in bad times. Banks put aside extra CET1 while credit grows too fast, and the regulator releases it in a downturn so that losses do not force banks to stop lending.
- Spot the trigger: the decision is driven by an economy-wide indicator (credit growing faster than GDP, a widening credit-to-GDP gap), not by one bank's own risk.
- Spot the timing: the buffer is built in the boom and can be released in the downturn, so it moves with the credit cycle.
- Spot the form: it is held in CET1 on top of the minimum and the conservation buffer.
- Those three features together describe the countercyclical capital buffer. In India, RBI's 2015 framework uses the credit-to-GDP gap as the main indicator, together with GNPA growth and other supplementary indicators, with the buffer ranging from 0 to 2.5% of RWA.
Why the others are wrong:
- A (Capital conservation buffer): The capital conservation buffer is a fixed CET1 cushion that banks hold at all times; it does not rise and fall with the credit cycle.
- B (Additional CET1 surcharge for domestic systemically important banks): The D-SIB surcharge depends on a bank's systemic importance (size, interconnectedness and similar factors), not on economy-wide credit growth.
- C (Leverage ratio): The leverage ratio is a backstop that compares Tier 1 capital with total exposure without risk weights; it is not a buffer built in booms and released in downturns.
- D (Pillar 2 capital add-on set after reviewing a bank's ICAAP): A Pillar 2 add-on depends on one bank's own risk profile found in the supervisory review of its ICAAP, not on a system-wide credit boom.
Check: Economy-wide credit-to-GDP signal + build in boom + release in bust + held in CET1 = countercyclical capital buffer.
Memory tip: ‘Counter-cyclical’ = goes against the cycle: build when credit runs hot, release when it cools.
Show answer
Answer: A — The risk that the protection seller cannot pay the agreed amount when the credit event occurs.
The idea: Buying CDS protection swaps the issuer's default risk for a smaller and usually better-rated risk: the risk that the protection seller fails to pay. The bank is covered against the infrastructure company only if the other bank can honour its promise.
- Identify the roles: the bank pays the premium, so it is the protection buyer. The other bank receives the premium, so it is the protection seller.
- On a credit event (such as the issuer's default), the protection seller pays the buyer an amount that roughly covers the loss on the bonds, through physical or cash settlement.
- So the issuer's default risk has moved to the protection seller, but the buyer now depends on the seller paying. That is counterparty credit risk.
- The worst case is a double default, where both the issuer and the protection seller fail.
Why the others are wrong:
- B (No risk at all, because a CDS also removes the bond's interest rate and liquidity risk): A CDS covers only the credit event on the reference entity; the bank still bears the bond's interest rate risk and market or liquidity risk.
- C (An obligation to pass all the bond's coupons and price gains to the protection seller): Passing all coupons and price changes to the other side describes the total return payer in a total return swap, not a CDS protection buyer.
- D (An obligation to compensate the other bank for the issuer's default): Paying compensation on default is the protection seller's obligation; the bank here is the buyer.
- E (The full default loss, because a CDS pays only after the bank has sold the bonds in the market): A CDS pays on the credit event itself; the buyer does not have to sell the bonds in the market first, and avoiding the default loss is the whole point of buying protection.
Check:
| Party | Pays | Receives | Main risk after the trade |
|---|---|---|---|
| Protection buyer (this bank) | Periodic premium | Payout on credit event | Seller fails to pay (counterparty risk) |
| Protection seller | Payout on credit event | Periodic premium | Reference entity's default |
Memory tip: Buyer pays premium and keeps counterparty risk; seller earns premium and takes the default risk.
Answer: A — The risk that the protection seller cannot pay the agreed amount when the credit event occurs.
The idea: Buying CDS protection swaps the issuer's default risk for a smaller and usually better-rated risk: the risk that the protection seller fails to pay. The bank is covered against the infrastructure company only if the other bank can honour its promise.
- Identify the roles: the bank pays the premium, so it is the protection buyer. The other bank receives the premium, so it is the protection seller.
- On a credit event (such as the issuer's default), the protection seller pays the buyer an amount that roughly covers the loss on the bonds, through physical or cash settlement.
- So the issuer's default risk has moved to the protection seller, but the buyer now depends on the seller paying. That is counterparty credit risk.
- The worst case is a double default, where both the issuer and the protection seller fail.
Why the others are wrong:
- B (No risk at all, because a CDS also removes the bond's interest rate and liquidity risk): A CDS covers only the credit event on the reference entity; the bank still bears the bond's interest rate risk and market or liquidity risk.
- C (An obligation to pass all the bond's coupons and price gains to the protection seller): Passing all coupons and price changes to the other side describes the total return payer in a total return swap, not a CDS protection buyer.
- D (An obligation to compensate the other bank for the issuer's default): Paying compensation on default is the protection seller's obligation; the bank here is the buyer.
- E (The full default loss, because a CDS pays only after the bank has sold the bonds in the market): A CDS pays on the credit event itself; the buyer does not have to sell the bonds in the market first, and avoiding the default loss is the whole point of buying protection.
Check:
| Party | Pays | Receives | Main risk after the trade |
|---|---|---|---|
| Protection buyer (this bank) | Periodic premium | Payout on credit event | Seller fails to pay (counterparty risk) |
| Protection seller | Payout on credit event | Periodic premium | Reference entity's default |
Memory tip: Buyer pays premium and keeps counterparty risk; seller earns premium and takes the default risk.
Show answer
Answer: C — Yellow zone: more exceptions than a sound model would usually produce, so the model is questionable and the capital multiplier is likely to be raised.
The idea: Backtesting asks a simple question: does the model's 'worst normal day' really get beaten only about 1 day in 100? A 99% VaR should be exceeded about 2 or 3 times in 250 days. Seven breaches is a warning sign but not proof that the model is broken, so it lands in the middle (yellow) band.
- Expected exceptions for a correct 99% model over 250 days = 1% × 250 = 2.5.
- Basel traffic-light bands for 250 observations at 99%: green = 0 to 4 exceptions, yellow = 5 to 9, red = 10 or more.
- 7 exceptions falls in 5 to 9, so the result is in the yellow zone.
- Yellow means the supervisor presumes a higher capital multiplier (the plus factor rises with each exception; in the 1996 framework it was 0.65 for 7 exceptions, taking the multiplier from 3 to 3.65), but can consider the reasons for the breaches.
- The bank should investigate the causes of the breaches, for example model weakness, intraday trading or bad luck.
Why the others are wrong:
- A (Green zone: 7 exceptions is normal for a 99% model, so no action is needed): Green covers only 0 to 4 exceptions; 7 is almost three times the 2.5 expected, so 'no action' is not correct.
- B (Red zone: the model is presumed inaccurate and the maximum penalty applies): Red starts at 10 exceptions; 7 is below that line, so the model is not automatically presumed inaccurate.
- D (No zone applies, because backtesting compares VaR with stressed VaR, not with actual losses): Backtesting compares the VaR estimate with actual (or hypothetical) daily P&L; stressed VaR is a separate measure, not the backtest benchmark.
- E (Green zone, because the exceptions are below 5% of the 250 days): The test is set against the 1% tail, not 5%. 7 exceptions is 2.8% of 250 days, well above the 1% (2.5 days) a correct 99% model would show.
Check:
| Exceptions in 250 days | Zone | Reading |
|---|---|---|
| 0–4 | Green | Model acceptable |
| 5–9 | Yellow | Questionable; graded capital increase |
| 10 or more | Red | Model presumed inaccurate |
Expected exceptions at 99% over 250 days = 2.5.
Memory tip: Think ‘4 and 10’: up to 4 is green, 10 and above is red, everything in between is yellow.
Answer: C — Yellow zone: more exceptions than a sound model would usually produce, so the model is questionable and the capital multiplier is likely to be raised.
The idea: Backtesting asks a simple question: does the model's 'worst normal day' really get beaten only about 1 day in 100? A 99% VaR should be exceeded about 2 or 3 times in 250 days. Seven breaches is a warning sign but not proof that the model is broken, so it lands in the middle (yellow) band.
- Expected exceptions for a correct 99% model over 250 days = 1% × 250 = 2.5.
- Basel traffic-light bands for 250 observations at 99%: green = 0 to 4 exceptions, yellow = 5 to 9, red = 10 or more.
- 7 exceptions falls in 5 to 9, so the result is in the yellow zone.
- Yellow means the supervisor presumes a higher capital multiplier (the plus factor rises with each exception; in the 1996 framework it was 0.65 for 7 exceptions, taking the multiplier from 3 to 3.65), but can consider the reasons for the breaches.
- The bank should investigate the causes of the breaches, for example model weakness, intraday trading or bad luck.
Why the others are wrong:
- A (Green zone: 7 exceptions is normal for a 99% model, so no action is needed): Green covers only 0 to 4 exceptions; 7 is almost three times the 2.5 expected, so 'no action' is not correct.
- B (Red zone: the model is presumed inaccurate and the maximum penalty applies): Red starts at 10 exceptions; 7 is below that line, so the model is not automatically presumed inaccurate.
- D (No zone applies, because backtesting compares VaR with stressed VaR, not with actual losses): Backtesting compares the VaR estimate with actual (or hypothetical) daily P&L; stressed VaR is a separate measure, not the backtest benchmark.
- E (Green zone, because the exceptions are below 5% of the 250 days): The test is set against the 1% tail, not 5%. 7 exceptions is 2.8% of 250 days, well above the 1% (2.5 days) a correct 99% model would show.
Check:
| Exceptions in 250 days | Zone | Reading |
|---|---|---|
| 0–4 | Green | Model acceptable |
| 5–9 | Yellow | Questionable; graded capital increase |
| 10 or more | Red | Model presumed inaccurate |
Expected exceptions at 99% over 250 days = 2.5.
Memory tip: Think ‘4 and 10’: up to 4 is green, 10 and above is red, everything in between is yellow.
Show answer
Answer: E — Lower earnings after the board decided to exit a profitable business line that later grew strongly.
The idea: Basel defines operational risk as the risk of loss from inadequate or failed internal processes, people and systems, or from external events. Legal risk is included; strategic and reputational risk are excluded. A poor business decision by the board is a strategic choice, not a breakdown in operations.
- Test each loss against the four causes: processes, people, systems and external events, with legal risk included.
- Cashier theft: people (internal fraud), so it is operational risk.
- Court penalty for mis-selling: legal risk arising from clients, products and business practices, which the definition includes, so it is operational risk.
- Core banking outage: systems failure and business disruption, so it is operational risk.
- Flood damage: external event causing damage to physical assets, so it is operational risk.
- Lower earnings from the board's decision to exit a business line: strategic risk, which the Basel definition excludes.
Why the others are wrong:
- A (Cash stolen by a branch cashier who manipulated vault records): Theft by a staff member is internal fraud, a people failure and one of the Basel operational loss event types.
- B (Penalty and compensation ordered by a court after customers were mis-sold a product): Legal risk is explicitly part of the Basel operational risk definition; mis-selling penalties fall under clients, products and business practices.
- C (A day of lost fee income and overtime costs when the core banking system crashed): A system crash is business disruption and system failure, a core operational risk event type.
- D (Repair costs after floodwater damaged a branch and its ATMs): Flood damage is an external event causing damage to physical assets, which is included in operational risk.
Check:
| Loss | Cause | Op risk? |
|---|---|---|
| Cashier theft | People (internal fraud) | Yes |
| Mis-selling penalty | Legal / business practices | Yes |
| Core system crash | Systems | Yes |
| Branch flood | External event | Yes |
| Exit of a business line | Strategic decision | No |
Memory tip: Op risk = process, people, systems, external events, and legal is in. Strategy and reputation are out.
Answer: E — Lower earnings after the board decided to exit a profitable business line that later grew strongly.
The idea: Basel defines operational risk as the risk of loss from inadequate or failed internal processes, people and systems, or from external events. Legal risk is included; strategic and reputational risk are excluded. A poor business decision by the board is a strategic choice, not a breakdown in operations.
- Test each loss against the four causes: processes, people, systems and external events, with legal risk included.
- Cashier theft: people (internal fraud), so it is operational risk.
- Court penalty for mis-selling: legal risk arising from clients, products and business practices, which the definition includes, so it is operational risk.
- Core banking outage: systems failure and business disruption, so it is operational risk.
- Flood damage: external event causing damage to physical assets, so it is operational risk.
- Lower earnings from the board's decision to exit a business line: strategic risk, which the Basel definition excludes.
Why the others are wrong:
- A (Cash stolen by a branch cashier who manipulated vault records): Theft by a staff member is internal fraud, a people failure and one of the Basel operational loss event types.
- B (Penalty and compensation ordered by a court after customers were mis-sold a product): Legal risk is explicitly part of the Basel operational risk definition; mis-selling penalties fall under clients, products and business practices.
- C (A day of lost fee income and overtime costs when the core banking system crashed): A system crash is business disruption and system failure, a core operational risk event type.
- D (Repair costs after floodwater damaged a branch and its ATMs): Flood damage is an external event causing damage to physical assets, which is included in operational risk.
Check:
| Loss | Cause | Op risk? |
|---|---|---|
| Cashier theft | People (internal fraud) | Yes |
| Mis-selling penalty | Legal / business practices | Yes |
| Core system crash | Systems | Yes |
| Branch flood | External event | Yes |
| Exit of a business line | Strategic decision | No |
Memory tip: Op risk = process, people, systems, external events, and legal is in. Strategy and reputation are out.
Show answer
Answer: B — Reverse stress testing.
The idea: Most stress tests ask, 'If this shock happens, how badly are we hurt?' A reverse stress test turns the question round: 'What would have to happen for us to fail?' It is used to find blind spots and severe but plausible combinations that normal scenarios might miss.
- Note the starting point: the exercise starts from a failure outcome (CET1 below the minimum), not from a given shock.
- Note the direction: it works backwards from the outcome to the events that could cause it.
- Starting from the outcome and working back to the causes is the defining feature of reverse stress testing.
- The findings feed the ICAAP and contingency planning, showing management which weak points to watch.
Why the others are wrong:
- A (Sensitivity analysis): Sensitivity analysis shocks one risk factor at a time (for example, +100 bp in rates) and measures the impact; it starts from the shock, not from failure.
- C (Historical scenario analysis): Historical scenario analysis replays a past crisis (for example, 2008 market moves) on today's balance sheet; it starts from a known past event.
- D (Backtesting of the VaR model): Backtesting compares VaR forecasts with actual P&L to check model accuracy; it is not a stress test.
- E (Forward-looking hypothetical scenario analysis): Forward-looking scenario analysis designs a plausible future set of shocks and works out the result; it runs from cause to effect, the opposite direction.
Check:
| Exercise | Starts from | Asks |
|---|---|---|
| Sensitivity | One factor shock | How much do we lose? |
| Scenario (historical or hypothetical) | Multi-factor shock set | How much do we lose? |
| Reverse stress test | Failure outcome | What would make us fail? |
Memory tip: Reverse = run the film backwards: start at the failure, find the cause.
Answer: B — Reverse stress testing.
The idea: Most stress tests ask, 'If this shock happens, how badly are we hurt?' A reverse stress test turns the question round: 'What would have to happen for us to fail?' It is used to find blind spots and severe but plausible combinations that normal scenarios might miss.
- Note the starting point: the exercise starts from a failure outcome (CET1 below the minimum), not from a given shock.
- Note the direction: it works backwards from the outcome to the events that could cause it.
- Starting from the outcome and working back to the causes is the defining feature of reverse stress testing.
- The findings feed the ICAAP and contingency planning, showing management which weak points to watch.
Why the others are wrong:
- A (Sensitivity analysis): Sensitivity analysis shocks one risk factor at a time (for example, +100 bp in rates) and measures the impact; it starts from the shock, not from failure.
- C (Historical scenario analysis): Historical scenario analysis replays a past crisis (for example, 2008 market moves) on today's balance sheet; it starts from a known past event.
- D (Backtesting of the VaR model): Backtesting compares VaR forecasts with actual P&L to check model accuracy; it is not a stress test.
- E (Forward-looking hypothetical scenario analysis): Forward-looking scenario analysis designs a plausible future set of shocks and works out the result; it runs from cause to effect, the opposite direction.
Check:
| Exercise | Starts from | Asks |
|---|---|---|
| Sensitivity | One factor shock | How much do we lose? |
| Scenario (historical or hypothetical) | Multi-factor shock set | How much do we lose? |
| Reverse stress test | Failure outcome | What would make us fail? |
Memory tip: Reverse = run the film backwards: start at the failure, find the cause.
Show answer
Answer: D — Pay fixed and receive floating on a notional of about ₹2,000 crore.
The idea: The bank earns a fixed rate on its loans but pays a floating rate on its deposits, so rising rates push funding costs up while loan income stays the same. Paying fixed and receiving floating in a swap brings in floating income that rises with deposit costs, which protects the margin.
- Map the gap: assets are fixed-rate, while liabilities are floating (they reprice quarterly). This is a liability-sensitive position, so higher rates reduce NII.
- To neutralise it, the bank needs an inflow that rises when rates rise, i.e. it should receive floating.
- In a plain-vanilla swap, receiving floating means paying fixed.
- Net effect: fixed loan income − fixed swap payment + floating swap receipt − floating deposit cost, so the floating legs largely offset and the margin is locked in.
- The notional should roughly match the exposure (about ₹2,000 crore), adjusted for duration and amortisation.
Why the others are wrong:
- A (Receive fixed and pay floating on a notional of about ₹2,000 crore): Receiving fixed and paying floating adds a second fixed asset funded by floating payments, which makes the NII loss from rising rates bigger.
- B (A basis swap that exchanges one floating benchmark for another floating benchmark): A basis swap swaps one floating index for another; it does not close the gap between fixed-rate assets and floating-rate liabilities.
- C (Buy credit default swap protection on the corporate borrowers): A CDS hedges the borrowers' default risk, not interest rate risk on the margin.
- E (A currency swap exchanging rupee principal for US dollar principal): A currency swap manages exchange-rate and cross-currency funding risk; this exposure is purely rupee interest rate risk.
Check:
| Leg | Effect when rates rise |
|---|---|
| Fixed loan income | Unchanged |
| Floating deposit cost | Rises |
| Swap: receive floating | Rises (offsets deposit cost) |
| Swap: pay fixed | Unchanged |
Pay-fixed swap = the classic hedge for fixed-rate assets funded by floating-rate liabilities.
Memory tip: Hedge the side that floats: floating liabilities → receive floating in the swap (pay fixed).
Answer: D — Pay fixed and receive floating on a notional of about ₹2,000 crore.
The idea: The bank earns a fixed rate on its loans but pays a floating rate on its deposits, so rising rates push funding costs up while loan income stays the same. Paying fixed and receiving floating in a swap brings in floating income that rises with deposit costs, which protects the margin.
- Map the gap: assets are fixed-rate, while liabilities are floating (they reprice quarterly). This is a liability-sensitive position, so higher rates reduce NII.
- To neutralise it, the bank needs an inflow that rises when rates rise, i.e. it should receive floating.
- In a plain-vanilla swap, receiving floating means paying fixed.
- Net effect: fixed loan income − fixed swap payment + floating swap receipt − floating deposit cost, so the floating legs largely offset and the margin is locked in.
- The notional should roughly match the exposure (about ₹2,000 crore), adjusted for duration and amortisation.
Why the others are wrong:
- A (Receive fixed and pay floating on a notional of about ₹2,000 crore): Receiving fixed and paying floating adds a second fixed asset funded by floating payments, which makes the NII loss from rising rates bigger.
- B (A basis swap that exchanges one floating benchmark for another floating benchmark): A basis swap swaps one floating index for another; it does not close the gap between fixed-rate assets and floating-rate liabilities.
- C (Buy credit default swap protection on the corporate borrowers): A CDS hedges the borrowers' default risk, not interest rate risk on the margin.
- E (A currency swap exchanging rupee principal for US dollar principal): A currency swap manages exchange-rate and cross-currency funding risk; this exposure is purely rupee interest rate risk.
Check:
| Leg | Effect when rates rise |
|---|---|
| Fixed loan income | Unchanged |
| Floating deposit cost | Rises |
| Swap: receive floating | Rises (offsets deposit cost) |
| Swap: pay fixed | Unchanged |
Pay-fixed swap = the classic hedge for fixed-rate assets funded by floating-rate liabilities.
Memory tip: Hedge the side that floats: floating liabilities → receive floating in the swap (pay fixed).
Topics covered today
- Module A — Risk and Risk Management Framework: ALM and interest rate risk in the banking book — Duration gap; Risk management framework — Risk appetite, capacity and limits
- Module B — Credit Risk: Measurement of credit risk — Expected loss; Credit derivatives — Credit default swap
- Module C — Market Risk: Value at Risk — Backtesting of VaR models
- Module D — Operational Risk: Operational risk — Definition and scope
- Module E — Basel and RBI Guidelines on Risk Management: Regulatory capital and capital adequacy — Tier 1 ratio; Basel III buffers — Countercyclical capital buffer; Stress testing — Reverse stress testing
- Module F — Derivatives and Risk Management: Swaps — Uses of interest rate swaps
Tomorrow’s post continues the series with another fresh set of 10 CAIIB Risk Management practice questions. Bookmark SimplifyingFin and revise one set a day.
Disclaimer: This quiz is an independent practice aid for educational purposes. It is not affiliated with, endorsed by, or published by IIBF. Always cross-check regulations and circulars from official RBI/IIBF sources before relying on any figure in an exam or at work.

