In this scenario, the client is placed in the wrong VLAN (VLAN 50) even though the ISE server is configured to assign VLAN 100. The key part of the issue is that the VLAN assignment returned by ISE is not being applied correctly.
Option A: "Configure the policy profile to allow ISE to override the VLAN."This is the correct answer. The policy profile on the Wireless LAN Controller (WLC) should be configured to allow the ISE server's VLAN assignment to override the locally configured VLAN settings on the WLC. Without this, the WLC might default to its pre-configured VLAN (VLAN 50) instead of the VLAN assigned by ISE (VLAN 100).
Option B: "Configure VLAN 100 as an SVI on the WLC."This option is unnecessary. While an SVI (Switched Virtual Interface) is required to route between VLANs, it is not the cause of the issue here. The problem is that the correct VLAN (VLAN 100) is not being applied to the client, not that the WLC lacks an SVI.
Option C: "Configure VLAN 100 on the trunk ports of the WLC."This option is also not relevant. The issue is not with trunking but with VLAN assignment from ISE. The trunking configuration ensures that VLANs are allowed across ports, but it does not address the client being placed in the wrong VLAN.
Option D: "Configure AAA VLAN enable on the WLAN."This option is not directly related to the issue. While enabling AAA VLAN can allow for more dynamic VLAN assignments, the core issue is related to overriding the default VLAN setting from ISE, which is handled by configuring the policy profile on the WLC.
Therefore,Option Ais the correct solution, as it ensures the WLC will allow the ISE server's VLAN assignment to override the default VLAN on the WLC, resolving the issue of incorrect VLAN assignment.
