Courseiva
ComputehardMultiple ChoiceObjective-mapped

350-601 Compute Practice Question

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?

⚠ Common exam trap

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.

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

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.

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.

  • 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.

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 →

How Courseiva writes practice questions · Editorial policy

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.