500-920 · Question #1
Which command sequence is required to reset Cisco Integrated Management Controller (IMC) of a Cisco UCS Server?
The correct answer is B. scope cimc | reset | commit-buffer. Option B is correct because Cisco UCS Manager CLI uses a scope-based hierarchy - scope cimc navigates into the CIMC context, reset initiates the reset action, and commit-buffer is the standard command required to apply any pending changes in UCSM CLI sessions. Why the distractors
Question
Which command sequence is required to reset Cisco Integrated Management Controller (IMC) of a Cisco UCS Server?
Options
- Aconnect cimc | reset | validate
- Bscope cimc | reset | commit-buffer
- Cconnect cimc | reset | commit
- Dscope cimc | reset | validate
How the community answered
(48 responses)- A2% (1)
- B92% (44)
- C4% (2)
- D2% (1)
Explanation
Option B is correct because Cisco UCS Manager CLI uses a scope-based hierarchy - scope cimc navigates into the CIMC context, reset initiates the reset action, and commit-buffer is the standard command required to apply any pending changes in UCSM CLI sessions.
Why the distractors fail:
- A & C use
connect cimc, which opens a direct terminal session to the CIMC (similar to SSH) rather than navigating the UCSM CLI scope - it's a different command paradigm entirely. Additionally, C usescommitwhich is not a valid UCSM CLI commit command. - D uses the correct
scope cimcentry point but replacescommit-bufferwithvalidate, which is not the command that applies changes;validatechecks syntax/config but does not execute the action.
Memory tip: In UCSM CLI, remember "Scope → Act → Commit-buffer" - every configuration change follows this three-step pattern. If you see connect instead of scope, or validate/commit instead of commit-buffer, it's wrong for UCSM CLI operations.
Topics
Community Discussion
No community discussion yet for this question.