Question 150
At the Nortonwood managed-network provider, a procurement team assumes FortiLink-managed multiple switches behave as one chassis with one shared hardware configuration. Which underlying issue most directly explains this situation?
Explanation
Correct Answer
The evidence indicates that fortiGate manages every member separately even when the switches form one Layer 2 managed stack. The appropriate response is to distinguish FortiLink-managed Layer 2 stack supervision from the individual FortiSwitch devices and their controller objects and demonstrate that an operator can identify and configure each managed switch separately in the topology.
Incorrect Answers
A downstream switch cannot be discovered if its inter-switch connection lacks the required FortiLink control path. That is not the mechanism that accounts for the stated failure at the Nortonwood managed-network provider.
The offered principle is: Excess broadcasts can consume shared switching bandwidth and CPU resources. In the source material it is associated with: Excess broadcasts can consume shared switching bandwidth and CPU resources. This case has a different controlling cause: FortiGate manages every member separately even when the switches form one Layer 2 managed stack. Its keyed mechanism is: FortiGate manages every member separately even when the switches form one Layer 2 managed stack.
Although different MSTP region parameters change how peers interpret instances and topology, the presented symptoms do not support that as the primary cause; they indicate that fortiGate manages every member separately even when the switches form one Layer 2 managed stack. For the Nortonwood managed-network provider, the direct corrective action is to distinguish FortiLink-managed Layer 2 stack supervision from the individual FortiSwitch devices and their controller objects.