Skip to content
7×7AI7x7
ProfessionalArchitect trackCCAR-P

Claude Certified Architect – Professional

Architect – Professional is the senior credential. It assumes you can build with Claude and asks whether you can take an enterprise solution from discovery to operation: choose the architecture, integrate it securely at scale, prove it works with an evaluation programme, govern its risks and carry stakeholders with you. Nearly half the weight sits in evaluation, governance and communication — the parts of the job that are not code.

Intended audience: Mid- to senior-level technical professionals who design, build and deliver production-grade AI solutions with Claude: solution architects, AI/ML engineers, technical leads and senior software engineers.

Exam content update: Pearson VUE lists updated content for this exam effective 7 December 2026, with a revised exam guide due 17 November 2026. The facts on this page reflect the current guide, version 1.0 (initial publication July 2026), and will be re-verified when the new guide is published. Source

Exam code
CCAR-P
Level
Professional
Official fee
$175
Fee may reflect a partner-tier discount
Duration
120 minutes
Questions
63 items
Format
Multiple choice & multiple response
Passing score
720 scaled
Scale 100–1,000
Validity
12 months

Verified against official exam guide version 1.0 (initial publication July 2026) on 4 November 2026.

Eligibility, prerequisites and registration

Official exam registration is through the Anthropic Partner Academy and is described by Anthropic as available to members of the Claude Partner Network (membership is free; firms join at claude.com/partners). AI7x7 resources may be used by anyone for learning and preparation.

Prerequisites: None mandatory. No courses required; credential awarded on exam performance alone.

Delivery: Proctored, online (Pearson OnVUE) or at a Pearson VUE test centre. Waiting periods of 14 days after the first failed attempt, 30 days after the second, 90 days after the third. Maximum four attempts per exam in any rolling 12-month period. Fee applies to each attempt.

Who should take this

Built for people who do this work

  • Solution architects accountable for production Claude deployments in regulated or large organisations
  • AI/ML engineers and technical leads who own evaluation, observability and cost for LLM systems
  • Senior engineers moving into architecture who need to show end-to-end delivery judgement, not just implementation skill
  • Consultants and partner-firm practitioners leading Claude engagements from discovery through handoff

Not intended for: Entry-level developers, casual users, people without end-to-end system design experience, or roles limited to isolated tasks such as prompt writing alone.

Recommended experience

  • — Software engineering best practices (modular design, separation of concerns, scalability)
  • — 3+ years in systems architecture or platform engineering
  • — 6+ months of hands-on experience with Claude or comparable LLM systems in production
  • — Experience delivering end-to-end systems from discovery through operationalisation

What it validates

A pass shows that

  • You can translate a business problem into a Claude architecture and justify the pattern: workflow, agentic or augmented LLM
  • You can design integrations that avoid capability bloat, close authentication gaps, choose the right protocol (MCP, API/CLI, agent-to-agent) and stay observable at scale
  • You can design a RAG pipeline with chunking, indexing and retrieval strategies matched to the data and the query pattern
  • You can define metrics, build evaluation datasets and test frameworks, run A/B tests and diagnose prompt failures, hallucinations and model mismatch
  • You can implement guardrails and human-in-the-loop validation, and reason about GDPR, HIPAA, FedRAMP and ethical risk
  • You can run discovery, communicate trade-offs, manage expectations and SLAs, document the architecture and support every lifecycle phase

Exam blueprint

Official domains and weights

7 domains, reproduced from the official exam guide 1.0 (initial publication July 2026).

1.Solution Design & Architecture

17%
  • Translate business problems into Claude-based AI solutions
  • Design end-to-end architectures (input → processing → output → feedback loops)
  • Select architectural patterns (workflow, agentic, augmented LLM)
  • Design multi-agent systems and orchestration strategies
  • Apply decomposition techniques for complex problems
  • Align solutions to business value pillars (efficiency, transformation, productivity, cost, performance SLAs)

2.Claude Models, Prompting & Context Engineering

13%
  • Select Claude models based on trade-offs
  • Design system prompts, templates and guardrails
  • Apply prompting techniques (zero-shot, few-shot, chain-of-thought)
  • Optimise context windows and manage token usage
  • Implement prompt reuse strategies (caching, modular prompts, Skills)

3.Integration

19%
  • Evaluate tool/agent configurations for capability bloat
  • Analyse authentication and authorisation requirements to identify security gaps
  • Evaluate accuracy-latency trade-offs and justify configuration decisions
  • Analyse observability challenges and select monitoring strategies at scale
  • Design a RAG pipeline with appropriate chunking and indexing strategies
  • Apply retrieval strategies matched to data shape and query pattern
  • Evaluate connection protocols and select integration mechanisms (MCP, API/CLI, agent-to-agent)
  • Evaluate progressive discovery vs monolithic context strategies

4.Evaluation, Testing & Optimization

16%
  • Define evaluation metrics (accuracy, latency, cost, safety, security)
  • Design evaluation datasets and test frameworks using mixed methodologies
  • Conduct A/B testing and iterative improvement
  • Diagnose system issues (prompt failure, hallucinations, model mismatch)
  • Optimise token usage, latency and cost-performance trade-offs
  • Monitor system performance using logging and observability tools

5.Governance, Safety & Risk Management

14%
  • Implement guardrails and safety controls
  • Identify risks, limitations and failure modes of LLM systems
  • Apply human-in-the-loop validation strategies
  • Ensure compliance with regulations (e.g. GDPR, HIPAA, FedRAMP)
  • Address ethical AI considerations (bias, fairness, transparency)

6.Stakeholder Communication & Lifecycle Management

14%
  • Conduct structured discovery and requirement gathering
  • Communicate architectural decisions and trade-offs
  • Manage stakeholder feedback loops and expectation alignment (including SLAs)
  • Document architectures and provide implementation guidance
  • Support lifecycle phases (discovery, design, handoff, monitoring, iteration)

7.Developer Productivity & Operational Enablement

7%
  • Configure Claude tools and environments for teams (e.g. Claude Code)
  • Improve developer workflows using AI-assisted tooling
  • Support debugging and operational issue resolution

Weights are reproduced from the official exam guide. Domain percentages are reported on the official score report but do not individually determine pass/fail.

Skills and practical examples

What each domain looks like at work

1.Solution Design & Architecture

17%

Skills

  • — Translate business problems into AI solutions
  • — Design input → processing → output → feedback architectures
  • — Select workflow, agentic or augmented-LLM patterns
  • — Design multi-agent orchestration and decomposition
  • — Align to value pillars: efficiency, transformation, productivity, cost, SLAs

In practice

  • A claims-triage request framed as 'use AI' becomes a workflow with one classification step and one summarisation step, plus a feedback loop from adjuster corrections — not an autonomous agent — because the SLA and audit requirements dominate.
  • Choosing an agentic pattern for a research assistant and a strict workflow for invoice posting is the same judgement applied to different risk profiles.

2.Claude Models, Prompting & Context Engineering

13%

Skills

  • — Select models on measured trade-offs
  • — Design system prompts, templates and guardrails
  • — Apply zero-shot, few-shot and chain-of-thought where each fits
  • — Optimise context windows and token use
  • — Reuse prompts via caching, modular prompts and Skills

In practice

  • A modular system prompt with a cached shared core and small per-tenant sections cuts cost and makes tenant-specific changes reviewable.
  • Replacing a 'think step by step' instruction with extended thinking changes cost and latency; the architect decides where that is worth it.

3.Integration

19%

Skills

  • — Audit tool and agent configurations for capability bloat
  • — Analyse authn/authz requirements and identify gaps
  • — Trade off accuracy and latency with justified configuration
  • — Select monitoring strategies for scale
  • — Design RAG chunking, indexing and retrieval
  • — Choose integration mechanisms: MCP, API/CLI, agent-to-agent
  • — Compare progressive discovery with monolithic context

In practice

  • An agent with write access to every internal system 'for flexibility' is a capability-bloat and authorisation finding; scoping tools per task and adding approval for writes is the fix.
  • Chunking contracts by clause with metadata indexing beats fixed 500-token windows when queries are clause-specific; the opposite can hold for narrative documents.

4.Evaluation, Testing & Optimization

16%

Skills

  • — Define accuracy, latency, cost, safety and security metrics
  • — Build evaluation datasets and mixed-method test frameworks
  • — Run A/B tests and iterate
  • — Diagnose prompt failure vs hallucination vs model mismatch
  • — Optimise token, latency and cost trade-offs
  • — Monitor with logging and observability tools

In practice

  • A golden set of 300 labelled examples, refreshed from production corrections each month, is what turns 'it seems better' into a release decision.
  • A rise in refusals after a model upgrade is diagnosed by replaying the eval set against both versions, not by editing the prompt until complaints stop.

5.Governance, Safety & Risk Management

14%

Skills

  • — Implement guardrails and safety controls
  • — Identify LLM failure modes and limitations
  • — Apply human-in-the-loop validation
  • — Design for GDPR, HIPAA and FedRAMP obligations
  • — Address bias, fairness and transparency

In practice

  • A patient-facing assistant in a HIPAA environment needs data-flow mapping, minimisation, access controls and a human review path before any model choice matters.
  • Disclosing to customers that a response was AI-generated, and logging the human override rate, are governance controls you design in, not add later.

6.Stakeholder Communication & Lifecycle Management

14%

Skills

  • — Run structured discovery and requirement gathering
  • — Communicate architectural decisions and trade-offs
  • — Manage feedback loops, expectations and SLAs
  • — Document architectures and give implementation guidance
  • — Support discovery, design, handoff, monitoring and iteration

In practice

  • An architecture decision record that states the rejected options and why survives staff turnover; a slide that states the chosen option does not.
  • Agreeing an SLA on p95 latency and a target human-override rate before build gives both sides something to measure the pilot against.

7.Developer Productivity & Operational Enablement

7%

Skills

  • — Configure Claude tools and environments for teams
  • — Improve developer workflows with AI tooling
  • — Support debugging and operational issue resolution

In practice

  • Standardising CLAUDE.md, permitted tools and a review skill across twelve repositories is an enablement decision with security and consistency consequences.

Example scenario

A regulated bank wants a knowledge assistant for 3,000 relationship managers

Relationship managers at a bank spend hours finding product terms, policy answers and compliance rules across 40,000 documents in four systems. Leadership wants an assistant that answers questions with citations, inside the bank's identity and access rules (not every manager may see every document), with a measurable accuracy target, and with sign-off from risk and compliance before the pilot expands.

Your task: Propose the architecture and integration approach, including retrieval design and access enforcement; define the evaluation programme and the metrics that gate expansion; identify the governance controls risk will ask for; and describe how you would run discovery, communicate trade-offs and document the design for handoff.

An original AI7x7 scenario illustrating the type of professional problem the exam tests. It is not an official exam item.

What this scenario tests

  • Solution design and pattern selection (Domain 1)
  • RAG design, authorisation-aware retrieval and integration mechanism choice (Domain 3)
  • Evaluation metrics, datasets and the release gate (Domain 4)
  • Guardrails, human-in-the-loop and regulatory obligations (Domain 5)
  • Discovery, trade-off communication, SLAs and documentation (Domain 6)

How to prepare

A 14-day study plan

Fourteen sessions of 90–120 minutes. The exam is about judgement across an end-to-end lifecycle, so the plan alternates between building something and writing the artefacts an architect produces: decision records, evaluation plans, risk registers and stakeholder summaries.

  1. 1

    Blueprint and value pillars (Domain 1)

    • — Read the exam guide; list the seven domains and all task statements
    • — Write a one-page problem statement for a real or invented enterprise use case, tied to a value pillar
  2. 2

    Architecture patterns (Domain 1)

    • — Design the same use case as a workflow, an agentic system and an augmented LLM; record the trade-offs
    • — Draw the input → processing → output → feedback loop
  3. 3

    Multi-agent design (Domain 1)

    • — Decompose the use case into agents; define contracts and orchestration
    • — Write an architecture decision record with rejected options
  4. 4

    Models, prompts and context (Domain 2)

    • — Build a modular, cacheable system prompt; measure the cost impact
    • — Compare zero-shot, few-shot and extended thinking on one task
  5. 5

    Integration: tools, auth, protocols (Domain 3)

    • — Audit an agent's tool set for capability bloat; scope it
    • — Map authn/authz requirements; identify a gap and close it
    • — Decide MCP vs API/CLI vs agent-to-agent for two integrations
  6. 6

    Integration: RAG (Domain 3)

    • — Build a small RAG pipeline; try two chunking strategies and two retrieval strategies
    • — Enforce document-level permissions at retrieval time
  7. 7

    Observability and discovery vs monolithic context (Domain 3)

    • — Add structured logging and tracing to the pipeline
    • — Compare progressive tool/context discovery with loading everything up front
  8. 8

    Evaluation design (Domain 4)

    • — Define accuracy, latency, cost, safety and security metrics for the use case
    • — Build a labelled evaluation set of at least 50 items
  9. 9

    Testing and diagnosis (Domain 4)

    • — Run the eval set across two model versions or prompt versions; compare
    • — Classify every failure: prompt, hallucination, retrieval, model mismatch
  10. 10

    Governance and safety (Domain 5)

    • — Write a risk register: failure modes, likelihood, impact, control
    • — Design guardrails and a human-in-the-loop path; map data flows for GDPR/HIPAA
  11. 11

    Ethics and compliance (Domain 5)

    • — Assess bias and transparency risks; decide disclosure and override logging
    • — List what FedRAMP-style environments would change in your design
  12. 12

    Stakeholders and lifecycle (Domain 6)

    • — Write a discovery questionnaire and run it against a colleague
    • — Draft an SLA and expectations memo; write the handoff documentation outline
  13. 13

    Developer enablement (Domain 7) and consolidation

    • — Standardise Claude Code configuration for a team: CLAUDE.md, tools, a review skill
    • — Re-read all seven domains against your artefacts; fill gaps
  14. 14

    Practice exam and review

    • — Sit the AI7x7 20-question practice exam under the timer
    • — For each missed item, name the domain and the judgement you got wrong

Preparation tips

  • — Read every option as a senior reviewer would: the distractors are usually technically possible but wrong for the stated constraints (regulation, SLA, scale, stakeholder)
  • — Evaluation (16%) and governance (14%) questions reward specifics: named metrics, a dataset strategy, a control, a review path
  • — Domain 6 is not soft: expect items about discovery, documentation and expectation management with concrete best answers
  • — Keep the value pillars in mind; several design questions turn on which pillar the business actually asked for

Official documentation to read

Practice with AI7x7

Free practice exam, free guide, $19 full-length package

Practice percentages are not the official 720 scaled score and do not predict your result. They tell you which domains need work.

Free

20-question practice exam

Timed 40-minute session with a domain breakdown and full explanations on completion. AI7x7 practice timing, not the official 120-minute duration.

Free exam in editorial review. Ask to be notified.
Free

Preparation guide (PDF)

A 12–20 page study guide: blueprint, domain-by-domain notes, worked examples, common mistakes and a 7-day and 14-day plan. Delivered by email.

Guide in editorial review. Ask to be notified.
$19 one-time

5 full-length practice exams

5 distinct 63-question timed simulations matching the official format, explanations for every option, domain reports and score history. Unofficial AI7x7 simulation.

Premium exams coming soon. Ask to be notified.

FAQ

CCAR-P questions, answered

Who is CCAR-P designed for?

Mid- to senior-level technical professionals who design, build and deliver production-grade Claude solutions — solution architects, AI/ML engineers, technical leads and senior software engineers. The guide explicitly says it is not intended for entry-level developers or roles limited to prompt writing.

Do I have to pass Architect – Foundations first?

No. The guide lists no mandatory prerequisites. The recommended profile is 3+ years in systems architecture or platform engineering and 6+ months delivering Claude or comparable LLM systems in production.

How many questions and how long?

63 items in 120 minutes, the most of any Claude certification, with a 720 scaled passing score.

What topics carry the most weight?

Integration (19%), Solution Design & Architecture (17%) and Evaluation, Testing & Optimization (16%). Governance and Stakeholder Communication each carry 14%, so non-technical judgement matters as much as code.

How much does the exam cost?

USD 175, the highest fee in the programme. The guide notes the fee may reflect a partner-tier discount. AI7x7 products are not exam fees.

Is the exam content changing?

Yes. Updated content takes effect on 7 December 2026 with a revised exam guide due 17 November 2026. AI7x7 will re-verify this page and its practice materials against the new guide.

Related certifications

Other Claude tracks

Official certification page: https://anthropic-partners.skilljar.com/claude-certified-architect-professional-certification · Exam guide: PDF (1.0 (initial publication July 2026))

AI7x7 is an independent exam preparation platform and is not affiliated with, sponsored by, or endorsed by Anthropic. Claude and related trademarks belong to their respective owners. AI7x7 practice questions are original and are not official exam questions.