350-701 · Question #705
A network administrator has configured TACACS on a network device using the key Cisc0466974274 for authentication purposes. However, users are unable to authenticate. TACACS server is reachable, but…
The correct answer is A. Configure the TACACS key on the server to match with the network device. TACACS+ authentication requires that the shared secret key configured on the network device must exactly match the key configured on the TACACS server for successful authentication.
Question
A network administrator has configured TACACS on a network device using the key Cisc0466974274 for authentication purposes. However, users are unable to authenticate. TACACS server is reachable, but authentication is falling. Which configuration step must the administrator complete?
Options
- AConfigure the TACACS key on the server to match with the network device.
- BInstall a compatible operating system version on the TACACS server.
- CImplement synchronized system clock on TACACS server that matches the network device.
- DApply an access control list on TACACS server to allow communication with the network device.
How the community answered
(43 responses)- A72% (31)
- B14% (6)
- C9% (4)
- D5% (2)
Why each option
TACACS+ authentication requires that the shared secret key configured on the network device must exactly match the key configured on the TACACS server for successful authentication.
For TACACS+ authentication to succeed, the shared secret key configured on the network device must precisely match the key configured on the TACACS server. This key is crucial for encrypting communication and verifying the authenticity of both the client and server, and any mismatch will result in authentication failures.
While operating system compatibility is important, an incorrect shared secret key is a more direct and common cause of TACACS+ authentication failure when the server is reachable.
Synchronized system clocks are vital for certain authentication protocols like Kerberos but are not the primary cause of TACACS+ authentication failure specifically due to a key mismatch.
If the TACACS server is reachable, it implies that basic network connectivity and necessary access control lists allowing communication are likely already configured or not the root cause of the authentication failure.
Concept tested: TACACS+ shared secret key configuration
Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_usr_tacacs/configuration/15-mt/sec-usr-tacacs-15-mt-book/sec-cfg-tac-plus.html
Topics
Community Discussion
No community discussion yet for this question.