How to prepare for the Claude Architect Foundations certification (CCAR-F)

I recently sat all three of Anthropic's Claude certifications — Developer, Architect Foundations, Architect Professional — and the result surprised me: the "Foundations" exam was the hardest of the three, and it is not close. It is more technical than the Developer exam, the questions are more ambiguous, and I walked out convinced I had failed. If you are going to sit one, that is the one that deserves respect — and preparation. This is the guide I wish I had read first: what the exam covers, which resources are worth your time, and what exam day actually feels like.

01What the exam is

Claude Certified Architect — Foundations (CCAR-F) is the entry point to Anthropic's architect track: 60 questions in 120 minutes, $125, delivered through Pearson VUE either online-proctored (OnVUE) or at a test centre. You need a scaled 720 out of 1,000 to pass, the credential lasts 12 months, and you get a digital badge through Credly. Where the Developer exam checks that you can use the Claude API, this one checks that you can design a system around it — the official page describes it as foundational knowledge across Claude Code, the Claude Agent SDK, the Claude API, and Model Context Protocol (MCP).

02The five domains — study where the marks are

• —Agentic architecture and orchestration — 27%. How agentic loops work, when an agent beats a fixed workflow, orchestrating tools and steps. The heart of the exam.
• —Claude Code configuration and workflows — 20%. Settings, CLAUDE.md, hooks, CLI flags, permissions.
• —Prompt engineering and structured output — 20%. System prompts, structured outputs, getting reliable, repeatable behaviour.
• —Tool design and MCP integration — 18%. What makes a good tool definition, and how MCP servers fit into a design.
• —Context management and reliability — 15%. Context windows, caching, keeping long sessions coherent.

Two things should jump out. Agentic architecture alone is more than a quarter of the exam, and Claude Code configuration is another fifth. And note the trap in the name: "architect" suggests whiteboards and trade-offs, but a big share of the questions are concrete and technical — CLI flags, parameter values, file locations, context-management details. In my sitting, roughly 25 of the 60 questions were technical in wording, and the answer choices were harder to eliminate than anything in the practice sets. They hid the hard questions in the "foundations" exam.

03The prep plan

First, book the exam. Buy it on the official page and schedule a Pearson VUE slot before you study anything — a fixed date is the best motivator, slots go faster than you expect, and rescheduling is a couple of clicks if you need it. Then:

• —Read the exam guide first (linked from the official page). It is the source of truth for domains, weights, and question style — everything else is commentary.
• —Work the free Anthropic Academy courses, weighted to the big domains: Claude Code 101, the platform and MCP courses, and Building with the Claude API cover most of it. Do not binge everything; spend your hours where the marks are.
• —Read the documentation like it is 2003 and you have an exam tomorrow. The exam asks for details you would normally just look up — docs.claude.com across the five domains, plus the MCP spec. Make a one-page cheat sheet per domain as you go; writing it is the studying.
• —Practice with real questions. CertSafari has 480 free CCAR-F questions with explanations, claudecertificationguide.com has a 15-minute diagnostic and a full 60-question mock, and the community mock-exam site is — in my experience — the only one at real exam difficulty. Practice until the wording stops surprising you.

You will see six-week study plans for this exam. Unless certification is your hobby, skip them: read the guide, do a practice exam, fill the gaps, sit it. But do not confuse "skip the six-week plan" with "no preparation" — I use Claude and Claude Code every day and still needed serious study, because daily use hides exactly the details this exam tests.

04Exam day

• —OnVUE is online proctoring: quiet room, webcam, stable connection, government ID, a photo check at setup, and no external screens or devices. Run Pearson's system test the day before, not the morning of.
• —120 minutes for 60 questions sounds comfortable. It is not, because the scenarios take reading. Flag anything slow and move on — I flagged 28 of 60 and worked back through them with the time left.
• —Read the scenario carefully. The obviously technical answer is often the wrong one: the exam tests how and when features should be used, not recall.
• —If you do not pass, retakes are allowed on the schedule in the exam policy PDF — read it before you book so the safety net is real, and walk in relaxed.

05Is it worth it?

You do not need to have built a multi-agent orchestration system to pass. A technical background speeds up preparation, but what the exam really wants is understanding how things work behind the scenes — how context flows through a long session, why one tool design is right and another is a footgun, what Claude Code is actually doing. That is learnable by anyone willing to read. Non-technical candidates will find the Claude Code and CLI stretch the hardest; budget extra cheat-sheet time there.

My honest verdict: a certificate proves you studied, not that you can ship. But preparing forced me to formalize things I normally just look up, and that has stuck — the same material is the design work behind the agent systems we build for clients. If agentic architecture is about to become part of your job, the exam is a cheap, structured way to make yourself learn it properly.