Question 410
At the Redhaven campus infrastructure group, an access switch has uplinks to two FortiSwitch distribution peers but the peers lack an approved MCLAG configuration. What risk should the team identify as the primary issue?
Explanation
Correct Answer
This identifies the root issue: two physical uplinks to independent peers are not a coordinated aggregate by default. At the Redhaven campus infrastructure group, the team should therefore deploy supported MCLAG peer and inter-chassis design before activating parallel uplinks.
Incorrect Answers
The offered action is: Overlay transport requires explicit compatibility and control reachability beyond a regular copper uplink. It is associated with this separate technical condition: Overlay transport requires explicit compatibility and control reachability beyond a regular copper uplink. The actual incident concerns a different dependency: Two physical uplinks to independent peers are not a coordinated aggregate by default. The corresponding change is: Two physical uplinks to independent peers are not a coordinated aggregate by default.
The offered alternative is: The documented shared FortiSwitch port feature set does not include DHCP snooping. It addresses this separate failure mode: The documented shared FortiSwitch port feature set does not include DHCP snooping. In the current case, the observed mechanism is: Two physical uplinks to independent peers are not a coordinated aggregate by default. The keyed action, Two physical uplinks to independent peers are not a coordinated aggregate by default., targets that condition more directly.
Unreviewed automatic authorization can admit a connected switch before identity and installation are checked. That is not the mechanism that accounts for the stated failure at the Redhaven campus infrastructure group.