350-401 Question #1031: Real Exam Question with Answer & Explanation

Question

A customer has two Cisco WLCs that manage separate APs throughout a building. Each WLC advertises the same SSID but terminates on different interfaces. Users report that they drop their connections and change IP addresses when roaming. Which action resolves this issue?

Options

• AConfigure high availability.
• BEnable fast roaming.
• CConfigure mobility groups.
• DEnable client load balancing

Explanation

Mobility Groups Resolve Cross-WLC Roaming Issues

Configuring mobility groups (Option C) allows the two WLCs to communicate and share client state information with each other. When a client roams from an AP on one WLC to an AP on the other, the mobility group enables the WLCs to tunnel the client's traffic back to the original WLC, preserving the client's IP address and session - this is called an inter-controller roam.

• Option A (High Availability) is wrong because HA is designed for WLC redundancy/failover, not for maintaining seamless roaming between two active controllers managing different APs.
• Option B (Fast Roaming) addresses authentication speed (e.g., 802.11r/OKC) to reduce re-association delays, but it does not prevent IP address changes when roaming across separate WLCs.
• Option D (Client Load Balancing) distributes clients across APs for better capacity management, but has no role in preserving IP addresses during roaming.

🧠 Memory Tip: Think of mobility groups as a "buddy system" between WLCs - they share client information so roaming users keep their IP address, just like staying logged into the same account across devices. If clients are changing IPs, the WLCs aren't talking to each other - mobility groups fix that conversation.

No community discussion yet for this question.