In EAP architecture, which entity is the device requesting access to the network?

In EAP architecture, which entity is the device requesting access to the network?

• A. Authenticator
• B. RADIUS
• C. Supplicant
• D. Compute

Answer: (C)

In EAP architecture, the device that wants to connect to the network is the supplicant. In this model, three roles exist: the supplicant (the client device requesting access), the authenticator (the network device such as a switch or wireless access point that enforces access control and passes authentication messages), and the authentication server (often a RADIUS server) that validates credentials. The supplicant initiates the authentication process, sending its credentials through the authenticator to the authentication server. The authenticator doesn’t make the access decision by itself; it simply gates the port based on the server’s response. The term compute isn’t a defined role in this context. So the device requesting access is the supplicant.

In EAP architecture, the device that wants to connect to the network is the supplicant. In this model, three roles exist: the supplicant (the client device requesting access), the authenticator (the network device such as a switch or wireless access point that enforces access control and passes authentication messages), and the authentication server (often a RADIUS server) that validates credentials. The supplicant initiates the authentication process, sending its credentials through the authenticator to the authentication server. The authenticator doesn’t make the access decision by itself; it simply gates the port based on the server’s response. The term compute isn’t a defined role in this context. So the device requesting access is the supplicant.