A network administrator at a logistics enterprise configures TACACS+ for centralized management of core routers. Network engineers can successfully authenticate to the router command-line interface using their domain credentials. However, when the engineers attempt to run restricted configuration commands, the router returns a permission error. The administrator verifies that credential validation against Active Directory is functioning properly. Which of the following describes the root cause of this operational issue?
- The TACACS+ server validated user identity during the authentication phase, but command-level authorization policies were not configured.Answer
- BThe router automatically granted authorization because TACACS+ combines authentication and command authorization into a single indivisible protocol transaction.
- CThe management interface denied access because internal network traffic is inherently trusted based on perimeter location without requiring privilege evaluation.
- DThe administrative access policy misclassified command authorization as a detective logging control rather than a preventive access control mechanism.
Answer
The correct answer states that the TACACS+ server validated user identity during the authentication phase, but command-level authorization policies were not configured.
The correct answer correctly identifies that TACACS+ separates authentication from authorization. While identity validation against Active Directory succeeded, specific command-level authorization policies were omitted, preventing the router from approving restricted commands.
Step-by-Step Solution
Key Concept
Separation of Authentication and Authorization in TACACS+ Operations
Estimated Time:1m 30s