Refer to the exhibit. A network administrator must delete a feature group from a Cisco Nexus 5000 Series Switch. Which action resolves the issue?

Question

Exhibits

Options

• ADetach the association with the no rule command within the role configuration mode
• BDetach the association with the no role command within the feature-group configuration mode
• CDetach the association with the no rule command within the feature-group configuration
• DDetach the association with the no role command within the role configuration mode

• A
  82% (14)
• C
  6% (1)
• D
  12% (2)

Explanation

Option A is correct because on Cisco Nexus 5000 switches, the association between a role and a feature group is created using a rule command within role configuration mode - so removing that association requires no rule in the same context before the feature group can be deleted.

Why the distractors fail:

• B uses no role (wrong command) and targets feature-group configuration mode (wrong context) - the association is managed from the role side, not the feature-group side.
• C gets the command right (no rule) but applies it in feature-group configuration mode - rules are configured under the role, not under the feature group.
• D is in the correct mode (role configuration) but uses no role instead of no rule - role is not the command used to manage feature-group associations within a role.

Memory tip: Think "Roles own the Rules." Feature-group associations are defined as rules inside the role, so you always enter role config mode and use (no) rule to attach or detach a feature group - never the other way around.

No community discussion yet for this question.