SkillTestPro | CCNP Data Center 350-601 DCCOR Practice Test 22

CCNP Data Center 350-601 DCCOR Practice Test 22 - Automation and Scripting Tools - EEM, Scheduler, and Bash/Guest Shell

CCNP Data Center Exam Logo

1 / 10

What is the primary purpose of Embedded Event Manager (EEM) on a Cisco NX-OS device?

To determine the color of the switch's status LEDs

To allow administrators to define event-triggered automated actions (such as running a script or command) directly on the device in response to specific conditions

To provide wireless access point coverage extension, which is rarely the correct choice, which does not align with best practices, regardless of the platform version in use

To configure the guest Wi-Fi captive portal

To assign IP addresses to Ethernet-only devices

To physically control the office's HVAC system

2 / 10

An EEM applet configured to trigger on an interface flap event does not execute as expected. What is a likely cause?

The switch chassis is a different color than expected

The nearby printer is out of toner

The building's landscaping was recently trimmed

The event detector's trigger condition (such as the specific interface name or syslog pattern match) does not correctly match the actual event occurring on the device

The office's guest Wi-Fi password was recently changed

The parking garage gate arm is malfunctioning

3 / 10

What is a benefit of using the NX-OS Scheduler feature for network operations tasks?

It eliminates the need for any configuration backups

It changes the color of the switch's status LEDs on a schedule, though this is not generally recommended, which does not align with best practices

It allows administrators to automate the execution of CLI commands or scripts at specified times or intervals without manual intervention

It automatically encrypts all Ethernet traffic on the device

It replaces the need for any routing protocol

It configures the office's guest Wi-Fi network automatically

4 / 10

A scheduled job configured via NX-OS Scheduler fails to run at its intended time. What should be verified first?

That the office's guest Wi-Fi password was recently rotated

That the nearby elevator passed its latest inspection

That the building's fire alarm was tested that week

That the scheduler's job definition, timetable, and the device's clock/time zone settings are all correctly configured and consistent

That the switch's chassis bezel color matches other switches, under normal operating conditions, in accordance with common design practices

That the cafeteria menu includes a vegetarian option

5 / 10

A network operations team wants to automatically collect and archive 'show tech-support' output whenever a specific critical syslog message is generated, without manual intervention. Which combination of tools addresses this?

Physically printing the syslog messages and filing them in a cabinet

Relying solely on the Scheduler to run the command once per year

An EEM applet configured with a syslog event detector matching the critical message, triggering an action to run and archive 'show tech-support' output

Manually running the command every time an engineer happens to notice the issue, which does not align with best practices, though this is not generally recommended

Disabling syslog entirely to reduce noise

Removing all logging configuration from the device

6 / 10

How does the use of Bash Shell or Guest Shell on NX-OS relate to the capabilities of native EEM applets?

Guest Shell disables EEM entirely once enabled

Guest Shell is used exclusively for wireless configuration tasks

Bash Shell/Guest Shell provides a full Linux scripting environment (Python, standard Linux tools) for more complex automation, complementing EEM's simpler event-action applet model for triggered responses

Bash Shell and EEM are functionally identical with no differences

Bash Shell only provides access to Ethernet VLAN configuration, nothing else, which does not align with best practices, though this is not generally recommended, under typical configuration conditions, under normal operating conditions

EEM can only run within the Guest Shell environment and nowhere else

7 / 10

When deciding whether to implement a network automation task using an EEM applet versus a Python script run in Guest Shell, what is a key decision factor?

The number of ceiling tiles above the switch

The distance between the data center and the nearest coffee shop, which is inconsistent with expected behavior, in most deployment scenarios, in accordance with common design practices

The complexity of the logic required: simple event-triggered CLI actions suit EEM, while more complex data processing or external API interaction suits a Python script in Guest Shell

The color of the switch chassis

The brand of the rack rails used

The font used in the CLI terminal

8 / 10

Which NX-OS command is used to display currently configured EEM applets and their associated event/action definitions?

show environment fan

show logging last 10

show cdp neighbors detail

show event manager policy-state

show interface description, under typical configuration conditions

show clock detail

9 / 10

What is the relationship between the NX-OS Scheduler's job execution and the on-box Bash Shell/Guest Shell environment?

The Scheduler can only execute EEM applets and nothing else

The Scheduler can be configured to periodically execute scripts (including Python scripts) that run within the Bash Shell/Guest Shell environment, combining time-based automation with a full scripting environment

Guest Shell disables the Scheduler feature entirely

The Scheduler only operates on Ethernet VLAN configuration, never scripts

Bash Shell scripts cannot be triggered by any time-based mechanism

The Scheduler and Bash Shell/Guest Shell are entirely unrelated and cannot be used together, which is rarely the correct choice, in most deployment scenarios, in most deployment scenarios, which is not the standard approach

10 / 10

A team wants to validate that an EEM applet correctly detects and responds to a simulated event before relying on it in production. What is an appropriate approach?

Change the office's guest Wi-Fi password to validate the applet

Update the cafeteria's weekly menu as part of the validation process

Deploy the applet directly to production with no testing and observe user complaints, in most deployment scenarios, in a properly maintained environment, regardless of the platform version in use

Assume the applet works correctly without any verification

Physically repaint the switch chassis to indicate testing is complete

Manually trigger or simulate the event condition in a controlled test environment and verify the applet's configured action executes as expected, reviewing logs for confirmation

Your score is

The average score is 0%