350-601 Storage Network Practice Question
A large enterprise uses Cisco Nexus 5548UP switches in FCoE mode. The storage array is connected via native FC to an MDS 9700. The FCoE switches are connected to the MDS via FC uplinks. Recently, the storage team deployed a new FCoE initiator that requires access to a specific LUN. After configuring the zone and VSAN, the initiator cannot discover the target. The zone includes the pWWN of the target and the FCoE initiator's pWWN (derived from its MAC address). The initiator is in VSAN 100, and the target is in the same VSAN. The MDS show flogi database shows the initiator. The show fcoe database on the Nexus shows the initiator but the session is not active (state: FIP-VN_Port not logged in). The engineer checks the FIP snooping policy and notices that the FCoE VLAN to VSAN mapping is correct. What is the most likely issue?
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 FIP snooping policy is blocking the FLOGI
The FCoE initiator appears in the FCoE database but is not logged in, indicating the FLOGI is being dropped. The FIP snooping policy on the Nexus switch may be blocking the FLOGI traffic because the initiator's MAC address is not in the allowed FCoE MAC list or the policy is misconfigured. Incorrect VN_Port MAC would prevent FCoE database entry, NPV is not required for FCoE native mode, and routing is not an issue within the same VSAN.
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 MDS does not have a route to the FCoE initiator's VSAN
Why it's wrong here
The initiator and target are in the same VSAN, so routing is irrelevant.
- ✗
The FCoE initiator is not using the correct VN_Port MAC address
Why it's wrong here
If the MAC were incorrect, the initiator would not appear in the FCoE database.
- ✓
The FIP snooping policy is blocking the FLOGI
Why this is correct
FIP snooping uses ACLs to enforce zoning; if misconfigured, it can drop FLOGI frames.
- ✗
The FCoE NPV is not enabled on the Nexus
Why it's wrong here
NPV is not required for this topology; the Nexus is in FCoE mode, not NPV.
Visual reference
Quick reference
Access Control Model Comparison
| Model | Acronym | Who Controls Access? | Best For |
|---|---|---|---|
| Discretionary Access Control | DAC | Resource owner | Small teams, file shares |
| Mandatory Access Control | MAC | System / security labels | Classified govt / military |
| Role-Based Access Control | RBAC | Administrator (via roles) | Enterprise environments |
| Attribute-Based Access Control | ABAC | Policy engine (user + resource attributes) | Fine-grained, dynamic policies |
| Rule-Based Access Control | RuBAC | System rules / ACLs | Firewall rules, network ACLs |
Go deeper
Related to this question
About these practice questions
This 350-601 question is part of Courseiva's 984-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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.