Question 350
An access controller accepts a staff user from RADIUS but assigns the guest role because the expected role attribute is absent. Which failure mechanism best explains the observed behavior?
Explanation
Correct Answer
The symptoms fit this mechanism. A targeted response is to correct the AAA enforcement profile to return the appropriate role assignment after verifying identity, followed by verification that the authenticated staff client receives its authorized role and access policy.
Incorrect Answers
That explanation fits a different case, such as when an access switch performs 802.1X on user ports, but unauthenticated clients are placed into production VLAN by an incorrect fallback policy. The symptoms here are better explained by successful authentication alone does not guarantee the intended network authorization attributes.
That explanation fits a different case, such as when a campus AAA deployment has two RADIUS servers, but requests continue timing out because both hostnames resolve to the same failed address. The symptoms here are better explained by successful authentication alone does not guarantee the intended network authorization attributes.
That explanation fits a different case, such as when a client presents a valid EAP-TLS certificate but its EKU or identity mapping does not meet the enterprise admission rule. The symptoms here are better explained by successful authentication alone does not guarantee the intended network authorization attributes.