Which of the following user logout methods does 802.1X authentication support? (Multiple choice)

Question

Options

• AThe client proactively logs off
• BAccess device controls user logout
• CThe authentication server controls users to go offline
• DThe accounting server controls users to go offline

• A
  81% (35)
• D
  19% (8)

Explanation

802.1X defines three logout mechanisms that correspond to its three-role architecture: the supplicant (client) can initiate logout by sending an EAPOL-Logoff message (A), the authenticator (access device) such as a switch or WAP can force a port into unauthorized state to drop the user (B), and the authentication server (typically RADIUS) can push a Disconnect-Request or Change-of-Authorization (CoA) message to terminate the session (C). Option D is incorrect because the accounting server is a passive collector - it records session data (start/stop times, bytes transferred) for billing and auditing purposes but does not have a signaling path to control session state. While accounting and authentication functions are often co-hosted on the same RADIUS server, the accounting role itself has no logout authority in the 802.1X framework.

Memory tip: Think of the three valid methods by the actor that owns each phase of the session - the user decides to leave (A), the door (access device) can be shut (B), and the gatekeeper (auth server) can revoke access (C). The bookkeeper (accounting server) just watches and writes things down - it never controls the door.

No community discussion yet for this question.