How the cases work
The CCAR-F exam frames its questions in six scenarios and picks four of them for each sitting. Each case below turns one scenario into a small fictional company with concrete systems, numbers and problems, so the exercise at the end of every lesson has something real to design against.
The same company returns in several lessons. By the end of the guide you will have designed, for example, the support agent's loop, its hooks, its tool errors, its escalation rules and its context strategy.
The companies, people and numbers are invented for study. Any resemblance to a real organisation is coincidental.
| Case | Exam scenario | The problem in one line |
|---|---|---|
| Cedar Ridge Outfitters | Customer support resolution agent | A support agent on the Agent SDK must resolve 80% of contacts and know when to hand off |
| Harbor Lane Software | Code generation with Claude Code | Sixty engineers share one monorepo and need consistent Claude Code configuration |
| Whitfield Research Group | Multi-agent research system | A coordinator and four subagents produce cited market reports |
| Lakeshore Freight | Developer productivity with Claude | An internal agent helps engineers understand a 15-year-old codebase |
| Keystone Payments | Claude Code for continuous integration | An automated pull request reviewer has lost developers' trust |
| Bayview Payables | Structured data extraction | Invoices and contracts must become validated JSON for the finance system |