Which statement best describes managing Cisco UCS servers using NX-OS CLI on the Fabric Interconnects?

Question

Options

• AThe NX-OS CLI on the Fabric Interconnects allows you to view, but not change the connectivity
• BThe NX-OS CLI on the Fabric Interconnects allows you to manage QoS parameters on the Fabric
• CThe NX-OS CLI on the Fabric Interconnects allows you to change the connectivity configuration
• DThe NX-OS CLI on the Fabric Interconnects allows you to change the connectivity configuration

• B
  3% (1)
• C
  7% (2)
• D
  90% (26)

Explanation

Option D is correct because the NX-OS CLI on Cisco UCS Fabric Interconnects does provide the ability to change connectivity configuration - it is not strictly a read-only interface, which makes option A incorrect and the most common trap answer on this topic.

Note that options C and D appear identical in this question, which is likely a typo; in the original source, one of them probably carried a different qualifier (such as "partially" or "only under specific conditions"), so treat D as the intended best answer.

Option B is wrong because QoS policy management in UCS is handled through UCS Manager (UCSM), not directly via the NX-OS CLI on the Fabric Interconnect - conflating the two management planes is a common misconception.

Memory tip: Think of the Fabric Interconnect's NX-OS CLI as a "full-access terminal" - unlike pure monitoring tools, it lets you read and write connectivity settings, but Cisco best practice is to use UCSM for policy-driven management to avoid configuration drift.

No community discussion yet for this question.