https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/eem/command/eem-cr-book/eem-cr-e1.html EEM usually schedules and executes policies based on an event specification that is included inside the policy itself. The event manager run command lets policies be run manually. The event none command has to be configured first to run the policy manually. The None Event Detector includes arguments when it publishes the none event. This command has no no form.

A. event manager applet ondemand event none action 1.0 syslog priority critical msg "This is a message from ondemand" B. event manager applet ondemand action 1.0 syslog priority critical msg "This is a message from ondemand" C. event manager applet ondemand event register action 1.0 syslog priority critical msg "This is a message from ondemand" D. event manager applet ondemand event manual action 1.0 syslog priority critical msg "This is a message from ondemand" The correct answer is: A

Concur with edg, action none first, then event manager run to kick it off manually.

Selected Answer: A cisco_R5#sh runn | b event event manager applet boom event syslog pattern "UP" action 1.0 puts "logging directly to console" event manager applet ondemand event none action 1.0 syslog priority critical msg "Hello WORLD)))" ! end cisco_R5#event manager run ondemand cisco_R5# *Dec 20 17:41:10.545: %HA_EM-2-LOG: ondemand: Hello WORLD))) cisco_R5#

Selected Answer: D The reason is that event none is not a valid event in Cisco EEM (Embedded Event Manager). The event none command doesn't exist as an event type for configuring an applet. To run an EEM applet manually, the event you should use is event manual, as in option D.

Selected Answer: A Router#sh run | s even event manager applet ondemand event none action 1.0 syslog priority critical msg "This is bullshit" Router#event manager run ondemand Router# *Apr 12 04:00:56.303: %HA_EM-2-LOG: ondemand: This is bullshit Router#

correct, you will see the syslog message when you type this cli comand: #event manager run ondemand

Selected Answer: A event manager applet ondemand: Creates an applet in the EEM registry with the name 'ondemand'. event none: Means the event type is none, so nothing will trigger the event, and it can only be run manually. action 1.0: This is the first action to run (in this example, there is only one action). syslog priority critical msg 'This is a message from ondemand': This action sends the message 'This is a message from ondemand' to the Syslog server with a severity level of critical.