Exam Structure
Total: 60 questions
Time: 120 minutes
Per question: 2 minutes average
Passing: 720/1000 (72%)
Format: Multiple choice, 4 options each
Scenarios: 4 of 6 randomly selected
Questions per scenario: ~15 per scenario × 4 scenarios = 60
(some scenarios may get more or fewer questions)
The 2-Minute Question Process
Step 1: Read the scenario setup (15 seconds)
What is being built? (customer support, code review, extraction?)
What is the problem? (reliability, compliance, performance?)
Step 2: Identify the domain(s) being tested (15 seconds)
Compliance enforcement → D1 hooks
Tool selection → D2 descriptions
CI/CD → D3
Structured output → D4
Error handling → D5
Step 3: Read all 4 options (20 seconds)
Don't stop at the first plausible option
Step 4: Eliminate clearly wrong options (20 seconds)
Usually 2 options are obviously wrong
Step 5: Apply the principle to the remaining 2 (30 seconds)
What does the scenario signal? ("must always" → determinism)
Which option embodies the correct principle?
Step 6: Answer and flag if uncertain (5 seconds)
If confident: answer and move on
If uncertain: guess best option, flag for review, move on
The 10 Most-Tested Concepts — Know These Cold
1. stop_reason drives loop control — never text parsing
2. Programmatic enforcement (hooks) vs prompt guidance
3. tool_choice: auto vs any vs forced — and when each applies
4. Minimal footprint — request only necessary permissions
5. Hub-and-spoke — coordinator is the only communication hub
6. CLAUDE.md hierarchy — user (not git) vs project (git) vs directory
7. -p flag required for CI/CD headless execution
8. JSON schema eliminates syntax errors, not semantic errors
9. Multi-instance review — independent instance, no shared context
10. Batch API — 50% cost, up to 24h, never for latency-sensitive work
60-Second Process for Uncertain Questions
You've eliminated 2 options. Two remain. You're not sure.
Step 1 (15 sec): Re-read the scenario for signal words
"must always" → determinism → enforcement
"compliance" → programmatic
"independent" → parallelize
"performance" → parallel execution
"files changed" → fresh session
Step 2 (15 sec): Apply the signal word to the two options
Which option embodies the signaled principle?
Step 3 (15 sec): Trust your first instinct
Your prepared knowledge is more reliable than exam-pressure reasoning
If no signal word helped: go with your gut and move on
Step 4 (15 sec): Flag and move
Mark for review. Time-box at 2 minutes. Move to the next question.
You can return to flagged questions if time permits.
Night Before — What to Review
DO review:
- The 10 most-tested concepts above (5 minutes each)
- The six scenario domain maps
- The two-right-answers pattern library
DO NOT:
- Read new material
- Try to learn anything you don't already understand
- Practice more questions after 9pm
DO:
- Sleep adequately — cognitive performance matters more than cramming
- Eat well before the exam
- Arrive/log in 15 minutes early
Passing Score Reality
720/1000 = 72% = 43-44 of 60 questions correct
You can get 16-17 questions WRONG and still pass.
This is not a perfection test. It's a mastery test.
If you've studied all 6 domains thoroughly, you know enough to pass.
Key Takeaways
- 2 minutes per question maximum — flag and move on if stuck
- Signal words → principles → answers — don’t analyze, pattern-match
- Know the 10 most-tested concepts cold — review the night before
- 720/1000 passing — you can miss 16-17 questions and still pass
- Sleep — cognitive performance matters more than last-minute cramming