Question 929 of 1,389
CCNA Network Services and Security Practice Question
Which two statements accurately describe the value of named administrative accounts?
⚠ Common exam trap
Beware of confusing named accounts with other security measures like password policies or role-based access control.
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
✓
They improve accountability by tying actions to specific individuals.
Named administrative accounts are valuable because they tie actions to individual identities and make access review more meaningful. In practical terms, when multiple people share one generic admin account, accountability becomes weaker. Named identities improve traceability and support auditing, investigations, and operational review. This is a core secure-administration concept and a good reasoning item rather than just a memorization exercise.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
They improve accountability by tying actions to specific individuals.
Why this is correct
Named accounts (like AAA with local or RADIUS/TACACS+) bind authenticated users to a unique identity, so every command or configuration change can be logged with the responsible person's username. This is the basis for accountability: when multiple admins share a generic credential, you cannot determine who executed a specific action, but named accounts unambiguously assign responsibility. This deterrence and forensic attribution is a core driver for using AAA rather than shared passwords.
- ✓
They improve traceability during audits or incident reviews.
Why this is correct
Traceability depends on logs that record not just what was done, but who did it. With named accounts, audit logs and incident-tracking can follow a single user's actions across sessions, even when the user reconnects from different IP addresses. This improves the value of syslog and AAA accounting records, enabling investigators to reconstruct a timeline of changes or security-relevant events.
- ✗
They replace the need for authorization controls.
Why it's wrong here
Identity is only one pillar of AAA; authorization is a separate step that dictates which resources or commands a user is permitted to execute. Even if a named account exists, the user might have read-only access, or be restricted to certain VLANs or device roles. Replacing authorization with identification alone would lead to excessive privilege and security breaches, because authentication only validates who you are, not what you may do.
When this WOULD be correct
In a scenario where a question asks if named administrative accounts can function independently without any authorization mechanisms, option C could be correct if it specifies that named accounts can be used in a context where no other access controls are enforced, such as in a poorly configured legacy system.
- ✗
They can be used only with Telnet and not SSH.
Why it's wrong here
Named accounts are protocol-independent and can be used with both Telnet and SSH, as well as console and auxiliary ports. In fact, security best practices discourage Telnet in favor of SSH, but if you enable AAA, both protocols pass the same authentication and authorization checks. Claiming that named accounts only work with Telnet is factually incorrect; Cisco's AAA does not discriminate by transport protocol.
When this WOULD be correct
In a question that specifically asks about the limitations of administrative account usage in legacy systems or protocols, stating that named administrative accounts are only applicable to Telnet could be correct if the context is focused on outdated practices where SSH was not implemented.
- ✗
They exist only for wireless guest administration.
Why it's wrong here
Named accounts are a general-purpose feature of AAA configuration on Cisco devices, not limited to any particular network service. They are used for network device administrators (SSH, console, enable), and also for network access (802.1X, NAC) for wired, wireless, and VPN users. Wireless guest administration is only one niche use case; the same identity concepts apply across all management access and network admission.
When this WOULD be correct
If the exam question specifically asked about the purpose of administrative accounts in the context of managing wireless guest access, then this option could be correct. For example, a question could state, 'What is a primary function of named administrative accounts in wireless guest networks?'
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 200-301 exam frequently reuses these exact scenarios with slightly different constraints.
✓They improve accountability by tying actions to specific individuals.Correct answer▾
Why this is correct
Named accounts (like AAA with local or RADIUS/TACACS+) bind authenticated users to a unique identity, so every command or configuration change can be logged with the responsible person's username. This is the basis for accountability: when multiple admins share a generic credential, you cannot determine who executed a specific action, but named accounts unambiguously assign responsibility. This deterrence and forensic attribution is a core driver for using AAA rather than shared passwords.
✗They replace the need for authorization controls.Wrong answer — click to see why▾
Why this is wrong here
Named accounts provide identification and authentication, but authorization (what actions an account can perform) is a separate control typically enforced via privilege levels, role-based access control (RBAC), or command authorization (e.g., using TACACS+). Replacing authorization with identity alone would violate the principle of least privilege.
★ When this WOULD be the correct answer
In a scenario where a question asks if named administrative accounts can function independently without any authorization mechanisms, option C could be correct if it specifies that named accounts can be used in a context where no other access controls are enforced, such as in a poorly configured legacy system.
Why candidates choose this
Students may confuse authentication (who you are) with authorization (what you can do), thinking that a named account inherently defines permissions. In reality, authorization must be explicitly configured, often through AAA or local privilege levels.
✗They can be used only with Telnet and not SSH.Wrong answer — click to see why▾
Why this is wrong here
Named accounts are protocol-agnostic and work with any management protocol, including SSH, HTTPS, and SNMPv3. Telnet is insecure and rarely used in modern networks; named accounts are actually more important with secure protocols to maintain accountability without compromising security.
★ When this WOULD be the correct answer
In a question that specifically asks about the limitations of administrative account usage in legacy systems or protocols, stating that named administrative accounts are only applicable to Telnet could be correct if the context is focused on outdated practices where SSH was not implemented.
Why candidates choose this
A test-taker might associate named accounts with older protocols like Telnet because both are commonly discussed in the context of legacy network management. However, named accounts are a best practice regardless of protocol, and SSH is the standard for secure remote access.
✗They exist only for wireless guest administration.Wrong answer — click to see why▾
Why this is wrong here
Named administrative accounts are used across all network device administration, including routers, switches, firewalls, and wireless controllers. Wireless guest administration typically uses separate guest accounts or captive portal authentication, not administrative accounts.
★ When this WOULD be the correct answer
If the exam question specifically asked about the purpose of administrative accounts in the context of managing wireless guest access, then this option could be correct. For example, a question could state, 'What is a primary function of named administrative accounts in wireless guest networks?'
Why candidates choose this
The phrase 'guest administration' might lead a student to think of guest wireless networks, but administrative accounts are for managing the network infrastructure itself, not for guest access. The term 'administration' here refers to device management, not user services.
Analysis generated from the official 200-301blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: May 17, 2026
This 200-301 practice question is part of Courseiva's free Cisco 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 200-301 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.