Network+ Domains Explained: What All 25 N10-009 Objectives Test

There are five Network+ domains on the N10-009 exam: Networking Concepts (23%), Network Implementation (20%), Network Operations (19%), Network Security (14%) and Network Troubleshooting (24%). Between them they hold 25 numbered objectives, from 1.1 to 5.5, and those objectives are the whole syllabus. If a topic is not on CompTIA's objectives document, it is not on the exam.

The weights tell you roughly how many questions each domain contributes. They do not tell you how much reading each domain needs, and that gap is where most study plans go wrong. Below is each domain in plain English: what its objectives actually ask of you, where candidates over- or under-study, and how the five domains feed into each other. Format, scoring and cost live in what the Network+ certification is; this post sticks to the syllabus.

The Network+ domains at a glance

Everything in this table comes from CompTIA's N10-009 exam objectives, Document Version 6.0.

The last column matters more than it looks. Every objective starts with a verb. Fifteen of them say Explain, Compare and contrast, or Summarize, which means you need to know what a thing is and how it differs from its neighbors. The other ten start with "Given a scenario," which means you will be handed a situation and asked to configure, choose or fix something. CompTIA does not say which objectives produce the performance-based questions, so treat that column as a measure of how applied the domain is, not a PBQ map.

One more reading of the table. Domain 1 spreads 23% over eight objectives, under 3% each on a simple average, while Domain 2 puts 20% on four, about 5% each. CompTIA does not weight individual objectives, so that is arithmetic, not policy, but the short domains are dense.

Domain 1.0: Networking Concepts (23%)

This is the vocabulary domain. Its eight objectives run from the OSI model (1.1) through networking appliances and functions (1.2), cloud concepts and connectivity (1.3), ports, protocols and traffic types (1.4), transmission media and transceivers (1.5), topologies and architectures (1.6), IPv4 addressing (1.7) and "evolving use cases for modern network environments" (1.8).

What it tests in practice is recognition and fit. A question describes a need, such as filtering what internal users can browse or terminating TLS in front of several web servers, and you pick the appliance that does that job. Cloud questions want service models (SaaS, IaaS, PaaS) kept separate from deployment models (public, private, hybrid).

Where people over-study: the OSI model itself. You need the seven layers, what lives at each, and the ability to place a symptom on a layer. You do not need a week of it.

Where people under-study: two objectives. Objective 1.4 is a fixed table of 20 protocols and their ports, and it rewards plain memorization. Watch the secure pairs, because the objectives list SMTPS on 587, not the 465 many older references show. Objective 1.8 is the newer material: SDN and SD-WAN, VXLAN, zero trust, SASE and SSE, infrastructure as code with source control, and IPv6 transition methods such as dual stack, tunneling and NAT64. Candidates who learned networking a few years ago tend to skip 1.8 because it feels like buzzwords. It is a full objective.

Objective 1.7 is the domain's only scenario objective, and it is subnetting: public versus private ranges, APIPA, loopback, classes, CIDR and VLSM. Subnetting shows up again in Domains 3 and 5, so learn it here properly.

Domain 2.0: Network Implementation (20%)

Four objectives, and each one is a real chunk of work. Objective 2.1 covers routing: static versus dynamic, the three named protocols (BGP, EIGRP, OSPF), route selection, NAT and PAT, FHRP and virtual IPs, and subinterfaces. Objective 2.2 is switching: VLANs, the VLAN database, SVIs, native and voice VLANs, 802.1Q tagging, link aggregation, speed and duplex, spanning tree, and MTU with jumbo frames. Objective 2.3 is wireless: channels and channel width, the 2.4, 5 and 6GHz bands, band steering, SSID types, antennas, autonomous versus lightweight APs, WPA2 and WPA3, PSK versus Enterprise, and guest networks with captive portals. Objective 2.4 is physical installation: MDF and IDF, racks, airflow, patch and fiber panels, UPS and PDU, power load, and environmental factors.

The two scenario objectives, 2.2 and 2.3, ask you to configure, not define.

The concept people get backward is route selection. Administrative distance decides between route sources, prefix length decides which route is most specific, and metric only ranks routes within one protocol. Know the order in which those apply and a whole family of questions gets easy.

Under-studied: 2.4. It reads like facilities trivia, so candidates skim it, and then lose easy points on rack units, hot and cold aisles, or how power load decides the size of a UPS. Over-studied: routing protocol internals. The objectives name BGP, EIGRP and OSPF; they do not ask you to configure them line by line.

Domain 3.0: Network Operations (19%)

The name sounds soft, so this domain gets shortchanged. It is nearly a fifth of the exam.

Objective 3.1 is organizational process: diagrams and documentation, asset inventory, IPAM, SLAs, life-cycle terms like end-of-life, change management, and baseline or golden configurations. Objective 3.2 is monitoring: SNMP (traps, MIBs, v2c versus v3, community strings), flow data, packet capture, baselines and anomaly alerting, log aggregation with syslog and SIEM, API integration and port mirroring. Objective 3.3 is disaster recovery: RPO, RTO, MTTR, MTBF, cold, warm and hot sites, active-active versus active-passive, and testing. Objective 3.4 is network services: DHCP (scopes, leases, reservations, relay), SLAAC, DNS with its record types, zones and DNSSEC, DoH and DoT, and time protocols NTP, PTP and NTS. Objective 3.5 is access and management: VPN types, split versus full tunnel, connection methods, jump boxes, and in-band versus out-of-band management.

Two scenario objectives live here, 3.2 and 3.4, and 3.4 is the one to respect. DHCP and DNS are the services most likely to break in a troubleshooting question later, so the configuration knowledge you build here pays twice.

The classic trap is RPO versus RTO. RPO is how much data you can afford to lose, measured backward in time. RTO is how long you can afford to be down. Questions swap them on purpose. The other habit worth forming: when a scenario says the production link is down and you still need to reach the device, the answer is out-of-band management.

Domain 4.0: Network Security (14%)

The smallest domain, with three objectives. Objective 4.1 covers basic concepts: encryption in transit and at rest, certificates and PKI, identity and access management (MFA, SSO, RADIUS, LDAP, SAML, TACACS+, least privilege, role-based access), physical security, deception technologies such as honeypots, the CIA triad and risk vocabulary, compliance (data locality, PCI DSS, GDPR), and segmentation for IoT, industrial systems, guest and BYOD networks. Objective 4.2 is attacks: DoS and DDoS, VLAN hopping, MAC flooding, ARP and DNS poisoning and spoofing, rogue DHCP servers and APs, evil twin, on-path attacks, social engineering and malware. Objective 4.3 is defenses: device hardening, NAC with port security, 802.1X and MAC filtering, key management, ACLs, URL and content filtering, and zones including the screened subnet.

The risk here is over-study. Candidates who plan to take Security+ next sometimes treat this domain as a head start and go deep on cryptography or threat frameworks. Network+ wants the network view: which layer an attack works at, what it does to the network, and which switch, firewall or access control stops it. ARP poisoning is a Layer 2 attack on hosts in one subnet; DNS poisoning hits a resolver's cache. Know that kind of distinction cold and move on.

The one scenario objective, 4.3, is where ACL logic appears. Rules are read top-down, first match wins, and an implicit deny sits at the end. Put a broad rule above a narrow one and the narrow one never fires.

Domain 5.0: Network Troubleshooting (24%)

The largest domain, and four of its five objectives are scenario objectives. Objective 5.1 is CompTIA's troubleshooting methodology, a fixed sequence from identifying the problem through establishing and testing a theory, planning and implementing the fix, verifying full functionality, and documenting. Objective 5.2 covers cabling and physical interfaces: wrong cable types, crosstalk, interference and attenuation, improper termination, TX/RX transposed, interface counters (CRC errors, runts, giants, drops), port status, PoE power budgets and transceiver mismatch. Objective 5.3 covers network services: spanning tree problems, wrong VLAN assignment, ACLs, routing tables and default routes, address pool exhaustion, and wrong gateways, IPs and subnet masks. Objective 5.4 covers performance: congestion, latency, packet loss, jitter, and wireless coverage and roaming problems. Objective 5.5 is tools: protocol analyzers, command-line utilities (ping, traceroute, nslookup, dig, tcpdump, netstat, arp, ip/ifconfig/ipconfig), Nmap, LLDP/CDP, speed testers, hardware tools, and a set of basic device show commands.

Objective 5.1 is the only part of this domain you can learn by rote, and you should: the seven steps, in CompTIA's wording and order. How hard the Network+ exam is works a methodology question through. The other four objectives cannot be memorized, because they are built from everything above.

How do the Network+ domains connect to each other?

Domain 5 is mostly Domains 1 through 4 asked a second time, with a broken network attached. Follow one thread through the outline and you can see it.

DHCP is configured in 3.4. A rogue DHCP server is an attack in 4.2. Address pool exhaustion is a fault in 5.3. And a client that gives up on DHCP assigns itself an APIPA address, which is an addressing fact from 1.7. One protocol, four objectives, three domains.

VLANs work the same way. You configure native VLANs and 802.1Q tagging in 2.2, meet VLAN hopping in 4.2, and troubleshoot incorrect VLAN assignment in 5.3. Spanning tree is configured in 2.2 and debugged in 5.3. SNMP has its ports in 1.4, its versions and traps in 3.2, and its security argument (v3 is the version with authentication and encryption) bridges into Domain 4.

That has a practical consequence. Troubleshooting carries 24% on paper, but the knowledge it draws on is spread across the other 76%. A candidate who skims Domain 2 to save time is also quietly giving up points in Domain 5. The reverse holds too: troubleshooting drills expose which earlier objective you never really learned.

Reading time versus practice time, by domain

Follow the weights for question practice and density for reading:

• Give Domain 1 its reading time, but split it: memorize 1.4, practice 1.7 until it is fast, and do not skip 1.8.
• Treat Domains 2 and 3 as configuration domains. Read them with the troubleshooting objectives in mind.
• Keep Domain 4 to its weight. Precision beats depth here.
• Do Domain 5 last as a reading topic and first as a practice topic, because its questions expose gaps everywhere else.

For a week-by-week version of this, see the Network+ study plan. To watch a scenario question pull from two domains at once, the Network+ practice questions walkthrough works through several.

If you want the outline turned into reading, our CompTIA Network+ N10-009 Study Guide 2026 gives each objective its own chapter, numbered 1.1 to 5.5, so the contents page doubles as a checklist of the syllabus.

FAQ

How many domains and objectives are on the Network+ N10-009 exam?

Five domains and 25 objectives. Domain 1 has eight objectives, Domains 3 and 5 have five each, Domain 2 has four and Domain 4 has three. The weights are 23%, 20%, 19%, 14% and 24%.

Which Network+ domain is the largest?

Network Troubleshooting, at 24%, with Networking Concepts close behind at 23%. Together they are nearly half the exam. Troubleshooting also has four of the ten "Given a scenario" objectives, so it is the most applied domain as well as the largest.

Are the "Given a scenario" objectives the performance-based questions?

Not necessarily. CompTIA says the exam is a mix of multiple-choice and performance-based questions, but it does not say which objectives the performance-based items come from. The ten scenario objectives are the ones that ask you to apply knowledge rather than recall it, so they are sensible places to practice hands-on tasks.

Is the Network Security domain enough preparation for a security exam?

No. Domain 4 is 14% of Network+ and covers security from a network administrator's angle: attacks on switches and protocols, access control, segmentation and basic concepts. It overlaps with security certifications but is much narrower.

Can I skip objective 1.8?

No. Objective 1.8, "evolving use cases for modern network environments," carries the same standing as subnetting or routing. It covers SDN and SD-WAN, VXLAN, zero trust, SASE and SSE, infrastructure as code, and IPv6 transition methods, so give it real reading time.

Want every objective explained in plain English? CompTIA Network+ N10-009 Study Guide 2026 gives each of the 25 objectives its own chapter, with worked drills for the ten scenario objectives and 164 original practice questions across five domain banks, every answer explained.

Simply Certified is an independent publisher. Network+, Security+ and CompTIA are trademarks of CompTIA, Inc. Our books are independent study material and are not affiliated with, endorsed by, or sponsored by CompTIA.