The exam reuses a small set of scenarios and a handful of exact values. Drill these until they're reflexive — they convert "thinking" questions into "recognition" questions.
The 6 recurring scenarios
Roughly four of these appear on any given exam instance. Each tests the same engineering judgement in a different costume.
| Scenario | Domains | What it tests |
|---|---|---|
| Customer Support Agent | 1, 2, 5 | Escalation triggers, structured errors, PreToolUse for refunds, context preservation |
| Code Generation | 3, 5 | CLAUDE.md hierarchy, plan mode, skills, independent review |
| Multi-Agent Research | 1, 2, 5 | Narrow decomposition, parallel Tasks, provenance, gap annotation |
| Developer Productivity | 1, 2, 3 | Grep vs Glob, MCP config, session management |
| CI/CD Pipeline | 3, 4 | -p flag, multi-pass review, independent review, duplicate prevention |
| Structured Extraction | 4, 5 | Nullable fields, self-correction, retry limits, batch API |
Don't memorise scenario-specific answers — the same principles transfer to any costume. When you recognise a scenario, recall its failure modes (above), then apply the 3 rules.