What Characterizes Seamless Layer 3 Roaming in Cisco Wireless Networks?

What is a characteristic of Layer 3 roaming?

  1. It provides seamless roaming between APs that are connected to different Layer 3 networks and different mobility groups.
  2. It is only supported on controllers that run SSO.
  3. Clients must obtain a new IP address when they roam between APs.
  4. It provides seamless client roaming between APs in different Layer 3 networks but within the same mobility group. Source Reference Answer

Community Votes

D
100%

100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

This question evaluates your understanding of Cisco WLC mobility group boundaries, specifically that seamless Layer 3 roaming preserves IP addresses only when controllers share the same mobility group configuration.

Layer 3 roaming enables wireless clients to traverse different IP subnets while retaining their original IP address. Community consensus strongly supports option D, confirming that seamless handoffs require all participating controllers to belong to the same mobility group.

Many candidates incorrectly choose option A, mistakenly believing that cross-subnet roaming inherently requires separate mobility groups. In reality, placing controllers in different mobility groups disrupts the seamless handoff, often forcing re-authentication or DHCP renewal, which contradicts the core definition of Layer 3 client roaming.

Community Discussion (6 comments)

matass_md 👍 1 Selected: D
D is correct . From Cisco <As the client moves from AP to AP, the controller manages all roaming activity, and the client is not affected. Even when a client roams to a different controller, it is not affected and will not even recognize the roaming event. This seamless roaming process implies that both controllers are IN THE SAME mobility group or domain.>
dkonly 👍 1 Selected: A
Answer A is correct "Layer 3 roaming in wireless networks typically takes place between different mobility groups (but in the same mobility domain). A mobility group refers to a set of WLCs that share information to facilitate client roaming. When a client device roams between access points controlled by different WLCs within the same mobility group, it’s usually referred to as layer 2 roaming. In this scenario, the client maintains its IP address and session as it moves between access points, and the WLCs coordinate handoffs seamlessly. However, when a client roams between access points controlled by WLCs in different mobility groups, it’s considered layer 3 roaming. In this case, the client may need to obtain a new IP address and establish a new session as it moves between different subnets or networks managed by different WLCs."
MrG 👍 2 Selected: D
chatGPT agrees
NetworkJanitor 👍 3
It's D. The "client" key word is missing from A, making it incorrect. A successful L3 client roam is provided by controllers in different groups. For Layer 3 roaming to function effectively within Cisco Mobility Groups, several dependencies must be met: 1. Mobility Group Configuration: All participating WLCs must be correctly configured within the same mobility group to share client and access point information. 2. Mobility List Entries: Controllers can communicate across different mobility groups if they include each other in their mobility lists, allowing clients to roam between access points in different groups. 3. Consistent IP Addressing: Clients should maintain the same IP address while roaming across different subnets. This is facilitated by Cisco Centralized Key Management (CCKM) and proactive key caching (PKC), which are specifically designed for inter-mobility-group roaming. 4. Multicast Messaging: Enabling multicast messaging can optimize communication between controllers, especially in large mobility groups, reducing network traffic and improving efficiency.
16561f6 👍 4
The correct answer is: A. It provides seamless roaming between APs that are connected to different Layer 3 networks and different mobility groups. Explanation: Layer 3 Roaming: This type of roaming allows clients to move between access points (APs) that may be on different subnets (Layer 3 networks) and even different mobility groups. It effectively enables clients to maintain their connections and session continuity, even as they switch between these different network environments
Hiro00 👍 3 Selected: D
D is correct.

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Expert Analysis

Understanding Layer 3 Roaming Architecture

In Cisco enterprise wireless deployments, Layer 3 roaming occurs when a client moves between access points that are connected to different IP subnets (Layer 3 networks). Unlike Layer 2 roaming, where the client stays on the same broadcast domain, Layer 3 roaming must preserve the client’s existing IP address to maintain active sessions (VoIP, video, SSH) without interruption.

Why Option D is Correct

Option D accurately describes the fundamental requirement for seamless Layer 3 roaming: controllers must reside within the same mobility group. When WLCs share a mobility group, they exchange client context information (including IP addresses, security policies, and session state) via the Mobility Protocol. As noted by community contributor matass_md, "the controller manages all roaming activity, and the client is not affected... This seamless roaming process implies that both controllers are IN THE SAME mobility group." Therefore, moving across different Layer 3 networks but staying within the same mobility group delivers true seamless roaming.

Why Other Options Are Incorrect

  • Option A suggests roaming across different mobility groups. While technically possible with advanced configurations, it breaks the seamless handoff. Controllers outside the same mobility group do not share real-time client state, often triggering full re-authentication or requiring the client to request a new IP, which contradicts "seamless."
  • Option B claims SSO (Stateful Switchover) is a strict requirement. SSO improves controller availability but is not a prerequisite for Layer 3 roaming functionality itself.
  • Option C states clients must obtain a new IP address. This directly contradicts the purpose of Layer 3 roaming, which is explicitly designed to retain the original IP address across subnet boundaries.

Practical Takeaway

As highlighted by NetworkJanitor, the wording in option A lacks the critical "client" context and misstates the mobility group dependency. Always associate "seamless Layer 3 roaming" with "same mobility group + different subnets."

Official Reference

https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/configuration_guide/b-wl-cg-9800/b_wl_cg_9800_chapter_011.html

Exam Strategy

When answering wireless roaming questions, immediately scan for keywords like "seamless," "IP address retention," and "mobility group." Cisco exams heavily test the boundary conditions of mobility domains; remember that seamless handoffs (both L2 and L3) strictly require controllers to be in the same mobility group, while different mobility groups introduce latency, re-authentication, or IP changes.

Related Analysis

Refer to the exhibit. What is achieved by the XML code? - ![

S-Grade

Which network devices secure API platforms?

A-Grade

What are two benefits of using Cisco TrustSec? (Choose two.)

S-Grade

Practice All 350-401 Questions

Access 218 questions with complete answers and detailed explanations.

View Full 350-401 Practice Test →

← Back to 350-401 Study Guide