Home › Articles › CCAO-F versus CCAR-F: the Associate and Architect exams compared
28 September 2026 · 4 min read · Anton Pavelko
CCAO-F versus CCAR-F: the Associate and Architect exams compared
The two Claude exams people most often confuse, compared on audience, content, difficulty and study time, with a simple rule for choosing between them.
Both exams are "Foundations". Both are 60 questions in 120 minutes with a pass mark of 720. Beyond that, the Claude Certified Associate - Foundations exam and the Claude Certified Architect - Foundations exam are about different jobs, and choosing the wrong one wastes weeks.
Who each exam is for
CCAO-F is for people who use Claude as a work tool without writing code: operations, marketing, project management, education, communications, support. It assumes you use the Claude apps daily and asks whether you use them well.
CCAR-F is for people who design production systems on Claude: agentic applications with the Agent SDK, Claude Code configured for a team, tools exposed through MCP, prompts that produce reliable structured output. It assumes six months or more of hands-on building.
If you have never called the Claude API or run Claude Code, CCAR-F is not the exam for you yet, whatever your job title says.
What they test
| CCAO-F | CCAR-F | |
|---|---|---|
| Domains | 7 | 5 |
| Biggest domain | Output Evaluation and Validation, 21% | Agentic Architecture and Orchestration, 27% |
| Format | Independent questions | 4 scenarios drawn from 6, about 15 questions each |
| Technology | The Claude apps, Projects, connectors, model choice | Agent SDK, Claude Code, MCP, the API, JSON schemas |
| Typical question | "Which check should you run before trusting this output?" | "Which change most effectively fixes this production failure?" |
| Counts toward partner eligibility | No | Yes |
CCAO-F's domains: prompting, output evaluation, product and model selection, workflow integration, configuration and knowledge management, governance and responsible use, troubleshooting. The surprise in the weights is that prompting is only 14% while checking outputs is 21%. The exam is more about judgment than technique.
CCAR-F's domains: agentic architecture, tool design and MCP, Claude Code configuration, prompt engineering and structured output, context management and reliability. Its surprise is the level of detail: flag names, file paths, parameter values, all tested exactly.
Which is harder?
Different kinds of hard. CCAO-F is hard for someone who has not used Claude much, because it tests habits of use. CCAR-F is hard for almost everyone, because it tests exact details across four technologies and because two candidates can sit noticeably different exams depending on which four scenarios they draw.
For a developer who uses Claude daily, CCAO-F is largely familiar and CCAR-F is a study project. For an operations lead, CCAO-F is a study project and CCAR-F is out of reach without months of building first.
Study time
CCAO-F: a couple of weeks for a daily Claude user, mostly on output evaluation and governance, which are the domains people underrate. Building one Project with custom instructions and knowledge files covers a surprising amount of the configuration domain.
CCAR-F: four weeks for an experienced builder, eight for someone newer, following our four-week study plan and the CCAR-F study guide. The builds in the plan are not optional; the exam tests things that only stick once typed.
Can you take both?
Yes, and some people do: CCAO-F first as a warm-up to the exam format and the partner registration process, then CCAR-F. Neither is a prerequisite for the other. The reverse order makes little sense, since CCAO-F would add little for someone who has passed CCAR-F.
The rule
Do you write code that calls Claude? No: CCAO-F. Yes, and you design systems: CCAR-F. Yes, but you mostly build features: look at the Developer exam instead; the comparison page has all four.
Written by Anton Pavelko, who holds the Claude Certified Architect, Associate and Developer credentials. An independent resource, not affiliated with Anthropic. Spotted an error? Email a correction.