What happens when you make changes from Clish on the SMO Master?

Question

Options

• AThe changes are synchronized to the SMS/MDS as a backup.
• BThe changes are synchronized to the MHO as a backup.
• CChanges are only applied on the SMO Master.
• DChanges are applied to all members in the SG.

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

Explanation

Making changes via Clish (the command-line shell) directly on the SMO Master applies those changes locally only - Clish operates at the device level and does not trigger any synchronization mechanism to other nodes or management layers. This is a critical distinction from changes made through the graphical management interface, which do propagate across the management infrastructure.

Why the distractors are wrong:

• A is wrong because Clish changes do not sync to the SMS/MDS - synchronization between management tiers happens through the management plane, not CLI-level edits.
• B is wrong for the same reason; the MHO is not a target for Clish-originated changes, and no backup sync occurs from local CLI modifications.
• D is wrong because applying a change to all SG members requires pushing policy or configuration through the management system - a local Clish command has no awareness of or reach to other group members.

Memory tip: Think of Clish as a "local screwdriver" - whatever you tighten on that one box stays on that box. To affect the whole group, you need the management console, which acts as the "remote control" for all members.

No community discussion yet for this question.