Which standard encapsulates EAP communications over a LAN or WLAN to implement port-based authentication?

Which standard encapsulates EAP communications over a LAN or WLAN to implement port-based authentication?

• A. MAC filtering
• B. IEEE 802.1X
• C. Supplicant
• D. RADIUS

Answer: (B)

The idea being tested is port-based network access control using a framework that carries EAP messages between a client and an authentication server over a LAN or WLAN. IEEE 802.1X provides this framework and the mechanism for controlling the switch or access point port so that it stays blocked until authentication succeeds. In this setup, the device trying to connect acts as the supplicant, the network device (switch or AP) is the authenticator, and an authentication server (often a RADIUS server) validates the credentials. The EAP messages are transported over the link using EAPOL (EAP over LAN), all encapsulated within the 802.1X exchange. This makes 802.1X the correct choice because it defines the port-based access control and the EAP exchange that governs whether a client gets network access. MAC filtering isn’t an authentication framework and only blocks based on a device’s MAC address. The supplicant label refers to the client entity, not the standard. RADIUS is the backend server protocol that handles the authentication, but the encapsulation and port-based control are defined by 802.1X.

The idea being tested is port-based network access control using a framework that carries EAP messages between a client and an authentication server over a LAN or WLAN. IEEE 802.1X provides this framework and the mechanism for controlling the switch or access point port so that it stays blocked until authentication succeeds. In this setup, the device trying to connect acts as the supplicant, the network device (switch or AP) is the authenticator, and an authentication server (often a RADIUS server) validates the credentials. The EAP messages are transported over the link using EAPOL (EAP over LAN), all encapsulated within the 802.1X exchange. This makes 802.1X the correct choice because it defines the port-based access control and the EAP exchange that governs whether a client gets network access.

MAC filtering isn’t an authentication framework and only blocks based on a device’s MAC address. The supplicant label refers to the client entity, not the standard. RADIUS is the backend server protocol that handles the authentication, but the encapsulation and port-based control are defined by 802.1X.