Question 790
At the Quayside regional network integrator, switch uplinks carry user data but the FortiGate cannot manage the switch after a VLAN change. Which explanation best accounts for the concern?
Explanation
Correct Answer
The problem stems from the fact that user VLAN forwarding can survive while the specific controller management path is broken. A correct solution would restore the approved FortiLink management VLAN reachability and trunk membership and check that the switch regains a stable controller session while user forwarding remains correct.
Incorrect Answers
The offered principle is: Power state alone cannot prove the management discovery path is physically or logically available. In the source material it is associated with: Power state alone cannot prove the management discovery path is physically or logically available. This case has a different controlling cause: User VLAN forwarding can survive while the specific controller management path is broken. Its keyed mechanism is: User VLAN forwarding can survive while the specific controller management path is broken.
The offered principle is: Application slowness cannot be attributed to switching congestion without traffic-level evidence. In the source material it is associated with: Application slowness cannot be attributed to switching congestion without traffic-level evidence. This case has a different controlling cause: User VLAN forwarding can survive while the specific controller management path is broken. Its keyed mechanism is: User VLAN forwarding can survive while the specific controller management path is broken.
A capture from the wrong interface cannot show the target packet path. That may occur elsewhere, but the evidence at the Quayside regional network integrator instead points to the fact that user VLAN forwarding can survive while the specific controller management path is broken.