Claude Certified Architect — Professional: What CCAR-P Measures, and How to Sit It: the free first lesson

Item construction

The lesson starts by fixing three words. The stem is the question prompt — everything before the options. A distractor is a plausible but incorrect option; not random nonsense, but the proposal that would make a convincing slide in the wrong meeting. Item construction is the deliberate design of a question and its options together. So a question that feels unfair because all four options look defensible is usually not badly written. It is well constructed, which is a slightly less comforting thought.

Knowing the material is necessary and not sufficient: the losses come from options that look right, not from topics you never learned. For CCAR-P the published rule is one best response per item, so you are choosing the best design, not every defensible one.

The wrong-answer shapes and their counters

Five shapes recur, each with a check that converts a vague feeling of doubt into a specific diagnostic:

The lesson adds two refinements that stop the counters misfiring. "Simplest" means simplest sufficient — not cheapest, not shortest, not minimalism as a principle; an option too thin to meet the requirement fails the same test from the other side. And your restatement is the comparison standard: make it operational — I need the first step that reduces this risk, or I need the design choice that best meets this constraint — and comparing options becomes a match against one sentence you wrote, instead of a contest between four paragraphs the exam wrote.

Changing an answer

Change an answer when you can name what you missed on the first read, not on a feeling. Uncertainty is theatrical: it arrives late, lowers the lights and tells you your first answer was probably foolish. A named miss sounds like "the stem says the response must be grounded in current internal documents". It does not sound like "nothing, but I dislike uncertainty". This is not stubbornness — in a leadership setting it is the difference between revising a decision because new information arrived and reversing it because the room became uncomfortable. And time is the constraint people forget: reopening settled decisions without new evidence costs you items you have not read yet.

The blueprint

At 19% of 63 items, Integration is roughly twelve questions; Developer Productivity, at 7%, about four. The eight-item gap is comfortably enough to decide a borderline result.

The exam is 63 questions in 120 minutes, $175 an attempt, passed at 720 on a 100–1,000 scaled score, and valid for 12 months.

Two misreadings of your own result

Both cost preparation time rather than marks. Treating a domain figure as a hurdle — "I failed that domain, therefore I failed the assessment" — when the decision is made on the total scaled score. And chasing a raw-percentage target the scoring never promised: converting a scaled score into a percentage-correct goal invents a number and then optimises against it. A reported score has meaning inside its own scale, the way a credit rating or an investment index does. In the other direction, the result is a certification outcome, not an operating review, a leadership assessment or a crystal ball.

The shape that dominates

The characteristic item gives you a business situation, a constraint that narrows it, and four architectures. The constraint decides: a latency budget, data residency, a human-review requirement, a cost ceiling, or an existing system you must integrate with rather than replace. So read the last sentence of the stem before the options; reading the options first primes you to like whichever one you would have picked in an unconstrained world.

Why can a defensible option still be wrong? Because it satisfies half the requirement. Improve monitoring is good advice — but if the stem asks for the immediate way to prevent unauthorised data exposure, monitoring detects rather than prevents. Add more context often helps — but if the retrieved information is stale, more of it is a larger pile of yesterday. The shift from concept recognition to requirement matching is where most of the available performance sits, and it is a habit, not a fact you can revise.

What the lesson will not tell you

Working the course

The lesson closes with the moves that make Alloy pay back: take the diagnostic first (24 questions, about 20 minutes, weighted like the exam); rate your confidence honestly on every answer, because certain-and-wrong is what fails people and Alloy can hand those questions back; work flashcards when they are due; prove material rather than tick it, since reading is the weakest evidence and Scenarios and Labs the strongest; open Recommended next when you do not know what to do; watch the readiness figure and sit a practice exam when it says so; and come back, because the curriculum is watched and kept current by people. All seven domains are taught — but coverage is not depth, so check yourself against the published blueprint before you sit.

The exam-strategy lesson is worth a 10–20% score bump.

Next step

Take the free CCAR-P diagnostic, then open lesson one and its podcast. The second lesson — splitting a request among Claude, existing systems and people, and pricing the split before you commit — is free too.