Claude Certified Architect (Foundations) Exam: A Study Guide and How I Passed

I took the exam at the start of the week and had my result by midweek, I passed. Below are the resources I leaned on and how the exam actually went.

One caveat up front. Some of these resources are official and some are community-made, and I've flagged which is which. The community ones are genuinely useful, but treat them as a study aid rather than gospel. A bit of vibe code energy, helpful but not authoritative.

Start here: the official docs

Read these before touching anything else. The point of reading them first is to know what to skip later.

The Exam Guide (official). You get this once you're granted access to the exam. It describes the exam content, lists the domains and task statements that get tested, includes sample questions, and recommends how to prepare, which together tell you what to study and what to skip. Reading it first saved me from over-studying corners that never came up.

The FAQ (official). This one shows up once you've purchased the exam. Short, but one line matters more than the rest. It recommends scoring above 900/1000 on the Practice Exam as your signal. The logic is that the real Certification Exam passes at 720, so if you're consistently clearing 900 on the practice, you've got a very strong sense you'll pass the real thing. I treated 900 as my "ready" line and didn't book the exam until I was clearing it comfortably.

The official courses

Anthropic publishes free training on Skilljar, and four courses cover what the Foundations exam actually tests:

• Building with the Claude API
• Claude Code in Action
• Introduction to Agent Skills
• Introduction to Model Context Protocol

Work through these before the community guides, since the exam maps closely to this material.

Community study resources

paullarionov/claude-certified-architect guide. This one was a genuinely useful read. It walks through the concepts in a way that helped me make better choices on the mock exam. The repo also includes a PDF version of the guide and a mock test you can repeat as many times as you want, which is where most of my practice reps came from besides the official mock exam.

The CCA-F study material site. Good for the "know this, avoid that" framing. It points you at concepts worth knowing and flags common traps. It also links out to the suggested study materials, which are worth reading rather than skimming.

For grounding the concepts in real code

Anthropic's claude-cookbooks. These are worked examples of how the concepts are actually implemented. I read through several of them and compared the code against what the courses taught. Even reading a handful made the abstract ideas concrete, which helped on the questions that test whether you actually understand a pattern rather than just recognize its name.

Claude Code in CI/CD pipelines (panaversity). I'm calling this out separately because the real exam had quite a few questions on git pipeline commands, more than I expected from the mock. This page has good examples of that material. If git and CI/CD aren't part of your daily muscle memory, spend time here.

ProctorFree exam setup

The exam runs online through a tool called ProctorFree, and getting from the invite to the first question takes more steps than I expected. An exam email arrives with a link, and following it walks you through downloading ProctorFree, installing it, and clearing its pre-exam setup, which runs a hardware and connection check across your camera, microphone, network, and screen recording. Once that passes you begin, and the whole session is recorded from start to finish. The step that's easy to fumble is the very end: after you submit, leave everything open until the recording has finished uploading.

A few things made the setup smoother for me. Run on a single screen and unplug any external monitors before you start, then shut down anything you don't need open. The obvious culprits are chat apps like Slack, Teams, and Discord, and the proctor also flags less obvious ones:

• other AI assistants, like Claude or ChatGPT
• translation tools
• IDEs and note-taking apps
• any stray browser tabs

Clear your desk, check that your camera and mic are working, and you should be ready.

At the end of the exam, after you submit, wait until the recording upload has fully completed before closing anything or shutting down.

The proctoring wasn't the hard part of the day, but it's worth getting your environment right beforehand so it never becomes one.

How the exam actually went

Scoring is officially 5 or more days but mine came back noticeably faster than that, so don't assume you'll be waiting all week.

The biggest gap between the mock and the real exam was the wording, not the difficulty of the underlying concepts. The real questions used more complex sentences, and they hide key qualifiers inside them. The correct answer often turns on a single word you have to slow down and find. On the mock I could move fast, but on the real exam reading carefully was the whole game.

What I'd tell you before you sit it

• Read the official Exam Guide first, so you know what to skip but also in which direction to go when answering. This is the single most useful thing you can do.
• Use the practice exam as your readiness gauge. Don't book until you're clearing 900/1000 comfortably. The FAQ's 900 line is good advice.
• Slow down on the wording. The real questions bury qualifiers in longer sentences. Find the qualifier before you pick.
• Don't skip git and CI/CD. The pipeline command questions showed up more than the mock suggested, and the panaversity page is a good drill.
• Read a few cookbooks, not just course slides. Seeing the patterns in code is what separates recognizing a concept from understanding it.
• Build the exercises the guide describes and actually run them, which pays off most if your experience so far leans more toward reading about the patterns than writing them, because working through something you can run and break yourself sticks far better than reading the description and nodding along.
• Take the community resources seriously but lightly. They're a great head start, not the source of truth. The official guide and FAQ are.

That's the lot. If you're on the fence about sitting it, the prep is doable with the resources above, and the certification is a solid checkpoint for getting your fundamentals straight.