Claude Certified Associate – Foundations: Where to Start if You Don't Write Code

Who the exam is written for

Anthropic names the audience and, unusually, names the exclusion too. CCAO-F is for professionals who use Claude as a productivity tool: operations, marketing, product management, education and communications. It is explicitly not for API developers or agentic-system designers — that is Architect and Developer scope.

Anthropic draws the same line from the other side when it teaches you to know your boundary. When a solution needs API integration, agent building or tool development, it belongs with a Claude Developer. When it needs enterprise architecture, integration design or governance at scale, it belongs with a Claude Architect. And recognising that boundary, and escalating across it, is itself an Associate-level skill.

That makes the boundary testable content rather than a syllabus footnote. A question that describes a request beyond operator scope is not asking you to solve it; it is asking whether you know to hand it on.

What the exam asks of someone who does not write code

The exam is scenario-style. Its 60 questions ask you to apply a skill or make a judgement rather than recall a fact, so expect a situation, a constraint and a decision — not a definition. Seven domains carry published weights, and each has a published list of objectives. Read as plain work, they ask for the following.

Output Evaluation and Validation — 21%, the largest. Evaluate what Claude gives you for accuracy and completeness; spot hallucinations, inconsistencies and bias; fact-check and validate; decide when a human must review; edit, adapt and compare outputs for the reader they are meant for; and choose the right output format — an artifact, an inline answer or structured data. Anthropic opens this topic by calling it the largest section of the exam, and gives the reason: when you put your name on a deliverable, you own every claim in it, whether you wrote the words or Claude did.

Workflow Integration and Solution Design — 16%. Use Claude to analyse requirements and use cases, to research and plan, to support design and iteration, and to fit into an existing workflow — and explain Claude's value and its limitations to the people around you.

Governance, Risk, and Responsible Use — 15%. Tell an appropriate use case from an inappropriate one, weigh data sensitivity, regulatory and privacy considerations, follow your organisation's AI policy, and understand the ethical implications. The course teaches which question to ask and who owns the answer; it does not supply named regulations, retention periods or legal thresholds, and neither does Anthropic's own material.

Prompting and Task Execution — 14%. Write effective prompts for business and technical tasks, break a complex request into steps, iterate a prompt to improve the result, and adapt your approach to the kind of task — analysis, research, drafting or brainstorming.

Product and Model Selection — 12%. Choose among Claude's product features (Projects, research mode, chat, artifacts), tell the Haiku, Sonnet and Opus models apart, match the model to the task's cost, speed and quality needs, and manage context limits — when to restart, summarise or keep something for later.

Configuration and Knowledge Management — 12%. Configure Projects with instructions and knowledge sources, manage uploaded knowledge and connectors such as Google Drive and Gmail, write system-level instructions, and keep all of it maintained.

Troubleshooting and Optimization — 10%. Diagnose a prompt or an output that is underperforming, adjust from feedback, and make a workflow more efficient.

None of that needs a line of code. All of it needs judgement, and the exam tests the judgement.

Four words that run through all seven domains

Anthropic names four competencies that recur in every area, and carrying them as one model helps, because scenario questions often turn on which one is really being tested:

When a question offers four reasonable-sounding actions, asking which of the four the scenario is about often separates the intended answer from the merely sensible ones. A question about a number that does not add up is a Discernment question, however much prompting appears in the stem.

Where to start

First, audit yourself against Anthropic's own capability lines. Anthropic states one capability per domain. Mark each one honestly as can do under a new scenario or cannot yet — not have read about:

Then check the audit with the free diagnostic, before you study anything. It is 24 questions and takes about 20 minutes. It draws from the same question bank, under the same rules, as the rest of the course, and its mix follows the exam's own weighting. For each domain it reports how many questions you saw and how many you got right — a pointer to where to begin, not a grade.

Then spend your hours by weight. The exam is scored on the total scaled score only — 720 on a 100–1,000 scale — with no separate minimum for any domain. So the rational plan is to maximise total items correct, which means weighting effort by how many items a domain carries. At 21% of 60 items, Output Evaluation and Validation is about 13 questions; Troubleshooting and Optimization, at 10%, is about 6. An hour that lifts your accuracy in the first by ten points is worth about 1.3 items; the same hour in the second is worth about 0.6. If two domains are equally shaky, open the heavier one first.

Study by re-deciding, not re-reading. That is Anthropic's own instruction: find your weakest area, study it against the weight it carries, and work back through its decision frameworks rather than rereading the prose.

What the first domain lesson looks like

The course's first domain lesson — free, with its podcast — shows what "no code" preparation means in practice. It teaches the five components a professional prompt is built from: role, context, task, constraints and output format. Its opening example takes "Write me a summary of how operations went last quarter" and rebuilds it: an operations analyst's perspective, a one-page update for a regional director who reads for throughput and cost, one task verb, only the three metrics that moved more than ten percent against target, and a headline with three one-sentence bullets. Same model, same data; what changed was the specification.

The lesson then shows that not every request needs all five — a quick factual question is complete with a task and one boundary — and that the component people leave out most is context: the audience, the situation, prior decisions and the source material Claude cannot see. It ends with task decomposition, where a request such as "assess these three vendors and tell me which one to go with" becomes ordered, checkable steps, with the evaluation criteria confirmed before any vendor is scored.

The mistakes that cost non-engineers the most

The exam in brief

These are the values Anthropic published in July 2026; confirm them with Pearson VUE when you register, and where a newer published revision disagrees, the newer revision wins.

Next step

Create a free account — no card, no trial clock — and take the diagnostic for CCAO-F: 24 questions, about 20 minutes. Then open the first two lessons, which are free with their podcasts: the exam-strategy lesson and the lesson on the five-part prompt and task decomposition.