A network security administrator is configuring centralized access control services across enterprise switches and routers. Match each operational capability or requirement on the left with the correct AAA framework element or protocol specification on the right.
- Per-command administrative authorization during active CLI management sessionsTACACS+ architecture leveraging TCP port 49 and decoupled AAA functions
- Payload encryption that obfuscates the entire packet body following the headerTACACS+ transport security mechanism providing full-body packet protection
- Authentication and authorization coupled together within single request/response pairsRADIUS protocol operation leveraging UDP ports 1812 and 1813
- Tracking user session duration, login timestamps, and commands executed for audit complianceAccounting component of the AAA security framework
Answer
Per-command CLI authorization matches TACACS+ architecture leveraging TCP port 49 and decoupled AAA functions. Full payload body encryption matches TACACS+ transport security mechanism providing full-body packet protection. Coupled authentication and authorization matches RADIUS protocol operation leveraging UDP ports 1812 and 1813. Session tracking and audit logging matches the Accounting component of the AAA framework.
TACACS+ uses TCP port 49 and decouples AAA functions to permit per-command authorization and full packet payload encryption. RADIUS operates over UDP ports 1812 (Authentication/Authorization) and 1813 (Accounting), combining authentication and authorization in a single transaction while only encrypting passwords. Accounting tracks user session metrics and activity logs.
Step-by-Step Solution
Key Concept
AAA Protocol Mechanics & Functional Separation (TACACS+ vs RADIUS)
Estimated Time:1m 30s