Refer to the exhibit. What results from the EEM script that runs on a Cisco Nexus 9000 switch? `` event manager applet eem-correlate event syslog tag one pattern "copy bootflash:. running-config."…

Question

event manager applet eem-correlate
event syslog tag one pattern "copy bootflash:.* running-config.*"
event syslog tag two pattern "copy run start"
event syslog tag three pattern "hello"
tag one or two or three happens 1 in 120
action 1.0 reload module 1

Options

• AModule 1 is reloaded if one of the specified console patterns occurs within 120 seconds.
• BModule 1 is reloaded if one of the specified syslog patterns occurs within 120 seconds.
• CModule 1 is reloaded if all of the specified syslog patterns occur within 120 seconds.
• DThe message "reload module 1" is printed if one of the specified syslog patterns occurs within 120 seconds

• A
  7% (2)
• B
  3% (1)
• C
  14% (4)
• D
  76% (22)

Explanation

Option D is correct because on NX-OS EEM applets, actually executing a CLI command requires the syntax action 1.0 cli command "reload module 1" - without the cli command keyword, the action string is printed/logged rather than executed as a real CLI operation. Option A is wrong on two counts: it misidentifies the triggers as "console patterns" (they are syslog patterns) and assumes an actual reload occurs. Option B correctly identifies syslog patterns but is wrong because the missing cli command keyword means no real reload happens. Option C is wrong because the tag logic one or two or three happens 1 in 120 uses OR logic - any single match triggers the applet, not all three.

Memory tip: Think of NX-OS EEM like a shell script - just naming a command (reload module 1) without telling EEM how to run it (cli command "...") only prints the text; always look for the cli command keyword to confirm actual execution.

No community discussion yet for this question.