H31-341_V2.5 · Question #915
LAG can only be configured in non-load sharing mode
The correct answer is B. False. B is correct because LAG (Link Aggregation Group) supports both load-sharing and non-load-sharing modes. In load-sharing mode, traffic is distributed across all active member links using hashing algorithms (based on MAC, IP, or port), maximizing bandwidth utilization. In…
Question
LAG can only be configured in non-load sharing mode
Options
- ATrue
- BFalse
How the community answered
(43 responses)- A19% (8)
- B81% (35)
Explanation
B is correct because LAG (Link Aggregation Group) supports both load-sharing and non-load-sharing modes. In load-sharing mode, traffic is distributed across all active member links using hashing algorithms (based on MAC, IP, or port), maximizing bandwidth utilization. In non-load-sharing (active/standby) mode, one link carries traffic while others remain on standby for failover - but both modes are valid LAG configurations.
Option A is wrong because it incorrectly restricts LAG to only non-load-sharing mode, which would eliminate the primary use case of LAG: aggregating bandwidth across multiple parallel links.
Memory tip: Think of LAG as a "bundle of cables" - you can either use all cables simultaneously (load sharing) or keep spares on standby (non-load sharing). LAG supports both strategies, so any answer claiming it's limited to just one mode is false.
Topics
Community Discussion
No community discussion yet for this question.