Controllers WLC_1 and WLC_2 are in the same mobility group. A wireless client that does not have the same VLAN interface roams from WLC_1 to WLC_2. What happens to the client roaming?

Deleting the context on WLC_1 and creating a new context on WLC_2 describes either a full re-association or a failed roam event, not the anchor-foreign mobility tunnel mechanism used in Layer 3 roaming.

Fully moving the client context from WLC_1 to WLC_2 describes a Layer 2 intra-VLAN roam where the same VLAN exists on the destination controller; because the VLAN is absent on WLC_2, WLC_1 cannot release its anchor role.

Choice C also describes a context copy but does not correctly characterize the anchor-foreign relationship or the traffic tunneling behavior; option D accurately reflects that WLC_1 retains anchor duties and forwards traffic from the wired side.

In a Layer 3 inter-controller roam, the client context is copied from WLC_1 to WLC_2, and WLC_1 remains as the anchor controller because the client's VLAN interface does not exist on WLC_2. WLC_2 becomes the foreign controller and encapsulates all client traffic in a mobility tunnel directed back to WLC_1, which forwards it to the wired network. This preserves the client's original IP address and session state across the roam without requiring a DHCP renewal.