9.1. Exam Strategy
Pacing. At roughly 75 questions in 120 minutes, you have about 1.5 minutes per question on average — enough to read carefully, but not enough to agonize. If a question isn't clicking within 60-90 seconds, flag it and move on; a fresh read after finishing the rest of the exam is almost always faster than staring at the same sentence.
Flag-and-return. Use the exam's flag/review feature liberally. Two questions this exam likes to disguise as "hard" are actually easy once flagged and revisited: (1) questions that hinge on a single precise term (fork vs. template, watch vs. follow, role vs. visibility) where a second read makes the distinction obvious, and (2) multi-select questions where re-reading "select all that apply" after answering everything else prevents a rushed, partial answer.
Read for the distinction, not the topic. GH-900 rarely asks "what is X" in isolation — it asks you to tell X apart from something that sounds similar (Git vs. GitHub, 2FA vs. passkey, fork vs. template, following vs. watching, role vs. visibility). When a question names two GitHub features in the same sentence, that's usually the actual thing being tested.
Eliminate before you select. On multiple-choice questions, actively rule out answers that describe a real GitHub feature that just doesn't fit the scenario — GH-900's distractors are usually accurate descriptions of the wrong feature, not made-up nonsense. Ruling those out first narrows a four-option question to a genuine two-way call more often than not.