Anti-patterns guide

The CCA exam is specifically designed so that wrong answers look reasonable. Every distractor represents a real mistake that engineers make when they understand the concepts partially but haven't internalized the production trade-offs.

Knowing these 7 patterns is worth 10–15 points on the real exam.

Study these before taking any practice questions

These anti-patterns appear in every domain. Once you recognize the pattern in a question, the correct answer becomes obvious — the wrong answers are deliberately constructed around these exact mistakes.

Why it's wrong

Few-shot examples are demonstrations — they influence Claude's behavior probabilistically, not deterministically. Showing Claude examples of "always call verify_identity before process_payment" reduces but cannot eliminate ordering violations. For financial or compliance workflows, "most of the time" is not acceptable.

✓ The correct approach

Use programmatic prerequisites: hooks that block downstream tool calls until required upstream tools have completed. The gate fires deterministically every time — not based on what Claude has "seen" in examples.

💡 Exam tip

If the exam asks about enforcing ORDERING or SEQUENCING of tool calls for compliance, the answer is never few-shot examples — it is always programmatic hooks or prerequisite gates.

---

The meta-pattern

All 7 anti-patterns share a common failure mode: substituting probabilistic mechanisms for deterministic ones.

Task	Probabilistic (wrong)	Deterministic (correct)
Enforce tool ordering	Few-shot examples	Programmatic prerequisite hooks
Escalation routing	Self-reported confidence	Rule-based triggers
Schema compliance	Prompt instructions	strict: true + JSON schema
Loop termination	Text content parsing	stop_reason check
Error recovery	Retry everything	isRetryable flag

When the exam asks "how do you ensure X always happens," the answer is always the deterministic mechanism — never the probabilistic one.