Refer to the exhibit. The WLC administrator sees that the controller to which a roaming client associates has Mobility Role Anchor configured under Clients > Detail. Which type of roaming is supported

Question

Exhibits

Options

• AIndirect
• BLayer 3 intercontroller
• CLayer 2 intercontroller
• DIntercontroller

• A
  12% (6)
• B
  81% (42)
• C
  2% (1)
• D
  6% (3)

Explanation

Explanation

When a WLC shows Mobility Role: Anchor under Clients > Detail, it indicates the controller is acting as the anchor controller in a Layer 3 intercontroller roam - meaning the client has moved to a different subnet (different IP addressing domain) served by a foreign controller, while the anchor controller maintains the original IP address assignment to preserve the client's session. This anchor/foreign controller relationship is the defining characteristic of Layer 3 intercontroller roaming, making B correct.

• A (Indirect) is incorrect because "Indirect" is not a standard Cisco WLC roaming classification - this is a distractor term.
• C (Layer 2 intercontroller) is incorrect because Layer 2 roaming occurs between controllers within the same subnet, so no anchor role is needed - the client simply reassociates and keeps its IP without any special mobility tunneling.
• D (Intercontroller) is too generic - while technically roaming is occurring between controllers, it doesn't specifically identify the anchor role behavior, which is exclusive to Layer 3.

Memory Tip: Think "Anchor = Layer 3" - just like a ship's anchor keeps it in place despite moving water, the anchor controller keeps the client's original IP address even as they roam across different subnets.

No community discussion yet for this question.