Refer to the exhibit. An engineer notices that traffic is not load-balanced across all four links. What is the most likely cause?
Source-dest-id can lead to polarization if many flows share the same pair; other algorithms like source-dest-ox-id provide better distribution.
Why this answer
The load-balancing algorithm for Fibre Channel port channels uses source-dest-id (SID and DID) by default. If the traffic flows are between a small number of source-destination pairs, the hash results will map most flows to the same link, preventing even distribution across all four links. This is a common cause of perceived load imbalance even when all links are operational.
Exam trap
Cisco often tests the misconception that load imbalance is always due to a configuration error or link failure, when in fact the default hash algorithm's behavior with limited source-destination pairs is the root cause.
How to eliminate wrong answers
Option A is wrong because the minimum-links setting (e.g., 2) only prevents the port channel from coming up if fewer than that number of links are active; it does not affect load balancing once the channel is up. Option B is wrong because LACP (IEEE 802.3ad) is not used on Fibre Channel; Fibre Channel port channels use the Fibre Channel standard (FC-BB-5/6) or Cisco's proprietary PAgP for FCoE, but LACP is irrelevant here. Option D is wrong because if the port channel were in admin down state, no traffic would pass at all, not just uneven load balancing.
Option E is wrong because all links in a Fibre Channel port channel must be in the same VSAN; if they were not, the port channel would not form or would have errors, but the exhibit shows the channel is up.