Two WLCs are mobility peers. A client roams from AP1 on WLC1 to AP2 on WLC2 and the controllers use different VLANs. How is the client's entry handled for inter-subnet roaming?

When a client roams between WLCs in different subnets, the original WLC (WLC1 in this case) becomes the "anchor" controller. It maintains the client's original IP address and security context. WLC1 creates an anchor entry for the client in its database. The new WLC (WLC2) where the client roams becomes the "foreign" controller. WLC2 creates a foreign entry for the client in its database and tunnels the client's traffic back to WLC1. This ensures the client maintains its IP address and session continuity despite changing subnets. The other options incorrectly assign the anchor or foreign roles, or reverse the data flow.