CompTIA Network+ is a vendor-neutral networking certification, which is its defining feature: the concepts apply to equipment from any manufacturer, so what you learn transfers across Cisco, Juniper, Aruba, or anything else, rather than teaching one vendor’s commands. It is the common bridge between an entry IT certification and either a Cisco-specific networking path (CCNA) or a security path (Security+). This guide is a full, self-study course. It works through each of the five domains in depth, teaches the foundations the exam actually tests, the OSI model, subnetting, ports and protocols, routing and switching, operations, security, and a structured troubleshooting method, and then turns all of it into a study plan and a final-preparation routine. It is original teaching material and study guidance only. It contains no exam questions of any kind, and you should always confirm the current objectives against CompTIA’s own certification page before you book, because the objectives change between versions.
Chapter 1: Exam overview and how to use this guide
What Network+ measures, and the current version
Network+ validates that you can design, configure, manage, and troubleshoot wired and wireless networks at a foundational level, regardless of vendor. The current version is N10-009, which replaced N10-008 and refreshed the coverage of modern network architectures, cloud, and security. Studying the right version matters, so confirm you are on N10-009. The exam is organised into five domains, and unlike some certifications, CompTIA does publish approximate weightings, which tell you exactly where to spend your hours: Networking Concepts (about 23%), Network Implementation (about 20%), Network Operations (about 19%), Network Security (about 14%), and Network Troubleshooting (about 24%). Read those numbers carefully, because they carry a clear message: Troubleshooting and Networking Concepts are the two heaviest domains, together roughly half the exam, so they deserve the most attention.
Format and scoring
The format is a maximum of 90 questions in 90 minutes, mixing multiple-choice questions with performance-based questions (PBQs), which present a task or a simulated environment and ask you to do something rather than pick an answer. The PBQs matter out of proportion to their number because they can be time-consuming, so pacing is a real skill. The exam is scored on a scale of 100 to 900, with 720 required to pass, and it is delivered at a Pearson VUE test centre or online through OnVUE. CompTIA does not publish a cohort pass rate; what is published is the scaled score and a pass/fail result. The credential is valid for three years and is renewed through CompTIA’s continuing-education programme (notably, passing Security+ also renews it).
How to use this course
Read the chapters in order at least once, because the foundations build on each other: the OSI model in Chapter 2 is the framework you will use to reason about implementation in Chapter 3 and troubleshooting in Chapter 6, and subnetting underpins much of the exam. Two skills deserve daily, little-and-often practice from the start rather than cramming at the end: subnetting and the troubleshooting methodology. Wherever a concept is easy to misread, a short worked illustration makes it concrete, but none of these are exam questions; they are teaching examples. Because the exam includes hands-on PBQs, supplement reading with practice in a network simulator or a small home lab. The final chapters convert the content into a schedule, a final-preparation routine, and a description of exam day.
Chapter 2: Networking Concepts (about 23%)
This is the foundation domain and one of the two heaviest. Everything else, implementation, operations, security, troubleshooting, rests on the models, addressing, and protocols introduced here, so build it solidly before moving on.
The OSI model
The OSI model is a seven-layer framework for reasoning about how networks communicate, and it is the single most useful mental tool on the exam, because it lets you place any protocol, device, or problem at the right layer. From the top down, the layers are Application (7), Presentation (6), Session (5), Transport (4), Network (3), Data Link (2), and Physical (1). A common memory aid for layers 7 to 1 is “All People Seem To Need Data Processing.” What matters is not reciting them but knowing what each does and what lives there: Layer 1 is cables, signals, and physical connections; Layer 2 is frames and MAC addresses, where switches operate; Layer 3 is packets and IP addresses, where routers operate; Layer 4 is end-to-end transport, where TCP and UDP and port numbers live. The TCP/IP model is a more compact, four-layer view of the same reality, and you should be able to relate the two. As a teaching example of why the model earns its keep: if a user cannot reach a website, asking “which layer is failing?”, cable unplugged (Layer 1), no IP address (Layer 3), or a blocked port (Layer 4), turns a vague problem into a structured search, which is exactly what the troubleshooting domain rewards.
TCP versus UDP, and common ports
At the transport layer, the exam expects you to distinguish TCP from UDP. TCP is connection-oriented and reliable: it establishes a connection (the three-way handshake), guarantees delivery and ordering, and is used where correctness matters (web, email, file transfer). UDP is connectionless and best-effort: it has less overhead and no delivery guarantee, and is used where speed matters more than perfect delivery (live video and voice, DNS lookups). On top of that sits port and protocol knowledge, a reliable source of marks. You should know the common ports cold: FTP (20/21), SSH and SFTP (22), Telnet (23), SMTP (25), DNS (53), DHCP (67/68), HTTP (80), HTTPS (443), NTP (123), SNMP (161/162), and RDP (3389), among others. The way to learn them is short, frequent flashcard reviews, grouping protocols by function (web, email, file transfer, remote access, naming, management) so they stick as a set rather than a random list.
Addressing, network types, and topologies
You also need the shape of networks. Know IPv4 addressing (including the private ranges and the idea of public versus private addresses) and the basics of IPv6, which exists largely because IPv4 addresses ran out and which uses much larger, hexadecimal addresses. Understand network types by scale, a LAN (local), a WAN (wide-area, spanning distance), and related terms, and topologies, the arrangement of a network, such as star (every device to a central switch, the common modern layout), mesh (many interconnections for resilience), and others. Cloud networking concepts appear here too in N10-009, reflecting how much infrastructure now lives in providers like AWS, Azure, and Google Cloud. The point is to recognise the trade-offs: a star is simple but depends on its centre; a mesh is resilient but expensive in connections.
Chapter 3: IP addressing and subnetting in depth
Subnetting deserves its own chapter because it is the single highest-return skill on Network+: it recurs across the exam and appears in the time-consuming performance-based questions. The goal is mechanical speed, the ability to move from a prefix to a mask, host count, and address ranges without hesitation.
Why subnetting exists
Subnetting divides one IP network into smaller logical networks (subnets). Organisations do this to use address space efficiently, to separate groups of devices for performance and security, and to control broadcast traffic. The key tool is the subnet mask, which marks where the network portion of an address ends and the host portion begins. Modern notation uses CIDR, a slash and a number (for example, /24) saying how many bits are the network portion. The exam expects you to translate fluently among the prefix, the dotted-decimal mask, and what they imply.
The mechanics you must automate
The relationships to internalise are these. A /24 is a mask of 255.255.255.0 and provides 254 usable hosts (256 addresses, minus the network and broadcast addresses, which cannot be assigned to devices). Each additional network bit halves the hosts: a /25 gives 126 usable, a /26 (mask 255.255.255.192) gives 62, a /27 (mask 255.255.255.224) gives 30, and a /30 (mask 255.255.255.252) gives just 2, the size used for point-to-point links between two routers. The two reserved addresses in every subnet, the first (network address) and the last (broadcast address), are why the usable count is always two fewer than the total. As a teaching example of reading a requirement: if a segment must hold 50 devices, a /26 (62 usable) fits and a /27 (30 usable) does not, so you would choose the /26, and being able to see that instantly is what the PBQs demand. Practise a handful of these every day until the arithmetic is automatic, because on the exam slow subnetting steals time you need for everything else.
Chapter 4: Network Implementation (about 20%)
This domain is about building the network: how traffic is forwarded by switches and routers, how wireless works, and the physical cabling and infrastructure underneath. Focus on how the pieces connect and why.
Switching
A switch operates at Layer 2 and forwards frames within a local network using MAC addresses, learning which device is on which port so it can send frames only where they need to go. The implementation concepts to know are VLANs, which logically segment one physical switch into separate networks (so, for example, finance and guest traffic stay apart even on shared hardware), and trunking, which carries multiple VLANs over a single link between switches. You should also recognise Power over Ethernet (PoE), delivering power and data over one cable to devices like access points and phones, and at a high level spanning tree, which prevents loops in a switched network. The instinct to build is that switching is local, frame-based, and about getting traffic efficiently around a single network segment.
Routing
A router operates at Layer 3 and forwards packets between different networks using IP addresses, consulting a routing table to decide the next hop. Know the distinction between a default gateway (the router a device uses to reach anything outside its own subnet) and routes to specific networks. Understand the difference between static routing (routes configured by hand, simple but not adaptive) and dynamic routing (routes learned automatically through protocols, which adapt as the network changes), and recognise common routing-protocol names at a conceptual level. NAT (Network Address Translation) belongs here too: it translates private addresses to public ones so many internal devices can share public address space, which is part of why IPv4 has lasted. The instinct to build is that routing is about moving traffic between networks, in contrast to switching within one.
Wireless and cabling
On wireless, know the Wi-Fi generations and standards (the 802.11 family, including newer ones such as 802.11ax), the difference between the 2.4 GHz and 5 GHz bands (range versus speed and congestion), and basic concepts like SSIDs and channels. On cabling and physical infrastructure, know the common media, twisted-pair copper (the Ethernet categories, with higher categories supporting higher speeds) and fibre (which carries data as light over longer distances and at higher speeds), along with the idea that every cable type has distance and speed limits. The exam connects these to troubleshooting, so understand that the wrong or damaged cable, or interference on a wireless channel, produces specific, recognisable symptoms.
Chapter 5: Network Operations and Network Security
This chapter covers two domains: Network Operations (about 19%), keeping networks running and documented, and Network Security (about 14%), protecting them. They are grouped because in practice they are two halves of running a network responsibly.
Network Operations
Operations is about the disciplines that keep a network healthy and recoverable. Monitoring means watching the network’s health and performance, often with SNMP (a protocol for collecting status from devices), logs, and tools that alert you when something is wrong, so problems surface before users report them. Documentation is a recurring theme: network diagrams, IP address schemes, and baselines that let you understand and troubleshoot the network, and the exam treats good documentation as part of doing the job, not an afterthought. Availability and disaster recovery introduce metrics that turn business needs into design: RTO (Recovery Time Objective), the maximum acceptable time to restore service after an outage, and RPO (Recovery Point Objective), the maximum acceptable data loss. High availability is achieved through redundancy, removing single points of failure with backup links, devices, or power. As a teaching example: a business that says it can tolerate almost no downtime is describing a tight RTO, which justifies redundant hardware and links rather than a single device whose failure takes everything down.
Network Security
Security is the smallest domain by weight but it is foundational, and it pairs naturally with Security+ next. The exam expects awareness of common attacks, including denial-of-service (DoS/DDoS), which overwhelms a service with traffic; on-path attacks (an attacker positioned between two parties to intercept traffic); spoofing; and social-engineering techniques like phishing. Against these you should know hardening and defensive measures: firewalls (which filter traffic by rules), network segmentation (using VLANs and subnets to limit how far an attacker can move), securing wireless with strong encryption, disabling unused ports and services, and changing default credentials. Secure remote access matters too, especially VPNs, which create an encrypted tunnel so remote users reach the network safely over the internet. The principle threading through the domain is defence in depth: layered controls so that no single failure exposes everything, and least access so devices and users can reach only what they need.
Chapter 6: Network Troubleshooting (about 24%)
Troubleshooting is the heaviest domain on the exam, and CompTIA tests its structured methodology directly, so learn the steps in order and be able to apply them. This is also where the OSI model and the tools come together.
CompTIA’s troubleshooting methodology
CompTIA teaches a seven-step method, and the exam expects you to know it in sequence: first identify the problem (gather information, ask what changed, reproduce if possible); then establish a theory of probable cause (a reasonable hypothesis, often working up or down the OSI layers); then test the theory to confirm or reject it; then establish a plan of action to resolve the issue; then implement the solution (or escalate if it is beyond your scope); then verify full system functionality and, where appropriate, put preventive measures in place; and finally document the findings, actions, and outcomes. The order is the point: you do not jump to a fix before you understand the cause, and you do not skip verification or documentation. A useful habit the exam rewards is using the OSI model to structure your theory, checking whether the problem is physical, a Layer 2 switching issue, a Layer 3 addressing or routing issue, or higher up, so your hypothesis is methodical rather than a guess.
Tools and commands
Troubleshooting also means knowing the tools and commands that gather evidence. Command-line utilities are central: ping tests basic reachability between hosts; traceroute/tracert shows the path packets take and where they stop; ipconfig/ifconfig shows a device’s IP configuration; nslookup/dig queries DNS to check name resolution. Recognise hardware tools too, a cable tester checks whether a cable is wired correctly and intact, and other tools help locate and diagnose physical issues. The exam often describes a symptom and expects you to choose the right tool or interpret its output, so understand what each tool reveals. As a teaching example of the reasoning: if a site loads by IP address but not by name, the evidence points to DNS, so the tool to reach for is one that queries name resolution, not a cable tester.
Chapter 7: Study plan and timeline
With the content understood, the work is pacing it so the two heaviest domains and the daily skills get the attention the weightings demand. Three things drive the plan: confirming the version, drilling subnetting and the troubleshooting steps little-and-often, and practising the hands-on tasks rather than only reading.
Confirm the version, then build foundations first
Start by confirming you are studying N10-009 and reading the current objectives, since they change between versions. Then build in the order the domains build on each other: foundations (OSI, addressing, ports, subnetting) first, because implementation, operations, security, and troubleshooting all assume them. Pair the official objectives with free video training and hands-on practice in a simulator or small home lab, because the exam’s performance-based questions reward having actually configured and diagnosed things, not just read about them.
An eight-week default, and how to flex it
A realistic plan runs about eight weeks at six to eight hours a week. Week one covers the OSI and TCP/IP models, topologies, and addressing. Week two concentrates on subnetting and ports/protocols, the two recall- and skill-heavy foundations. Week three covers routing and switching; week four covers wireless and cabling. Week five covers network operations and availability; week six covers network security. Week seven is troubleshooting methodology and tools, drilled until the seven steps are automatic. Week eight is full-length timed reviews including the PBQs, watching your pacing. If you have an IT background, compress to a four-week intensive at around twelve hours a week, two domains a week, weighted toward addressing, routing/switching, and troubleshooting. If you are new to networking, stretch to twelve weeks at around four hours, taking extra time on the fundamentals before security and troubleshooting. Throughout, keep subnetting as a daily habit rather than a single block. To turn whichever timeline you choose into dated weeks for your own start date, use the free study-plan generator.
Where the weightings tell you to spend time
Use the published weightings as your guide. Troubleshooting (about 24%) and Networking Concepts (about 23%) are the two heaviest domains, so give them the most hours, and within them prioritise the troubleshooting methodology and subnetting, both of which also surface in the performance-based questions. Network Security (about 14%) is the lightest, but do not skip it, it is foundational and pairs into Security+ if that is your next step. If you are still choosing your path, the honest framing is that Network+ is vendor-neutral groundwork: if you are set on a Cisco-centric networking career, many people go straight to CCNA, which carries more weight with networking employers; if you are aiming at security, Security+ may be the better single investment. Worth it as a foundation, less so as a destination.
Chapter 8: Final preparation, exam day, and format
Final preparation
In the closing weeks, switch from learning to full-length, timed practice tests with the performance-based tasks included, and watch your pacing, because the PBQs can eat the clock. Read each practice result as a map of weak domains and shore them up, making sure subnetting and CompTIA’s troubleshooting methodology are both solid, since the exam tests the methodology directly and subnetting appears throughout. Aim to clear the 720 pass mark comfortably on fresh questions before you book. Steer clear of sites that leak or sell stolen test content; they breach CompTIA’s certification policy and copyright, and they do nothing to build the subnetting fluency and structured troubleshooting the exam actually measures.
Renewal and what comes next
The certification is valid for three years, renewed through CompTIA’s continuing-education programme, by earning continuing-education units, taking CertMaster CE, or earning a higher CompTIA certification, plus the renewal fee. Conveniently, passing Security+ also renews Network+, which is one reason the Network+ then Security+ path is so common. After Network+, the natural next steps are Security+ for a security focus or CCNA for a deeper, Cisco-specific networking credential, depending on where you want your career to go.
Exam day and format
On the day, expect a maximum of 90 questions in 90 minutes, including performance-based questions, at a Pearson VUE centre or online through OnVUE, so prepare your environment and identification in advance. Manage the clock deliberately: the PBQs take longer, so a sensible tactic is to give a hard one your best effort, flag it, and return after clearing the quicker multiple-choice questions, rather than letting one task drain your time. Apply the habits you built, use the OSI model to structure your thinking, subnet quickly and confidently, recall ports and protocols by function, and follow the troubleshooting steps in order. Having drilled subnetting daily and practised the PBQs under time, the exam will feel like work you have already done, which is exactly the advantage the weeks of practice were meant to build.