Chapter 03 · CCA-P · all 5 domains
15 anti-patterns to avoid on the CCA-P 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 15 patterns across 7 CCA-P domains.
Exam guide · 4 chapters
OverviewCCARP-D1 · 17% of CCA-P
Solution Design & Architecture
3 anti-patterns
Open the 63-question mock → · Get Pro →
AP-CCARP-D1-01Critical
Wrong call
Reaching for an agentic architecture before checking if a workflow suffices
Defaulting to a full agent loop with tool use for a problem that's actually a fixed sequence of deterministic steps. Agents add cost, latency, and failure surface that a workflow doesn't need.
Right call
Apply the workflow-vs-agent decision criteria first
If the steps and their order are known in advance, use a workflow. Reserve agentic patterns for open-ended tool use where the path genuinely can't be predetermined.
AP-CCARP-D1-02Common
Wrong call
Designing the system before naming the business-value pillar it serves
Jumping straight to components and data flow without first stating whether the design is optimizing for cost, efficiency, or a performance SLA. The architecture then has no anchor to justify trade-offs against.
Right call
Name the business-value pillar explicitly, then design against it
State which pillar (cost, efficiency, performance) the design serves before choosing components. Every later trade-off gets evaluated against that stated pillar.
AP-CCARP-D1-03Common
Wrong call
Treating requirements gathering as a one-time input
Capturing requirements once at the start and never revisiting them as the design evolves. Feedback loops get bolted on at the end instead of designed in from the start.
Right call
Bake feedback loops into the architecture from the start
A CCA-P-grade architecture answer includes input, processing, output, and feedback as one continuous loop, not four separate phases.
CCARP-D2 · 13% of CCA-P
Claude Models, Prompting & Context Engineering
2 anti-patterns
AP-CCARP-D2-01Common
Wrong call
Defaulting to the largest model regardless of the task
Reaching for the highest-capability model 'to be safe' on every call, even for simple classification or extraction tasks that a cheaper, faster model handles equally well.
Right call
Choose the model on cost, latency, and capability trade-offs matched to the task
Match model tier to task complexity. Reserve the highest-capability model for the calls that genuinely need it.
AP-CCARP-D2-02Common
Wrong call
One monolithic mega-prompt instead of modular, reusable components
Stuffing every instruction, example, and edge case into a single giant system prompt that gets copy-pasted and hand-edited across projects.
Right call
Optimize context and reuse through caching, modular prompts, and Skills
Break prompts into reusable, cacheable components. This is both a cost optimization (prompt caching) and a maintainability win.
CCARP-D3 · 19% of CCA-P
Integration
3 anti-patterns
AP-CCARP-D3-01Critical
Wrong call
Granting an agent broad, standing credentials 'to be safe'
Provisioning wide-scope API keys or roles so the agent 'can do whatever it needs' rather than scoping access per tool. This is the single most-tested Integration security gap.
Right call
Scope auth and access control narrowly, per tool, least-privilege
Analyze authentication and authorization requirements per tool and grant only what that specific capability needs.
AP-CCARP-D3-02Critical
Wrong call
Loading the full tool and document surface into context up front
Registering every available tool and injecting every relevant document at session start. This is capability bloat and monolithic context in one move - both degrade selection accuracy and burn tokens.
Right call
Use progressive disclosure - reveal tools and context only as needed
Expose the minimal tool and context surface for the current step, expanding only when the task genuinely requires it.
AP-CCARP-D3-03Common
Wrong call
Optimizing for accuracy alone, ignoring latency and cost
Picking the configuration that scores highest on an accuracy benchmark without weighing what it costs in latency or spend for the actual SLA the system needs to meet.
Right call
Weigh accuracy, latency, and cost trade-offs explicitly against the stated SLA
State the SLA first, then choose the configuration that meets it at the lowest cost and latency - not the one that maximizes accuracy in isolation.
CCARP-D4 · 16% of CCA-P
Evaluation, Testing & Optimization
2 anti-patterns
AP-CCARP-D4-01Critical
Wrong call
Eyeballing a handful of transcripts and calling it 'evaluated'
Reviewing 5-10 sample conversations manually and declaring the system production-ready, with no defined metric and no dataset that represents the actual traffic distribution.
Right call
Define evaluation metrics and datasets before declaring anything production-ready
Set explicit metrics across accuracy, latency, cost, and safety, and build a test dataset that mirrors real traffic before making a launch call.
AP-CCARP-D4-02Common
Wrong call
Shipping without a production monitoring plan
Treating pre-launch testing as the only evaluation gate, with no logging or observability tooling watching for regressions once the system is live.
Right call
Monitor production performance continuously with logging and observability
Evaluation doesn't stop at launch. Instrument the system so drift and regressions surface in production, not from a customer complaint.
CCARP-D5 · 14% of CCA-P
Governance, Safety & Risk
2 anti-patterns
AP-CCARP-D5-01Critical
Wrong call
Relying on system-prompt instructions as the only safety control
Telling the model 'never do X' in the system prompt and treating that as sufficient for a high-stakes action. Probabilistic enforcement fails under load or adversarial input.
Right call
Implement guardrails and safety controls programmatically, with human-in-the-loop for high-risk actions
Deterministic controls (not prompt instructions) gate irreversible or high-risk actions, with human review where the stakes justify it.
AP-CCARP-D5-02Common
Wrong call
Assuming a generic risk assessment covers GDPR, HIPAA, or FedRAMP
Running one all-purpose compliance checklist regardless of the actual regulatory regime the deployment falls under.
Right call
Map compliance requirements to the specific regulatory regime that applies
GDPR, HIPAA, and FedRAMP each impose distinct requirements. Identify which regime applies to this deployment and design against that one, not a generic template.
CCARP-D6 · 14% of CCA-P
Stakeholder Communication & Lifecycle
2 anti-patterns
AP-CCARP-D6-01Common
Wrong call
Designing in isolation, then presenting a finished architecture
Skipping structured discovery and building the full design before ever showing it to the stakeholders who'll depend on it, then treating their feedback as scope creep.
Right call
Run structured discovery and iterative feedback loops before finalizing
Gather requirements through structured discovery, share design direction early, and treat stakeholder feedback as part of the design process, not a post-hoc objection.
AP-CCARP-D6-02Common
Wrong call
No documentation handoff - the original architect becomes the only source of truth
Shipping a working system with the design decisions living only in the architect's head (or a Slack thread), so the team that inherits it can't safely modify it.
Right call
Document architecture decisions and trade-offs for implementation handoff
Write down what was decided, why, and what trade-offs were accepted, so the system is maintainable by people who weren't in the room.
CCARP-D7 · 7% of CCA-P
Developer Productivity & Operational Enablement
1 anti-pattern
AP-CCARP-D7-01Edge case
Wrong call
Leaving every developer to configure Claude Code individually, ad hoc
No shared team configuration - each developer sets up their own tools, rules, and environment from scratch, so debugging and workflows differ person to person.
Right call
Configure shared team tooling and environments centrally
Configure Claude tools and environments once for the team, including Claude Code, so operational debugging and workflows stay consistent across contributors.
Ready to test yourself?
Take the CCA-P diagnostic, no sign-up. Most distractors are one of the 15 patterns above.
▪Last reviewed ·