nerdexam
Cisco

350-401 · Question #135

When a wireless client roams between two different wireless controllers, a network connectivity outage is experience for a period of time. Which configuration issue would cause this problem?

The correct answer is B. Not all of the controllers within he mobility group are using the same virtual interface IP address.. Explanation When wireless clients roam between controllers, each controller uses a virtual interface IP address as a common gateway to manage client reassociation and DHCP processes during roaming - all controllers in the same mobility group must share the identical virtual inter

Submitted by lukas.cz· Mar 6, 2026Infrastructure

Question

When a wireless client roams between two different wireless controllers, a network connectivity outage is experience for a period of time. Which configuration issue would cause this problem?

Options

  • ANot all of the controllers in the mobility group are using the same mobility group name.
  • BNot all of the controllers within he mobility group are using the same virtual interface IP address.
  • CAll of the controllers within the mobility group are using the same virtual interface IP address.
  • DAll of the controllers in the mobility group are using the same mobility group name.

How the community answered

(60 responses)
  • A
    3% (2)
  • B
    93% (56)
  • C
    2% (1)
  • D
    2% (1)

Explanation

Explanation

When wireless clients roam between controllers, each controller uses a virtual interface IP address as a common gateway to manage client reassociation and DHCP processes during roaming - all controllers in the same mobility group must share the identical virtual interface IP address for seamless roaming to occur. If controllers use different virtual interface IP addresses, the client's roaming process breaks down, causing the connectivity outage described in the question, making B correct.

Option A is incorrect because having different mobility group names would prevent controllers from forming a mobility group altogether - controllers wouldn't communicate, but this is a different issue than a roaming outage between otherwise functioning controllers. Option C is incorrect because all controllers should share the same virtual interface IP address - this is the desired, correct configuration, not a problem. Option D is incorrect because sharing the same mobility group name is also correct and required behavior - it's what allows controllers to communicate and coordinate roaming.

Memory Tip: Think of the virtual interface IP as a "shared handshake address" - if controllers don't agree on it, the client gets confused during the handoff. Remember: same virtual IP = smooth roam; different virtual IP = dropout!

Topics

#Wireless Mobility#Cisco WLC#Virtual Interface#Client Roaming

Community Discussion

No community discussion yet for this question.

Full 350-401 Practice