How Long Is the CCA Exam? 120 Minutes and a Pacing Plan

The CCA Foundations (CCA-F) exam is 120 minutes long. In that time you answer 60 scenario-based questions, which works out to two minutes per question on average. Confirm the current time limit on the official Anthropic Academy or Pearson VUE page before you register, since exam specifications can be revised.

Two hours sounds generous until you meet a question with a 200-word scenario and four options that all look reasonable. This post covers how the time actually gets spent, how to pace a flag-and-return strategy, and why we run our mock on 90 minutes instead of 120.

Is 120 minutes enough for 60 scenario questions?

For most prepared candidates, yes, but the margin is smaller than the arithmetic suggests. Questions vary widely in length:

• Short items (roughly a third). A two-sentence stem asking about a specific mechanism: which permission mode, which tool_choice value, which hook fires. Under a minute each if you know the material.
• Medium items (roughly half). A paragraph describing a system and a constraint, then four design options. Two to three minutes to read carefully and eliminate.
• Long items (the rest). A full architecture description: a multi-agent pipeline, a CI workflow, a support agent with escalation rules. Four to five minutes, sometimes more if you re-read.

If you spend five minutes on ten long questions, that is 50 minutes gone on one-sixth of the exam. The remaining 50 questions then get 70 minutes, which is comfortable only if the short items really are short for you. Time pressure on this exam comes from reading, not from calculating.

What is the best way to pace the CCA-F exam?

Use a flag-and-return approach with three passes. The Pearson VUE interface normally lets you flag items and jump back to them before you submit; verify this in the tutorial that runs before the timer starts.

Pass	Time budget	What you do
First pass	~75 minutes	Answer every question. Pick a provisional answer for anything uncertain and flag it. Do not leave blanks.
Second pass	~30 minutes	Return to flagged items. Re-read the constraint sentence, eliminate options that violate it, decide.
Final buffer	~15 minutes	Check every multiple-response item has the required number of selections. Submit.

The rule that saves the most candidates: never let a single question consume more than four minutes on the first pass. Pick the least bad option, flag it, move on. Unanswered questions score zero; a provisional guess on a four-option question is worth a quarter of a point in expectation, and much more if you have eliminated two options.

Why does our mock use 90 minutes instead of 120?

Our mock exam has the same 60 questions, sampled by official domain weight, but a 90-minute clock. That is 90 seconds per question, deliberately tighter than the real exam. The reasoning:

• Practising under a stricter clock builds the habit of deciding and moving on rather than lingering.
• On exam day, nerves and unfamiliar phrasing slow you down. If your comfortable pace is 90 seconds per question, the real 120 seconds gives you a built-in buffer.
• A 90-minute session is easier to fit into an evening, which means you actually take more mocks.

If you consistently finish the mock with time to spare and score above 80%, the length of the real exam should not be a concern. If you run out of time on the mock, that is a diagnostic: you are re-reading too much or you do not yet recognise the patterns quickly. Address it in the practice hub with untimed domain sets first, then return to timed mocks.

What does the exam day timeline look like?

The 120 minutes is only the scored portion. A realistic schedule for an online proctored (OnVUE) sitting:

1. 30 minutes before. Log in, run the system check, photograph your ID and workspace, wait for a proctor. Test centers have their own check-in.
2. 0 minutes. Agree to the candidate rules, complete the short interface tutorial. The tutorial is usually untimed and separate.
3. 0 to 120 minutes. The exam. No unscheduled breaks in most online proctored setups; leaving camera view can end the session.
4. After submitting. A brief survey and, typically, a preliminary result on screen. The official score report follows.

Confirm break rules and check-in requirements for your specific delivery method on the Pearson VUE page, and read your confirmation email; it is the authoritative source for your appointment.

What is the exam really testing with a time limit?

The time limit is a proxy for something the exam wants to measure: can you read a scenario, spot the binding constraint, and reject designs that ignore it, quickly and reliably. Most stems boil down to “given this constraint, which option is the least bad.” Candidates who lose to the clock are usually reading every option in full detail before finding the constraint. Read the constraint first, then scan options for the ones that violate it. That single habit reclaims 15 to 20 minutes across the exam.

Next step

Take the 90-minute mock exam once under strict timing and note where the clock hurt. Then read the Domain 1 study guide; its long orchestration scenarios are where most candidates lose time, and knowing the patterns cold is the fastest way to buy it back.