Question 110
At the Elmhurst infrastructure service operator, a FortiGate manages the first FortiSwitch but a new downstream member never appears through the intended inter-switch link. What risk should the team identify as the primary issue?
Explanation
Correct Answer
This identifies the root issue: a downstream switch cannot be discovered if its inter-switch connection lacks the required FortiLink control path. At the Elmhurst infrastructure service operator, the team should therefore validate the FortiSwitch port role and supported ISL discovery or configured inter-switch trunk.
Incorrect Answers
The offered action is: HA failover can strand managed switches when the new active FortiGate has no valid management path. It is associated with this separate technical condition: HA failover can strand managed switches when the new active FortiGate has no valid management path. The actual incident concerns a different dependency: A downstream switch cannot be discovered if its inter-switch connection lacks the required FortiLink control path. The corresponding change is: A downstream switch cannot be discovered if its inter-switch connection lacks the required FortiLink control path.
The offered alternative is: An ordinary access VLAN cannot preserve multiple independent customer VLAN identities across a provider handoff. It addresses this separate failure mode: An ordinary access VLAN cannot preserve multiple independent customer VLAN identities across a provider handoff. In the current case, the observed mechanism is: A downstream switch cannot be discovered if its inter-switch connection lacks the required FortiLink control path. The keyed action, A downstream switch cannot be discovered if its inter-switch connection lacks the required FortiLink control path., targets that condition more directly.
A route pointing at an unreachable neighbor cannot forward outside connected subnets. That is not the mechanism that accounts for the stated failure at the Elmhurst infrastructure service operator.