I sat the Claude Certified Associate, Foundations exam (CCAO-F) this week and passed. Sixty questions, 120 minutes, Pearson VUE, $99. On paper it's the entry point to Anthropic's certification track, the one that sits below the Developer and Architect exams and is aimed squarely at non-developers: operations, marketing, project management, HR, finance, education.
I'm leading with the result because everything after this is critical, and I'd rather you read it as feedback from someone who cleared the bar than as a post-mortem from someone who didn't.
I went in expecting the Anthropic equivalent of the AWS Certified Cloud Practitioner. That's the wrong mental model, and the gap between what I expected and what I got is the whole story here.
Some context on my bias, and on why I'm being this specific. I hold nine AWS certifications. More relevant: I've been on the other side of the table. I participated in the AWS exam development process for multiple certifications, doing item writing and review, so I've sat in the room where a stem gets torn apart by five SMEs because one of them can read it two ways. I know what that process costs, and I know what an exam looks like when it hasn't been through it.
I've watched the AWS program mature over roughly a decade, from exams that felt like they'd been assembled in a conference room to a psychometrics operation with trained item writers, SME review panels, beta scoring, and a house style you can feel in every stem. I'm not comparing Anthropic to AWS-in-2026 because it's fair. I'm doing it because it's the only yardstick most of us have, and because knowing what a mature program looks like makes it easier to name what a young one is missing.
Anthropic's program launched in March 2026 with one exam and expanded to four by July. This exam is, in the most literal sense, early. What follows is peer review, not a takedown.
1. "Foundations" means two very different things
The AWS Cloud Practitioner is a recognition exam. It asks *what is this thing, and which one fits this job.* You need to know that S3 is object storage, that a Region contains Availability Zones, that Trusted Advisor exists and roughly what it does. It's a vocabulary test with a service catalog attached. You can pass it by learning nouns.
CCAO-F is not that. It's a **process** exam. It's trying to test whether you know how to approach a task with an AI system: how you'd frame it, how you'd check the output, when you'd escalate, what you'd do when the result is wrong. The published domain weightings tell the story. Output Evaluation and Validation is the single heaviest area at 21%, ahead of Workflow Integration and Solution Design at 16% and Governance, Risk, and Responsible Use at 15%. Prompting itself is only 14%. Product and model selection, the closest thing to the AWS "pick the right service" muscle, sits at 12%.
That's a genuinely more ambitious design, and I want to give credit for it before I start critiquing. Anthropic looked at the foundational-exam genre and decided not to build a trivia quiz about model names. They're testing judgment. For a technology where the failure mode is *confidently wrong output that a human accepted*, weighting evaluation and validation the heaviest is the correct instinct.
The problem is that testing judgment is much harder to write well than testing nouns. And this is where the seams show.
2. The stems are doing work they shouldn't have to
This was my loudest signal, and it started early.
For a foundational exam, I spent an unreasonable amount of cognitive budget just parsing the questions. Not answering them. Parsing them. The stems are constructed out of English words that do not consistently assemble into clear US-English sentences. Several read like they went from draft to item bank without a native-speaker editorial pass or an SME review round.
The effect is that the exam accidentally tests the wrong thing. When I can't tell what's being asked, I'm no longer demonstrating whether I know how to validate an AI output. I'm demonstrating reading-comprehension endurance against ambiguous phrasing. Those are different skills, and only one of them is on the blueprint.
This matters more at the foundational tier than anywhere else, and I want to be precise about why. The target audience for CCAO-F is explicitly the non-technical professional: the ops lead, the HR generalist, the marketing manager. That person does not have the domain fluency to reverse-engineer a badly worded question into the answer the author probably meant. I do, because I've been doing this for thirty years and I've sat enough exams to pattern-match my way through a bad stem. A first-time certification taker from a non-technical function has no such fallback. They'll read it three times, guess, and walk away believing they don't understand AI, when what actually happened is that the question didn't understand itself.
Language quality on a foundations exam isn't polish. It's the accessibility layer. Get it wrong and you've built a gate that filters for test-taking experience instead of competence.
**The fix is not exotic.** Every mature program does the same three things: a US-English editorial pass by someone who didn't write the item, an SME review panel that flags ambiguity before the item goes live, and a beta period where item-level statistics surface the questions everyone gets wrong for the wrong reasons. AWS didn't invent this. It's standard certification practice, and it's the most obvious place for Anthropic to invest next.
3. A brand-new exam testing features that are already dated
Here's an irony specific to this industry. The certification is five months old. Some of what it quizzes you on is already behind.
I use these tools every working day. I build with them. And more than once I hit a question where the "correct" answer described a capability, limit, or product behavior that has since moved. Not wrong in an abstract sense. Wrong relative to the product I'd used that morning.
I'm sympathetic here in a way I'm not about the language issue. Item development has a lead time. You write, you review, you beta, you publish, and by the time that cycle completes, a frontier AI lab has shipped four times. AWS has the same problem and manages it by keeping foundational content deliberately abstract. You're tested on *what object storage is for*, not on the current maximum object size.
That's the lesson Anthropic should take. The half-life of a specific feature detail in this space is measured in weeks. The half-life of "how do you decide whether an output is trustworthy" is measured in years. Every item that anchors to a version-specific behavior is a scheduled maintenance obligation, and at the foundations tier those items are buying you almost nothing in return. Test the durable layer. Let the Developer and Architect exams carry the version-specific weight, where the audience is tracking releases anyway.
The 12-month credential validity suggests Anthropic already knows the content will move. Fair enough. But annual re-certification is a way to manage drift, not a substitute for writing drift-resistant items.
4. The persona carousel
This is the structural issue, and it's the one I'd fix first if I ran the program.
The exam is trying to be broad, which is the right ambition for a foundations credential aimed at everyone. The execution is to rotate the persona in the scenario: this question is a finance analyst, the next is a program manager, then a business analyst, then an HR representative. Each item drops you into a new role, a new department, a new set of assumed constraints.
Even as a deeply technical person, I found it hard to track. Every stem required a context switch. Reload who I am, what I care about, and what "good" looks like from this chair, and only then start evaluating the answer options. Across sixty items, that tax compounds badly.
And here's what makes it more than an annoyance: **the underlying process is the same regardless of persona.** That's the actual insight, and the exam misses it.
The finance analyst validating a generated variance summary and the HR rep validating a generated job description are performing the *identical* workflow. Frame the task. Give the model the context it needs. Generate. Check the output against a source of truth. Decide whether it's fit for purpose. Escalate or ship. The domain vocabulary changes. The judgment loop does not.
An exam that understood this would teach it. It would establish one clean, generalized frame: the practitioner, the task, the output, the validation step. Then it would vary the *difficulty of the judgment*, not the job title of the person making it. Persona would be color, not cognitive load.
Instead, persona churn is doing work that the item difficulty should be doing. It makes the exam feel harder without making it a better measurement. And for the non-technical audience it's aimed at, it does something worse. It obscures the single most valuable thing a foundations credential could impart, which is that *there is a repeatable process here and it works no matter what your job title is.*
Commoditize the personas. Teach the loop.
5. So: is it worth taking?
Yes, with clear eyes.
It's $99 and two hours. The blueprint is pointed at the right competencies: evaluation, integration, and governance. Studying for it will genuinely sharpen how you think about AI output validation, which is the skill most organizations are shortest on right now. The credential is early enough that it still signals something.
But go in knowing it is more detailed and more demanding than the "foundational" label implies, and considerably more so than the AWS Cloud Practitioner. If you're recommending it to non-technical colleagues, and I think the *intent* of this exam deserves that recommendation, set expectations accordingly. Tell them that some questions will read badly and that this is the exam's problem, not theirs.
What I'd want to see in v2
1. **An editorial and SME review pass on every item.** US-English clarity, one unambiguous reading, no stem that requires three passes.
2. **Version-resistant items at the foundations tier.** Test durable process, not current feature behavior. Push the version-specific content up to Developer and Architect.
3. **A generalized persona frame.** One practitioner model, varied difficulty. Stop making candidates context-switch sixty times.
4. **A published, sharper audience definition.** Right now the exam reads like it's trying to serve every non-technical function simultaneously. Naming the target reader precisely would resolve most of the above by itself.
---
A note on where this feedback went first
Most of what's above, I submitted through the exam's own feedback mechanism before I wrote a word of this post. I want to be clear about that sequencing, because there's a version of this article that's just a public complaint, and that's not what this is.
Certification programs get better when practitioners tell them what broke, in the channel built for it, while the detail is still fresh. I did that. This post exists because the observations seemed useful to other people considering the exam, not because the feedback form was a dead end. For all I know it landed exactly where it should have.
And I'll say the obvious thing out loud. If Anthropic is building out an item-writing and review bench for this program, I'd be glad to be part of it. I've done the work before, for AWS, across multiple exams. I know how to write a stem with one reading, how to argue that a distractor is doing no work, and how to sit in a review panel without falling in love with my own items. If that's a conversation worth having, my inbox is open.
Good first attempt. And *good* is relative. Set against a program that is five months old, this is a credible, ambitious swing at a genuinely hard problem, and I'd rather see a lab aim at judgment and miss than aim at trivia and hit.
But the bar moves. AWS didn't get to nine-certifications-deep credibility by shipping and walking away. It got there by iterating on item quality for years. I fully expect Anthropic to level up here, and the fastest path runs through clarity: clarity in the stems, clarity in the content half-life, and clarity about exactly who this exam is for.
*I'm Darin Deters: cloud architect, founder of [Skyform](https://skyform.io), nine-time AWS certified, newly Claude Certified Associate (Foundations), and a former contributor to the AWS exam development process. Tech With Darin covers enterprise AI adoption and cloud cost optimization, weekly. If you've sat CCAO-F, I want to hear whether your experience matched mine.*