Identifying Bandwidth Saturation from Time-Based VoIP Issues

N10-009 By islever Editorial Last updated

Short answer

C Insufficient bandwidth causes local VoIP and video degradation during peak hours due to congestion on the shared edge connection, while remote users remain unaffected.

Question

A customer migrates its phone system from analog to a new hosted VoIP/software application solution with integrated video. After installation, some users notice issues with dropped calls, broken video, and slow internet access. The issues start in the mid-morning and continue into the afternoon. However, remote users do not report the same issues. Which of the following is the most likely cause of the issues?
  1. Roaming misconfiguration
  2. Signal degradation
  3. Insufficient bandwidth Correct Answer
  4. Miswired cable

Key Takeaways

The main trap is confusing variable performance issues with constant physical layer faults; time-based symptoms indicate congestion, not broken cables.

This CompTIA Network+ N10-009 question explains how to identify insufficient bandwidth as the root cause of time-dependent VoIP and video failures.

Common mistake: Option D (Miswired cable) is the most plausible wrong answer because candidates often jump to physical layer issues first. However, a miswired cable would cause persistent failure, not intermittent issues tied to morning activity peaks.

Expert Analysis

Time-of-Day Pattern The scenario describes issues that begin in the mid-morning and continue into the afternoon. This temporal correlation strongly suggests a variable load rather than a static physical defect. In networking, symptoms that appear only during peak business hours typically point to resource exhaustion or congestion.

Local vs. Remote Traffic Path The key differentiator is that local users experience dropped calls and slow internet, while remote users do not. Hosted VoIP and video applications are highly bandwidth-intensive. When local employees use these services simultaneously with general internet browsing, they consume significant upstream and downstream capacity on the site's edge connection. If this link lacks sufficient bandwidth, packet loss and jitter occur, degrading VoIP and video quality.

Eliminating Physical Layer Issues Options A (Roaming), B (Signal degradation), and D (Miswired cable) represent physical or configuration errors that are generally constant. As noted by community members, a miswired cable would likely result in no connectivity at all or persistent, intermittent failures regardless of the time of day. It would not explain why the system works perfectly at 8 AM but fails later when more users are active. Similarly, signal degradation or roaming issues would affect remote users equally or cause consistent problems for local users, not just during peak loads.

Conclusion The behavior matches classic bandwidth saturation. The local network path becomes congested as concurrent VoIP, video, and web traffic exceeds the pipe's capacity. Remote users, presumably connecting via a different path or experiencing less aggregate contention from the same local burst, remain unaffected.

Exam Strategy

When troubleshooting network performance, always correlate symptoms with user activity patterns. If issues are time-dependent (e.g., starting during business hours), suspect bandwidth congestion or QoS misconfiguration before checking physical layers. Physical faults like bad cables usually present consistently, regardless of how many users are online.

Frequently Asked Questions

Why don't remote users have the same VoIP issues?

Remote users connect from outside the local network, bypassing the congested local edge link. Their traffic does not compete with the local burst of simultaneous VoIP, video, and web usage that saturates the office's internet connection.

Could this be a QoS issue instead of bandwidth?

While QoS misconfiguration could cause similar symptoms, the question implies the link itself is overwhelmed. Insufficient bandwidth is the primary constraint; even perfect QoS cannot fix a pipe that is physically too small for the total traffic volume.

More N10-009 FAQ →

Discussion 3 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 3

  1. ERB14 👍 1 Answered C
    Insufficient Bandwidth: During peak operating hours (mid-morning through afternoon), as local employees actively use the new bandwidth-intensive hosted VoIP and integrated video app alongside standard internet traffic, the site's internet connection reaches capacity. This leads to packet loss, video degradation, and slow browsing locally, while remote users (who connect directly from outside networks) remain unaffected.
  2. smittywerbenjagermanjensen 👍 1 Answered C
    It's C this guy Skri113xX is trolling. If it were a miswired cable, it wouldn't work at all. It says in the question that it works fine at 8am then slows down by 10:30, which wouldn't be the case if it were just a cable.
  3. Skri113xX 👍 1 Answered D
    My gut says D. It aligns with best practices.

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Practice All N10-009 Questions

Access 100 questions with complete answers and detailed explanations.

View Full N10-009 Practice Test →

← Back to N10-009 Study Guide