What this is about # Domain 2 — Tool Design & MCP Integration — is 18% of the Claude Certified Architect – Foundations exam, across five task areas: designing tool interfaces, structuring error responses, distributing tools across agents, integrating MCP servers, and choosing built-in tools well. It’s a lighter domain than Agentic Architecture, but arguably the most immediately practical one — every point here shows up the first time you give an agent a tool that doesn’t work the way you expected.
What this is about # Domain 4 — Prompt Engineering & Structured Output — ties Claude Code Configuration & Workflows for second-heaviest domain on the Claude Certified Architect – Foundations exam, at 20%. Its six task areas move from how you write a prompt to how you guarantee what comes back is actually usable: explicit criteria, few-shot examples, schema-enforced output, validation loops, multi-instance review, and batch processing for scale.
What this is about # Claude Certified Architect – Foundations is Anthropic’s certification for designing Claude systems, not just using them. Where the Claude Certified Associate exam tests whether you can operate Claude with professional discipline — good prompts, sound judgment on output, the right entry point for the job — the Architect exam tests something a level up: can you design the agentic system, the tool integrations, and the configuration that other people build on top of. The ideal candidate has 6+ months of hands-on experience building with the Claude API, the Claude Agent SDK, Claude Code, and Model Context Protocol (MCP) — this isn’t a first certification, it’s the next one.
What this is about # Domain 5 — Context Management & Reliability — is the lightest domain on the Claude Certified Architect – Foundations exam at 15%, but its six task areas cover what decides whether a long-running agent stays trustworthy: preserving critical facts across long interactions, knowing when to escalate, letting a multi-agent system recover from failure instead of silently degrading, managing context at scale, and calibrating how much to trust the output.
What this is about # Domain 3 — Claude Code Configuration & Workflows — ties Prompt Engineering & Structured Output for second-heaviest domain on the Claude Certified Architect – Foundations exam, at 20%. Its six task areas are all about how you set up and drive Claude Code itself: configuration file hierarchy, custom commands and skills, conditional rules, choosing plan mode vs. diving straight in, iterating well, and wiring Claude Code into CI/CD.
What this is about # Domain 1 — Agentic Architecture & Orchestration — is the single heaviest domain on the Claude Certified Architect – Foundations exam, worth 27% on its own. The exam guide breaks it into seven task areas: the agentic loop, multi-agent orchestration, subagent configuration, multi-step workflows, SDK hooks, task decomposition, and session management. That’s a lot of ground, so this post condenses it into the five ideas that actually carry the weight, with the smaller two folded into a quick round-up at the end.
What this is # This wraps up the Becoming a Claude Architect series with a self-check: 100 practice questions, 20 per domain, covering everything from Domain 1 — Agentic Architecture & Orchestration through Domain 5 — Context Management & Reliability. Click an answer and you’ll see immediately whether it’s right, with a short explanation either way.
What this is about # Domain 7 of the Claude Certified Associate – Foundations exam is Troubleshooting and Optimization. It’s worth 10% — the lightest domain on the exam. But it’s the one that closes the loop on the other six: everything from prompting to configuration to model selection eventually produces an output that underperforms, and this domain is the discipline of tracing that failure to its root cause, fixing it, and making sure the fix persists instead of getting re-discovered next week.
What this is about # Domain 6 of the Claude Certified Associate – Foundations exam is Configuration and Knowledge Management. It’s worth 12%. The line it draws: using Claude means typing a good prompt today. Operating Claude means building an environment where the right context, instructions, and procedures already exist, so every conversation starts from a configured baseline instead of a blank slate. Configuration is leverage — set it up once, benefit on every conversation that follows — and it’s also what turns individual skill into team capability, since two people asking the same question against the same configured Project get the same quality of answer.
What this is about # Domain 5 of the Claude Certified Associate – Foundations exam is Product and Model Selection. It’s worth 12%. The framing: before prompting even starts, four decisions already set the quality ceiling for the session — the right entry point, the right capability layer, the right model tier, the right context strategy. Get those four wrong and no amount of prompt polish fixes it. Get them right and the prompt has to do a lot less work.
