In the Agile Controller admission control scenario, which one is correct about the role description of RADIUS server/client?

Question

Options

• AAgile Controller integrates all functions of RADIUS server and client
• BThe Agile Controller acts as the RADIUS server, and the user terminal acts as the RADIUS client
• CThe authentication device (such as an 802.1x switch) acts as a RADIUS server, and the user
• DThe Agile Controller acts as the RADIUS server, and the authentication device acts as the

• A
  2% (1)
• B
  14% (6)
• C
  7% (3)
• D
  76% (32)

Explanation

D is correct because in Huawei's Agile Controller admission control architecture, the Agile Controller functions as the RADIUS server - it receives authentication requests and makes access decisions - while the authentication device (such as an 802.1x-capable switch) functions as the RADIUS client, forwarding credential requests from end users to the Agile Controller.

Why the distractors fail:

• A is wrong because Agile Controller does not simultaneously hold both server and client roles; it is strictly the server-side component in this architecture.
• B is wrong because the user terminal (endpoint) is not the RADIUS client - it runs an 802.1x supplicant and communicates via EAP, not RADIUS; the switch is the RADIUS client.
• C is wrong because it inverts the roles: the authentication device (switch) is the RADIUS client, not the server.

Memory tip: Think of the flow as User → Switch → Agile Controller. The switch is the "middleman" (RADIUS client) that relays requests, and the Agile Controller is the "decision-maker" (RADIUS server) - the server always sits furthest from the user endpoint.

No community discussion yet for this question.