Claude Certification Blog
What does the Claude certification cover, and what does it leave out?
What does the Claude certification cover? Four different things, depending which of the four exams you sit — and in every case a chain of connected decisions rather than a list of features to memorise.
What does the Claude certification cover depends on which exam: everyday product use for Associate – Foundations, building on the API for Developer – Foundations, end-to-end system design for Architect – Foundations, and enterprise design and governance for Architect – Professional. Each publishes five to seven weighted domains. What none of them publishes, and what the exams actually test, is how those domains depend on each other.
One cycle, not a topic list
A blueprint reads like independent chapters. The exam does not treat them that way. The Associate domains, for instance, form a single operating loop — the choice of product and model bounds what the prompt can do, the prompt produces the output the evaluation domain has to judge, and governance sits over every link rather than beside them.
That matters for a practical reason. If you study the domains as separate chapters, a question that starts in one and is answered in another reads as unfair. Once you can see the edges, the same question reads as obvious.
What does the Claude certification cover, exam by exam?
Four blueprints, four different through-lines. They overlap far less than the shared brand suggests.
| Exam | Domains | The through-line |
|---|---|---|
| CCAO-F | 7 | Using Claude well and responsibly: pick the fit, configure it, prompt it, judge the output, govern the whole thing. |
| CCDV-F | 6 | One engineering decision in six layers: platform mechanics, then one call, then an agent, then production hardening. |
| CCAR-F | 7 | One request traced end to end: surface, API call, prompt and eval, tools, retrieval, MCP, and the agent loop around it. |
| CCAR-P | 5 | One engagement in five acts: design it, harden it, prove it is safe, carry it to stakeholders, leave a team that can run it. |
Judgment, not recall
Every objective is phrased as something you do — select, evaluate, apply, diagnose, design — and the items follow. A scenario describes a situation and asks what to do next, so the wrong options are usually accurate statements that fail a decision rule rather than factual errors. Knowing that Projects hold knowledge sources earns nothing; knowing when a Project is the wrong container earns the item.
It is also why the same bar — a scaled 720 — applies to all four exams regardless of item count. And it is why the exams age slowly despite a fast-moving product: the decision rules — validate before you polish, authorisation is separate from access, match capability to measured risk — outlast any particular feature. Working through Claude certification sample questions makes the pattern obvious faster than reading another objective list.
The questions that span two domains
The hardest items sit on an edge rather than inside a node, and there is a reliable way through them. When a scenario seems to belong to two domains, separate the one supplying the mechanism from the one supplying the judgment call on top of it. The mechanism domain is rarely wrong on its own facts; the judgment domain is where the difficult distractors live.
Follow the edge, not the label
A stem that opens with a retrieval pipeline is often answered by an authorisation rule; one that opens with a model choice is often answered by an evaluation rule. The domain named in the scenario is rarely the domain that governs the answer.
What it deliberately leaves out
None of the four is a coding exam. All are multiple-choice and multiple-response, so nothing you build is assessed, no repository is reviewed, and no live system is inspected. The Developer and Architect exams assume you can read an API request, a tool schema or an agent loop and reason about it — but you demonstrate that by choosing between options, not by shipping anything.
They also do not test speed, tool fluency in any specific IDE, or knowledge of the newest model released last month. And they do not certify outcomes: passing says you can pick the defensible action in a described situation, not that you have delivered one. That gap is worth being honest about when you weigh whether a Claude certification is worth it against the fee and the hours. If you are still choosing between the four, the guide to which Claude certification to take compares them side by side.
Key takeaways
- Four exams, four through-lines — everyday use, building on the API, end-to-end design, and enterprise governance. They are not a ladder.
- Domains are a dependency chain, not independent chapters. The edges are where the hard questions live.
- Objectives are verbs. Every one is phrased as something you do, and the items test exactly that.
- On a cross-domain item, split mechanism from judgment. The judgment domain governs the answer.
- Nothing you build is assessed. These are multiple-choice judgment exams, not practical ones.
Every domain, every objective, published in full
The blueprint for all four Claude certifications — domains, approximate weights and every published objective — laid out per exam.
Browse the exam blueprintsQuestions
Frequently asked
The follow-up questions people search next.
What are the Claude certification domains?
Each exam publishes its own: seven for Associate and Architect – Foundations, six for Developer – Foundations, five for Architect – Professional. Each domain carries an approximate weight and its own list of objectives, and every certification page here lists them in full.
Is the Claude certification blueprint published?
Yes. Each official exam guide publishes its domains, their approximate weights and the objectives under each one. Weights are approximate rather than a guaranteed item count on any single form, but they are stable enough to plan study time around.
Does the exam test the Claude API or the Claude app?
It depends which exam. Associate – Foundations is about using Claude through its product surfaces; Developer – Foundations and both Architect exams are about building and designing with the API, tools, retrieval and MCP. There is no single answer across the four.
Do I need to write code to pass a Claude certification?
Not for Associate – Foundations, which tests product judgment rather than implementation. The Developer and Architect exams assume you can read and reason about API requests, tool schemas and agent loops, though they are multiple-choice rather than a coding test.
Are Claude certification exam topics the same across all four exams?
No, and they are not a ladder either. The four blueprints overlap in prompt engineering and evaluation, but diverge sharply after that — everyday product use, API and agent construction, end-to-end system design, and enterprise governance are genuinely different exams.
Keep reading
Related posts
Not affiliated with, or endorsed by, Anthropic or Pearson VUE. Details are summarised from publicly published program information and can change — always confirm against the official exam guide before booking.