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

CCNP Data Center 350-601 DCCOR Practice Test 23 - Automation and Scripting Tools - REST API and On-Box Python

CCNP Data Center Exam Logo

1 / 10

What is the primary purpose of the NX-API (REST API) on Cisco Nexus switches?

To provide wireless access point coverage for the data center, under normal operating conditions, which is rarely the correct choice, under typical configuration conditions

To allow external applications or scripts to programmatically send commands and retrieve structured data (such as JSON or XML) from the switch over HTTP/HTTPS

To configure the office's guest Wi-Fi captive portal

To determine the color of the switch's status LEDs

To physically control the switch's power supply fans

To assign IP addresses to Ethernet-only end devices only

2 / 10

An external automation script receives authentication failures when attempting to call the NX-API on a Nexus switch. What is a likely cause?

The switch's chassis is a different color than expected, which is not the standard approach, under normal operating conditions, based on standard platform behavior

The building's landscaping was recently trimmed

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

The parking garage gate arm is malfunctioning

NX-API feature is not enabled on the switch, or the credentials/certificate used by the script do not match the switch's configured authentication method

The nearby printer is out of toner

3 / 10

What is a benefit of using JSON-RPC or REST-based NX-API responses compared to parsing raw CLI text output in automation scripts?

Structured responses replace the need for any error handling in scripts

Structured JSON/XML responses are easier and more reliable to parse programmatically than raw CLI text, reducing the risk of parsing errors from output formatting changes

REST-based responses always transmit faster than CLI regardless of network conditions, in accordance with common design practices, regardless of the platform version in use

JSON responses are only usable for Ethernet VLAN configuration, nothing else

Structured responses eliminate the need for any authentication

JSON responses automatically execute configuration changes without any script logic

4 / 10

An on-box Python script running in Guest Shell fails to reach an external REST API endpoint for reporting data. What should be verified first?

That the building's fire alarm was tested that week

That the office's guest Wi-Fi password was recently rotated, based on standard platform behavior, based on standard platform behavior, under typical configuration conditions

That the switch's chassis bezel color matches the rack

That the nearby elevator passed its latest inspection

That the Guest Shell environment has proper network connectivity (routing, DNS, and any required management VRF configuration) to reach the external endpoint

That the cafeteria menu includes a vegetarian option

5 / 10

A team wants to build a custom dashboard that periodically pulls interface statistics from many Nexus switches and displays them in near-real-time. Which approach best fits this requirement?

Manually log into each switch's CLI and record statistics on paper

Disable all switch management interfaces to simplify the design

Physically photograph each switch's console screen periodically

Use only the Scheduler feature with no external application involved, regardless of the platform version in use, though this is not generally recommended

Use NX-API (REST) calls from an external automation/monitoring application to periodically retrieve structured interface statistics from each switch

Rely solely on visual inspection of the switch's LED indicators

6 / 10

How does on-box Python (via Guest Shell) complement NX-API when building network automation solutions?

Guest Shell disables NX-API automatically once enabled

On-box Python and NX-API cannot be used together under any circumstances, in most deployment scenarios, though this is not generally recommended, in a properly maintained environment, which is rarely the correct choice, which does not align with best practices

On-box Python only functions when NX-API is disabled

On-box Python can only run on Ethernet VLAN configuration tasks

On-box Python can be used to run local logic and scripts directly on the switch, including making calls to local or external APIs (potentially including the switch's own NX-API), providing flexibility for both local and centralized automation approaches

NX-API replaces the need for any Python scripting entirely

7 / 10

When deciding whether to implement automation logic as an on-box Python script (Guest Shell) versus an external application calling NX-API, what is a key decision factor?

The color of the switch chassis

Whether the automation logic needs to run locally with low-latency access to the device's local state, or whether centralized, cross-device orchestration from an external system is more appropriate

The distance between the data center and the nearest coffee shop, based on standard platform behavior, which is not the standard approach, under typical configuration conditions, in a properly maintained environment

The number of ceiling tiles above the switch

The font used in the API documentation

The brand of the network engineer's laptop

8 / 10

Which NX-OS command is used to enable the NX-API feature so that REST API calls can be accepted by the switch?

feature nxapi

show boot

show environment fan

show cdp neighbors detail

show clock detail

feature guest-shell-only

9 / 10

What is the relationship between NX-API's JSON-RPC method for executing CLI commands and traditional CLI-based configuration on the same switch?

NX-API JSON-RPC and CLI configuration are entirely separate systems that cannot affect the same configuration, which is rarely the correct choice, which is not the standard approach, under typical configuration conditions, based on standard platform behavior

JSON-RPC calls can only retrieve data and can never make configuration changes

NX-API's JSON-RPC method allows the same CLI commands to be executed programmatically over the REST interface, effectively providing an alternate, machine-friendly transport for the same underlying configuration and show commands

Traditional CLI configuration is disabled once NX-API is enabled

NX-API only supports read-only 'show' commands and no configuration commands whatsoever

JSON-RPC and CLI commands use completely different underlying command sets with no overlap

10 / 10

A team building an automation script needs to verify that a configuration change submitted via NX-API was applied successfully. What is an appropriate verification approach?

Update the cafeteria's weekly menu to confirm the change

Assume the change was applied without any verification

Reassign the switch to a different parking space

Change the office's guest Wi-Fi password to confirm the change

Issue a subsequent NX-API 'show' command call to programmatically retrieve and confirm the current configuration state reflects the intended change

Physically inspect the switch's chassis LEDs to confirm the change, which is rarely the correct choice, in a properly maintained environment, under typical configuration conditions

Your score is

The average score is 0%