Study guide

Asset Inventory, Baselines, SLAs, SOPs, and Runbooks

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

Asset Inventory, Baselines, SLAs, SOPs, and Runbooks

Key Takeaways Explain This Topic AI

Asset inventory (often a CMDB) records what exists, where it is, who owns it, its support status, software version, and criticality — every other operation depends on it.

A baseline is documented normal behavior (configuration, performance, traffic, wireless), measured during representative business cycles, used to detect drift and anomalies — it is not a hard maximum.

An SLA defines service expectations (availability, response/resolution time, hours, escalation); SLOs are measurable targets and OLAs are internal inter-team agreements.

Standard Operating Procedures standardize routine repeatable work; runbooks give task-specific steps with commands, validation, decision points, rollback, and escalation contacts.

Operational records must be version controlled, owned, reviewed, and tested — an untested runbook can fail during a real outage.

Last updated: June 2026

Operations Records You Must Distinguish

Network operations gets easier when a team can quickly answer four questions: what devices exist, what normal looks like, what service level is promised, and what procedure to follow. N10-009 objective 3.1 lists asset inventory, baselines, SLAs, and procedural documents together, and the exam loves to make you pick the one record that resolves a scenario. Because Domain 3 is about roughly one in five questions, knowing these distinctions cold is high-yield.

Asset Inventory and the CMDB

An asset inventory is the authoritative list of network items. It may live in a Configuration Management Database (CMDB) , an IPAM platform, an endpoint management system, or a ticketing system.

  • Inventory field Example
  • Asset ID NET-SW-IDF2-004
  • Device type Access switch
  • Manufacturer / model Vendor model and hardware revision
  • Serial number Vendor serial for support/RMA
  • Location Building, floor, room, rack, RU
  • Owner Network operations team
  • Support status Covered by contract through a stated date
  • Software version Current OS or firmware build
  • Criticality Core, distribution, access, lab, or spare

Inventory quality matters because patch planning, contract renewal, vulnerability response, incident triage, capacity planning, and decommissioning all start with knowing what exists. If you cannot find a serial number during an outage, you cannot open a vendor support case.

Baselines: Normal, Not Maximum

A baseline is a documented normal state. It can describe configuration, performance, traffic, or security posture, and it lets teams recognize drift or abnormal behavior.

  • Baseline type Examples
  • Configuration baseline Approved firmware, NTP servers, SNMP settings, syslog destination, AAA method
  • Performance baseline Typical CPU, memory, interface utilization, latency, jitter, packet loss
  • Traffic baseline Normal application flows, busy-hour bandwidth, expected protocols
  • Wireless baseline Normal RSSI, SNR, channel utilization, client counts per AP

Baselines must be measured during representative cycles. A baseline captured at midnight does not represent a call center at 10 a.m., and a sample taken during a known outage must never be treated as healthy. The classic exam trap is calling a baseline a hard threshold; it is a comparison reference , so a router idling at 20-35% CPU that suddenly sits at 92% is anomalous only because the baseline told you what normal was.

SLAs, SLOs, and OLAs

A Service Level Agreement (SLA) is a formal commitment, commonly defining availability targets, support hours, response time, resolution targets, maintenance windows, reporting, and escalation.

  • Term Meaning
  • SLA Agreement with a customer or service consumer
  • SLO (Service Level Objective) Measurable target used to gauge service quality
  • OLA (Operating Level Agreement) Internal agreement between supporting teams
  • Maintenance window Approved time for planned service impact
  • Escalation path Who is contacted when a target is at risk

For example, a circuit SLA might promise 99.9% availability (roughly 8.76 hours of downtime allowed per year) and a one-hour provider response. The SLO is the internal metric you track against it; the OLA is what your monitoring team owes your WAN team.

SOPs and Runbooks

Standard Operating Procedures describe repeatable routine work. Runbooks are task-specific and usually include exact commands, checks, decision points, rollback steps, and escalation contacts.

  • Document Best use
  • SOP Monthly firewall rule review process
  • Runbook Steps to fail over a WAN circuit
  • Checklist Pre-change validation items
  • Escalation matrix Who to contact by severity and system

A strong runbook lists prerequisites, required access, expected output, verification steps, rollback instructions, and the evidence to attach to a ticket — and it must be tested. A runbook that has never been practiced often fails the first time it is needed in production.

Practical Scenario

A monitoring alert shows high latency across a WAN link. The team uses the inventory to identify the circuit and provider, compares current metrics to the baseline to confirm the anomaly, checks the SLA for the provider's response obligation, opens a ticket, and follows the runbook to collect evidence and escalate once thresholds are exceeded. Each record plays a distinct, non-interchangeable role.

Common Exam Traps

Trap Better exam reasoning

"Inventory is only for accounting." It drives supportability, security, troubleshooting, and lifecycle.

"A baseline is a maximum limit." A baseline is normal behavior used for comparison.

"An SLA is the same as a runbook." An SLA sets expectations; a runbook lists operator steps.

"SOPs can live in one engineer's notes." Procedures need shared access, ownership, and version control.

Quick Drill

Decide whether interface utilization is unusual: performance baseline .

Find the serial number of a failed switch: asset inventory .

Know whether a provider must respond within one hour: SLA .

Replace a failed firewall using approved steps: runbook .

Define the recurring access-rule review process: SOP .