A network engineer is experiencing issues enabling LAG on the WLC. Which four characteristics should be validated to ensure LAG configuration? (Choose four.)

When LAG is enabled on the WLC, all physical ports automatically join the LAG bundle by default without requiring individual port-level configuration on the controller.

When LAG is enabled, all WLC interfaces are associated with the logical LAG bundle rather than being moved specifically to port 1; there is no designated anchor port in a WLC LAG configuration.

Primary and secondary port assignments describe the WLC port redundancy feature, which is a separate mechanism from LAG; LAG does not use primary or secondary port designations per interface.

Multiple untagged interfaces cannot be mapped to the same port under LAG because each physical port supports only one native (untagged) VLAN, and assigning multiple untagged interfaces would create a configuration conflict.

The switch-side EtherChannel must be statically configured as mode 'on' because the Cisco WLC does not support LACP or PAgP negotiation; dynamic EtherChannel modes will prevent the bundle from forming.

LAG provides physical redundancy so that if all but one port fail, the single remaining functional port continues to pass traffic for all WLC interfaces without interruption.

The WLC requires a reboot after LAG is enabled for the configuration change to take effect; LAG cannot be activated on a running controller without a reboot.