Claude Architect Exam: 6-Week Study Plan, Cheat Sheet and Exam-Day Tips

📚 Exam guide v1.0 (July 2026)🔄 Checked against official sources: 11 Nov 2026✏️ Updated: 12 Nov 2026⏱️ 8 min read🎯 All five domains (revision)

👋 In plain words: You have covered every topic. Now you need a plan that fits your week, a one-page sheet to revise from, and a calm routine for exam day. This lesson gives you all three.

You’ve covered every domain. This lesson turns it into a plan, a one-page revision sheet, and tactics for exam day.

📖 What You’ll Learn: You will leave with a week-by-week plan, a revision sheet and a strategy for exam day.

🔑 Key terms

Mock test: A timed practice exam. Ours have 30 questions in 60 minutes.
Readiness target: 85% or more on three mock tests before booking the real exam.
Flagging: Marking a question to come back to later in the exam.

📖 The story in this lesson

Ravi has six weeks, about 7 hours a week, and a full-time job. Here is how he fits the course, the labs and the mock tests in, and what he does on exam day.

💡 Think of it like this

Exam prep is like training for a 10 km run. Steady weekly sessions beat cramming, practice runs show where you are, and on race day you pace yourself instead of sprinting the first kilometre.

🗺️ 6-week study plan (6–8 hours a week)

Week	Study	Practice
1	Read the official exam guide; Module 2 lessons on loops and orchestration	Labs 1–2
2	Hooks, decomposition, sessions; Module 3 (tools and MCP)	Labs 5 and 7
3	Module 4 (Claude Code)	Labs 6 and 8 · Mock Test 1
4	Module 5 (prompting, structured output, batches)	Labs 3–4 · Mock Test 2
5	Module 6 (context, escalation, provenance) and the 6 scenarios	Mock Tests 3 and 4
6	Revise weak domains with the cheat sheet	Mock Test 5 timed · book the exam once three mocks score 85%+

🌍 Real-world example: Ravi's week 3

Monday and Wednesday evenings: Module 4 lessons. Saturday morning: Labs 6 and 8 on his own repository. Sunday: Mock Test 1, timed. He writes down every domain where he scored below 70% and revisits those lessons the following week.

📋 One-page cheat sheet

LOOP        continue while stop_reason=="tool_use"; stop on "end_turn". Never parse text.
RESULTS     all tool_results for a turn → ONE user message.
MUST-HOLD   money / identity / compliance → hooks & gates, not prompts.
HOOKS       pre-tool interception = block/redirect;  PostToolUse = normalise results.
SUBAGENTS   Task tool; allowedTools includes "Task"; pass context explicitly; parallel = many Task calls in ONE turn.
NARROW?     whole areas missing, subagents "succeeded" → coordinator decomposition too narrow.
TOOLS       description = selection signal; 4–5 tools per agent; rename/split overlaps.
TOOL_CHOICE auto | any (must call some) | {"type":"tool","name"} (must call X) | none.
ERRORS      isError + category + isRetryable; empty ≠ failure.
MCP         .mcp.json (team, ${ENV}) vs ~/.claude.json (personal); resources = catalogues.
CLAUDE.md   ~/.claude (you) | repo (team) | subdir; @import; .claude/rules + paths; /memory.
SKILLS      context: fork | allowed-tools | argument-hint; personal variant = new name.
PLAN MODE   architecture / multi-file → plan; clear single fix → direct.
CI          claude -p ; --output-format json --json-schema ; independent reviewer.
BATCH       50% off, ≤24h, no SLA, custom_id, no mid-request tools; never for blocking checks.
SCHEMA      kills syntax errors, not semantic ones; nullable for absent data; enum+other+detail.
RETRY       with specific error; useless when info is absent.
CONTEXT     case-facts block; trim tool output; key findings first; scratchpad; /compact.
ESCALATE    explicit human request | policy gap | no progress. Not sentiment/confidence.
REVIEW      segment accuracy by type & field; stratified sampling; calibrated confidence.
PROVENANCE  claim→source+date; keep conflicting values, annotated.

🌍 Real-world example: Revising in 10 minutes a day

Ravi prints the cheat sheet and covers the right-hand side of each line with a card. He says the answer aloud, then checks. Any line he can't explain gets a mark, and he re-reads that lesson the same day.

📚 Official resources

Anthropic Partner Academy and the official exam guide: anthropic-partners.skilljar.com
Free Anthropic Academy courses: anthropic.skilljar.com (Building with the Claude API, Claude Code in Action, Introduction to MCP, MCP Advanced Topics, Introduction to agent skills, Introduction to subagents)
Claude API docs: platform.claude.com/docs · Claude Code and Agent SDK docs: code.claude.com/docs · MCP: modelcontextprotocol.io
Pearson VUE Claude certification page: pearsonvue.com/us/en/anthropic.html

🌍 Real-world example: Using official sources wisely

Ravi takes the free 'Claude Code in Action' course on Anthropic Academy during week 3, alongside Module 4, and keeps the official exam guide open while planning, so he studies the objectives the exam actually lists.

🏁 Exam-day tactics

Read the final line of each question first: “most effective first step”, “most likely root cause”, “choose TWO”.
Underline constraint words: guarantee, must, every developer, without committing secrets, cost is the priority.
Eliminate options that fix a different problem or over-engineer a first step.
In multiple-response items, judge each option independently.
Flag anything over 3 minutes and come back to it. Never leave a blank.
For online testing: clear desk, one monitor, system check done, ID ready 30 minutes early.

🌍 Real-world example: A question that seems to have two right answers

Ravi reads the last line first: 'What is the most effective first step?' Two options would work, but one needs a new classifier. He picks the cheaper fix that targets the root cause, flags nothing, and moves on in 90 seconds.

🚫 Common beginner mistake: Booking the exam after one good mock score. Wait until three mocks are at 85% or more.

🛠️ Try it yourself (about 10 minutes)

Open your calendar and block six weekly study slots.
Write the module or lab for each slot, following the plan table.
Put Mock Test 1 at the end of week 3.

✅ You are done when: six slots are booked and each one names its module, lab or mock test.

🧪 Exam-Style Practice Questions

Try these before opening the answers. They use the same scenario style as the real exam.

Question 1. Which coordinator prompt style best lets subagents adapt?

A. "Do your best"
B. Research goals plus quality criteria (coverage, source types, recency)
C. A full transcript of past runs
D. A numbered list of exact search queries to run

Show answer

Answer: B. Goals and criteria let subagents choose their own tactics. D: rigid procedures stop them adapting to what they find. A: too vague. C: noise.

Question 2. The agent keeps using built-in Grep instead of your more capable code_search MCP tool. What's the first fix?

A. Rename it to grep2
B. Improve the MCP tool's description to explain its capabilities and outputs
C. Remove Grep
D. Move the server to user scope

Show answer

Answer: B. Selection follows descriptions. C may break other workflows. A adds confusion. D changes who can use it, not how it's chosen.

Question 3. Developers dismiss many findings, and you want to analyse which code constructs cause false positives. What should you add to the findings schema?

A. detected_pattern
B. model_version
C. timestamp
D. sentiment

Show answer

Answer: A. It lets you analyse dismissals by pattern. B and C are useful metadata but don't identify triggers. D is irrelevant.

📝 Assignment

Do these tasks in order. Each one has a Done when check, so you know when it is complete. The stretch task is optional but close to what the exam expects from an architect. Keep your answers in one notes file or Git repository, and revisit them in your final week of revision together with the cheat sheet in the last lesson of this course.

Task 1: Put the six-week plan in your calendar with fixed study slots.
✅ Done when: Six weekly study slots are in your calendar, with the module or lab for each slot named.
Task 2: Print the cheat sheet and mark the lines you cannot explain yet.
✅ Done when: Every line of the cheat sheet you could not explain is marked, and you revisited its lesson.
Stretch: take all five mock tests and book the exam once three are 85% or higher.
✅ Done when: You have three mock scores of 85% or higher before booking the exam.

❓ Frequently Asked Questions

🤔 How long should I study for CCAR-F?

About six weeks at six to eight hours a week if you already build software.

🤔 What score should I aim for on mock tests?

At least 85% on three mocks before booking the real exam.

🤔 What happens if I fail?

You can retake after 14 days, then 30, then 90, with up to four attempts in a rolling twelve months.

🤔 Is the exam open book?

No. Notes, documentation and AI assistants are not allowed.

🏁 Summary

Six weeks at 6–8 hours a week: one module per week, with labs and a mock test from week 3.
Revise from the one-page cheat sheet and re-read the lesson behind any line you cannot explain.
Book the exam once three mocks score 85% or more; on exam day, read the final line of each question first.

📝 Test yourself: Mock Test 1 · Mock Test 2 · Mock Test 3 · Mock Test 4 · Mock Test 5 (30 scenario-based questions in 60 minutes, with explanations).

You have finished the course. Now take the timed mock tests.

🎬 Prefer video? Watch QA, automation and AI testing tutorials on the SQA Tools YouTube channel.

Independent study material by SQA Tools. Not affiliated with, endorsed by or sponsored by Anthropic. Claude is a trademark of Anthropic. Mock questions are original practice items, not real exam content. Exam facts checked against Anthropic's official exam guides and certification FAQ on 11 November 2026.