Why would a WLAN administrator rarely see the 'authenticated' step on the AP?

• A. Because authentication is skipped in most WLAN deployments.
• B. Because the AP completes authentication internally.
• C. Because clients pass the authentication stage and immediately proceed into the association stage.
• D. Because authentication happens after association.

Answer: (C)

On an 802.11 WLAN, a station goes through authentication first, then association, before it can use the network. In practice this authentication is either very quick or handled off the air (for example with Open System or 802.1X/EAP). Once the client proves it’s allowed to access, it immediately proceeds to the association step to establish its presence with the AP. Because that transition happens so rapidly and the AP’s view is mainly “connected” once both steps succeed, you don’t usually see a distinct, lingering “authenticated” state on the AP. That’s why administrators commonly don’t observe a separate authenticated step; the client passes authentication and immediately moves into association.

Other choices aren’t typical in real deployments: authentication isn’t universally skipped, the AP doesn’t perform credentials entirely by itself (that’s handled by the authenticator/DAC server), and authentication is not something that happens after association in normal WLAN workflows.