ExamFinch.com My Study

Study guide

Acronyms and Command-Line Tool Quick Table

Practice this exam

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

Acronyms and Command-Line Tool Quick Table

Key Takeaways Explain This Topic AI

Acronym items are usually scenario questions in disguise—map each acronym to where it appears in a troubleshooting workflow.

Command-line tools map to layers: local config, name resolution, path testing, port/socket testing, and packet inspection.

Use ipconfig/ifconfig/ip to verify local addressing before chasing remote services, then move outward.

Use ping and traceroute carefully—ICMP can be filtered even when the application works fine.

Use nslookup/dig for DNS, arp for local neighbor mapping, and netstat/ss for listening ports and active sessions.

Last updated: June 2026

Acronyms and Command-Line Tools

N10-009 acronym items (Objective 1.8 lists the official acronym set) are usually scenario questions in disguise. A prompt rarely asks "What does DHCP mean?" Instead it says a client has an APIPA address and asks which service or tool to check. Likewise, tool questions (Objective 5.x) hand you a symptom and ask which command isolates it. Learn each item by its job in the workflow.

Acronym Quick Table

  • Acronym Meaning Fast association
  • ACL Access Control List Permit or deny traffic
  • ARP Address Resolution Protocol IPv4-to-MAC on the local segment
  • BGP Border Gateway Protocol Internet/external routing (path-vector)
  • CIDR Classless Inter-Domain Routing Prefix notation such as /24
  • DHCP Dynamic Host Configuration Protocol Automatic IP assignment
  • DNS Domain Name System Names to IP addresses
  • FHRP First Hop Redundancy Protocol Gateway redundancy concept
  • HSRP/VRRP Hot Standby / Virtual Router Redundancy Redundant default gateway
  • IDS/IPS Intrusion Detection/Prevention System Alerts vs blocks
  • LDAP Lightweight Directory Access Protocol Directory queries
  • MTU Maximum Transmission Unit Largest payload before fragmentation (1500 default)
  • NAC Network Access Control Posture/identity-based access
  • NAT Network Address Translation Private-to-public translation
  • NTP Network Time Protocol Time synchronization
  • OSPF Open Shortest Path First Link-state interior routing
  • PoE Power over Ethernet Power + data on twisted pair
  • RADIUS Remote Authentication Dial-In User Service AAA for VPN/Wi-Fi/802.1X
  • SNMP Simple Network Management Protocol Monitoring/management
  • STP Spanning Tree Protocol Layer 2 loop prevention
  • VLAN Virtual LAN Layer 2 segmentation
  • VPN Virtual Private Network Encrypted tunnel over untrusted network
  • VRF Virtual Routing and Forwarding Separate routing tables
  • Command-Line Tool Table
  • Tool Platform Use
  • ipconfig Windows View/renew IP config (/all, /release, /renew)
  • ifconfig Linux/macOS (legacy) View interface config
  • ip Linux Addresses, routes, links (ip addr, ip route)
  • ping All Reachability/latency via ICMP
  • traceroute / tracert Linux·macOS / Windows Hop-by-hop path discovery
  • pathping / mtr Windows / Linux Combined path + per-hop loss
  • nslookup / dig All / Linux·macOS DNS query testing
  • arp -a All Local IPv4-to-MAC cache
  • netstat / ss All / Linux Connections and listening ports
  • route / netsh All / Windows View or change routing and config
  • nmap Installed Port scan/service discovery (with authorization)
  • tcpdump / Wireshark Linux·macOS / GUI Packet capture and analysis
  • curl All Test HTTP/HTTPS endpoints
  • Tool Selection Workflow
  • Question Tool examples
  • Valid IP, mask, gateway, DNS? ipconfig /all, ip addr, ip route
  • Does the name resolve? nslookup, dig
  • Reachable at Layer 3 (ICMP allowed)? ping
  • Where does the path stop? traceroute, tracert, mtr
  • Is the service port open/listening? netstat, ss, nmap, curl
  • What is actually on the wire? tcpdump, Wireshark
  • Mini Scenarios
  • Symptom First useful tool
  • Windows client has no network access ipconfig /all
  • Linux server may have wrong default route ip route
  • Site fails only by name nslookup or dig
  • Suspected blocked HTTPS service curl, port test, firewall logs
  • Suspected duplicate IP on the LAN arp -a, switch MAC table
  • Worked Scenario: "The Server Is Down" (But It Isn't)

A help-desk ticket says an internal web app is "down." Resist jumping to a tool—work outward by layer. First confirm local addressing with ipconfig /all or ip addr: a 169.254 address or a missing gateway redirects you to DHCP, not the server. Next test name resolution with nslookup app.corp.local; a wrong or empty record points at DNS, not the app. If the name resolves, try ping to the server IP, but remember ICMP may be filtered, so a failed ping is not proof of an outage. The decisive test is the actual service port: curl -v https://app.corp.local or a port check on 443.

If the TCP handshake completes but the page errors, the network is fine and the application or web service is the fault domain. This sequence—local config, DNS, reachability, port, application—prevents the most common Network+ trap of blaming the wrong layer.

ICMP, TTL, and MTU Gotchas

Three behaviors trip candidates. ICMP can be rate-limited or blocked by firewalls, so traceroute may show timeouts mid-path while traffic still flows end to end—do not read a starred hop as a dead router. The TTL (time to live) field decrements at each hop and prevents loops; a destination unreachable due to TTL expiry signals a routing loop, not a dead host.

MTU mismatches (default Ethernet 1500 bytes) cause large packets to fail while small ones like ping succeed; the clue is "small transfers work, large file copies or TLS handshakes hang." Knowing these means you interpret tool output correctly instead of misreading a filtered or fragmented path as a true failure.

Common Traps

Running traceroute before confirming the host even has a valid IP configuration.

Assuming a ping failure proves the application is down—ICMP may simply be filtered.

Using nmap or packet capture without authorization in a production environment.

Forgetting that DNS can return the wrong address even when the server responds.

Confusing ARP (local IPv4-to-MAC) with DNS (name-to-IP) resolution.

Treating a command name as universal when flags differ across operating systems.