The four Claude certifications, compared
CCAO-F, CCDV-F, CCAR-F and CCAR-P — who each one is for, how they differ, and which to sit first if you are choosing between them.
Anthropic's certification programme has four credentials across three tracks and two levels. If you are trying to work out which one to sit, the differences are clearer than the codes make them look.
| Code | Credential | Who it is for |
|---|---|---|
CCAO-F | Claude Certified Associate – Foundations | Anyone using Claude in their work, not necessarily building with it |
CCDV-F | Claude Certified Developer – Foundations | Engineers implementing against the API and SDK |
CCAR-F | Claude Certified Architect – Foundations | Architects designing production systems on Claude |
CCAR-P | Claude Certified Architect – Professional | The advanced architect credential |
The pattern is a two-letter track code — AO associate, DV developer, AR architect — followed by the level, F for Foundations or P for Professional. If you have seen this exam called CCA-F or CCAF, those are community spellings of CCAR-F.
The distinction that matters
Track is about what kind of decision you make, not seniority.
The associate credential is about using Claude well: structured prompting, checking output, choosing a model and feature for a task, and knowing where privacy, data sensitivity and human review come in. You do not need to be writing code.
The developer credential is about implementing: working against the API and SDK, wiring things up correctly, making them run.
The architect credential is about trade-offs. Its exam does not ask whether you can build an agentic loop — it assumes you can, then asks whether you would use a coordinator here or a single loop, whether this belongs in a hook or in the prompt, whether this failure should escalate or retry. The published description is explicit that it validates informed decisions about trade-offs when implementing real-world solutions with Claude.
That framing is why the architect exam is a judgement test rather than a recall test, and why experience matters more than study hours for it.
What CCAR-F involves
60 items in 120 minutes, closed book, proctored through Pearson VUE either online or at a test centre. $125 USD. You pass at a scaled score of 720 out of 1,000, and the credential is valid for 12 months.
Questions are grouped under four scenarios drawn at random from a published bank of six — a customer support agent, Claude Code in a team workflow, a multi-agent research system, developer productivity tooling, Claude Code in CI, and structured data extraction.
The five domains and their weights: Agentic Architecture & Orchestration (27%), Claude Code Configuration & Workflows (20%), Prompt Engineering & Structured Output (20%), Tool Design & MCP Integration (18%), Context Management & Reliability (15%).
The ideal candidate has around six months of hands-on experience with the Claude API, Agent SDK, Claude Code and MCP. That is a description of readiness, not a gate.
Do you need one before another?
No. Foundations-level credentials have no formal prerequisites. You can sit CCAR-F without holding CCAO-F or CCDV-F, and most people building production systems on Claude should go straight to it.
The one real sequencing question is CCAR-F before CCAR-P — the Professional credential is the advanced tier of the same track, so Foundations first is the natural order.
Choosing
Sit CCAR-F if you design systems: you decide how agents are orchestrated, where tools come from, how context is managed and when a human gets involved. This is the one this site prepares you for.
Sit CCDV-F if you implement against someone else's design and want to certify that capability.
Sit CCAO-F if you use Claude as part of your work — analysis, writing, research — and want a credential for using it well rather than for building with it.
Sit CCAR-P after CCAR-F, when it is available to you and the Foundations material feels straightforward.
If you are genuinely between the developer and architect tracks, a useful test: when something breaks in production, is your instinct to fix the implementation or to question the design? The architect exam rewards the second.
Is it worth it?
Honestly, it depends on what you want from it. This is a new programme, so the credential has little hiring signal yet — nobody has a hiring pipeline that filters on it.
What it does have is a genuinely well-constructed blueprint. The task statements map onto real decisions, the scenarios are drawn from actual customer use cases, and the out-of-scope list is disciplined enough that preparing for the exam is a reasonable way to cover production Claude architecture properly. As a forcing function for structured study, it is a good one. As a line on a CV, wait and see.
The 12-month validity is worth factoring in too: this is a credential you re-earn, though renewing on time only requires a free non-proctored assessment rather than sitting the full exam again.
If you decide to sit it, the curriculum here covers all 30 task statements, and there is a free mock exam weighted to the real blueprint.