CCNA Practice Question: A network engineer notices that users in VLAN 10 report intermittent connectivity and…
A network engineer notices that users in VLAN 10 report intermittent connectivity and slow file transfers to a server on the same switch. The engineer issues the show interfaces fa0/1 command on the switch port connected to the server and observes a high number of runts, input errors, and CRC errors, while output errors are minimal. The interface configuration shows speed 100 and duplex full.
Practise it in a lab
VLANs and 802.1Q trunking
Configure real Cisco IOS in your browser, with each task checked as you go.
⚠ Common exam trap
Cisco often tests the misconception that speed and duplex mismatches always occur together; the trap here is that a duplex mismatch can exist even when speed matches, and the error pattern (high input errors, low output errors) specifically points to duplex, not cabling or VLAN issues.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The server NIC is auto-negotiating to 100 Mbps half-duplex, resulting in a duplex mismatch.
The symptoms—high runts, input errors, and CRC errors with minimal output errors—are classic indicators of a duplex mismatch. When the switch port is hardcoded to 100 Mbps full-duplex and the server NIC auto-negotiates to 100 Mbps half-duplex (a common fallback when one side is manually set), the half-duplex side experiences collisions while the full-duplex side does not sense the collision. These collisions cause the half-duplex side to truncate frames, resulting in runts and CRC errors on the full-duplex switch port. The speed matches (both 100 Mbps), so the issue is purely duplex-related.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The server NIC is set to 10 Mbps half-duplex, causing a speed mismatch.
Why it's wrong here
A speed mismatch—such as one side at 10 Mbps and the other at 100 Mbps—does not cause intermittent connectivity with high input errors; it prevents the link from establishing altogether. Ethernet requires both ends to agree on the same bit rate, so a forced 10 Mbps NIC talking to a 100 Mbps switch port will leave the interface in a down/down state or show carrier loss, producing no traffic counters at all. The reported runts, CRC errors, and input errors instead point to a duplex mismatch, not a speed mismatch.
- ✓
The server NIC is auto-negotiating to 100 Mbps half-duplex, resulting in a duplex mismatch.
Why this is correct
Hard-coding the switch port to 100 Mbps full duplex usually disables auto-negotiation on it. The server's NIC, still auto-negotiating, detects the speed but cannot learn the duplex, so it falls back to half duplex. The half-duplex side backs off and abandons frames when it sees traffic, and the full-duplex switch receives those cut-off frames as runts and CRC errors. Set both sides to auto, or hard-code both identically.
- ✗
The cable connecting the server to the switch is faulty, introducing excessive noise.
Why it's wrong here
A damaged cable can cause CRC errors, but it usually produces errors in both directions, often alongside link flaps, and rarely gives this clean pattern of runts and input errors on one side with almost no output errors. That pattern matches a duplex mismatch, especially with one side hard-coded. Fix the duplex first; if errors continue with both sides matching, then test or replace the cable.
- ✗
The switch port is configured with an incorrect native VLAN, causing duplex negotiation issues.
Why it's wrong here
The native VLAN setting controls which VLAN carries untagged frames on an 802.1Q trunk and is a Layer 2 function; it has no bearing on physical-layer auto-negotiation or duplex selection. An incorrect native VLAN can cause VLAN mismatch or spanning-tree issues, but it would not generate runts, CRC errors, or input-error counters on the switch interface. Duplex negotiation is handled by the PHY during link establishment and is unrelated to VLAN configuration, making this option a category error.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The 200-301 exam frequently reuses these exact scenarios with slightly different constraints.
✓The server NIC is auto-negotiating to 100 Mbps half-duplex, resulting in a duplex mismatch.Correct answer▾
Why this is correct
Hard-coding the switch port to 100 Mbps full duplex usually disables auto-negotiation on it. The server's NIC, still auto-negotiating, detects the speed but cannot learn the duplex, so it falls back to half duplex. The half-duplex side backs off and abandons frames when it sees traffic, and the full-duplex switch receives those cut-off frames as runts and CRC errors. Set both sides to auto, or hard-code both identically.
✗The server NIC is set to 10 Mbps half-duplex, causing a speed mismatch.Wrong answer — click to see why▾
Why this is wrong here
Misconception that speed mismatch produces specific error counters; in reality, incompatible speeds cause link failure, not runts and CRC errors.
✗The cable connecting the server to the switch is faulty, introducing excessive noise.Wrong answer — click to see why▾
Why this is wrong here
Misconception that CRC errors alone point to a bad cable; duplex mismatch is one of the most common causes of runts and CRC errors on forced-full interfaces.
✗The switch port is configured with an incorrect native VLAN, causing duplex negotiation issues.Wrong answer — click to see why▾
Why this is wrong here
Misconception that a VLAN mismatch can trigger interface errors; these errors are purely physical/data-link layer phenomena unrelated to VLAN settings.
Analysis generated from the official 200-301 blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Visual reference
Go deeper
Related to this question
Learn chapter
Exam Trap: NAT Configuration Errors
Key term
Switch
A switch is a networking device that connects devices on a local area network and uses MAC addresses to forward data only to the intended recipient.
Key term
CRC
CRC (Cyclic Redundancy Check) is an error-detecting code used to detect accidental changes to raw data in digital networks.
About these practice questions
One of 1,352 original 200-301 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
You might also like
Similar 200-301 questions
- Which two statements accurately compare IPv4 private addresses and public addresses?
- Which TWO statements are correct regarding Protocol Data Units (PDUs) and data encapsulation in the OSI model?
- Which TWO statements accurately describe the responsibilities of the OSI model's Transport layer?
- A network engineer is troubleshooting a connectivity issue between two hosts on different subnets. The sending host has…
- Which TWO statements accurately describe cabling and SFP transceiver diagnostics?
Written by Johnson Ajibi, MSc IT Security
Security Systems Architect · founder of Courseiva
This 200-301 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 200-301 exam.