The answer is to verify that the new switch's target-facing interfaces are not in shutdown state. This is correct because when integrating a new Cisco MDS switch into an existing Fibre Channel SAN, the most common oversight after cabling and zone configuration is that the target-facing ports remain in an administrative shutdown state by default, preventing storage targets from being discovered by initiators even when the ISL and VSAN are fully operational. On the Cisco DCCOR / CCNP Data Center Core 350-601 exam, this scenario tests your understanding of MDS interface states and the integration workflow—specifically that a zone set activation and ISL bring-up do not automatically enable target-facing interfaces. A common trap is to assume the issue lies with domain ID conflicts or zone set propagation, but since the ISL is up and FCIDs are exchanged, the logical next step is to check the interface configuration on the new switch. Memory tip: "Shutdown stops the show—always check port admin state before chasing zones or domains."
350-601 Storage Network Practice Question
This 350-601 practice question tests your understanding of storage network. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A storage administrator has been tasked with integrating a new Cisco MDS 9706 switch into an existing Fibre Channel SAN. The existing SAN consists of two Cisco MDS 9148S switches configured in a VSAN 100 with a single zone set that contains all initiator and target WWPNs. The administrator connects the new switch to one of the existing switches using an ISL and configures the new switch with VSAN 100 and the same zone configuration. The administrator activates the zone set on the new switch and verifies that the ISL is up and both switches see each other's Fibre Channel IDs. However, servers attached to the existing switches still cannot discover the storage targets that are connected to the new switch. The administrator has confirmed that the ISL is operational and that the zone set on the new switch is activated with the correct WWPNs. What should the administrator check next?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Verify that the new switch's target-facing interfaces are not in shutdown state.
The most likely cause is that the target-facing interfaces on the new switch are in administrative shutdown. The first logical next step is to verify that the interfaces to the storage targets are not shutdown (Option A). Option B is already confirmed. Option C is not necessary in a single VSAN environment. Option D is unlikely because the ISL is operational, indicating no domain ID conflict.
Key principle: A trunk being up does not mean the VLAN is allowed across it. Always verify the allowed VLAN list and whether the VLAN exists on both switches.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Confirm that the zone set on the new switch is activated and contains correct WWPNs.
Why it's wrong here
Already confirmed, so this is not the issue.
✗
Ensure that the trunk protocol is enabled on the ISL and that allowed VSANs include VSAN 100.
Why it's wrong here
ISL works without trunk if both sides are in the same VSAN; not required.
✗
Check that the new switch's domain ID is unique and not conflicting.
Why it's wrong here
Domain IDs are already resolved since the ISL is up and FC IDs are seen.
✓
Verify that the new switch's target-facing interfaces are not in shutdown state.
Why this is correct
Interfaces must be administratively enabled to allow login.
Related concept
Access ports place end devices into a single VLAN.
Common exam traps
Common exam trap: an active trunk can still block the VLAN you need
A trunk being up does not prove every VLAN is crossing it. Check allowed VLAN lists, native VLAN mismatch, VLAN existence and access-port assignment.
Detailed technical explanation
How to think about this question
VLAN questions usually combine access-port and trunking clues. The key is to identify whether the issue is local to one switchport, caused by the trunk, or caused by the VLAN not existing where it needs to exist.
KKey Concepts to Remember
Access ports place end devices into a single VLAN.
Trunk ports carry multiple VLANs between switches.
Allowed VLAN lists decide which VLANs can cross a trunk.
Native VLAN mismatch can create confusing symptoms.
TExam Day Tips
→Use show vlan brief to verify access VLANs.
→Use show interfaces trunk to verify trunk state and allowed VLANs.
→Do not treat every same-VLAN issue as a routing problem.
Key takeaway
A trunk being up does not mean the VLAN is allowed across it. Always verify the allowed VLAN list and whether the VLAN exists on both switches.
Real-world example
How this comes up in practice
A help-desk technician troubleshoots why a newly connected PC cannot reach shared printers on the same floor. The cable is good, the switch port is active, but the PC is in VLAN 20 and the printers are in VLAN 10. The uplink trunk only allows VLAN 10. A trunk being up does not mean every VLAN crosses it.
What to study next
Got this wrong? Here's your next step.
Review VLAN allowed lists, native VLAN mismatch detection, and how to verify VLAN membership with show vlan brief and show interfaces trunk. Then practise related 350-601 questions on switching, trunking, and access-port configuration.
Storage Network — This question tests Storage Network — Access ports place end devices into a single VLAN..
What is the correct answer to this question?
The correct answer is: Verify that the new switch's target-facing interfaces are not in shutdown state. — The most likely cause is that the target-facing interfaces on the new switch are in administrative shutdown. The first logical next step is to verify that the interfaces to the storage targets are not shutdown (Option A). Option B is already confirmed. Option C is not necessary in a single VSAN environment. Option D is unlikely because the ISL is operational, indicating no domain ID conflict.
What should I do if I get this 350-601 question wrong?
Review VLAN allowed lists, native VLAN mismatch detection, and how to verify VLAN membership with show vlan brief and show interfaces trunk. Then practise related 350-601 questions on switching, trunking, and access-port configuration.
What is the key concept behind this question?
Access ports place end devices into a single VLAN.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.