Exam-Day Time Management and PBQ Order
Key Takeaways
- The 90-minute limit requires active pacing; do not let one performance-based question consume the time needed for easier points.
- Use an initial PBQ triage: complete familiar PBQs, mark partially solvable ones, and defer confusing ones.
- Multiple-choice questions should be answered with a one-pass, flag, and return strategy.
- Final review should prioritize flagged questions with strong evidence gaps, not questions already answered confidently.
- Exam-day notes should include a compact subnetting grid, domain weights, timing checkpoints, and personal weak areas.
Exam-Day Timing and PBQ Order
Network+ N10-009 gives you 90 minutes for up to 90 questions. Because the exam can include both multiple-choice and performance-based questions, time pressure is not evenly distributed. Some questions take 20 seconds. Some PBQs can take several minutes. Your pacing plan should protect the full exam, not just the first difficult task.
The 90-Minute Budget
A practical budget is:
| Time remaining | Target status |
|---|---|
| 90 minutes | Read instructions, stay calm, begin triage |
| 80 minutes | PBQs have been completed, partially answered, or flagged |
| 55 minutes | Roughly one-third to one-half of multiple-choice complete |
| 30 minutes | Most multiple-choice complete; flagged list is controlled |
| 15 minutes | Final pass on flagged PBQs and high-value uncertain questions |
| 5 minutes | Submit only after checking unanswered items |
This is not a rigid rule. It is a set of checkpoints. If you are far behind a checkpoint, stop perfecting one question and move to the next answerable item.
PBQ Triage
PBQs often appear near the beginning. Treat them with a triage pass:
| PBQ type | Action |
|---|---|
| Familiar and mechanical | Complete now, verify, move on |
| Long but understandable | Complete obvious parts, flag, return later |
| Confusing after one careful read | Flag and move on |
| Requires calculations | Do the setup if quick; otherwise mark and return |
| Has many objects | Identify required end state before dragging or configuring |
Partial progress can matter. If a PBQ has five configurations and you are certain about three, complete the three, flag the question, and return later. Avoid random broad changes. PBQs are usually testing whether you can reach a requested state, not whether you can touch every field on the screen.
Multiple-Choice Flow
Use a three-pass method:
- First pass: answer questions you can solve with high confidence in under a minute.
- Second pass: return to flagged questions where one or two choices remain plausible.
- Final pass: check unanswered items, math questions, and PBQs with incomplete work.
Flagging is useful only if you are selective. If you flag half the exam, your final pass becomes noise. Flag questions where a second look may change the outcome: subnet math, close qualifiers, route-table comparisons, wireless design, and troubleshooting sequence questions.
Time Traps
| Trap | Better behavior |
|---|---|
| Recalculating the same subnet three times | Write a clean block-size line once and move on |
| Re-reading a confusing PBQ repeatedly | Flag it and harvest easier points |
| Changing confident answers without new evidence | Leave them unless you found a specific misread clue |
| Treating every acronym as a memorization question | Reconnect it to the scenario function |
| Overbuilding firewall or ACL answers | Match source, destination, direction, protocol, and port |
Scratch Notes to Build Before You Start
Use scratch space only for high-value items. A compact setup may include:
| Note | Why it helps |
|---|---|
| Domain weights: 23%, 20%, 19%, 14%, 24% | Keeps review balanced |
| CIDR anchors: /24, /25, /26, /27, /28, /29, /30 | Speeds subnet math |
| Troubleshooting flow | Prevents process-order mistakes |
| Personal weak ports | Keeps known misses visible |
| PBQ rule: task, scope, baseline, apply, verify | Creates a repeatable approach |
Do not spend several minutes writing every port number or acronym from memory. That burns time before you have seen what the exam is asking. Write only what you know you personally use under pressure.
PBQ Verification Checklist
Before leaving a PBQ, check:
- Did I satisfy the exact requested end state?
- Did I configure the correct source and destination?
- Did I choose the secure protocol when the prompt required security?
- Did I avoid exposing management services directly to untrusted networks?
- Did I use the correct VLAN, subnet, route, SSID, or policy object?
- Did I leave any required object unconfigured?
Final Review Rules
Use the last minutes carefully. First, make sure every question has an answer. Second, revisit PBQs with incomplete known work. Third, revisit flagged questions where a qualifier may have been misread. Fourth, avoid changing answers solely because they feel too simple. Simple is acceptable when the evidence is simple.
Exam-day success is not just knowledge. It is pacing, evidence discipline, and recovery from uncertainty. You do not need every question to feel comfortable. You need a process that keeps you moving and prevents one hard item from taking time away from many answerable ones.
You encounter a long PBQ at the start. After one careful read, you understand three required settings but are unsure about two. What is the best pacing choice?
Which flagged question is most worth revisiting during a final pass?
Put the exam flow in a practical order.
Arrange the items in the correct order