The answer is a firmware version mismatch between the server’s CIMC and the Fabric Interconnect. When a UCS server is stuck in “Discovery: In Progress” state, even after a chassis power-cycle and with correct FEX fabric port configuration, the Fabric Interconnect cannot complete its inventory and management handshake with the server’s Cisco Integrated Management Controller. If the CIMC firmware is incompatible with the FI’s firmware version, the discovery process hangs indefinitely because the FI cannot properly communicate with or provision the server. On the Cisco DCCOR / CCNP Data Center Core 350-601 exam, this scenario tests your understanding of UCS server lifecycle states and the critical role of firmware consistency across the management plane. A common trap is to blame physical cabling or port configuration, but the real culprit is almost always a version mismatch. Memory tip: “CIMC and FI must agree to see” — if their firmware versions don’t match, discovery will never complete.
350-601 Compute Practice Question
This 350-601 practice question tests your understanding of compute. 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 CCNP engineer is troubleshooting a UCS environment where a server is stuck in 'Discovery: In Progress' state. The chassis has been power-cycled, but the issue persists. FEX fabric port is configured correctly. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Firmware version mismatch between the server's CIMC and the Fabric Interconnect.
When a server is stuck in 'Discovery: In Progress' state and the chassis has been power-cycled with correct FEX fabric port configuration, the most likely cause is a firmware version mismatch between the server's Cisco Integrated Management Controller (CIMC) and the Fabric Interconnect (FI). During discovery, the FI attempts to inventory and manage the server via CIMC; if the firmware versions are incompatible, the discovery process cannot complete, leaving the server in a perpetual 'In Progress' state.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Incorrect IP address on the Fabric Interconnect management interface.
Why it's wrong here
That would affect management connectivity but not server discovery specifically.
✓
Firmware version mismatch between the server's CIMC and the Fabric Interconnect.
Why this is correct
CIMC firmware must match the FI's supported version for discovery to complete.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The chassis is not connected to the FI via a valid fabric cable.
Why it's wrong here
Power cycling would likely resolve if it were a simple cabling issue.
✗
The server's service profile is not associated.
Why it's wrong here
Service profile association happens after discovery.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the misconception that a server stuck in discovery is due to a physical connectivity issue (Option C) or a service profile association problem (Option D), when in fact the root cause is a firmware version mismatch that prevents the FI from completing the inventory handshake.
Detailed technical explanation
How to think about this question
The discovery process uses the Fabric Interconnect's internal discovery protocol (e.g., Cisco Discovery Protocol or a proprietary exchange) to query the CIMC for its firmware version, hardware inventory, and capabilities. If the CIMC firmware is older or newer than what the FI supports, the FI may reject the discovery response or fail to parse it, causing the state to hang. In real-world scenarios, this often occurs after a firmware upgrade on the FI without correspondingly updating the server CIMC firmware, or when a new server model is introduced with a different CIMC version.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Compute — This question tests Compute — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Firmware version mismatch between the server's CIMC and the Fabric Interconnect. — When a server is stuck in 'Discovery: In Progress' state and the chassis has been power-cycled with correct FEX fabric port configuration, the most likely cause is a firmware version mismatch between the server's Cisco Integrated Management Controller (CIMC) and the Fabric Interconnect (FI). During discovery, the FI attempts to inventory and manage the server via CIMC; if the firmware versions are incompatible, the discovery process cannot complete, leaving the server in a perpetual 'In Progress' state.
What should I do if I get this 350-601 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
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.