What is the most likely cause of this problem?

The central office is currently using a combination of 4400 and 2100 series WLAN controllers
running v4.2 and a variety of LWAPP-enabled access points servicing both 2.4 GHz and 5 GHz.
The WLAN deployment has been extended to each remote office by implementing a 526 WLAN
controller running v4.1 and several 521 access points. Wireless client deployment uses EAP-TLS
authentication using a centralized RADIUS server plus 802.11n for performance. After the first
remote office deployment, remote office users complain that they are not connecting via 802.11n.
What is the most likely cause of this problem?

The central office is currently using a combination of 4400 and 2100 series WLAN controllers
running v4.2 and a variety of LWAPP-enabled access points servicing both 2.4 GHz and 5 GHz.
The WLAN deployment has been extended to each remote office by implementing a 526 WLAN
controller running v4.1 and several 521 access points. Wireless client deployment uses EAP-TLS
authentication using a centralized RADIUS server plus 802.11n for performance. After the first
remote office deployment, remote office users complain that they are not connecting via 802.11n.

What is the most likely cause of this problem?

A.
The 526 WLAN controller does not support external authentication via RADIUS, prohibiting authentication.

B.
The 521 AP does not support 5 GHz, which prohibits 802.11n.

C.
The 521 AP and 526 WLAN controllers do not support AES, which prohibits 802.11n.

D.
The 526 WLAN controller does not support 802.11n with v4.1 and must be upgraded to v4.2.

E.
The 526 WLAN controller does not support 802.11n with either v4.1 or v4.2.



Leave a Reply 0

Your email address will not be published. Required fields are marked *