1X authentication supports two authentication methods: EAP termination and EAP relay. Which of the following descriptions of these two authentication methods are correct? (Multiple choice)

Question

Options

• AEAP termination has high requirements for access devices. Access devices need to encapsulate
• BThe difference between the EAP termination and EAP relay authentication processes lies in the
• CBoth EAP termination and EAP relay support EAPTLS, EAP-TTLS, EAP-PEAP, MD5-Challenge
• DThe authentication server must support EAP in EAP relay mode

• A
  79% (26)
• C
  21% (7)

Explanation

A is correct because in EAP termination mode, the access device must process and terminate the EAP exchange itself, converting EAP messages into standard RADIUS attributes (e.g., MD5-Challenge) - this demands significantly more capability from the access device compared to simply forwarding packets.

B is correct because the core distinction between the two methods is where EAP is processed: in EAP termination, the access device handles the EAP negotiation and converts it before forwarding to the RADIUS server, while in EAP relay, the access device transparently passes EAP packets through to the authentication server unchanged.

D is correct because in EAP relay mode, EAP packets are forwarded intact all the way to the RADIUS server, so the server itself must natively understand and process EAP - unlike EAP termination, where the server only receives converted (non-EAP) RADIUS messages.

C is wrong because EAP termination only supports simpler methods like MD5-Challenge; complex certificate-based or tunneled methods (EAP-TLS, EAP-TTLS, EAP-PEAP) require the full EAP dialogue to reach the authentication server, making them exclusive to EAP relay mode.

Memory tip: Think of it as "Relay = Reach" - in EAP relay, EAP packets reach all the way to the RADIUS server (so the server must speak EAP), while "Termination = Tough on the switch" - the access device does the heavy lifting and only simple EAP types are supported.

No community discussion yet for this question.