Launch Deal · 50% off 1st month ·
← CCAR-P study guide

CCAR-P exam topics

The CCAR-P exam (Claude Certified Architect (Professional)) covers 7 domains and 38 topics. This page lists all of them with the weight of each domain, so you can see what the exam tests and where most of the marks are.

Domains and weights

DomainWeightTopics
Domain 1: Solution design & architecture17%6
Domain 2: Claude models, prompting & context engineering13%5
Domain 3: Integration19%8
Domain 4: Evaluation, testing & optimisation16%6
Domain 5: Governance, safety & risk management14%5
Domain 6: Stakeholder communication & lifecycle management14%5
Domain 7: Developer productivity & operational enablement7%3

Domain 1: Solution design & architecture · 17%

  • Translating Business Problems into Claude Solutions

    Translating a business problem into a Claude solution produces a measurable success criterion, a bounded scope, and a defensible boundary between the model and ordinary software.

  • End-to-End Architectures and Feedback Loops

    Every production Claude system has six stages: Input — ingestion, validation, normalisation, PII handling (decide before model); Context assembly — retrieval, memory, prompt construction; Processing — model call(s): single, workflow, or agent loop; Output — schema validation, business-rule checks, guardrail screening, designed failure path. Model output is untrusted until validated.; Delivery — sync, async, event, or draft-for-review (risk decision); Feedback loops — user feedback, automated eval on sampled traffic, monitoring → iteration.

  • Selecting Architectural Patterns

    Find the simplest solution that meets requirements; add complexity only when it demonstrably improves outcomes. Escalate tier only when the simpler tier cannot meet a named requirement.

  • Multi-Agent Systems and Orchestration

    Excels at breadth-first work that parallelises cleanly: research across independent directions, analysis of many independent units, tasks exceeding one context window, work needing distinct specialisms/tools/permissions.

  • Decomposition Techniques for Complex Problems

    One pass covering too much → inconsistent depth, missed items, contradictory judgements. Fix (both mandatory):; Per-unit local passes (consistent depth on every unit); Separate integration pass (cross-unit issues invisible to local passes).

  • Aligning Solutions to Business Value Pillars

    Test: does the capability already exist? Yes → efficiency. No → transformation. Design Decisions Tied to Pillars: Model selection — per-task cost/performance; smallest model that meets quality bar; Prompt caching — ~90% cache-read cost reduction; serves cost + latency SLA (static first, dynamic last); Batch processing — halves cost of async work; sacrifices request-path latency; Multi-agent — ~15× tokens; name the pillar that pays for it.

Domain 2: Claude models, prompting & context engineering · 13%

  • Selecting Claude Models on Trade-Offs

    Model selection = which model clears this task’s quality bar at the lowest cost that meets the latency budget. Never “which model is best”.

  • System Prompts, Templates, and Guardrails

    System prompt = standing contract (role, audience, policy, output format). User turns carry per-request data. Template = prompt with named slots. Guardrail = limit on what the model receives or returns.

  • Zero-Shot, Few-Shot, and Chain-of-Thought

    Diagnose before adding anything. Instruction quality is the first, free fix. Matching Technique to Failure: Output format wrong/drifting, Inconsistent classification at boundaries, Wrong answers on multi-step reasoning, Stated rules ignored, Any of the above.

  • Optimising Context Windows and Token Usage

    Context window = everything Claude sees in one request (system, history + tool results, tool definitions, output + thinking). Every token is billed every time it appears.

  • Prompt Reuse: Caching, Modular Prompts, and Skills

    Three mechanisms for three reuse questions: Prompt caching, Modular prompts, Skills; Prefix Mechanics: Order: tools → system → messages. Front-load stability: static system/policy/examples first, dynamic content last. A timestamp early in the prompt defeats the entire cache.

Domain 3: Integration · 19%

Domain 4: Evaluation, testing & optimisation · 16%

Domain 5: Governance, safety & risk management · 14%

Domain 6: Stakeholder communication & lifecycle management · 14%

  • Structured Discovery and Requirement Gathering

    The request is not the requirement. Discovery finds the problem behind the request. Six Outputs Discovery Must Produce: Business problem with measured baseline — hours, error rates, backlog, revenue at risk; Real workflow (including workarounds); Output the system must produce (fixes task shape); Consequence when that output is wrong + thresholded, owned success criteria; Data — what exists, quality, ownership, lawful basis; Constraints and accountable decision-maker.

  • Communicating Architectural Decisions and Trade-offs

    Simplifying past the point of truth is not translation. Say the Error Rate Out Loud: State the rate, the population, and the handling path for residual errors. A demo is a sample from the favourable tail — never a substitute for the measured rate.

  • Expectation Alignment and Service-Level Commitments

    Engineer first, then promise. Never the reverse. Anatomy of a Defensible Commitment (Six Elements): Metric — what is measured and how; Percentile or threshold — means conceal the tail; Measurement point — where the clock starts and stops; Window — over what period compliance is assessed; Population — who and what it covers (defined before measurement); Breach behaviour — what happens when it is missed.

  • Documentation and Implementation Guidance

    A handover pack transfers judgement, not history. Test for every page: does it change what a competent stranger would do?

  • Supporting the Lifecycle Phases

    Phases are gated by outputs, not dates. The architect’s job does not end at deployment. Phase Outputs: Discovery, Design, Build & validate, Handoff, Operate & monitor, Iterate.

Domain 7: Developer productivity & operational enablement · 7%

CCAR-P exam facts

Questions63
Time limit120 minutes
Passing score720 on a scale of 1,000
Exam fee$175 USD
Certification valid for12 months

Study these topics

Skillmarked is independent and not affiliated with Anthropic. The topic list follows the public exam outline; check the official exam page for the current version before you book.