Claude Certified Architect — Professional (CCAR-P) FAQ: the exam, its seven domains and the free diagnostic

Claude Certified Architect – Professional (CCAR-P) is Anthropic's advanced architect certification, official and live as of July 2026. It tests whether you can take a business problem to a scalable Claude-based solution across its whole lifecycle.

Mid-level and senior architects — typically with three or more years of architecture experience and six or more months running Claude in production.

Foundations has five domains; Professional has seven, led by Integration, and adds the business and lifecycle side of architecture — value, evaluation, governance and stakeholders. Alloy's Professional course assumes you already understand agent control flow and tool use.

63 questions in 120 minutes — about one minute fifty per question.

$175 per attempt.

720 on a scaled score from 100 to 1,000.

No. A scaled score is a result on a defined range, not a percentage of items answered correctly. Do not convert it into a raw-percentage target.

No. The decision is made on the total scaled score. Per-domain percentages are informational, not separate pass gates.

• Integration — 19%
• Solution Design & Architecture — 17%
• Evaluation, Testing & Optimization — 16%
• Stakeholder Communication & Lifecycle Management — 14%
• Governance, Safety & Risk Management — 14%
• Claude Models, Prompting & Context Engineering — 13%
• Developer Productivity & Operational Enablement — 7%

That is not published; the weights are informational percentages, not a promised count per sitting. Applied to 63 items, Integration is roughly 12 and Developer Productivity about 4.

Judging tool and agent configuration for capability bloat, finding authentication and authorisation gaps, justifying accuracy-versus-latency configuration, observability at scale, retrieval pipelines with suitable chunking and indexing, retrieval strategies matched to data shape and query pattern, choosing MCP, an API or CLI, or agent-to-agent connections, and progressive discovery versus monolithic context.

Translating business problems into Claude solutions, end-to-end architectures with feedback loops, choosing between workflow, agentic and augmented-LLM patterns, multi-agent orchestration, decomposition, and aligning a design to a business value pillar — efficiency, transformation, productivity, cost or performance SLAs.

Metrics for accuracy, latency, cost, safety and security; evaluation datasets and test frameworks; A/B testing; diagnosing prompt failures, hallucinations and model mismatch; optimising tokens, latency and cost; and monitoring through logging and observability.

Structured discovery and requirements gathering, communicating decisions and trade-offs, managing feedback and expectations including SLAs, documenting architectures with implementation guidance, and supporting discovery, design, handoff, monitoring and iteration.

Guardrails and safety controls, the risks and failure modes of LLM systems, human-in-the-loop validation, compliance obligations such as GDPR, HIPAA and FedRAMP, and bias, fairness and transparency.

Choosing models on their trade-offs, system prompts, templates and guardrails, zero-shot, few-shot and chain-of-thought prompting, context-window and token management, and prompt reuse through caching, modular prompts and Skills.

Configuring Claude tools such as Claude Code for teams, improving developer workflows with AI-assisted tooling, and supporting debugging and operational issue resolution.

Every item has exactly one intended answer. You are choosing the best design, not every defensible one.

Typically a business situation, a constraint that narrows it, and four architectures that all look reasonable if you skim. The constraint decides — a latency budget, data residency, a human-review requirement, a cost ceiling, or an existing system you must integrate with.

Yes. An unanswered question is scored as incorrect and there is no penalty for guessing, so never leave an item blank.

Neither is published, and anyone stating them confidently is guessing.

No. Across the forty question-shaped items in Anthropic's official course material, exactly one carries a recorded correct answer. The material records stems and options, not keys.

That cannot be tested — with one key in forty items, the pattern cannot be checked either way. Never let it override a reading of the constraint.

The absolutist; the answer that is true but irrelevant; the right action at the wrong layer; the over-engineered option; and the option answering a different question. The most common trap on this exam is an option that is individually defensible but satisfies only half the requirement.

Only when you can name what you missed — a specific constraint, detail or interpretation. If the honest answer is "nothing, but I dislike uncertainty", keep your original choice and move on.

About one minute fifty on average. If a question has taken three minutes, you are more than a full item behind; choose the best option you have and move.

Up to four in a rolling 12 months. The waits compound — 14 days after a first failure, 30 after a second, 90 after a third — so sit when you are ready, not early.

Pass or fail, the scaled score, and percent correct by domain. If you do not pass, keep the breakdown: it tells you where to spend the time before your next attempt.

12 months.

Identification whose name matches your registration exactly. Check the spelling when you book, not on the day.

24 questions drawn from all seven domains, weighted like the exam and taken in one sitting of about 20 minutes. It draws from the same question bank, under the same rules, as the rest of the course.

Your first run is free and needs no card; a retake uses credits.

A starting readiness figure and each domain reported as questions right out of questions asked — three or four per domain, enough to show where to look first, not to grade a domain on its own.

Because certain-and-wrong is what fails people. Alloy watches the gap between how sure you were and how right you were, and can hand you back exactly the questions you were confident about and got wrong.

No. Its length is set by the course. A partial diagnostic measures less and still reports with the same confidence, so it is a worse diagnostic, not a smaller one.

Run the confident-and-wrong practice set, then open your weakest heavy domain, or follow Recommended next, which puts the single action that would move your readiness most in front of you.

Fifteen lessons: an exam-strategy lesson, then fourteen domain lessons — three for Integration, two each for Solution Design & Architecture, Evaluation, Testing & Optimization, Governance, Safety & Risk Management, Stakeholder Communication & Lifecycle Management and Claude Models, Prompting & Context Engineering, and one for Developer Productivity & Operational Enablement.

The exam-strategy lesson, on what CCAR-P measures and how to sit it, and the first domain lesson, on splitting a request among Claude, existing systems and people and pricing the split before you commit. Both come with podcasts, hosted by Morgan and Casey.

Yes. The exam-strategy lesson is worth a 10–20% score bump.

No. Alloy's course is preparation for CCAR-P, not the official exam or certification, and Alloy is not affiliated with Anthropic.

Yes. Alloy's Full membership covers all four Claude certification courses, including Claude Certified Architect — Foundations, and every course that opens while you are a member. Prices are on the pricing page.