NetworkingNetwork+

Network Performance Troubleshooting for CompTIA Network+ N10-009

Q: How do I test actual throughput vs link speed?

Use iperf3: run iperf3 as a server on one endpoint ('iperf3 -s'), then connect from the other ('iperf3 -c server-ip'). It measures actual TCP throughput. Compare result to link speed (show interface) to see efficiency. Significant gap between link speed and iperf3 throughput indicates: packet loss, duplex mismatch, TCP window size issues, or QoS throttling. iPerf3 is available for Windows, Linux, and macOS.

Performance troubleshooting addresses slow network response, high latency, packet loss, and bandwidth issues that degrade application quality without completely breaking connectivity. CompTIA Network+ N10-009 tests performance troubleshooting systematically — identifying whether the problem is congestion, latency, packet loss, or application-layer, and using the right tools to measure each.

7 min

2 sections · 7 exam key points

1 practice questions

Identifying Performance Problems

High latency: measure with ping RTT. Compare against baseline. Sources: congestion (queuing delay at congested links), distance (long physical paths through many hops), poorly optimized routing (traffic taking suboptimal path). Traceroute identifies high-latency hops. If one hop has significantly higher RTT, that segment is the bottleneck or the hop rate-limits ICMP.

Packet loss: 'ping -n 100 destination' (Windows) or 'ping -c 100 destination' (Linux) reveals loss rate. Any loss on a LAN = problem (physical, duplex mismatch, congestion). Internet packet loss > 1–2% degrades TCP performance (retransmissions) and VoIP quality. MTR (my traceroute) combines ping + traceroute — shows per-hop loss rates.

Bandwidth saturation: check interface utilization via SNMP or interface counters. High outbound utilization → traffic going out faster than link allows → congestion, queueing delay, drops. QoS can prioritize critical traffic; physical upgrade may be needed if all traffic is essential.

Application Performance Issues

VoIP quality (choppy, echo, delay): measure jitter and one-way latency. One-way latency > 150ms: unacceptable. Jitter > 30ms: audio breakup. Packet loss > 1%: audible artifacts. Solutions: QoS (DSCP EF marking, LLQ), separate Voice VLAN, upgrade bandwidth, reduce congestion.

Slow file transfers: may indicate bandwidth saturation, packet loss causing retransmissions, or MTU issues (fragmentation). Test with iperf3 for maximum throughput measurement. Check for interface errors (CRC, drops) that indicate physical issues compounding performance.

Inconsistent performance (works fine sometimes, slow at peak times): indicates congestion during peak hours. Capture NetFlow data to identify bandwidth-consuming flows. Identify the top talkers and traffic types. Apply QoS policies or address the congestion through capacity upgrade.

Key exam facts — Network+

Ping: measures latency (RTT); repeated ping measures consistency and packet loss
Traceroute: identifies high-latency hops and path problems
iperf3: measures actual maximum throughput between two endpoints
MTR: combines ping + traceroute — per-hop loss and latency
NetFlow: identifies top bandwidth consumers (top talkers)
VoIP requirements: < 150ms one-way, < 30ms jitter, < 1% packet loss
LAN packet loss should be near zero — any loss indicates a problem

Common exam traps

High ping latency always means the network is congested

ICMP ping may be rate-limited or deprioritized by intermediate routers — they process data packets in hardware but handle ICMP in software with lower priority. High ping RTT to an intermediate hop doesn't always mean congestion; check if the final destination RTT is also high

Practice questions — Performance Troubleshooting

These questions are representative of what you will see on Network+ exams. The correct answer and explanation are shown immediately below each question.

Q1.Users report VoIP calls are clear for the first few minutes but become choppy during large file transfers by other users. Which solution addresses this without adding bandwidth?

A.Replace all network cables

B.Configure QoS to prioritize VoIP (DSCP EF) over file transfer traffic

C.Disable file transfers during business hours

D.Move VoIP to a separate physical network

Explanation: QoS (Quality of Service) prioritizes VoIP traffic over file transfer traffic when the link is congested. DSCP EF marking and LLQ (Low Latency Queuing) ensure VoIP packets are forwarded first, maintaining low latency and jitter. File transfer traffic is deferred — slightly slower but not time-sensitive. This resolves the problem without adding bandwidth or physically separating networks.

Frequently asked questions — Performance Troubleshooting

How do I test actual throughput vs link speed?

Use iperf3: run iperf3 as a server on one endpoint ('iperf3 -s'), then connect from the other ('iperf3 -c server-ip'). It measures actual TCP throughput. Compare result to link speed (show interface) to see efficiency. Significant gap between link speed and iperf3 throughput indicates: packet loss, duplex mismatch, TCP window size issues, or QoS throttling. iPerf3 is available for Windows, Linux, and macOS.

Practice this topic

Network+practice questions

Test yourself on Performance Troubleshooting

JT Exams routes you to questions in your exact weak areas — automatically, after every session.

Free practice test Start 7-Day Free Trial

No credit card · Cancel anytime