Question 820
At the Goldport branch IT department, a remote FortiSwitch island cannot reach its controller after an upstream WAN route update. Which setting or practice should be reviewed in future?
Explanation
Correct Answer
After implementation, the team should monitor controller reachability across routed WAN changes as the appropriate recurring safeguard against the identified issue.
Incorrect Answers
Test upgrade compatibility in a staging environment first. That safeguard would help prevent recurrence of: An incompatible controller and switch software combination can disrupt FortiLink management. The risk being reviewed here is instead: FortiLink over Layer 3 requires functional routed controller reachability. The matching ongoing control is: Monitor controller reachability across routed WAN changes.
The suggested preventive check is: Alert on binding renewal failures when enabling anti-spoofing. Its technical scope concerns: Stale or absent IP-to-MAC-to-port bindings can reject otherwise valid packets. This question asks how to sustain control over: FortiLink over Layer 3 requires functional routed controller reachability. The more targeted safeguard is: Monitor controller reachability across routed WAN changes.
Remove mirrors and delete expired sensitive captures after each incident. That safeguard would help prevent recurrence of: Network diagnostic captures may expose credentials or customer information unrelated to the incident. The risk being reviewed here is instead: FortiLink over Layer 3 requires functional routed controller reachability. The matching ongoing control is: Monitor controller reachability across routed WAN changes.