C is correct

mobility tunnel allows the controllers to share information about client devices, facilitating seamless roaming as clients move between access points managed by different controllers. CAPWAP is used primarily for communication between WLCs and their associated access points. It manages the configuration, control, and management of APs. While CAPWAP tunnels do carry data and control traffic between APs and WLCs, they are not specifically used to facilitate intercontroller roaming.

It is asking for, "TYPE" of tunnel. Not the protocol used. C is the most specific answer to this question - always go exactly what is being asked. https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/213913-building-mobility-tunnels-on-catalyst-98.html

Mobility for intercontroller roaming. https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-5/config-guide/b_cg85/overview.pdf

from OCG Chapter 19 page 550: Recall that Cisco controllers use CAPWAP tunnels to connect with lightweight APs. CAPWAP tunnels are also built between controllers for layer 3 roaming. The tunnel tethers the client to its original anchor controller (and original IP subnet), regardless of its location or how many controllers it roams through. answer is A

ill pick C, cause it asks for "type", not for protocol

The Cisco Catalyst 9800 Series Wireless Controller mobility tunnel is a CAPWAP tunnel with control path (UDP 16666) and data path (UDP 16667). The control path is DTLS encypted by default. Data path DTLS can be enabled when you add the mobility peer.

Answer appears to be C. While it's true that mobility tunnels are build from CAPWAP tunnels both GPT4 and the following link are saying mobility https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-5/config-guide/b_cg85/overview.html

For Layer 3 intercontroller roaming its CAPWAP. But its not true for Layer 2 inter controller roaming.

Should be C. Mobility WLCs need mobility tunnels in order for clients to roam between APs on the different controllers. I promise lol

I'm voting A because of question 935.

A Layer 3 intercontroller roam involves building an additional CAPWAP tunnel between the client’s initial WLC and the WLC to which it has roamed. The tunnel transmits the data to and from the client just like it is still associated with the original IP subnet and WLC. When a Layer 3 roam happens, the original WLC is called the anchor controller, and the current WLC where the roamed client is reassociated is called the foreign controller. The client is anchored to the original WLC even if it roams to different controllers.

To enable inter-controller roaming (or inter-controller mobility) between two WLAN Controllers (WLCs), a Layer 3 tunnel is typically required. This type of tunnel allows client session information to be securely transferred between the controllers, facilitating seamless handoff of clients as they move between different areas covered by different controllers within the same mobility domain. Ans: A

C is correct

i'm going with C

A Layer 3 intercontroller roam involves building an additional CAPWAP tunnel between the client’s initial WLC and the WLC to which it has roamed.

"Recall that Cisco controllers use CAPWAP tunnels to connect with lightweight APs. CAP- WAP tunnels are also built between controllers for Layer 3 roaming. The tunnel tethers the client to its original anchor controller (and original IP subnet), regardless of its location or how many controllers it roams through." - OCG On page 551 of the OCG you can also see a clear picture of the tunnel between the 2 WLCs