CCAO-F: the biggest domain isn't prompting. 6 traps that cost people points

Most people preparing for CCAO-F (Claude Certified Associate – Foundations) spend their time on prompting. That makes sense: it's the fun part. But look at the domain weights:

The largest domain is about judging what Claude gives you, not about asking for it. And the questions are written so that the confident-sounding option is often the wrong one.

Here are six patterns worth knowing before exam day.

1. Trusting step-by-step instructions for a system Claude has never seen

Hallucinations aren't spread evenly. They cluster where Claude has the least to go on: your company's internal tools, very recent events, and precise figures that weren't in the material you gave it.

The riskiest shape is a tidy, numbered how-to for an internal system. It reads like documentation, which is exactly why it's dangerous. If an answer option says "follow the steps, they're clear and specific", be suspicious. Specific is not the same as grounded.

A related trap: Claude saying it has done something outside the chat, such as sent an email or saved a file somewhere. Claude can hallucinate its own actions too.

2. Fixing the one contradiction you spotted

You notice the summary says revenue went up while the table shows it went down. Tempting answer: correct that line and send it.

The better answer: an inconsistency is a signal that the output as a whole isn't reliable. Re-check the whole thing against the source, not just the sentence that caught your eye.

3. Treating bias as one bad word

Bias in outputs shows up as a pattern: in how different people are described, what's assumed about them, which framing gets used. Deleting one loaded word doesn't fix a pattern.

Read across descriptions side by side rather than sentence by sentence. If you swapped the names, would the descriptions still read the same?

4. Picking the reviewer by seniority

When an output needs human review, the exam cares about who reviews it. The right reviewer is someone qualified in the subject who can actually change the output. The most senior person in the room, or whoever's free, is the distractor.

And what makes something need review? Things like an external audience, legal or financial consequences, decisions about people, safety, or anything you can't take back once it's sent. One of those is enough. Note what's not on the list: how polished or confident the draft sounds.

5. Escalating everything "to be safe"

The opposite failure is just as wrong. Sending every routine internal note through formal review buries reviewers and slows down the outputs that really need them. If an option escalates a low-stakes draft "just in case", it's usually not the answer.

6. Putting the reference document in the custom instructions

This one is from Configuration and Knowledge Management (12%), and it catches a lot of people.

A Claude Project has two halves:

• Custom instructions: how Claude should behave (tone, role, format, standing rules)
• Project knowledge: the material Claude works from (documents, files)

A quick test: is this a rule about behaviour, or material to consult? Rules go in the instructions; material goes in knowledge. Pasting a whole policy document into the instructions "so Claude never misses it" is the classic wrong answer, and so is uploading a standing rule as a file and expecting it to govern every reply.

A practical way to build a Project: whatever you re-explain at the start of every chat belongs in the instructions; whatever you re-attach belongs in knowledge.

How to study for this

Set up a real Claude Project for something you do every week while you study. Deciding what goes in instructions versus knowledge, and checking the outputs critically, covers a big share of what the exam tests.

We run Skillmarked, an independent exam-prep site (not affiliated with Anthropic). The full CCAO-F study guide is free, 30 lessons across all seven domains, and there's a free 10-question mock test you can take without an account.