Which of the below feature intersection of a Cisco 5760 Wireless LAN Controller with HA AP SSO is true?

Which of the below feature intersection of a Cisco 5760 Wireless LAN Controller with HA AP SSO is true?
A . Mobility paths and tunnels to the MO and other peer MCs are not disrupted upon switchover.
However that under which the HA pair exists and is re-learnt from the new Active controller when the client re­associate
B . The new active controller doesn’t have to re-learn the shun list from IPS and other MCs,prior to redistribute
C . Roamed clients that have their data path going through the Mobility Tunnel Endpoint(MTE) “becomed foreign” Anchoring. L3 Roamed Clients are only affected when roaming occurs between CUWN and CA controllers.
D . Switchover during AP pre-image download does not cause the APs to start image download all over again from the new Active controller.

View Answer

Answer: A

Explanation:

NOTE: Exam option might miss spelled words in the middle of A and C, in the the end of B and D.

From: http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/5700/software/release/ ios_xe_33/5760_HA_DG_iosXE33.html

Feature Intersection with AP SSO

Switchover during AP Pre-Image download causes the APs to start image download all over again from the new Active controller.

Rogue APs and clients are not synced to Standby and are re-learnt upon switchover.

Infrastructure MFP key is not synced to the Standby controller and is re-learnt upon switchover.

New Active controller re-learns the shun list from IPS and other MCs, and redistributes it to the MAs.

wIPS information is not synced to the Standby unit and is re-learnt upon switchover.

Clean Air detected Interferer devices are re-learnt after switchover.

Net Flow records are cleared upon switchover and collection starts fresh on the new Active controller.

Mobility paths and tunnels to the MO and other peer MCs are not disrupted upon switchover.

However the Client state is cleaned up on the MO under which the HA pair exists and is re-learnt from the new Active controller when the client re-associates.

Roamed clients that have their data path going through the Mobility Tunnel Endpoint (MTE) “become Local” in case of L2 with Sticky Anchoring and L3 Roam. L2 Roamed Clients are not affected except when roaming occurs between CUWN and CA controllers.

RRM related configurations and the AP neighbor list in the Leader HA pair is synced to the Standby controller.

Upon Guest Anchor controller switchover, mobility tunnels stay active, APs remain connected, clients rejoin at MA or MC, and are anchored on the new Active controller.