What is causing the issue?

A user is trying to connect to a wireless network that is configured for WPA2-Enterprise security using a corporate laptop. The CA certificate for the authentication server has been installed on the Trusted Root Certification Authorities store on the laptop. The user has been prompted to enter the credentials multiple times, but the authentication has not succeeded. What is causing the issue?
A. There is an IEEE invalid 802.1X authentication policy on the authentication server.
B. The user Active Directory account is locked out after several failed attempts.
C. There is an invalid 802.1X authentication policy on the authenticator.
D. The laptop has not received a valid IP address from the wireless controller.

cisco-exams

2 thoughts on “What is causing the issue?

  1. i think A is correct Answer. “There is an IEEE invalid 802.1X authentication policy on the authentication server”
    C is invalid in my opinion as u son’t configure a policy on authenticator, you only configure 802.1x setttings

  2. A

    This is a classic Cisco putting ambiguous questions that will have multiple right answers. The IP address response is incorrect and can be ruled out because DHCP occurs after an 802.1x authentication when the client is in the run state (assuming no WebAuth). That leaves an invalid authentication policy on the authenticator which it could be if they didn’t define the AAA settings properly. It could be an account lockout as the user will not be notified if it’s locked. The final option is an invalid authentication policy on the authentication server. All three of these could be right but I would choose the user account is locked because it says you are troubleshooting a user-specific issue. The misconfigured authenticator or authentication server would have widespread problems affecting multiple users wheras the individual user account being locked would explain a user-specific problem.

Leave a Reply

Your email address will not be published. Required fields are marked *


The reCAPTCHA verification period has expired. Please reload the page.