Official Domain Weights and an 8-12 Week Study Plan
Key Takeaways
- N10-009 has five domains: Networking Concepts, Network Implementation, Network Operations, Network Security, and Network Troubleshooting.
- Network Troubleshooting is the largest domain at 24%, followed closely by Networking Concepts at 23%; together they are nearly half the exam.
- An 8-week plan suits candidates with regular hands-on exposure; a 12-week plan adds time for subnetting and command-output fluency.
- Allocate study time by both official weight and personal weakness, especially subnetting, VLAN trunking, routing, and troubleshooting order.
- The final third of study should emphasize mixed scenarios, PBQ-style practice, and timed review under the 90-minute clock.
Official N10-009 Domain Weighting
| Domain | Name | Exam weight |
|---|---|---|
| 1.0 | Networking Concepts | 23% |
| 2.0 | Network Implementation | 20% |
| 3.0 | Network Operations | 19% |
| 4.0 | Network Security | 14% |
| 5.0 | Network Troubleshooting | 24% |
Troubleshooting (5.0) is the single largest domain, but it depends on everything before it: you cannot diagnose VLANs, DHCP, routing, DNS, wireless, or cabling if those foundations are weak. Notice that Concepts (1.0) and Troubleshooting (5.0) together total 47% of the exam, so OSI/TCP-IP reasoning and methodical fault isolation are the highest-leverage skills.
Key content moved or added in N10-009 versus the retired N10-008 includes expanded software-defined networking (SDN), SD-WAN, infrastructure as code (IaC), zero trust and SASE concepts, and clearer cloud-networking coverage, while some legacy hardware detail was trimmed. Study from the current objectives so you do not over-invest in retired material.
When you skim the five domains, recognize that they are not independent silos but a stack of dependencies. Domain 1 defines the vocabulary (OSI model, encapsulation, IPv4/IPv6, ports, traffic types). Domain 2 puts that vocabulary into a topology (cabling, devices, VLANs, routing, cloud and WAN connectivity). Domain 3 keeps that topology healthy (monitoring, baselines, documentation, change control). Domain 4 protects it (segmentation, hardening, AAA, secure protocols). Domain 5 repairs it. A weakness in Domain 1 silently caps your score in every later domain, which is why the plans below front-load fundamentals.
8-Week Study Plan
Use this pace if you already work around switches, routers, wireless, cloud networks, or service-desk escalation.
| Week | Primary focus | Output |
|---|---|---|
| 1 | OSI/TCP-IP model, IPv4/IPv6 addresses, ports, traffic types | Layer-and-protocol decision table |
| 2 | Subnetting, routing, switching, wireless basics | Daily subnetting drills and topology labels |
| 3 | Network devices, cabling, transceivers, physical design | Media-selection and appliance-placement drills |
| 4 | VLANs, inter-VLAN routing, NAT, VPNs, cloud and data-center concepts | Diagram three segmented networks |
| 5 | Operations: monitoring, documentation, change/configuration management | Interpret logs, baselines, and diagrams |
| 6 | Security: segmentation, hardening, AAA, secure protocols, zero trust | Replace insecure designs with safer alternatives |
| 7 | Troubleshooting methodology, tools, command output, common failures | Fault-isolation scenarios by OSI layer |
| 8 | Mixed PBQ-style practice, timed sets, missed-question repair | Two timed mixed reviews and a final readiness sheet |
12-Week Study Plan
Use this pace if networking is new or if subnetting and command output still feel slow.
| Weeks | Focus | What to practice slowly |
|---|---|---|
| 1-2 | Domain 1 foundations | OSI layers, TCP/IP, IPv4, IPv6, ports, traffic types |
| 3-4 | Switching, routing, wireless, addressing | VLANs, trunking, subnet math, route selection |
| 5-6 | Domain 2 implementation | Cables, optics, appliances, cloud networking, site connectivity |
| 7-8 | Domain 3 operations | Diagrams, monitoring, configuration management, backups, policies |
| 9 | Domain 4 security | AAA, secure protocols, segmentation, device hardening |
| 10 | Domain 5 troubleshooting | Tools, symptoms, root cause, command output |
| 11 | Mixed scenarios and PBQ workflow | Drag/drop mapping, configuration interpretation, topology repair |
| 12 | Timed readiness | Pacing, final weak areas, calm review of high-yield tables |
Time Allocation Example
If you have 72 total study hours, seed the split from the official weights, then adjust after a diagnostic set. Because PBQs are heavy and live mostly in implementation and troubleshooting, lean slightly toward hands-on practice there.
| Domain | Weight | Approximate hours |
|---|---|---|
| Networking Concepts | 23% | 17 |
| Network Implementation | 20% | 14 |
| Network Operations | 19% | 14 |
| Network Security | 14% | 10 |
| Network Troubleshooting | 24% | 17 |
| Total | 100% | 72 |
Pacing Math You Should Internalize
With up to 90 questions in 90 minutes, your average budget is about one minute per item. Multiple-choice recall should take 20-40 seconds; bank that saved time for PBQs, which can each consume 3-5 minutes. A safe plan: clear straightforward items first, flag anything slow, and return to PBQs with the time you saved. Never leave an item blank, because there is no penalty for a wrong guess on a scaled exam.
Scenario: Adjust the Plan by Evidence
A candidate scores well on port memorization but misses subnetting, VLAN trunking, and "what changed" troubleshooting questions.
| Weakness | Better adjustment |
|---|---|
| Subnetting is slow | Do 10 short subnet prompts daily until the process is automatic |
| VLAN questions are missed | Draw access ports, trunks, native VLANs, and inter-VLAN routing paths |
| Troubleshooting feels vague | Write symptom, affected scope, likely layer, and confirming tool before choosing |
| PBQs feel rushed | Read the instructions first, then label known-good facts before moving items |
Domain weights tell you where attention belongs in general; your missed-question evidence tells you where your next hour belongs specifically.
Take a short diagnostic before week one and again at the midpoint. A 40-50 question mixed set, scored by domain, exposes whether your real gaps match the official weights. If you already score above 80% on Concepts but below 50% on Troubleshooting, do not spread hours evenly; pour them into fault-isolation drills and command output. Conversely, if subnetting alone is dragging three different domains down (it appears in Concepts, Implementation, and Troubleshooting), fixing that one skill lifts your whole score.
Treat the diagnostic as the steering wheel and the weights as the map: the map shows the terrain, but the wheel responds to where you actually are.
Which N10-009 domain has the highest official exam weight?
Match each N10-009 domain to its official weight.
Match each item on the left with the correct item on the right
A candidate has 12 weeks and struggles with subnetting and VLAN concepts. Which plan is most appropriate?