Refer to the exhibit. After an unexpected reload of the Cisco Nexus 9000 Series Switch, the network administrator noticed that one of the Software Maintenance Upgrades (SMU) images is inactive. The…

Question

Exhibits

Options

• ACommit the package using the install commit command.
• BSave the running configuration after activating the package.
• CDeactivate and uninstall the active core package.
• DCopy the SMU package file on the bootflash.

• A
  73% (36)
• B
  4% (2)
• C
  16% (8)
• D
  6% (3)

Explanation

On Cisco NX-OS, activating an SMU only applies the patch to the running system - it does not survive a reload unless you run install commit, which persists the activated package to the install database so it remains active after future reloads. Option A is the only action that completes the three-step install workflow: add → activate → commit.

Why the distractors are wrong:

• B - copy running-config startup-config saves device configuration (interfaces, routing, etc.), but the SMU activation state is tracked separately in the install infrastructure, not in the running config.
• C - Deactivating and uninstalling a package removes it; this is the opposite of preserving it.
• D - Copying the file to bootflash only ensures the binary is present on the device. Without add/activate/commit steps, the file does nothing on its own.

Memory tip: Think of SMU installation like editing a document - activating is making edits in memory, and install commit is hitting Save. If you close the file (reload) without saving, your changes are lost.

No community discussion yet for this question.