Guides

Pacing and how to use flags

Updated 20 Nov 2026. Unofficial guide, checked against the official exam guides.

Every Claude exam lasts 120 minutes, but the number of items isn’t the same, so the time per item isn’t either:

Exam and version Items Time per item
Developer Foundations, until 6 Dec 2026 53 about 2:16
Associate Foundations, until 6 Dec 2026 60 2:00
Architect Foundations 60 2:00
Architect Professional, until 6 Dec 2026 63 about 1:54
Associate, Developer Foundations and Architect Professional, from 7 Dec 2026 70 about 1:43
Developer Professional 70 about 1:43

Two minutes sounds generous until you meet the scenarios. The items are long, the options are close, and many of them ask you to hold a set of constraints in your head while you compare several plausible answers. Two of the candidate write-ups linked below spend a good part of their length on the clock.

What the clock did to candidates

John Weidner found out on his first practice run that he was reading too slowly. A third of the way in, he could see he would run out of time.

On the real exam he flagged about seven of his first ten questions. The pile of flags made him more nervous with every question. He reached the end with 18 minutes left. On a second read the flagged items looked far less frightening, and he changed about half of those answers. The clock ran out while he was on the last one.

Szymon Paluch spent almost the full two hours answering and reviewing. His slowest questions were the ones with several reasonable answers, where one detail in the scenario decided.

Neither account is about not knowing the material. Both are about how long careful reading takes.

Plan two passes

The plan used in Prlić Consulting’s courses is simple. Finish the first pass at 1:45 on the clock, which leaves 15 minutes for flagged items.

Items Checkpoints on the first pass
53 Q13 at 0:26, Q27 at 0:53, Q40 at 1:19, Q53 at 1:45
60 Q15 at 0:26, Q30 at 0:52, Q45 at 1:19, Q60 at 1:45
63 Q16 at 0:27, Q32 at 0:53, Q48 at 1:20, Q63 at 1:45
70 Q18 at 0:27, Q35 at 0:52, Q53 at 1:20, Q70 at 1:45

At 70 items that works out to about 1:30 per item on the first pass. Check yourself against the clock only at the checkpoints. If you look at the clock after every item, you are spending time on the clock instead of the scenario.

If you’re behind at a checkpoint, don’t try to win it all back on the next item. Spend a little less on each of the next few.

How to read an item quickly

  1. Read the question line first. Look for words such as best, first, most likely cause, or choose two. They tell you what kind of answer you’re looking for before you read the scenario.
  2. Then read the scenario for its constraints. Cost ceilings, latency targets, compliance rules, who sees the output and what must never happen are what decide between close options. The guide to two answers that look right is about this step.
  3. Eliminate before you choose. Strike options that rely on prompt wording for something that must always happen, options that only detect a problem when the scenario needs it prevented, and absolute options such as “always” or “never review”.

On Architect Foundations, the four scenarios each come with a block of items. Read each scenario’s introduction once, slowly. Its constraints decide many of the items that follow, and reading it carefully once is quicker than skimming it four times.

Flags: a tool, not a parking lot

A flag means “I’ve answered, but I want a second look”. It doesn’t mean “I’ll think about this later”. Use these rules:

  • Always answer before you flag. If time runs out, a flagged item with your best guess can still score, and a blank can’t.
  • Flag after about two minutes, not after twenty seconds. If you flag every item that makes you hesitate, you’ll have a review list too long to work through, and the length of the list will rattle you. That is the trap Weidner describes.
  • Write down why you flagged. One word on the scratch material, if Pearson provides any (“latency?”, “first step?”), turns the second look into a check instead of a fresh start.
  • Change an answer only for a reason you can name. Change it if you misread a constraint or missed a word like “first”. Don’t change it because it feels too easy.

Unscored items don’t change the plan

The 70-item forms include 10 unscored items. You can’t tell which ones they are, and the guides tell you to allow time for every item. Don’t try to spot them. Give every item the same care.

Practise at exam pace

Each free form has an exam mode. Its timer runs at the pace of the version you choose: 20 items at 70-item pace gives you 35 minutes. Use the flag button the way you plan to use it on the day, then compare how many flags you set with how many answers you actually changed.

All guides Changes log