mediummatchingObjective-mapped

Match each access-control term to its most accurate meaning.

Question 1mediummatching
Full question →

Match each access-control term to its most accurate meaning.

Answer choices are not available in this preview. Open the full question page for the complete review.

Common exam trap

Common exam trap: answer the scenario, not the keyword

A common exam trap is confusing authentication with authorization, assuming they are interchangeable. Candidates often mistake authentication as the process that controls what resources a user can access, but authentication only verifies identity. Another trap is overlooking the principle of least privilege, which is critical in security design but sometimes ignored or confused with authorization. Additionally, candidates may misinterpret a local database as a general authentication method rather than recognizing it as a specific credential source stored on the device itself for local login validation.

Technical deep dive

How to think about this question

Access control in Cisco networking fundamentally relies on three distinct but related concepts: authentication, authorization, and least privilege. Authentication is the process of verifying the identity of a user or device attempting to access the network or device. This can involve credentials such as usernames and passwords, digital certificates, or other verification methods. Authorization follows authentication and determines what resources or commands the authenticated user is permitted to access or execute. Least privilege is a security principle that enforces granting users only the minimum level of access necessary to perform their tasks, reducing the risk of accidental or malicious misuse. In Cisco device management, these concepts are implemented through various mechanisms. Authentication can be performed locally using a local database stored on the device or remotely via protocols like RADIUS or TACACS+. Authorization is often configured through role-based access control (RBAC) or command authorization, which restricts user privileges after successful authentication. The local database contains usernames and passwords or encrypted secrets and is critical for local login authentication when remote servers are unavailable. The principle of least privilege is applied by assigning users to specific privilege levels or roles that limit their access to only required commands or resources. A frequent source of confusion in CCNA exams is mixing these terms or assuming they overlap. Authentication does not grant access rights; it only confirms identity. Authorization is the gatekeeper that enforces what authenticated users can do. Least privilege is a design principle ensuring that authorization is as restrictive as possible. The local database is a concrete implementation detail for authentication, not a conceptual access control term. Understanding these distinctions helps in correctly configuring and troubleshooting Cisco devices and answering exam questions accurately, especially those related to device security and management access.

KKey Concepts to Remember

  • Authentication verifies the identity of a user or device before granting network or device access.
  • Authorization determines the specific actions or resources an authenticated user is permitted to access.
  • The principle of least privilege restricts user access to only the minimum necessary permissions for their role.
  • A local database on a Cisco device stores user credentials used for local authentication during login.
  • Authentication must occur before authorization can enforce access controls on commands or resources.
  • Least privilege reduces security risks by limiting potential damage from compromised or misused accounts.
  • Local databases provide a fallback authentication method when remote servers like RADIUS or TACACS+ are unavailable.
  • Authorization uses role-based access control to assign permissions based on authenticated user identity.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Related practice questions

Related 200-301 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this 200-301 question test?

Authentication verifies the identity of a user or device before granting network or device access.

What exam trap should I watch out for?

Common exam trap: answer the scenario, not the keyword: A common exam trap is confusing authentication with authorization, assuming they are interchangeable. Candidates often mistake authentication as the process that controls what resources a user can access, but authentication only verifies identity. Another trap is overlooking the principle of least privilege, which is critical in security design but sometimes ignored or confused with authorization. Additionally, candidates may misinterpret a local database as a general authentication method rather than recognizing it as a specific credential source stored on the device itself for local login validation.

What should I do if I get this 200-301 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.