NetworkingNetwork+

Bandwidth, Throughput, and Latency for CompTIA Network+ N10-009

Understanding the difference between bandwidth, throughput, and latency is fundamental to network performance analysis and troubleshooting, both of which are tested throughout CompTIA Network+ N10-009. These concepts appear in performance metrics questions (Domain 3: Network Operations) and troubleshooting scenarios where you must diagnose whether a problem is a capacity issue, a congestion issue, or a delay issue.

7 min
3 sections · 7 exam key points
2 practice questions

Bandwidth, Throughput, and Goodput

Bandwidth is the theoretical maximum data transfer rate of a connection, measured in bits per second (bps). It is the capacity of the pipe — a 1 Gbps Ethernet interface has 1 Gbps of bandwidth regardless of actual traffic. Bandwidth is determined by the physical medium and technology standard, not by the amount of data currently flowing.

Throughput is the actual amount of data successfully transferred per unit of time, accounting for protocol overhead, retransmissions, and network conditions. Throughput is always less than or equal to bandwidth. If a 1 Gbps link achieves 800 Mbps throughput, overhead and inefficiency consume the remaining 200 Mbps.

Goodput (application-level throughput) is the useful application data transferred per second — throughput minus protocol headers, retransmissions, and acknowledgments. This is what users and applications actually experience. A VoIP call over a 100 Mbps link consumes about 87.2 kbps of goodput per call.

Latency and Jitter

Latency (delay) is the time it takes for data to travel from source to destination. Measured in milliseconds (ms). Sources of latency: propagation delay (speed of signal through medium), processing delay (router/switch decision time), queuing delay (waiting in buffers), serialization delay (time to transmit bits onto the wire). RTT (Round Trip Time) measures the full path: source → destination → source. Ping measures RTT.

Jitter is the variation in latency over time — inconsistent delay. Low latency with high jitter still causes problems for real-time applications. VoIP and video conferencing are sensitive to both latency and jitter. Acceptable VoIP latency: under 150ms one-way. Acceptable VoIP jitter: under 30ms.

Bandwidth-Related Concepts

Bottleneck: the slowest link in a path determines the maximum throughput. Even if a WAN link is 1 Gbps, if the access link is 100 Mbps, throughput is capped at 100 Mbps. Always check all links in the path when troubleshooting performance.

Full vs half duplex bandwidth: a 100 Mbps full-duplex link can transfer 100 Mbps simultaneously in each direction. A 100 Mbps half-duplex link shares 100 Mbps across all devices in both directions. Duplex directly impacts effective throughput.

Traffic shaping and QoS: bandwidth management techniques that prioritize certain traffic types (VoIP, video) over others (bulk file transfers, backups) to ensure critical applications receive consistent bandwidth and low latency. Network+ tests QoS concepts in both implementation and operations domains.

Performance Metric Comparison

MetricDefinitionUnitMeasured By
BandwidthMaximum capacity of linkbps (Mbps, Gbps)Interface specification
ThroughputActual data transfer ratebps (Mbps, Gbps)Performance tools
GoodputApplication-useful data ratebpsApplication-layer tools
LatencyDelay for data to reach destinationMilliseconds (ms)Ping, traceroute
RTTRound-trip timeMilliseconds (ms)Ping
JitterVariation in latencyMilliseconds (ms)Specialized tools

Key exam facts — Network+

  • Bandwidth = theoretical maximum; throughput = actual measured; goodput = useful application data
  • Throughput is always ≤ bandwidth due to overhead and protocol inefficiency
  • Latency = delay; jitter = variation in latency — both affect real-time applications
  • VoIP requirements: <150ms one-way latency, <30ms jitter
  • Bottleneck = slowest link in path determines maximum throughput
  • RTT is measured by ping; traceroute measures per-hop latency
  • QoS prioritizes bandwidth-sensitive or latency-sensitive traffic

Common exam traps

Higher bandwidth guarantees better performance

High bandwidth does not help if latency is also high — a satellite link can have 100 Mbps bandwidth but 600ms latency, making interactive applications unusable

Bandwidth and speed are the same thing

Bandwidth is capacity; speed often refers to latency (how fast data arrives). A high-bandwidth, high-latency connection has 'speed' problems despite having capacity

Throughput equals bandwidth in real networks

Protocol overhead, error correction, retransmissions, and queue management always consume some bandwidth — throughput is consistently less than the raw bandwidth figure

Practice questions — Bandwidth and Throughput

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

Q1.A user reports that voice calls are choppy and break up, but internet browsing works fine. Which network metric is most likely the cause?

A.Low bandwidth
B.High latency only
C.High jitter
D.Packet loss over 0.1%

Explanation: Choppy voice (VoIP audio breaking up) is a classic symptom of high jitter — inconsistent packet arrival times disrupt the voice stream. Low bandwidth would affect all applications. High latency alone causes delay but not choppiness. Packet loss over 1% causes VoIP issues, but jitter is the primary cause of choppy audio described here.

Q2.A network link is rated at 1 Gbps. During a performance test, actual data transfer achieves 750 Mbps. What is the term for this 750 Mbps measurement?

A.Bandwidth
B.Throughput
C.Goodput
D.Latency

Explanation: Throughput is the actual measured data transfer rate — 750 Mbps in this case. Bandwidth is the theoretical maximum (1 Gbps). Goodput would be the application-useful data rate, which is a subset of throughput. Latency measures delay, not data rate.

Frequently asked questions — Bandwidth and Throughput

How do I measure network throughput?

Use tools like iperf3 (network throughput testing between two endpoints), speed test services (for internet connections), or protocol analyzers (Wireshark). For VoIP quality, use DSCP marking monitors or VoIP-specific tools that measure MOS (Mean Opinion Score), jitter, and latency. Ping measures RTT, not throughput.

What is the MOS score for VoIP quality?

MOS (Mean Opinion Score) rates VoIP call quality from 1 (unacceptable) to 5 (excellent). Scores above 4.0 are excellent, 3.5–4.0 are acceptable, and below 3.5 are considered poor. MOS accounts for codec quality, latency, jitter, and packet loss. G.711 codec can achieve MOS 4.4 under ideal conditions.

Practice this topic

Test yourself on Bandwidth and Throughput

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

No credit card · Cancel anytime

Related certification topics