350-601 Storage Network Practice Question
Exhibit
Refer to the exhibit.
MDS-A# show running-config interface fc1/1
!Command: show running-config interface fc1/1
!Time: Mon Apr 15 10:30:00
interface fc1/1
switchport mode F
switchport speed 16000
no shutdown
MDS-A# show interface fc1/1
fc1/1 is up
Hardware is Fibre Channel, SFP is short wave laser
Port WWN is 20:01:54:7f:ee:00:01:00
Admin port mode is F, operational port mode is F
fc1/1 is part of VSAN 100
5 minutes input rate 1.20 Gbps, 0.80 Gbps output rate
3045 frames input, 3045 frames output
CRC errors: 12, CRC error threshold: 15
Credits: 16, Credits used: 4
Link failures: 0, Sync losses: 0Refer to the exhibit. The interface shows CRC errors. What is the most likely cause of these errors?
⚠ Common exam trap
Cisco often tests the distinction between physical-layer errors (CRC, alignment errors) and flow-control issues (buffer credits, credit loss), leading candidates to mistakenly attribute CRC errors to buffer credit problems or port configuration mismatches.
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
✓
Faulty SFP or fiber cable.
CRC errors indicate that frames are being received with invalid checksums, which is typically caused by physical-layer issues such as a faulty SFP module or damaged fiber cable. These errors occur when the cyclic redundancy check computed by the receiver does not match the CRC appended by the sender, pointing to corruption during transmission. In Fibre Channel storage networks, a faulty SFP or cable is the most common root cause of CRC errors, as they directly affect signal integrity.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Insufficient buffer credits for the distance.
Why it's wrong here
Buffer credit issues cause credit starvation, not CRC errors.
- ✗
The port is configured as F port but should be E port.
Why it's wrong here
CRC errors are not a symptom of port mode misconfiguration.
- ✗
Speed mismatch between the ports.
Why it's wrong here
Speed mismatch would cause link failures, not CRC errors.
- ✓
Faulty SFP or fiber cable.
Why this is correct
CRC errors are typically caused by signal degradation from hardware.
Go deeper
Related to this question
About these practice questions
One of 984 original 350-601 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 →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 350-601 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 350-601 exam.