What is a limitation of TACACS+?

The selection highlighting a slower response time than RADIUS is accurate in the context of TACACS+. TACACS+ uses TCP, which establishes a connection-oriented session and introduces an additional layer of overhead compared to the connectionless UDP used by RADIUS. This connection-oriented nature can result in longer response times due to the requirement to establish and manage sessions.

Additionally, TACACS+ processes each authentication request in a separate exchange, while RADIUS combines authentication and accounting into a single request, which can lead to faster processing for simpler authentication tasks. Therefore, in scenarios requiring quick access, RADIUS may provide a more responsive solution.

The other options are not accurate representations of TACACS+ capabilities. For instance, TACACS+ does not inherently have limitations regarding bandwidth; it is designed to provide robust security, which does not necessarily correlate with reduced bandwidth. Furthermore, TACACS+ actually supports multiple protocols, including the ability to work within environments using SSH, IP, and more. Lastly, TACACS+ does provide encryption for the entire body of the packet, ensuring a high level of security in transmitted authentication data.