Question 350
At the Umberfield infrastructure service operator, a fleet manager upgrades FortiOS but neglects FortiSwitchOS compatibility and causes managed-switch instability. What risk should the team identify as the primary issue?
Explanation
Correct Answer
The architectural weakness is that firmware version mismatches can break expected FortiLink and feature operation. It can be addressed through the controlled change to validate the Fortinet compatibility guidance and stage supported switch firmware upgrades from the management controller.
Incorrect Answers
The offered action is: Missing port identity makes correct endpoint provisioning and incident isolation harder. It is associated with this separate technical condition: Missing port identity makes correct endpoint provisioning and incident isolation harder. The actual incident concerns a different dependency: Firmware version mismatches can break expected FortiLink and feature operation. The corresponding change is: Firmware version mismatches can break expected FortiLink and feature operation.
Split-interface redundancy intentionally limits active forwarding until a supported MCLAG state permits more. That may occur elsewhere, but the evidence at the Umberfield infrastructure service operator instead points to the fact that firmware version mismatches can break expected FortiLink and feature operation.
The offered alternative is: Two physical uplinks to independent peers are not a coordinated aggregate by default. It addresses this separate failure mode: Two physical uplinks to independent peers are not a coordinated aggregate by default. In the current case, the observed mechanism is: Firmware version mismatches can break expected FortiLink and feature operation. The keyed action, Firmware version mismatches can break expected FortiLink and feature operation., targets that condition more directly.