Study guide

OSI and TCP/IP Models with Device and Protocol Mapping

CompTIA Network+ N10-009

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

Current Exam Facts and Applied Networking Judgment Official Domain Weights and an 8-12 Week Study Plan How to Use Labs, Practice, and PBQ Workflow Missed-Question Notebook and Final Readiness Metrics

2 Domain 1: Networking Concepts (23%)

OSI and TCP/IP Models with Device and Protocol Mapping Networking Appliances and Where They Operate Ports and Protocol Decision Table Traffic Types and Encapsulation Flow

3 Domain 1: Media, Connectors, Transceivers, and Network Architectures

Copper, Fiber, Coax, and DAC Media Connector and Transceiver Selection Network Topologies and Design Patterns Cloud and Virtual Networking Concepts

4 Domain 1: IP Addressing and Subnetting Mastery

IPv4 Classes, Private/Public, APIPA, and Loopback CIDR, VLSM, and Subnet Math IPv6 Address Types and Notation Routing Basics and Longest Prefix Match

5 Domain 2: Network Implementation - Routing

Static vs Dynamic Routing and Route Selection OSPF, EIGRP, and BGP Basics at Network+ Depth NAT/PAT, VIP/FHRP, and Subinterfaces Routing PBQs and Troubleshooting Route Table Clues

6 Domain 2: Network Implementation - Switching

VLANs, Access Ports, Trunks, and Native VLAN STP/RSTP Loop Prevention and Bridge Roles Port Aggregation/LACP, MTU, Jumbo Frames, and Interface Settings Switch Implementation PBQs and Common Misconfigurations

7 Domain 2: Network Implementation - Wireless and Physical Implementation

Wi-Fi Standards, Bands, and Channels SSID Security, Guest Networks, and Authentication Antennas, Coverage, Roaming, Interference, and Site Surveys Physical Installation Implications

8 Domain 2: Network Implementation - Services Implementation

DNS Record Types and Troubleshooting Cues DHCP, DHCPv6, SLAAC, Scopes, Leases, and Relay NTP, PTP, NTS, and Time-Sensitive Networking Service Implementation PBQs: DNS, DHCP, VLANs, and Firewall Direction

9 Domain 3 Part A: Network Operations Documentation and Governance

Physical, Logical, Rack, Cable, Wireless Diagrams, and IPAM Asset Inventory, Baselines, SLAs, SOPs, and Runbooks Change Management and Request Tracking Lifecycle, EOL, EOS, Decommissioning, and Configuration Management

10 Domain 3 Part B: Monitoring, Remote Access, and Resilience

SNMP, Flow, Syslog, Packet Capture, Log Aggregation, APIs, and Port Mirroring Baselines and Performance Metrics Remote Access, Management Paths, and Secure Admin Habits DR and HA Concepts: RPO, RTO, MTTR, MTBF, Sites, Failover, and Testing

11 Domain 4: Logical Security and Secure Access (14%)

Encryption in Transit, Encryption at Rest, PKI, and Certificates IAM, MFA, SSO, Directory Services, and AAA Authorization, Least Privilege, RBAC, Geofencing, and Time-Based Access VPNs and Secure Management Design

12 Domain 4: Segmentation, Risk, and Network Attacks (14%)

Segmentation for Guest, BYOD, IoT, IIoT, SCADA, ICS, and OT Risk, Compliance, Audit, Data Locality, PCI, and GDPR Network Attacks and Scenario Cues Attack-to-Mitigation PBQ Tables

13 Domain 4: Security Controls and Hardening (14%)

Firewalls, IDS, IPS, Security Zones, and Screened Subnets ACLs, Filtering, NAC, Hardening, and Key Management Deception Technologies and Physical Security Zero Trust, SASE, and Trusted or Untrusted Zone Decisions

14 Domain 5: Troubleshooting Methodology and Tools (24%)

Official Troubleshooting Methodology and Evidence Handling Command-Line Tools: ping, traceroute, nslookup, dig, ipconfig, ifconfig, ip, arp, netstat, ss, and route Packet, Protocol, and Wi-Fi Analyzers Choosing the Right Tool by Symptom PBQs

15 Domain 5: Physical, Interface, and Wireless Troubleshooting (24%)

Cable Issues: Type, Attenuation, Crosstalk, Termination, and TX/RX Interface Issues: Errors, Discards, Duplex, Speed, Port Status, and PoE Transceiver, Fiber, and Signal Strength Troubleshooting Wireless Troubleshooting: Interference, Channels, Roaming, RSSI/SNR, Security, and Captive Portals

16 Domain 5: Network Services, Switching, Routing, and Performance Troubleshooting (24%)

DHCP, DNS, NTP, and IP Addressing Issues VLAN, STP, Trunk, Native VLAN, and ACL Issues Routing, Default Gateway, Route Table, and NAT Issues Congestion, Latency, Jitter, Packet Loss, and Application Performance Clues

17 Performance-Based Question Labs

Subnetting and VLSM Design Lab VLAN, Trunk, Router-on-a-Stick, and Firewall Rule Lab Wireless Deployment and Troubleshooting Lab Monitoring, Log Triage, and Route or Service Troubleshooting Lab

18 High-Yield Reference and Final Study Plan

High-Yield Ports and Protocols Table Wi-Fi, Cabling, Connectors, and Transceivers Quick Table Acronyms and Command-Line Tool Quick Table Final 7-Day Review Plan and Readiness Checklist

19 Final Synthesis: Strategy, Remediation, and Readiness

Mixed-Set Decision Strategy for Qualifiers and Close Answers Missed-Question Remediation Notebook by Error Type Exam-Day Time Management and PBQ Order 100-Question Readiness Simulation Blueprint Mapped to N10-009 Weights

OSI and TCP/IP Models with Device and Protocol Mapping

Key Takeaways Explain This Topic AI

The OSI model is a seven-layer troubleshooting map: Physical, Data Link, Network, Transport, Session, Presentation, and Application.

The TCP/IP model collapses the same functions into four layers: Link, Internet, Transport, and Application.

Devices and protocols are identified by the layer where their primary forwarding or decision logic lives.

Encapsulation adds a header (and a frame trailer) at each layer going down and strips them going up (de-encapsulation).

Layer thinking narrows symptoms, selects the right tool, and stops you from replacing the wrong component.

Last updated: June 2026

The OSI Model as a Troubleshooting Map

The CompTIA Network+ (N10-009) exam launched June 20, 2024 and is a 90-question, 90-minute test scored 100-900 with a passing score of 720 . Domain 1, Networking Concepts, is the largest objective at 23% , and the Open Systems Interconnection (OSI) model is its backbone. Memorize the layers bottom-up with "Please Do Not Throw Sausage Pizza Away" (Physical, Data Link, Network, Transport, Session, Presentation, Application) and top-down with "All People Seem To Need Data Processing."

The exam uses OSI to organize symptoms, not as trivia. If the link light is dark, start at Layer 1. If IP works but names fail, look at Layer 7. If TCP connects but the app rejects credentials, the path is fine and the problem is the application. The model also dictates which tool you reach for: a cable certifier and toner probe live at Layer 1, a managed switch CLI and show mac address-table live at Layer 2, ping , traceroute , and route tables live at Layer 3, netstat and port scans live at Layer 4, and protocol analyzers such as Wireshark let you read whichever header you suspect.

Anchoring tools to layers keeps you from, for example, replacing a cable when a name-resolution failure clearly sits at the top of the stack.

A second reason the exam loves OSI is that each layer is a clean handoff point. The unit of data at every layer has a specific name, called a protocol data unit (PDU), and being able to say "the problem is at the packet level, not the frame level" is the difference between a confident diagnosis and a guess. Watch the boundary cases: TLS encryption is presentation-layer work even though it rides inside a Layer 4 segment, and ARP straddles the line between Layer 2 (it deals in MAC addresses) and Layer 3 (it resolves IP addresses), which is why many references call it a Layer 2.5 protocol.

OSI layer Primary job Protocol data unit Examples Troubleshooting clue

7 Application User-facing network services Data HTTP, HTTPS, DNS, DHCP, SMTP, SNMP, SSH Name failure, service error, app timeout

6 Presentation Format, encryption, encoding Data TLS, SSL, ASCII, JPEG, compression Certificate warning, cipher mismatch

5 Session Setup, manage, tear down sessions Data RPC, NetBIOS, session control Session drops, half-open conversations

4 Transport End-to-end delivery, ports, reliability Segment (TCP) / Datagram (UDP) TCP, UDP, port numbers Connection refused, retransmits, blocked port

3 Network Logical addressing and routing Packet IPv4, IPv6, ICMP, routers, L3 switches Wrong gateway, no route, TTL exceeded

2 Data Link Framing, MAC addressing, VLANs Frame Ethernet, 802.1Q, ARP, switches VLAN mismatch, duplex error, MAC table

1 Physical Signaling and media Bits / Symbols Cabling, fiber, radio, transceivers No link, bad cable, EMI, attenuation

Mapping OSI to the TCP/IP Model

The TCP/IP model (also called the DoD model) compresses the seven OSI layers into four. The exam expects you to translate fluently between them, because real protocol stacks follow TCP/IP while diagnosis vocabulary follows OSI.

  • TCP/IP layer OSI mapping Examples
  • Application OSI 5-7 DNS, DHCP, HTTP, HTTPS, SMTP, SSH, SNMP
  • Transport OSI 4 TCP, UDP
  • Internet OSI 3 IPv4, IPv6, ICMP, routing
  • Link (Network Access) OSI 1-2 Ethernet, Wi-Fi, ARP, switching, cabling
  • Device and Protocol Layer Mapping

Most N10-009 "which layer" questions hinge on the primary decision a device makes. A hub repeats electrical signals (Layer 1); a switch reads MAC addresses (Layer 2); a router reads IP addresses (Layer 3).

  • Item Primary layer Why
  • Hub / repeater 1 Regenerates signals, makes no addressing decision
  • Switch 2 Forwards frames using the MAC address table
  • Access point 1/2 Bridges wireless clients onto the wired LAN
  • Router 3 Forwards packets between IP networks by longest-prefix match
  • Layer 3 switch 2/3 Switches within VLANs, routes between them
  • Firewall 3/4/7 Filters by IP, port, state, or application
  • Load balancer 4 or 7 Distributes by transport or application data
  • ARP 2/3 boundary Maps an IPv4 address to a MAC on the local segment
  • Worked Scenario: Narrow by What Works

A desktop has a link light, gets a DHCP lease, can ping its default gateway, but cannot open https://intranet.example by name. Walk up the stack:

  • Evidence What it proves
  • Link light on Layer 1 functional
  • DHCP lease present Layer 2 reach to relay/server, basic IP config OK
  • Gateway ping succeeds Local Layer 3 path OK
  • Name lookup fails Layer 7 (DNS) or the cert/HTTPS service is the suspect

The clue points to DNS resolution , so the fix is nslookup , the resolver config, or the DNS server, not a cable swap. As data leaves the host each lower layer adds its header (encapsulation), and the receiving stack removes them in reverse (de-encapsulation). Knowing the protocol data unit names, Data, Segment/Datagram, Packet, Frame, Bits, lets you describe exactly where a capture or counter sits.

A disciplined approach for any N10-009 layered question is to confirm each layer from the bottom up before blaming the one above it, because every working layer rules out a whole class of causes. In the example, a valid DHCP lease proves the host completed a Layer 2 exchange and holds correct Layer 3 settings, and a successful gateway ping proves ICMP echo (Layer 3) reaches the router and returns. Only the name lookup is left, so the fault is isolated to DNS without touching cabling, switches, or routing.

The same logic runs in reverse for top-down questions: if a browser shows a certificate error, you already know Layers 1 through 4 work, so you investigate the Presentation layer, the certificate, cipher, or system clock, rather than re-running connectivity tests. This is precisely the reasoning the exam rewards, and it is why memorizing layer numbers alone is not enough; you must know what each working layer lets you eliminate.