Free Cisco 350-601 Practice Exam with Questions & Answers

Option B is correct because on Cisco Nexus NX-OS, the command aaa authentication login default group < server-group > local creates the default login authentication method list and tells the switch to try the named AAA server group first, then fall back to the local user database if the AAA servers are unreachable or do not respond. Cisco’s NX-OS AAA documentation states that the default login method list is used for user logins, and that the group keyword points authentication to a configured TACACS+ or RADIUS server group. It also notes that local authentication is the fallback method unless that behavior is explicitly disabled. (Cisco)

The key reason the answer is B is the syntax: group ISE local means “authenticate with the TACACS+ server group named ISE first, then use local if the server is unavailable.” Option C uses only local authentication, so it does not use TACACS+ at all. Option D applies to console login configuration and is not the correct default user-login command. Option A is incorrect syntax for enabling this behavior; Cisco documents fallback error local as a behavior that is already present by default and can be disabled with the no form. (Cisco)

The correct answer is A because Cisco Nexus 9000 Series switches use JSON-RPC 2.0 format for NX-API requests when interacting programmatically. In this format, the required fields include jsonrpc, method, params, and id. To retrieve operational or configuration data using a show command, Cisco specifies the use of the method cli_show, which is designed for read-only commands such as show running-config.

The params section must include the command (cmd) and the API version (version: 1). This aligns with Cisco NX-API documentation, where cli_show ensures that the output is returned without modifying the system.

Option D is incorrect because the method cli is used for configuration commands, not show commands. Options B and C are invalid because they use JSON-RPC 1.0 format, which is not supported in modern NX-API implementations for Nexus 9000 switches.

Therefore, the properly structured JSON-RPC 2.0 request using cli_show is required to retrieve the running configuration, making A the correct answer.

To establish EIGRP adjacency on Cisco NX-OS, the global configuration must match the parameters defined at the interface level. Let ' s break down why Option A is the only correct choice:

The Key Chain Name:

Looking at the interface command: ip authentication key-chain eigrp NXOS EIGRP

The first " NXOS " refers to the EIGRP instance name, and " EIGRP " (case-sensitive) is the name of the key chain.

Option A correctly defines key chain EIGRP. Options B, C, and D use lowercase or entirely different names, which would cause an authentication mismatch.

The EIGRP Instance Name:

The interface command ip router eigrp NXOS identifies the EIGRP instance as NXOS.

Option A and Option B correctly use router eigrp NXOS. Options C and D use " EIGRP " as the instance name, which contradicts the interface-level configuration.

Authentication Mode:

The interface specifies MD5: ip authentication mode eigrp NXOS md5.

While NX-OS often requires the mode to be set on the interface, including it under the router eigrp process (as seen in Option A) ensures the process is configured to handle that authentication type.