Study guide

Baselines and Performance Metrics

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

Baselines and Performance Metrics

Key Takeaways Explain This Topic AI

A baseline captures normal behavior for a specific link, device, or time so deviations stand out; refresh it after major changes.

Bandwidth is capacity and latency is delay — they are independent, and a high-bandwidth link can still have high latency.

Jitter (variation in latency) and packet loss are the metrics most directly tied to poor voice and video quality.

Interface errors, CRC errors, and discards point to physical, duplex, or congestion problems rather than application bugs.

Wireless health uses RSSI, SNR, and channel utilization; usable RSSI for data is roughly -67 dBm or better and SNR above 20 dB.

Last updated: June 2026

Baselines and Performance Metrics

Monitoring data only becomes actionable when you can compare it against normal . A baseline is a documented record of normal behavior for a specific network, link, device, application, or time window. With a baseline, a reading of 95 percent utilization is alarming; without one, the same number is just a number.

Why baselines matter

Baselines drive five activities the exam cares about: troubleshooting, alert threshold tuning , capacity planning , change validation, and anomaly detection. If a WAN link normally runs 40 percent at peak and suddenly hits 95 percent, the gap is the clue. Baselines must capture business cycles — a school, clinic, warehouse, and 24x7 SaaS office all peak at different hours — and must be refreshed after major changes such as a new application rollout, a circuit upgrade, a wireless redesign, or a routing change. A stale baseline produces false alarms or, worse, masks a real regression.

Core wired metrics

  • Metric Meaning Typical cause when abnormal
  • Bandwidth Maximum capacity of a path (e.g., 1 Gbps) Link is undersized for demand
  • Utilization Percent of capacity in use Congestion when sustained near limit
  • Latency One-way or round-trip delay Long paths, queuing, slow links
  • Jitter Variation in latency Choppy voice and video
  • Packet loss Packets that never arrive Retransmissions, dropped calls
  • CRC / frame errors Frames failing checksum Bad cable, optic, EMI, or duplex mismatch
  • Discards Frames dropped intentionally Full queues, congestion, policy
  • CPU / memory Device resource use Control-plane or management instability

Bandwidth and latency are independent. A 10 Gbps satellite link can still have 600 ms latency. The exam loves the trap that "more bandwidth fixes latency" — it does not. Likewise, a duplex mismatch produces late collisions and CRC errors on a link that pings fine, so correlate errors with throughput, not just reachability.

Wireless metrics

Wi-Fi is a shared medium, so one bad client degrades a whole cell. Key indicators:

  • Metric What it indicates Healthy guideline
  • RSSI Received signal strength (dBm, negative) -67 dBm or better for voice/data
  • SNR Signal-to-noise ratio (dB) 20 dB+ for reliable data, 25 dB+ for voice
  • Channel utilization Airtime consumed on the channel Below ~50% before contention hurts
  • Retries Frames resent due to loss/interference High retries signal interference
  • Client count / roaming Density and mobility Overloaded AP if count spikes

Remember RSSI is negative: -50 dBm is stronger than -75 dBm. A client at -80 dBm with high retries will feel slow even though the wired uplink is idle.

Thresholds, alerts, and trends

Thresholds should reflect operational impact and duration , not raw values, to avoid alert fatigue.

  • Alert pattern Example rule
  • Static threshold WAN utilization above 90% for 15 minutes
  • Baseline deviation Traffic is 3x normal for this hour
  • Rate of change DHCP scope filling unusually fast
  • Composite High latency AND packet loss AND interface errors

Trend analysis forecasts when a resource will need attention: a WAN circuit projected to exceed capacity next quarter, an access switch with rising PoE budget consumption, or a DHCP scope nearing exhaustion. This is proactive capacity planning rather than reactive firefighting.

Practical scenario

After a cloud backup agent is deployed, users report afternoon slowness. The baseline shows WAN utilization is normally 45 percent at 2 p.m., but monitoring now reports 98 percent for two hours. Flow data confirms backup traffic dominates. Remedies include rescheduling the backup, applying QoS to protect interactive traffic, upgrading bandwidth, or traffic shaping — the baseline made the diagnosis fast.

Reading errors versus discards

The exam distinguishes errors from discards because they have different causes. Errors are frames that arrived damaged — they failed the cyclic redundancy check, or were runts, giants, or alignment errors — and they almost always trace to a physical problem: a kinked or out-of-spec cable, a dirty fiber connector, electromagnetic interference, or a duplex mismatch where one side is half duplex. Discards, by contrast, are intact frames the device chose to drop, usually because an output queue was full during congestion or a policy such as an access control list or quality-of-service drop matched.

So rising errors say "check the physical layer," while rising discards say "check for congestion or policy." Treating them as interchangeable leads to replacing good cable when the real fix is more bandwidth or smarter queuing.

Interpreting utilization over time

A single utilization reading is nearly meaningless; the shape over time is what counts. A link that briefly touches 100 percent during a backup window is healthy, while a link that sits at 85 percent every business hour is a capacity problem waiting to surface as latency and loss. This is why thresholds combine a level with a duration — "above 90 percent for 15 minutes" filters out harmless spikes. Sampling interval matters too: averaging over five minutes can hide one-second microbursts that still overflow a switch buffer and cause discards.

When users complain of slowness but the five-minute graph looks fine, drop to a shorter interval or a packet capture to expose the burst.

Common exam traps

High bandwidth does not guarantee low latency; they are separate metrics.

A single metric rarely proves root cause — correlate utilization, errors, loss, logs, and user impact.

Errors are damaged frames (physical layer); discards are intact frames dropped by congestion or policy.

RSSI is negative: closer to zero is stronger.

Baselines are not permanent; refresh them after major changes and seasonal shifts.