mediummultiple choiceObjective-mapped

Which statement best describes why authorization is different from authentication in AAA?

Question 1mediummultiple choice
Full question →

Which statement best describes why authorization is different from authentication in AAA?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Best answer

Authentication verifies identity, while authorization determines permitted actions.

This is correct because the two AAA functions address different stages of access control.

B

Distractor review

Authorization is used only for DHCP address assignment.

This is wrong because authorization is not a DHCP function.

C

Distractor review

Authentication decides routing metrics, while authorization chooses VLANs.

This is wrong because AAA functions are not routing metric or VLAN selection features.

D

Distractor review

Authorization replaces the need for accounting.

This is wrong because accounting is a separate AAA function.

Common exam trap

Common exam trap: answer the scenario, not the keyword

A common exam trap is to assume that authentication alone controls what a user can do after logging in. Many candidates mistakenly believe that once a user is authenticated, they automatically have full access. However, authentication only verifies identity, while authorization explicitly restricts or permits specific actions. Overlooking this distinction can cause confusion in AAA-related questions, leading to incorrect answers that conflate identity verification with permission enforcement.

Technical deep dive

How to think about this question

Authentication and authorization are two distinct but complementary functions within the AAA (Authentication, Authorization, and Accounting) framework used in Cisco networking. Authentication is the initial step that verifies the identity of a user or device attempting to access the network, typically through credentials like usernames and passwords. Authorization follows authentication and determines what resources or commands the authenticated user is permitted to access or execute, enforcing access control policies. In Cisco devices, after a user is authenticated, the authorization process evaluates the user's privileges and restrictions based on predefined policies or roles. This separation allows for granular control, where a valid user might have limited permissions depending on their role or the context of access. For example, a network technician might be authorized to execute configuration commands, while a guest user might only have read-only access. A common exam trap is confusing authentication with authorization, assuming that verifying identity automatically grants full access. In practice, authentication only confirms who the user is, while authorization explicitly defines what the user can do. Cisco IOS and other Cisco platforms implement this distinction to enhance security by preventing unauthorized actions even from authenticated users, which is critical in secure administrative and operational environments.

KKey Concepts to Remember

  • Authentication verifies the identity of a user or device before granting any network access.
  • Authorization determines the specific actions or resources an authenticated user is permitted to access on the network device.
  • AAA separates authentication and authorization to enforce granular access control policies based on user roles or attributes.
  • Authentication uses credentials such as usernames and passwords to confirm identity, while authorization applies policy rules to limit permissions.
  • Authorization does not replace accounting; accounting separately tracks user activities for auditing and compliance.
  • Authorization policies can restrict command sets or access levels even after successful authentication.
  • Confusing authentication with authorization can lead to security risks by granting excessive permissions to users.
  • Cisco devices implement AAA to ensure that identity verification and permission granting are distinct, enhancing network security.

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 any network access.

What is the correct answer to this question?

The correct answer is: Authentication verifies identity, while authorization determines permitted actions. — Authentication answers who the user is, while authorization answers what that authenticated user is allowed to do. In practical terms, confirming identity is not the same as granting permission scope. A user may be validly identified but still restricted to a limited command set or role. This distinction is central to secure administrative design.

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.