1.1 Certification Context

What CCAR-F Actually Tests

Claude Certified Architect - Foundations now uses the Pearson exam code CCAR-F; older materials and this route use CCA-F. It launched on March 12, 2026 with the Claude Partner Network (CPN). The exam validates that a solution architect can design, scope, and deploy production applications built on Claude; it is not a consumer chatbot-usage test.

The questions are scenario-driven. You are given a business situation ("a support team needs to route 10,000 tickets a day with an audit trail") and asked to pick the design that best balances reliability, cost, latency, and safety. The correct answer is the architecture trade-off that fits the stated constraints, which is why memorizing syntax fails and this guide teaches design reasoning.

Exam Logistics at a Glance

The current Anthropic certification page and Pearson program page control logistics; confirm them again before scheduling.

A 720 of 1000 scaled score does not mean "72% of questions correct." Anthropic does not publish a raw-score conversion or public pass rate.

The Five Exam Domains and Their Weights

CCA-F is organized into five competency domains. Their relative weight tells you exactly where to spend study time: Agentic Architecture is the single largest domain, so the agent-versus-workflow decision, agentic loops, and multi-agent orchestration deserve the most attention.

Note that Domains 2, 3, and 4 together account for 58% of the exam, but no single one dominates. Domain 1 at 27% is the heaviest, and Domain 5 at 15% is the lightest yet still meaningful. A balanced study plan weights practice roughly to these percentages rather than treating every topic equally.

Where CCA-F Sits in the Roadmap

Foundations is the entry tier. Anthropic announced three additional 2026 tracks:

• Seller certification for go-to-market professionals.
• Developer certification for hands-on implementation engineers.
• Advanced Architect for complex, multi-system enterprise design.

CPN membership itself is free for qualifying organizations and provides training, technical support, and joint market development. Membership is not a hard prerequisite for sitting CCA-F, but it is the channel through which most candidates discover the exam and access prep resources.

The Architecture Lens to Read Every Question With

The exam rewards a consistent mental checklist. For each scenario, ask:

1. What does the user actually need? Distinguish the outcome from the implementation.
2. What does failure cost? A wrong medical summary is catastrophic; a wrong movie suggestion is not. Cost-of-error sets the reliability bar.
3. Is the path predictable? Predictable, repeatable tasks favor a workflow (orchestrated by code). Open-ended tasks needing dynamic decisions favor an agent.
4. What data must be fetched, and from where? This drives retrieval and tool design.
5. Which tool permissions are strictly necessary? Apply least privilege.
6. How will the team know it still works after a model, prompt, or integration change? This is the evaluation and monitoring requirement.

Common Traps

• Choosing the most powerful or most autonomous design "to be safe" — the exam usually penalizes unnecessary autonomy and cost.
• Treating CCAR-F like a coding test and memorizing endpoint parameters; the exam tests design choices, not syntax.
• Using launch-era logistics — the current exam is $125, valid for 12 months, and delivered through Pearson VUE.

This guide teaches the principles and trade-offs above. It does not reproduce live exam wording, private partner materials, or proprietary questions.

The Claude Ecosystem You Are Being Tested On

CCA-F assumes fluency in the building blocks Anthropic ships, because production architecture means choosing among them correctly. The exam draws scenarios from this surface area:

• The Messages API - the primary interface for sending conversations to Claude, including system prompts, multi-turn history, and tool use (function calling) where Claude requests a tool and your code returns the result.
• The Claude Agent SDK - Anthropic's framework for building agents that run the gather-context, act, verify loop, with built-in session management, subagents, and tool wiring.
• Model selection across the Claude family - choosing a smaller, faster model for high-volume classification and a more capable model for complex reasoning. The exam frames this as a cost-latency-quality trade-off, not a "always use the biggest model" decision.
• Prompt caching - reusing a large, stable prefix (such as a long system prompt or document) across calls to cut cost and latency. Knowing when caching pays off (stable, repeated context) is a recurring theme.
• Structured output - constraining Claude to return JSON that matches a schema, so downstream code can parse it reliably.
• Retrieval-augmented generation (RAG) - fetching relevant documents at request time and grounding answers in them, with citations.
• The Model Context Protocol (MCP) - the open standard for connecting Claude to external data and tools through a uniform server interface.

Why "Architecture" Is the Operative Word

A developer asks "how do I call the API?" An architect asks "given this volume, budget, latency SLA, and risk profile, which combination of model, pattern, retrieval, and guardrails best serves the user?" CCA-F is written for the second question. Expect distractor answers that are technically functional but mismatched to the stated constraints - for example, an autonomous agent proposed for a task that a two-step prompt chain would handle more cheaply and predictably. Your job on each item is to select the design whose trade-offs align with the scenario, then be able to defend why the alternatives are worse.