Which action occurs during a Layer 3 roam?

A primary benefit of Layer 3 roaming is that the client retains its current IP address, avoiding any network disruption that would result from acquiring a new address.

While controllers assume roles like 'anchor' and 'foreign,' the specific action of marking a client is a part of the process, but the core event enabling mobility is the transfer of the client's complete database entry.

In a Layer 3 roam, the client's database entry, which contains its authentication state, IP address, and security context, is transferred from the original (anchor) controller to the new (foreign) controller, ensuring seamless session continuity.

Client traffic is typically tunneled back to the original (anchor) controller after a Layer 3 roam to maintain the client's original IP subnet and gateway, but this is a consequence of the client database entry being transferred, not the transfer action itself.