Fin Maverick
Foundations VocabularyAccounting & ReportingEconomics & MacroQuant Methods & ProgrammingBusiness & Company AnalysisCorporate Finance & ValuationBehavioural Finance
Banking & Market InfrastructureFixed Income & RatesDerivatives & Structured ProductsPublic EquitiesTransactions & DealsPortfolio ConstructionFunds & AMCs
Private Markets & AlternativesRisk, Treasury & ControlAI & Digital FinanceStochastic Calculus & PricingWealth & Personal FinanceIndian Markets & RegulationProfessional Practice
CalculatorComparison
Frameworks
Explore Bootcamps
Equity ResearchPortfolio ManagementMutual Fund MasteryInvestment Banking Analyst
Private Equity AnalystQuant & Hedge Fund AnalystBreaking Into VCFinancial Analyst Program
Risk Management ProgramPrivate Wealth ManagementDebt Capital MarketsDerivatives Foundation
Explore Free Courses

Equity Research6

Writing an Investment ThesisBuilding a Discounted Cash FlowReading an Annual Report FastReading a Sector Before a CompanySpotting Quality of Earnings Red FlagsBuilding a Revenue Forecast From Drivers

Portfolio Management3

Rebalancing: When, Why and What It CostsStrategic and Tactical Asset AllocationMeasuring Risk in a Portfolio

Mutual Fund Mastery3

Comparing Funds Without Being FooledHow a NAV Is Struck and Which Day You GetReading a Fund Factsheet Properly

Derivatives Unlocked4

Hedging a Real ExposureThe Greeks, PracticallyFutures, the Basis and What Moves ItReading an Option Payoff

AI For Finance2

Retrieval and Grounding for FinanceDocument Extraction in Finance

Breaking Into Quants4

Backtesting a StrategyHypothesis TestingCleaning Financial DataRegression for Finance

Breaking Into VC3

Sizing a MarketReading a Term Sheet as a FounderHow a Venture Round Actually Works

Financial Analyst Program4

Common Size and Trend AnalysisReading a Cash Flow StatementRatio Analysis That Says SomethingBuilding a Working Capital Schedule

Risk Management Program2

Credit Exposure and How It Is ReducedValue at Risk and What It Hides

Investment Banking Analyst3

Precedent Transactions and Why They DifferReading a Term Sheet StructurallyBuilding a Comparable Companies Table

Private Wealth Management3

Tax Aware Portfolio DecisionsBuilding a Client Risk ProfileGoal Based Planning Arithmetic

Debt Capital Markets3

Analysing an Issuer's CreditDuration and What It Does Not Tell YouBond Pricing and Yield Mechanics

Private Equity Analyst2

Fund Waterfalls and CarryThe LBO in Structure

Hedge Funds Analyst2

Short Selling MechanicsLong Short Mechanics
QuarksCourses
Explore Interview Preparation
Investment BankingEquity ResearchVenture CapitalistPrivate EquityHedge Funds
QuantFinancial AnalysisPrivate Wealth ManagementDebt Capital MarketsRisk Management
Derivatives FoundationPortfolio ManagementMutual Fund Mastery
PartnershipsShowdown
Log inSign up
Interview tracksAll
1Investment Banking
Question bankPuzzlesCase studies
2Equity Research
Question bankPuzzlesCase studies
3Venture Capital
Question bankPuzzlesCase studies
4Private Equity
Question bankPuzzlesCase studies
5Hedge Funds
Question bankPuzzlesCase studies
6Quant
Question bankPuzzlesCase studies
7Financial Analysis
Question bankPuzzlesCase studies
8Private Wealth Management
Question bankPuzzlesCase studies
9Debt Capital Markets
Question bankPuzzlesCase studies
10Risk Management
Question bankPuzzlesCase studies
11Derivatives Foundation
Question bankPuzzlesCase studies
12Portfolio Management
Question bankPuzzlesCase studies
13Mutual Fund Mastery
Question bankPuzzlesCase studies
097

Case 097Risk measurement and limitsHard

Vairagi's 99% one-day VaR was exceeded 8 times in 250 days, against 2.5 expected. Is the model wrong? Use the binomial distribution and the traffic-light idea to decide.

1The situation

Vairagi Capital's risk team backtests the fund's one-day 99% value at risk over the past 250 trading days. An exception is a day on which the realised loss exceeded that morning's VaR. A correct model should produce one exception in a hundred days, 2.5 over the year. The log shows 8, on days 37, 112, 118, 119, 121, 122, 205, 236.

The portfolio manager's view is that the year was unusually turbulent and eight is nothing to act on. The chief risk officer wants a number, not a view.

2Your task

Decide whether eight exceptions are consistent with a correct model, using the binomial distribution and the traffic-light zones, and say what else in the log matters.

Quick check

Under a correct 99% model, how likely are 8 or more exceptions in 250 days?

Worked solution

Try it on paper, then open one step at a time.

30-second answerThe answer to give first

Under a correct model the chance of 8 or more exceptions in 250 days is 0.40%, about one year in 248, so the model is presumed wrong until shown otherwise. Eight sits in the amber zone of the traffic-light framework, where a correct model lands only 10.8% of the time. The observed rate of 3.2% says the number reported as 99% VaR behaves like a 96.8% VaR, and the clustering of five exceptions in eleven days points at a volatility input that lagged the market.

Step 1What is the chance of eight under a correct model?

A coin that is meant to land heads one time in a hundred lands heads eight times in 250 throws. You do not need a theory of coins to be suspicious; you need the binomial distribution. If each day has an independent 1% chance of an exception, the count over 250 days is binomial with mean 2.5 and standard deviation 1.57, and the chance of 8 or more is 0.40%. That is one year in about 248. The portfolio manager's turbulent-year point is not an answer, because the VaR is supposed to update to the turbulence: a model that produces exceptions whenever markets are volatile is a model that does not measure volatility. The formal version is the Kupiec test: the likelihood ratio comparing p = 1% with the observed 3.2% is 7.7, against a chi-square critical value of 3.841, with a p-value of about 0.54%.

The relationship
P(X≥8)=1−∑k=07(250k) 0.01k 0.99250−k≈0.0040LR=−2ln⁡0.99242 0.0180.968242 0.0328≈7.7P(X \ge 8) = 1 - \sum_{k=0}^{7} \binom{250}{k}\, 0.01^k\, 0.99^{250-k} \approx 0.0040 \qquad LR = -2\ln\frac{0.99^{242}\,0.01^{8}}{0.968^{242}\,0.032^{8}} \approx 7.7
Xthe number of exceptions in 250 days, binomial under a correct model
LRKupiec's likelihood ratio, chi-square with one degree of freedom under the null
0.032the observed exception rate, 8 over 250
What it says in wordsAdd up the chances of 0 to 7 exceptions and subtract from 1; the remainder, under half a percent, is how often a correct model produces a year this bad.
Eight exceptions almost never happen under a correct modelgreen: 0 to 4amber: 5 to 9red: 10+10%20%30%08.1120.5225.7321.5413.456.762.7789101112observed: 8P(8 or more) = 0.40%Number of exceptions in 250 days, expected 2.5A correct model lands in amber 10.8% of the time and in red 0.03% of the time.
Under Vairagi's stated 1% rate the exception count peaks at 2 and is below 1% by 7; the observed 8 lies deep in the amber zone with a 0.40% chance of 8 or more, and a correct model enters amber only 10.8% of the time.
Step 2What do the traffic-light zones add?

The zones turn the probability into a rule a committee can apply without arguing. The Basel framework for 250-day backtests puts 0 to 4 exceptions in green, 5 to 9 in amber and 10 or more in red, chosen so that a correct model is green about 89% of the time and red almost never. Amber carries a capital multiplier that rises with the count, and the burden of proof shifts to the risk team to explain why the model is not wrong. Confirm the current thresholds and multipliers before quoting them; the numbers here are the framework's design logic, not a live regulatory figure. The zones also admit what the test cannot do: with 250 days it is weak. If the true exception rate were 2%, double the stated risk, the model would still land in green 44% of the time. A green light is not a clean bill of health; a red or deep amber is a strong signal.

ZoneExceptions in 250 daysChance under a correct modelResponse
Green0 to 489.2%Accept; no capital add-on
Amber5 to 910.8%Investigate; add-on scales with the count
Red10 or more0.03%Model presumed wrong; maximum add-on
The traffic-light zones for a 250-day backtest of 99% VaR. Vairagi's 8 is amber; a correct model reaches amber 10.8% of the time, so the count alone is strong evidence against the model.
Step 3How wrong is the model, and where?

Eight exceptions estimate the true tail probability at 3.2%, and a 95% lower bound on it is about 1.6%, so the data rule out 1% but not 1.6%. Under a normal model, a quantile that is breached 3.2% of the time instead of 1% is at 1.85 standard deviations instead of 2.33, so the model understates volatility by roughly 26%, if the shape is right and the scale is wrong. The log tells you where to look: five of the eight exceptions fall between day 112 and day 122, and two pairs are on consecutive days. Under independence at a 3.2% rate, the chance that two or more of eight exceptions are followed next day by another is about 2.5%. Clustering is the signature of a volatility input that lagged the market for one stretch, a long lookback window or a slow decay, rather than a tail that is permanently fat. The Christoffersen test formalises this: it tests the count and the independence separately, and this log fails both.

Where the exceptions fell: five of eight inside eleven daysday 1day 50day 100day 150day 200day 25037112, 118, 119, 121, 122205236An independent 1% process spreads 2 or 3 exceptions over the year with no pattern.Here 2 of the 8 are followed next day by another; chance of that under independence at 3.2%: about 2.5%.Clustering says the volatility input lagged the market during one stretch.Two failures to test: the count (Kupiec) and the independence (Christoffersen).
Vairagi's eight exceptions are not spread across the year: five fall inside eleven days from day 112 to 122, and 2 are followed the next day by another, which an independent process at the observed rate does only about 2.5% of the time.
Step 4What do you tell the chief risk officer?

Lead with the number, then the diagnosis, then the fix. The count is inconsistent with a correct model at any reasonable confidence, the realised rate is about three times the stated one, and the exceptions cluster, so the first suspect is the volatility estimate's speed of response, not the distribution's shape. Rerun the year with a faster decay or a shorter window and count again; if the cluster disappears and the count falls to the green zone, the fix is the window. If exceptions remain spread through calm periods, the tail is fat and the model needs a heavier-tailed distribution or a historical simulation. Say the limitation: 250 days is a short record, the test cannot see a model that is 50% too small, and a single cluster can be one bad fortnight. The response is to fix and re-test, not to raise the VaR by 26% and move on.

Where candidates lose it

The common loss is accepting the turbulent-year defence: eight exceptions because markets were wild. The VaR's job is to track that wildness. Exceptions that arrive together are evidence of a model that lagged, not of bad luck.

The second is treating the mean of 2.5 as a target and 8 as merely above it, without computing the tail. The binomial puts 8 at 3.5 standard deviations; the probability, under half a percent, is the answer.

What the interviewer asks next

  • How many exceptions would a 97.5% expected-shortfall backtest expect, and how would you test it?
  • Rerun the count for 500 days with 12 exceptions: which zone, and how does the test's power change?
  • How would you test the independence of exceptions formally rather than by eye?
  • If the eight exceptions were all small breaches of VaR, does that change your conclusion?
← Case 096Stambhika joins the bid at Rs 250.00 behind 40,000 shares with a 10,000 share buy order. Fills arrive at 2,000 shares a minute, and 60% of the selling that reaches the bid comes just before a 5 paise drop. How long until you fill, what is the chance the price moves first, and what is the adverse selection per fill worth?Case 098 →Corvinta runs two markets on the same pair of dice: A settles at their sum and B at the first die minus the second. Another player quotes A at 6.5 bid, 7.5 offer and B at -0.5 bid, 0.5 offer. The first die is revealed as 5. Update both fair values and find the trades.

Company names and figures are illustrative.

Fin Maverick Free CoursesExplore Free Courses
Fin Maverick BootcampsExplore Bootcamps
Fin Maverick

Finance education that ends in a job, not a certificate that gathers dust. Built for young India.

LEARN
CalculatorsFrameworksComparisonsInterview RoadmapsShowdown
RESOURCES
All CoursesFree CoursesBootcampsInternships
COMPANY
AboutJob openingPartnership
LEGAL
Privacy PolicyTerms & ConditionsContent LicenseReturn & Refund Policy
© 2026 FIN MAVERICK / BUILT FOR INDIA.DO FINANCE, DO NOT JUST READ ABOUT IT.