Chapter 03 · CCA-A · all 5 domains
17 anti-patterns to avoid on the CCA-A exam.
Exam distractors are almost always anti-patterns dressed up to look correct. Spot the anti-pattern and eliminate wrong answers before reading them in detail. This reference covers 17 patterns across 7 CCA-A domains.
Exam guide · 4 chapters
OverviewCCAOF-D1 · 14% of CCA-A
Prompting & Task Execution
2 anti-patterns
Open the 60-question mock → · Get Pro →
AP-CCAOF-D1-01Common
Wrong call
Using the same prompting approach for analysis, research, drafting, and brainstorming
Writing every prompt the same way regardless of whether the task is analytical, exploratory, or generative, then blaming Claude when the output doesn't fit the task.
Right call
Adapt prompting strategy to the task type
Analysis, research, drafting, and brainstorming each call for a different prompt structure - match the approach to what the task actually needs.
AP-CCAOF-D1-02Common
Wrong call
Sending one giant complex request instead of decomposing it
Asking for an entire multi-step deliverable in a single prompt, then getting an output that's shallow on every step because none of them were isolated.
Right call
Apply task-decomposition technique to structure complex requests
Break a complex ask into its component steps and prompt for them individually or sequentially, iterating on each.
CCAOF-D2 · 21% of CCA-A
Output Evaluation & Validation
4 anti-patterns
AP-CCAOF-D2-01Critical
Wrong call
Accepting fluent-sounding output as correct without a validation pass
Treating confident, well-written prose as evidence of accuracy, and shipping it without checking whether the facts actually hold up.
Right call
Evaluate output for accuracy and completeness, every time
Fluency is not accuracy. Run an explicit accuracy-and-completeness check before anything Claude produces goes out the door.
AP-CCAOF-D2-02Critical
Wrong call
Assuming an authoritative tone means the content is fact-checked
Mistaking a confident, well-structured answer for one that's been verified, and skipping the fact-checking step because the output 'sounds right.'
Right call
Apply fact-checking technique and actively look for hallucinations, inconsistencies, and bias
Tone is not a signal of correctness. Actively check for hallucinated facts, internal inconsistencies, and bias before trusting the output.
AP-CCAOF-D2-03Common
Wrong call
Shipping the raw draft to a different audience than it was written for
Forwarding Claude's first-pass output directly to a client or executive without adjusting register, structure, or level of detail for who's actually going to read it.
Right call
Edit and adapt outputs for the intended audience before they ship
The first draft is written for you as the prompter. Adapt register and structure before it reaches its actual audience.
AP-CCAOF-D2-04Common
Wrong call
Defaulting to inline chat text when a shareable document is what's needed
Leaving a deliverable as scrollback in a chat window when it needs to be a standalone document, spreadsheet, or structured artifact someone else can open and use.
Right call
Choose the output format deliberately: artifacts vs inline vs structured data
Match the format to how the result will actually be used and shared, not to whatever the chat interface defaults to.
CCAOF-D3 · 12% of CCA-A
Product & Model Selection
2 anti-patterns
AP-CCAOF-D3-01Common
Wrong call
Using plain chat for a task that needs a Project with persistent knowledge
Re-explaining the same background context in every new chat instead of setting up a Project that holds instructions and knowledge sources persistently.
Right call
Select the Claude product feature that matches the task
Projects, research mode, chat, and artifacts each fit different task shapes - choose deliberately instead of always reaching for plain chat.
AP-CCAOF-D3-02Common
Wrong call
Picking a model tier by habit rather than the cost/speed/quality the task needs
Always using whichever model tier you used last time, regardless of whether this task needs the extra quality or would be served just as well by a faster, cheaper tier.
Right call
Differentiate Haiku, Sonnet, and Opus and align the choice to the requirement
Match model tier to the specific cost, speed, and quality trade-off the task in front of you actually requires.
CCAOF-D4 · 16% of CCA-A
Workflow Integration & Solution Design
3 anti-patterns
AP-CCAOF-D4-01Common
Wrong call
Bolting Claude onto a workflow without analyzing the requirements first
Introducing Claude into a team process because it seems useful, without first analyzing what the workflow actually needs or where the gap is.
Right call
Use Claude to analyze requirements and use cases before redesigning anything
Start with requirements analysis and research and planning, then decide where Claude actually fits.
AP-CCAOF-D4-02Common
Wrong call
Redesigning the whole team process around Claude on day one
Replacing an entire established workflow with a Claude-first version overnight, before anyone has validated that the augmented version actually works better.
Right call
Integrate incrementally, augmenting the existing workflow first
Fold Claude into the existing process as an augmentation before considering a full redesign.
AP-CCAOF-D4-03Edge case
Wrong call
Never explaining Claude's limitations to stakeholders, only its wins
Presenting only the successful outputs to stakeholders, leaving them with an inflated sense of what Claude can reliably do and no calibration on where it fails.
Right call
Communicate both Claude's value and its limitations
Set expectations honestly - stakeholders who understand the limitations trust the wins more, not less.
CCAOF-D5 · 12% of CCA-A
Configuration & Knowledge Management
2 anti-patterns
AP-CCAOF-D5-01Common
Wrong call
Uploading a knowledge source once and never revisiting it
Setting up a Project's knowledge base at launch and letting it go stale as the underlying information changes, so Claude keeps citing outdated material.
Right call
Keep configurations, knowledge sources, and instructions current over time
Treat Project configuration as a living asset that needs periodic review, not a one-time setup task.
AP-CCAOF-D5-02Edge case
Wrong call
Connecting every available connector without scoping what's needed
Enabling every knowledge connector (Drive, Gmail, and more) 'just in case' rather than scoping access to what the Project actually requires.
Right call
Manage uploaded knowledge and connectors deliberately, scoped to the task
Connect only the sources a given Project genuinely needs - broader access isn't free and isn't automatically better.
CCAOF-D6 · 15% of CCA-A
Governance, Risk & Responsible Use
2 anti-patterns
AP-CCAOF-D6-01Critical
Wrong call
Pasting sensitive or regulated data into Claude without a data-sensitivity check
Sharing client data, health information, or other regulated content with Claude without first checking whether it's appropriate to do so.
Right call
Apply data-sensitivity, regulatory, and privacy considerations before data enters Claude
Check data sensitivity and applicable regulation before anything goes into a prompt or Project - not after.
AP-CCAOF-D6-02Common
Wrong call
Treating AI governance policy as someone else's problem
Assuming IT or compliance owns AI governance entirely, and using Claude without checking whether the organization's own policy actually permits this use case.
Right call
Follow organizational AI governance policy as a personal responsibility
Governance policy applies to how you personally use Claude day to day, not only to the systems IT builds.
CCAOF-D7 · 10% of CCA-A
Troubleshooting & Optimization
2 anti-patterns
AP-CCAOF-D7-01Common
Wrong call
Blaming Claude and giving up when a prompt underperforms
Concluding 'Claude just can't do this' after one weak output, instead of diagnosing what specifically went wrong with the prompt or task framing.
Right call
Diagnose why the output is weak and adjust approach based on feedback
Treat a weak output as a diagnostic signal about the prompt, not a verdict on the tool. Adjust and retry.
AP-CCAOF-D7-02Common
Wrong call
Optimizing a single output instead of the workflow that produces it
Fixing one bad result by hand-editing it, without changing the prompt or process that will produce the same weak result again next time.
Right call
Optimize the workflow for efficiency and effectiveness
Fix the pattern that produced the weak output, not just the one instance in front of you.
Ready to test yourself?
Take the CCA-A diagnostic, no sign-up. Most distractors are one of the 17 patterns above.
▪Last reviewed ·