Claude Certified Architect — Professional: Architect-level exam strategy starts with blind-spot detection

The paper

• 63 questions in 120 minutes — about one minute fifty each. Enough to read a scenario carefully once and decide; not enough to relitigate.
• $175 per attempt, and the credential is valid for 12 months.
• One intended answer per item. Unlike the Associate exam, which mixes multiple choice with multiple response, you are choosing the best design, not every defensible one.
• 720 on a 100–1,000 scaled score, judged on the total. The per-domain percentages on your report are informational, not separate gates.
• Unanswered questions are scored as incorrect, and there is no penalty for guessing. A guess has positive expected value and a blank has none; if time is running out, fill everything.

Step 1: find the blind spots

Take a diagnostic before you study. Alloy's is free: 24 questions, about 20 minutes, weighted like the exam, with each domain reported as questions right out of questions asked and a confidence rating on every answer. The confident-and-wrong answers are the ones to find first — being unsure and wrong sends you back to check; being certain and wrong never does.

Step 2: weight by the blueprint, not by experience

Because no single domain can fail you, you are not raising a floor; you are maximising total items correct. An hour that lifts Integration by ten points is worth about 1.2 items, the same hour on Developer Productivity about 0.4. The per-domain counts on the day are not published — the right-hand column is each weight applied to 63 — but the eight-item gap between largest and smallest is enough to decide a borderline result.

Check yourself against the published blueprint before you sit. Coverage is not the same as depth; work every domain against its weight rather than against how many lessons mention it.

Step 3: read for the constraint

The characteristic CCAR-P item gives you a business situation, a constraint that narrows it, and four architectures that all look reasonable if you skim. The constraint is what decides: a latency budget, data residency, a human-review requirement, a cost ceiling, or an existing system you must integrate with rather than replace.

• Read the last sentence of the stem before the options. That is where the constraint usually sits, and reading options first primes you to like whatever you would pick in an unconstrained world.
• Restate the question as a sentence you can measure against — "I need the first step that reduces this risk", "I need the design choice that best meets this constraint". Comparing options then becomes a match against one sentence you wrote, not a contest between four paragraphs the exam wrote.
• Expect partial truth. An option can be individually defensible and contextually wrong. Improve monitoring detects exposure; it does not prevent it. Add more context does nothing for context that is stale. The shift from concept recognition to requirement matching is where most of the available performance sits.

Step 4: apply the five checks

1. 1.The absolutist — "always", "never", "all", "only", "every". Name one credible counter-example and it is out.
2. 2.True, but irrelevant — a correct answer to the wrong request is still wrong. Re-read the stem's final sentence.
3. 3.Right action, wrong layer — name where the problem lives (prompt, retrieval, application or model) before reviewing options.
4. 4.The over-engineered option — choose the simplest sufficient option. That is not the cheapest or the shortest; an option too thin to meet the requirement fails the same test from the other side.
5. 5.An answer to a different question — your restatement is the standard every option is measured against.

Step 5: change answers only with a named miss

Uncertainty is theatrical: it arrives late, lowers the lights and tells you your first answer was foolish. A named miss sounds like "the stem says the response must be grounded in current internal documents" — a specific constraint that changes the evaluation. "Nothing, but I dislike uncertainty" is not one. This is not stubbornness; it is the difference between revising a decision because new information arrived and reversing it because the room became uncomfortable. And watch the clock: if a question has taken three minutes, you are already more than a full item behind — choose the best option you have and move.

Step 6: ignore the shortcuts

Across the forty question-shaped items in Anthropic's official course material, exactly one carries a recorded correct answer, so nobody is reading the keys from that material, and "the longest option is usually right" cannot be tested in either direction. Whether items can be flagged and revisited, whether delivery adapts, and how many items each domain contributes on the day are also unpublished. The official material's checkpoints outnumber its quizzes almost six to one: it stops you after a decision and asks whether you can defend it. Prepare the same way.

Step 7: book deliberately, and use the result

You have up to four attempts in a rolling 12 months, and the waits compound — 14 days after a first failure, 30 after a second, 90 after a third — so a fourth attempt sits more than four months behind the third. That is the strongest argument for sitting when ready. Bring identification whose name matches your registration exactly; check the spelling when you book.

Your report returns pass or fail, the scaled score and percent correct by domain. If you do not pass, keep the breakdown: it tells you where the next fourteen days should go. And read the result for what it is — a certification outcome, not an operating review, a leadership assessment or a crystal ball.

Next step

Take the free CCAR-P diagnostic, then the free exam-strategy lesson and its podcast. The exam-strategy lesson is worth a 10–20% score bump.