350-401 Question 331
Single answerA network engineer is tasked with automating the process of collecting interface status data on a Cisco router whenever an interface goes down. They decide to use an Embedded Event Manager (EEM) applet for this purpose. Which of the following EEM applet configurations is correct?
- A
event manager applet Interface_Down event syslog pattern "%LINEPROTO-5-UPDOWN:.*down" action 1.0 cli command "show ip interface brief"
- B
event manager applet Interface_Down event timer countdown time 60 action 1.0 cli command "show ip interface brief"
- C
event manager applet Interface_Down event interface name GigabitEthernet0/0 state down action 1.0 cli command "show ip interface brief"
- D
event manager applet Interface_Down event neighbor-discovery interface GigabitEthernet0/0 state down action 1.0 cli command "show ip interface brief"
Show answer and explanation
Correct answer: C
Explanation
The 'event interface' trigger is specifically designed to monitor the operational state of network interfaces. In this scenario, the engineer needs to automate a response to an interface going down, and the third option correctly uses the 'event interface' trigger with the appropriate state condition ('down'). Other triggers, like syslog patterns, timers, or neighbor-discovery events, are either less precise or unrelated to the task.
- A. Incorrect.
This option uses a syslog pattern to detect interface down events; however, it is not the most efficient or targeted method for this scenario. Using the 'event interface' trigger is more appropriate for interface state monitoring.
- B. Incorrect.
This option uses a timer-based event trigger, which is unrelated to interface state changes. It does not fulfill the requirement of monitoring and responding to interface down events.
- C. Correct.
This is the correct configuration. The 'event interface' trigger specifically monitors the state of the specified interface (GigabitEthernet0/0) for a down event, making it the most suitable choice for this scenario.
- D. Incorrect.
This option incorrectly uses the 'neighbor-discovery' trigger, which is intended for events related to neighbor discovery protocols like CDP or LLDP, not interface state changes.