How to Block Configuration Mode Using Cisco EEM Applets?
Refer to the exhibit. An engineer constructs an EEM applet to prevent anyone from entering configuration mode on a switch. Which snippet is required to complete the EEM applet? - 
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
It tests precise knowledge of EEM execution timing and parameter validity, with the common trap being the misconception that 'sync yes' can be paired with 'skip' to control command execution.
This question evaluates the correct configuration of Cisco Embedded Event Manager (EEM) applets to intercept and block specific CLI commands. Community consensus strongly supports 'sync no skip yes' as the required syntax to asynchronously trigger the applet and prevent the original command from executing.
Candidates frequently select 'sync yes skip no' or 'sync yes skip yes', incorrectly assuming synchronous execution allows the applet to gatekeep the CLI command, when in reality 'sync yes' does not support the 'skip' parameter and executes differently.
Community Discussion (9 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
EEM Command Interception Fundamentals
Cisco Embedded Event Manager (EEM) allows administrators to automate responses to system events, including CLI command triggers. To prevent users from entering configuration mode viaconfigure terminal, an EEM applet must intercept the command before it reaches the CLI parser.Decoding the Syntax Parameters
The critical piece missing in the exhibit is the synchronization and skipping directive appended to theevent cli pattern line:
- sync no: Configures the applet to run asynchronously ahead of the matched CLI command. This ensures the EEM script executes first, giving it the opportunity to log messages, send alerts, or modify state before the original command proceeds.
- skip yes: Explicitly instructs the router/switch to discard the original CLI command after the EEM applet finishes. Without this flag, the command would still execute regardless of the applet's actions.
Why Option B is Correct
Option B (sync no skip yes) is the only valid combination that achieves the stated goal. As noted by community experts,sync no guarantees the applet runs first, and skip yes actively blocks configure terminal from ever taking effect. This pair is specifically designed for command interception and policy enforcement.Why the Other Options Fail
- Option A & D (sync yes ...): The
sync yesparameter changes the execution model entirely. It typically waits for the CLI command to complete or runs concurrently, and critically, IOS does not support theskipkeyword whensync yesis configured. Attempting this in a real device will result in a syntax error. - Option C (sync no skip no): While
sync nocorrectly prioritizes the applet,skip notells the system to proceed with the original CLI command afterward. This defeats the entire purpose of blocking configuration mode.
Official Reference
Exam Strategy
When answering EEM applet questions, always map the business requirement to execution timing first. If the goal is to intercept or block a command, immediately look for 'sync no skip yes'; if the goal is to run additional tasks after a command succeeds, use 'sync no skip no'. Always verify parameter compatibility, as IOS restricts certain flags based on the sync setting.
Related Analysis
Practice All 350-401 Questions
Access 218 questions with complete answers and detailed explanations.
View Full 350-401 Practice Test →