Exam-Day Time Management and PBQ Order
Key Takeaways
- The 90-minute limit demands active pacing; never let one PBQ consume the time needed for many easier points.
- Triage PBQs up front: complete familiar ones, capture partial work on long ones, and defer confusing ones.
- Answer multiple-choice with a one-pass, flag, and return strategy rather than perfecting items in order.
- Final review should prioritize flagged questions with real evidence gaps, not items already answered confidently.
- Build compact scratch notes: a 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, and because it mixes multiple-choice with performance-based questions (PBQs), time pressure is uneven. A simple multiple-choice item can take 20 seconds; a multi-step PBQ can take several minutes. Your pacing plan must protect the entire exam, not just the first hard task. PBQs typically appear near the start, which is exactly when an unprepared candidate sinks 12 minutes into one drag-and-drop and then races the clock through 60 answerable questions.
The 90-Minute Budget
Treat these as checkpoints, not rigid rules:
| Time remaining | Target status |
|---|---|
| 90 minutes | Read instructions, stay calm, begin PBQ triage |
| 80 minutes | PBQs completed, partially answered, or flagged |
| 55 minutes | Roughly one-third to one-half of multiple-choice done |
| 30 minutes | Most multiple-choice done; flagged list controlled |
| 15 minutes | Final pass on flagged PBQs and high-value uncertain items |
| 5 minutes | Submit only after confirming nothing is blank |
If you fall well behind a checkpoint, stop perfecting one item and move to the next answerable one. The exam rewards finishing far more than it rewards polishing a single hard PBQ.
PBQ Triage
Give every PBQ a quick triage decision on first read:
| PBQ type | Action |
|---|---|
| Familiar and mechanical | Complete now, verify, move on |
| Long but understandable | Complete the obvious parts, flag, return later |
| Confusing after one careful read | Flag and move on immediately |
| Requires calculation | Do the setup if quick; otherwise mark and return |
| Has many objects | Identify the required end state before dragging or configuring |
Partial progress can score. If a PBQ asks for five configurations and you are sure of three, set the three, flag the item, and return. Avoid random broad changes; a PBQ tests whether you can reach the requested end state, not whether you can touch every field on screen.
Multiple-Choice Flow
Use a three-pass method:
- First pass: answer every item you can solve confidently in under a minute.
- Second pass: return to flagged items where one or two choices remain plausible.
- Final pass: check unanswered items, math questions, and PBQs with incomplete work.
Flagging only helps if you are selective. Flag items where a second look could change the outcome: subnet math, close qualifiers, route-table comparisons, wireless design, and methodology-sequence questions. If you flag half the exam, the final pass becomes noise and the strategy collapses.
Time Traps
| Trap | Better behavior |
|---|---|
| Recalculating the same subnet three times | Write one clean block-size line and move on |
| Re-reading a confusing PBQ repeatedly | Flag it and harvest easier points |
| Changing confident answers with no new evidence | Leave them unless you found a specific misread |
| Treating every acronym as pure recall | Reconnect it to its scenario function |
| Overbuilding a firewall or ACL answer | Match source, destination, direction, protocol, port |
Scratch Notes to Build Before You Start
Use the provided scratch space for high-value items only:
| Note | Why it helps |
|---|---|
| Domain weights 23 / 20 / 19 / 14 / 24 | Keeps a sense of where points cluster |
| CIDR anchors /24 /25 /26 /27 /28 /29 /30 with block sizes 256/128/64/32/16/8/4 | Speeds subnet math |
| Seven-step troubleshooting flow | Prevents process-order errors |
| Personal weak ports | Keeps known misses visible |
| PBQ rule: task, scope, baseline, apply, verify | A repeatable approach |
Do not spend several minutes dumping every port number from memory before you have seen a single question. Write only the handful of items you personally fumble under pressure; the rest you will recall in context.
PBQ Verification Checklist
Before you leave any PBQ, confirm:
- 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
Spend the last minutes deliberately. First, make sure every question has an answer; an unanswered item is a guaranteed zero, while a guess on a four-option item is roughly 25%. Second, revisit PBQs with incomplete known work. Third, revisit flagged items where a qualifier such as "first" or "least disruptive" may have been misread. Fourth, resist changing answers only because they feel too simple; simple is fine when the evidence is simple.
Exam-day success is pacing, evidence discipline, and recovery from uncertainty as much as it is knowledge. You do not need every question to feel comfortable. You need a process that keeps you moving and prevents one hard PBQ from stealing time from many answerable items.
You hit a long PBQ at the start. After one careful read you know three required settings but are unsure of two. What is the best pacing choice?
Which flagged question is most worth revisiting during the final pass?
Put the exam-day flow in a practical order.
Arrange the items in the correct order