Free Practice Questions for Cisco 350-601 Exam

Anycast gateway mac, 2022, anycast gateway, 2021

The correct answer is B because Cisco OSPF MD5 authentication on an interface requires two specific elements: enabling message-digest authentication and defining a message-digest key. On Cisco platforms, the correct syntax is:

ip ospf authentication message-digest

ip ospf message-digest-key < key-id > md5 < encryption-type > < password >

In this question, the engineer must use MD5 and store the password using 3DES encryption, which corresponds to encryption type 3 in Cisco syntax. Therefore, ip ospf message-digest-key 2 md5 3 P@ssw01 is the valid form. The key ID can be any matching integer on both neighbors, and here it is 2.

Option A is incorrect because authentication-key is used for simple password authentication, not MD5 message-digest authentication. Option C is incorrect because ip ospf authentication md5 is not the NX-OS/IOS syntax used here; Cisco uses authentication message-digest. Option D is invalid because authentication-key does not take md5 in that format.

So the issue is resolved only by enabling message-digest authentication and configuring the MD5 key with encryption type 3, which is exactly what B does.

The goal is to automatically enable interface Eth1/2 whenever interface Eth1/1 is shut down. An EEM applet consists of an event (the trigger) and an action (the response).

The Applet Name:

The command event manager applet [name] initializes the applet.

Options A and B incorrectly put the event syslog pattern before the applet definition. In NX-OS and IOS, you must first enter the applet configuration context before defining its parameters.

The Event Trigger:

The requirement is to trigger the script when Eth1/1 is shut down.

Option C specifies event syslog pattern " Interface Ethernet 1/1, changed state to administratively down " . This matches the standard syslog message generated when an interface is manually disabled.

Option D is incorrect because it monitors Eth1/2 instead of Eth1/1, meaning the script would only trigger if the interface it ' s trying to open was the one being shut.

The Action Sequence (from the exhibit):

The provided exhibit shows the actions that will be executed once the event occurs:

action 1.0 cli command " enable " (Enter privileged mode).

action 1.5 cli command " config t " (Enter configuration mode).

action 2.0 cli command " interface Eth1/2 " (Select the target interface).

action 2.5 cli command " no shutdown " (Enable the target interface).

The correct answer is B because Cisco MDS RBAC authorizes a user based on the union of all permitted commands across all assigned roles. In the exhibit, the default role network-admin permits configuration of NTP, SSH, and TACACS+, while the additional role Custom-Role-B permits configuration of DPVM and includes a deny entry for TACACS+. Cisco documentation for MDS RBAC explains that when a user belongs to multiple roles, the user can execute the combined set of commands permitted by those roles, and importantly, access takes priority over deny when there is a conflict across roles.

Applying that rule here, User A is allowed to configure:

NTP (config feature ntp) from network-admin

SSH (config feature ssh) from network-admin

TACACS+ (config feature tacacs+) from network-admin

DPVM (config feature dpvm) from Custom-Role-B

The deny for TACACS+ in Custom-Role-B does not remove access because another assigned role already permits it. Options containing hardware or environment are incorrect because those are show permissions, not configuration permissions.

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.