Courseiva
Network SecurityhardMultiple ChoiceObjective-mapped

N10-009 Network Security Practice Question

An organization needs to authenticate network administrators and control which commands each administrator can execute on routers and switches. The solution must support granular per-command authorization and encrypt the entire session. Which protocol is best suited for this requirement?

⚠ Common exam trap

CompTIA often tests the distinction that RADIUS is commonly used for network access control (e.g., 802.1X) but fails for device administration because it lacks per-command authorization and full-session encryption, leading candidates to mistakenly choose RADIUS due to its familiarity.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

TACACS+

TACACS+ is the correct choice because it separates authentication, authorization, and accounting (AAA) functions, allowing granular per-command authorization on routers and switches. It encrypts the entire session, including the username, password, and all command traffic, unlike RADIUS which only encrypts the password. This makes TACACS+ ideal for environments requiring strict command-level control and full session encryption.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • TACACS+

    Why this is correct

    TACACS+ (Terminal Access Controller Access Control System Plus) is the correct protocol for this scenario because it provides robust Authentication, Authorization, and Accounting (AAA) services specifically designed for network device administration. It encrypts the entire communication session, not just the password, and offers granular command authorization, allowing administrators to define precisely which commands a user or group can execute on a network device. This level of control is essential for security and compliance in managing critical infrastructure.

  • RADIUS

    Why it's wrong here

    RADIUS (Remote Authentication Dial-In User Service) is a widely used AAA protocol, but its primary strength lies in network access control, such as authenticating users for Wi-Fi (802.1X), VPNs, or dial-up connections. While it provides authentication and some authorization, its authorization capabilities are typically limited to network access parameters (e.g., VLAN assignment, access duration) rather than granular command-level control for device administration. Additionally, RADIUS encrypts only the password in the access-request packet, not the entire session, and uses UDP, making it less robust for command-level authorization compared to TACACS+.

    When this WOULD be correct

    When the requirement is to authenticate users for network access (e.g., VPN or 802.1X) and optionally authorize network services, but does not require per-command authorization or full-session encryption.

  • LDAP

    Why it's wrong here

    LDAP (Lightweight Directory Access Protocol) is primarily used for querying and modifying directory services, such as Microsoft Active Directory or OpenLDAP, to retrieve user attributes or authenticate users against a directory. While it can be used for authentication by binding to a directory, it does not inherently provide the granular command-level authorization capabilities required to control which specific commands a network administrator can execute on a network device. It lacks the built-in AAA framework for device management.

  • Kerberos

    Why it's wrong here

    Kerberos is a network authentication protocol that provides strong authentication for client-server applications by using secret-key cryptography. It issues 'tickets' to users, allowing them to access various services without re-authenticating repeatedly (single sign-on). However, Kerberos primarily focuses on authentication and does not natively offer the fine-grained, per-command authorization capabilities necessary to control specific administrative actions on network devices. It authenticates access to a service, but not the specific commands within that service.

    When this WOULD be correct

    An organization needs to implement single sign-on for users accessing multiple services within a Windows domain, with mutual authentication and ticket-based access control.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The N10-009 exam frequently reuses these exact scenarios with slightly different constraints.

TACACS+Correct answer

Why this is correct

TACACS+ (Terminal Access Controller Access Control System Plus) is the correct protocol for this scenario because it provides robust Authentication, Authorization, and Accounting (AAA) services specifically designed for network device administration. It encrypts the entire communication session, not just the password, and offers granular command authorization, allowing administrators to define precisely which commands a user or group can execute on a network device. This level of control is essential for security and compliance in managing critical infrastructure.

RADIUSWrong answer — click to see why

Why this is wrong here

RADIUS encrypts only the password in the authentication packet, not the entire session, and does not support per-command authorization; it is designed for network access control, not device administration.

★ When this WOULD be the correct answer

When the requirement is to authenticate users for network access (e.g., VPN or 802.1X) and optionally authorize network services, but does not require per-command authorization or full-session encryption.

Why candidates choose this

Candidates often confuse RADIUS with TACACS+ because both are AAA protocols, and they may assume RADIUS also provides command authorization and encryption, not realizing its limitations in device administration contexts.

KerberosWrong answer — click to see why

Why this is wrong here

Kerberos is designed for authentication and single sign-on in a trusted network, but it does not provide per-command authorization or session encryption for network device administration.

★ When this WOULD be the correct answer

An organization needs to implement single sign-on for users accessing multiple services within a Windows domain, with mutual authentication and ticket-based access control.

Why candidates choose this

Candidates may associate Kerberos with strong authentication and encryption, mistakenly believing it can also handle granular command authorization for network devices.

Analysis generated from the official N10-009blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

Quick reference

AAA Protocol Comparison

ProtocolPort(s)EncryptionTransportPrimary Use
RADIUS1812 / 1813Password onlyUDPNetwork access control
TACACS+49Full packetTCPDevice administration
Diameter3868Full sessionTCP / SCTPCarrier / mobile networks
802.1XEAP-basedLayer 2Port-based access control

TACACS+ encrypts the entire packet; RADIUS only encrypts the password field — a key exam distinction.

About these practice questions

Courseiva writes every N10-009 question from scratch — 464 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This N10-009 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the N10-009 exam.