I built AI systems with Claude for months before I sat the exam. Tool-calling agents, RAG pipelines, multi-agent orchestrators — the code was there. What I didn't have was a structured, validated understanding of the architectural patterns and terminology Anthropic uses to describe these systems. The Claude Certified Architect – Foundations exam gave me that, and the process of preparing for it sharpened my thinking in ways that have already changed how I design systems.
This post is the guide I wish I'd had when I started preparing. It covers the five exam domains with their weights, what actually appears on the test (not just what the syllabus says), my study approach, and the resources that made the biggest difference. Whether you're brand new to the Claude ecosystem or already shipping Claude-powered features in production, this will tell you where to focus.
Exam snapshot: Proctored (online or at a test center), 60 multiple-choice and multiple-response items, 120 minutes, a scaled score of 720 on a 100–1,000 scale to pass (from Anthropic's official exam guide, version 1.0). On pass you receive a Credly digital badge. My badge: Claude Certified Architect – Foundations.
The 5 Exam Domains
| Domain | Weight | Core focus |
|---|---|---|
| 1. Agentic Architecture & Orchestration | 27% | Tool-use loop, multi-agent patterns, stop_reason, coordinator/subagent design |
| 2. Claude Code Configuration & Workflows | 20% | CLAUDE.md, skills/slash commands, plan mode, CI/CD integration |
| 3. Prompt Engineering & Structured Output | 20% | Explicit criteria, few-shot examples, JSON schemas, batch processing |
| 4. Tool Design & MCP Integration | 18% | Tool descriptions, structured errors, Model Context Protocol |
| 5. Context Management & Reliability | 15% | Context windows, escalation strategies, error propagation, provenance |
The weights matter. Domain 1 at 27% is not slightly ahead of the others — it is the exam. Everything else is the support act.
Domain 1: Agentic Architecture & Orchestration (27%)
This is where the exam spends the most time and where preparation pays the highest return.
What it tests: The mechanics of how Claude executes multi-step work using tools. Not the concept — the exact sequence of events: how the model decides to call a tool, what the response looks like, how the result gets injected back into the conversation, and how the loop terminates.
The key concept — the tool-use loop:
1. You send a message with available tool definitions
2. Claude responds with stop_reason: "tool_use" + a tool_use content block
3. You execute the tool and get a result
4. You add a "tool_result" message to the conversation
5. You call the API again — Claude continues reasoning
6. Loop repeats until stop_reason: "end_turn"stop_reason is the primary termination signal. Know its values cold: end_turn (done), tool_use (expects a result), max_tokens (truncated), stop_sequence (custom stop hit).
Multi-agent patterns tested:
- Coordinator/subagent: A top-level orchestrator breaks work into tasks and delegates to specialised subagents. Each subagent has its own context — they don't share conversation history with each other.
- Hub-and-spoke: One coordinator routes to multiple domain-specific agents. The coordinator synthesises results.
- When to use a subagent vs a tool call: If the task needs its own reasoning loop and context — subagent. If it's a deterministic operation (DB query, API call, calculation) — tool call.
Spend 40% of your total study time on Domain 1. A strong understanding here easily covers more than a quarter of the exam and makes Domains 4 and 5 much easier to follow.
Domain 2: Claude Code Configuration & Workflows (20%)
What it tests: How Claude Code is configured and how it behaves in practice — not just what the features are, but when they apply.
Key areas:
CLAUDE.md — the project instruction file. The exam tests: where it lives (repo root, ~/.claude/, .claude/), how multiple files are merged, and what kind of guidance belongs there (architecture conventions, project-specific commands, tool allowlists).
Skills / slash commands — packaged task definitions. Know that a skill is invoked with /skill-name and that the runtime loads its instructions before Claude acts, not as general memory.
Plan mode — Claude outlines an approach before executing. Exam questions test when plan mode is appropriate (large refactors, destructive operations) versus when it adds friction unnecessarily.
CI/CD integration — headless Claude Code in automated pipelines. Know the --print flag for non-interactive output, how to scope permissions in CI, and the difference between a hook and a permission.
Domain 3: Prompt Engineering & Structured Output (20%)
What it tests: Writing prompts that reliably produce consistent, parseable output — not prompt tips, but the engineering discipline of prompt design.
Explicit evaluation criteria: The exam is strong on prompts that tell the model how to judge its own output. "Be concise" is weak. "Respond in under 3 sentences, include a concrete example, and avoid jargon" is testable.
Few-shot examples: Use them when output format is non-trivial or when zero-shot produces inconsistent quality. 3–5 examples is the sweet spot. Include at least one edge-case example.