In the WLAN network environment using Agile Controller, which of the following steps does not belong to the 802.1x authentication troubleshooting procedure?

Question

Options

• ACheck whether the number of online users reaches the maximum
• BCheck that the AAA configuration of the device is correct
• CCheck whether the 802.1x configuration is correct
• DCheck whether the web authentication configuration is correct

• A
  4% (1)
• B
  4% (1)
• C
  15% (4)
• D
  78% (21)

Explanation

Option D is correct because web authentication (also called portal authentication) is an entirely separate authentication method from 802.1x - they are distinct protocols with their own configurations, so checking web auth settings has no relevance when troubleshooting an 802.1x failure.

Options A, B, and C are all legitimate 802.1x troubleshooting steps: reaching the maximum user limit (A) can silently block new authentications; incorrect AAA configuration (B) - including RADIUS server address, shared keys, or accounting settings - directly breaks the 802.1x exchange; and a misconfigured 802.1x policy (C) on the AP or controller (wrong SSID binding, EAP method, etc.) prevents clients from authenticating at all.

Memory tip: Think of it as "stay in your lane" - 802.1x troubleshooting only covers 802.1x components (the protocol itself, AAA/RADIUS, and capacity limits). Web authentication belongs to portal/captive-portal troubleshooting, a completely different lane. If the question mentions 802.1x, anything web/portal-related is automatically out of scope.

No community discussion yet for this question.