Claude Certified Architect – Foundations questions sit inside realistic scenarios rather than floating as isolated facts. Exam-guide summaries describe six scenario themes, four of which are drawn at random for each sitting. You cannot choose which four you get, so prepare for all six. Each scenario mixes domains: one situation may ask about loop design, then tool errors, then caching.
Customer support resolution agent
An agent resolves customer tickets using tools for orders, accounts and refunds. Expect questions on loop limits, tool errors, escalation triggers and handoffs, policy thresholds enforced in code, and caching a long, stable system prompt. Our bank has 19 practice questions set in this scenario.
Code generation with Claude Code
A team uses Claude Code to write and change code. Expect CLAUDE.md scoping, plan mode for risky changes, custom commands, hooks for formatting or protected paths, and clearing or compacting sessions. Our bank has 11 practice questions set in this scenario.
Multi-agent research system
A coordinator delegates research to subagents. Expect parallel fan-out, subagent briefs, structured findings with citations, handling contradictions and keeping the coordinator's context small. Our bank has 9 practice questions set in this scenario.
Developer productivity with Claude
Claude helps a development team explore and operate systems. Expect MCP server choice and scope, transports, tool consolidation, read-only access and shared project configuration. Our bank has 14 practice questions set in this scenario.
Claude Code for continuous integration
Claude Code runs in pipelines. Expect headless invocation, structured output, restricted tool allowlists, independent review passes, batch processing and reliable retries. Our bank has 9 practice questions set in this scenario.
Structured data extraction
Claude turns documents into structured records. Expect schema design with nullable fields and enums, forced tool use, validation-retry loops, truncation checks and cost choices such as batching. Our bank has 9 practice questions set in this scenario.
How to use scenarios when studying
Pick one scenario a day and build a small version of it — a ticket agent with two tools, a Claude Code repository with a CLAUDE.md and a hook, a two-subagent research script, a forced-tool extractor. Then break it on purpose: return an error from a tool, let the loop run away, change the start of a cached prompt, truncate an output. Each failure you watch and fix maps directly onto the kind of question the exam asks. When you sit the practice exam, every question shows its scenario so you can see which settings you handle best.
The scenario list comes from published exam-guide summaries; our descriptions of what each one emphasises are our own study guidance, not official content.