Reason to Implement LAG on a Cisco WLC
What is one reason to implement LAG on a Cisco WLC?
Community Insight
The question tests the purpose of LAG on a WLC, and the trap is confusing LAG with WLC high availability (stateful/SSO failover) or assuming it changes VLAN assignments during a failure.
This CCNA 200-301 question asks why a Link Aggregation Group (LAG) is implemented on a Cisco Wireless LAN Controller. The page establishes that LAG bundles multiple physical ports into one logical link to gain both added bandwidth through load balancing and link redundancy if a member port or cable fails.
Option D is the most tempting wrong answer: stateful and link-state failover describes WLC high availability / SSO redundancy between controllers, not the function of a port-channel LAG on a single controller. Options A and B also misattribute security encryption and VLAN changes to LAG.
Community Discussion (4 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
A Link Aggregation Group on a Cisco WLC bundles multiple physical switch-facing ports into a single logical port-channel using LACP or a static (on) mode. Because multiple links carry traffic in the bundle, the controller gains aggregate bandwidth and per-flow load balancing across member links. Equally important, if one member port, cable, or switch port fails, the remaining links continue carrying traffic, so the wireless control link is not lost. This dual benefit of link redundancy plus load balancing is exactly what option C describes, and it matches Cisco's documented purpose for LAG on WLC platforms such as the 2500/5500/8500 and Catalyst 9800 series.Why the Other Options Are Wrong
Option A is incorrect because LAG is a Layer 2 link-bundling feature; it does not encrypt management frames — that is the role of management frame protection (MFP/802.11w) and of the Dataplane Security feature. Option B is incorrect because a LAG bundles ports into one logical interface carrying the same VLANs; it does not make ports failover onto different VLANs, and member links in a port-channel must have consistent VLAN configurations. Option D describes WLC high availability with stateful (SSO) failover between a primary and standby controller, which is a separate controller-redundancy feature, not a property of LAG, as TMan2000 also noted.Community Comment Notes
TMan2000's comment directly supports option C with the reasoning "Multiple links → more reliability + load sharing" and correctly separates LAG from HA by noting stateful failover belongs to WLC high availability. Arinamohammed's comment "why D is not correct?" reflects the most common point of confusion addressed above. The remaining comments on the thread are greetings and do not add technical substance to the discussion.Exam Strategy
When you see LAG or EtherChannel wording, immediately think bandwidth aggregation, load balancing, and link redundancy — not failover between devices. Reserve stateful/SSO failover language for WLC high-availability (AP SSO) scenarios between primary and standby controllers.
Frequently Asked Questions
Why is D (stateful and link-state failover) not the correct reason for LAG on a WLC?
Stateful (SSO) failover is a WLC high-availability feature between primary and standby controllers, preserving session state. LAG only bundles ports on a single controller's uplink and provides link redundancy, not session failover.
Can LAG members on a WLC be configured on different VLANs or ports with different speeds?
No. All member ports of a WLC LAG must share the same speed, duplex, and VLAN configuration and be connected to the same switch, since the bundle acts as one logical interface.
Related Analysis
Practice All 200-301 Questions
Access 220 questions with complete answers and detailed explanations.
View Full 200-301 Practice Test →