350-401 Question 333
Single answerA network administrator wants to automate the collection of interface error statistics on a Cisco router whenever the interface goes down. They decide to use an Embedded Event Manager (EEM) applet. Which EEM applet configuration would achieve this goal?
- A
event manager applet InterfaceDown event syslog pattern "%LINK-5-CHANGED: Interface .* changed state to administratively down" action 1.0 cli command "show interfaces"
- B
event manager applet InterfaceDown event interface name GigabitEthernet0/1 state down action 1.0 cli command "show interfaces"
- C
event manager applet InterfaceDown event timer cron cron-entry "0 0 * * *" action 1.0 cli command "show interfaces"
- D
event manager applet InterfaceDown event none action 1.0 cli command "show interfaces"
Show answer and explanation
Correct answer: B
Explanation
The correct answer is Option 2, as it uses the 'event interface' trigger to monitor the status of a specific interface and execute the desired command ('show interfaces') when the interface state changes to down. This directly aligns with the requirement to automate data collection upon an interface-down event. Other options either use inappropriate triggers (e.g., syslog pattern, cron timer, or none) or fail to address the scenario properly.
- A. Incorrect.
This configuration uses an 'event syslog' trigger, which matches a syslog pattern for an administratively down state. However, it does not specifically capture the event of an interface going down due to an issue, and the trigger may not execute as intended.
- B. Correct.
This configuration correctly uses the 'event interface' trigger to monitor a specific interface (GigabitEthernet0/1) and execute the 'show interfaces' command when the interface state goes down, making it the most appropriate solution.
- C. Incorrect.
This configuration uses a 'cron' timer event, which triggers at scheduled intervals, regardless of the interface state. It does not fulfill the requirement to collect data specifically when the interface goes down.
- D. Incorrect.
This configuration uses the 'event none' trigger, which does not respond to any specific condition or event. It is not suitable for automating data collection when an interface goes down.