Which statement is true about intercontroller roaming?

Intercontroller roaming refers to the ability of a wireless client to move seamlessly between access points (APs) that are managed by different controllers. When intercontroller roaming occurs, it is essential that the client remains authenticated throughout the process. This means that as a client transitions from one AP to another, even if those APs are managed by different controllers, the client does not lose its authentication status.

Maintaining authentication is crucial for user experience, as it allows for continuous connectivity without forcing the user to enter credentials again during the roaming process. This seamless transition is particularly important in environments where mobility is critical, such as in corporate or educational settings, where users often move between different access points.

The other statements incorporate inaccuracies regarding the nature of intercontroller roaming. For instance, changing the client’s SSID would disrupt the connection and typically requires the user to authenticate again. Similarly, requiring re-authentication for every switch conflicts with the principle of seamless mobility that intercontroller roaming aims to provide. Lastly, while roaming might occur in layered scenarios, it is not restricted to layer 3; roaming can also happen at layer 2 depending on the network configuration.