A customer has implemented an N+1 cluster of WLCs without using an AP high availability configuration and is experiencing an unacceptable delay when clients are roaming. Which two configuration…

Question

Options

• ASet master controller mode on the least loaded WLC.
• BSet the AP failover priority identically on contiguous access points.
• CPut all WLCs in the same mobility group.
• DPlace all WLCs in the same RF group.
• EDefine a primary controller on contiguous access points.

• A
  5% (1)
• B
  15% (3)
• C
  75% (15)
• D
  5% (1)

Explanation

Two changes address roaming delay in this scenario: (C) Placing all WLCs in the same mobility group enables inter-controller roaming by allowing WLCs to share client state (PMK caching, 802.11r keys, IP binding) over the mobility tunnel. Without a shared mobility group, each controller roam is treated as a new association, causing full re-authentication delays. (E) Defining a primary controller on contiguous access points ensures APs in the same physical coverage area join the same WLC, maximizing intra-controller roams-which are near-instantaneous because no inter-WLC handoff is needed. The distractors are wrong because: (A) Master controller mode controls where new APs join, not roaming behavior; (B) identical AP failover priority is a high-availability setting, not a roaming optimization; (D) RF groups coordinate RRM (radio resource management) across WLCs but do not affect client mobility or roaming speed.

No community discussion yet for this question.