350-601 Practice Test 25 — 15 Questions

Question 1

Refer to the exhibit. What is the intended effect of this Ansible playbook task?

Accepted Answer

It ensures VLAN 10 exists with the name 'Automation_VLAN' on the target switches.. The Ansible playbook task uses the `cisco.nxos.nxos_vlans` module with the `state: merged` directive, which ensures that the specified VLAN configuration (VLAN 10 with name 'Automation_VLAN') is present on the target Nexus switches. If VLAN 10 does not exist, it will be created; if it exists with a different name, it will be updated. The `merged` operation does not delete or reboot; it only applies the configuration to align the device's state with the playbook's desired state.

Answer

It deletes VLAN 10 from all switches.

Answer

It saves the running configuration to startup.

Answer

It reboots the Nexus switches after applying the configuration.

Question 2

A network team is planning to automate configuration management of a brownfield Nexus 9000 fabric using YANG data models and NETCONF. Which consideration is critical when implementing this solution?

Accepted Answer

The operational state must be modeled against the device-specific YANG model to avoid configuration drift.. In a brownfield Nexus 9000 fabric, the operational state (e.g., interface status, routing table) must be modeled against the device-specific YANG model to detect and correct configuration drift. NETCONF uses YANG models to define both configuration and operational data, but only the device-specific native model accurately reflects the actual running state. Without this alignment, automated remediation may push incorrect configurations, leading to network instability.

Answer

NETCONF replaces CLI entirely; no fallback necessary.

Answer

Using NETCONF for configuration ensures zero touch provisioning.

Answer

All NX-OS versions support the same YANG models; no compatibility check needed.

Question 3

Which TWO statements are true regarding the differences between REST API (NX-API) and NETCONF for automating Nexus switches?

Accepted Answer

NX-API uses HTTP/HTTPS as the transport protocol. NX-API (REST API) uses HTTP or HTTPS as its transport protocol, allowing RESTful operations (GET, POST, PUT, DELETE) over standard web ports. This is in contrast to NETCONF, which uses SSH as its transport (RFC 6241). Therefore, option B is correct.

Answer

NETCONF can only be used for configuration, not for operational state

Answer

NETCONF primarily uses JSON for data encoding

Answer

Both use SSH as their default transport

Question 4

When using Cisco NSO (Network Services Orchestrator) to automate service creation across a data center network, what is a key consideration regarding device compatibility?

Accepted Answer

Each device must have a corresponding NED that matches its OS version.. B is correct because Cisco NSO uses Network Element Drivers (NEDs) to translate service models into device-specific CLI, SNMP, or NETCONF commands. Each NED is tied to a specific device OS version (e.g., IOS-XE 16.12, NX-OS 9.3), so mismatched NEDs cause configuration failures or incomplete deployments. Without a compatible NED, NSO cannot communicate with or configure the device.

Answer

NSO requires NETCONF for all devices.

Answer

Device YANG models must be hand-coded by the team.

Answer

NSO only supports Cisco devices.

Question 5

A network engineer wants to automate the deployment of VLANs across 50 Nexus switches in a data center. Which approach provides the most consistent and repeatable results with minimal manual effort?

Accepted Answer

Ansible playbook with nxos_vlan module. Ansible playbook with the nxos_vlan module is the correct choice because it provides idempotent, declarative automation that ensures consistent VLAN configuration across all 50 Nexus switches with minimal manual effort. Ansible handles SSH connectivity and state management natively, eliminating the need for custom scripting and reducing the risk of human error.

Answer

Python script using netmiko

Answer

Manual CLI on each switch

Answer

Bash script with SSH

Question 6

An Ansible playbook using the cisco.nxos.nxos_config module fails with the error: 'Unsupported parameters for (cisco.nxos.nxos_config) module: connection type setting'. What is the most likely cause?

Accepted Answer

The playbook includes an invalid parameter 'connection: network_cli' inside the task block.. The error 'Unsupported parameters for (cisco.nxos.nxos_config) module: connection type setting' occurs because the `connection: network_cli` parameter is being passed inside the task block of the playbook. The `cisco.nxos.nxos_config` module does not accept a `connection` parameter at the task level; connection settings must be defined at the play or inventory level. This is a common syntax error when using Ansible network modules.

Answer

The SSH key authentication is misconfigured.

Answer

The module is not installed correctly.

Answer

The playbook is targeting a device running an unsupported NX-OS version.

Question 7

An engineer receives an error 'XML namespace mismatch' when using NETCONF to configure a Nexus switch. The YANG model used is from the Cisco NX-OS openconfig model. What is the most likely cause?

Accepted Answer

The namespace in the XML payload does not match the YANG model. The 'XML namespace mismatch' error occurs when the namespace URI declared in the XML payload does not match the namespace defined in the YANG module. NETCONF uses the namespace to identify the correct YANG model for parsing the configuration data. If the namespace in the XML does not exactly match the one in the Cisco NX-OS openconfig YANG model, the switch rejects the operation with this specific error.

Answer

The switch is running in VM mode

Answer

The YANG model is not supported on this switch version

Answer

The NETCONF session is not authenticated

Question 8

Refer to the exhibit. An engineer is trying to automate configuration using NX-API on a Nexus 9000 switch. They have enabled 'feature nxapi' but when they attempt to send a POST request to the NX-API endpoint, they receive '400 Bad Request' with 'Invalid message format'. What is the most likely missing configuration?

Accepted Answer

The NX-API HTTP/HTTPS server is not configured with a port (e.g., 'nxapi http port 80').. The '400 Bad Request' with 'Invalid message format' error indicates the NX-API server is not listening on the expected port. Even with 'feature nxapi' enabled, the HTTP or HTTPS server must be explicitly configured with a port (e.g., 'nxapi http port 80') to accept REST API requests. Without this, the switch does not expose the NX-API endpoint, causing the client to receive a malformed response.

Answer

The switch does not have the 'nxapi' feature enabled.

Answer

The engineer is using the wrong URL path; should be /ins instead of /api.

Answer

The authentication method is set to 'none' but should be 'basic'.

Question 9

A data center automation script uses Python's requests library to call the NX-API for a Nexus 9000 switch. The script works but returns HTTP 400. Which is a likely cause?

Accepted Answer

The request payload is malformed. HTTP 400 indicates a bad request, which in the context of NX-API typically means the JSON or XML payload sent to the switch does not conform to the expected schema. Common issues include missing required fields (e.g., 'ins_api' version, 'type', 'chunk', 'sid', 'input', 'outputformat'), incorrect JSON syntax, or invalid values for parameters like 'version' or 'type'. The requests library successfully delivered the HTTP request, but the NX-API rejected it due to malformed content.

Answer

The switch has no management IP

Answer

The script uses HTTP instead of HTTPS

Answer

The API is not enabled

Question 10

A network automation engineer is writing an Ansible playbook to configure Nexus switches. Which three modules are available to manage NX-OS configuration? (Choose three.)

Accepted Answer

nxos_config. The `nxos_config` module is the primary Ansible module for managing NX-OS device configurations, allowing you to apply, replace, or merge configuration snippets directly onto Nexus switches. It is part of the `cisco.nxos` collection and is specifically designed for NX-OS, unlike `ios_config` which targets Cisco IOS/IOS-XE devices.

Answer

eos_config

Answer

ios_config

Question 11

A Cisco UCS upgrade from release 3.1(1) to 4.0(4) is planned. The current release has a known issue that affects NVRAM backup. What is the best practice to avoid an outage during this upgrade?

Accepted Answer

Upgrade to an intermediate release that is recommended for the upgrade path.. Option D is correct because Cisco UCS firmware upgrades must follow a supported upgrade path to avoid incompatibilities and known issues. Skipping directly from 3.1(1) to 4.0(4) is not supported; an intermediate release (e.g., 3.2(x) or 4.0(1)) is required to resolve the NVRAM backup issue and ensure a seamless upgrade without service disruption.

Answer

Perform a cold reboot of all Fabric Interconnects before starting.

Answer

Upgrade all components simultaneously to reduce transition time.

Answer

Upgrade the firmware on the chassis first, then the Fabric Interconnects.

Question 12

A UCS domain has two fabric interconnects in end-host mode. The engineer needs to implement a policy that ensures all traffic from a specific vNIC is load-balanced across both uplinks to the upstream switches. Which type of policy should be used?

Accepted Answer

Pin group policy. In a UCS domain with fabric interconnects in end-host mode, a Pin Group policy is used to explicitly map a vNIC's traffic to specific uplink ports, ensuring load balancing across the upstream switches. This policy overrides the default MAC-based hashing and allows the engineer to control traffic distribution, which is critical for consistent performance and redundancy.

Answer

Link aggregation policy

Answer

QoS policy

Answer

Network control policy

Question 13

Refer to the exhibit. The blade server is unassociated. Which action is required to assign a service profile to this server?

Accepted Answer

Create a service profile and associate it with the server. A service profile defines the server identity, firmware, policies, and connectivity settings for a UCS blade server. When a server is unassociated, you must create a service profile and then associate it with the server to apply those configurations and bring the server into operation.

Answer

Configure the server's BIOS settings

Answer

Create a boot policy

Answer

Create a vNIC template

Question 14

An engineer is troubleshooting a UCS B-Series server that fails to boot from SAN. The SAN boot LUN is correctly zoned and presented. The service profile has WWPNs configured. What is a likely cause?

Accepted Answer

Incorrect boot policy order. The SAN boot LUN is correctly zoned and presented, and the WWPNs are configured in the service profile, so the connectivity and identity are set. However, if the boot policy order is incorrect (e.g., the SAN boot target is listed after a local disk or another boot device), the server will attempt to boot from the wrong device first and fail to boot from the SAN. The boot policy defines the sequence of boot devices, and a misconfigured order is a common cause of boot failures in UCS B-Series.

Answer

Server firmware mismatch

Answer

Missing vNIC template

Answer

VLAN mismatch

Question 15

Refer to the exhibit. A UCS manager profile is configured with two vNICs on separate fabrics. The server is failing to communicate with the default gateway on VLAN 100. Both vNICs are up. What is the most likely issue?

Accepted Answer

The VLAN 100 is not defined on the fabric interconnects. The most likely issue is that VLAN 100 is not defined on the fabric interconnects. In UCS Manager, even if the vNICs are up and the MAC pool is available, the server cannot communicate with the default gateway if the VLAN is not present on the fabric interconnect's VLAN database. The fabric interconnect must have VLAN 100 created and assigned to the appropriate uplink ports or port-channels for traffic to be forwarded.

Answer

The MAC pool is exhausted

Answer

The boot policy is missing

Answer

The server is using active-standby NIC teaming and the active vNIC is on a fabric that does not have the VLAN

350-601 Practice Test 25 — 15 Questions

Exhibit

350-601 Practice Test 25 — 15 Questions

Exhibit