Question 600
A rogue switch appears as discovered and an administrator considers enabling global auto-authorization without checking its identity. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
Explanation
Correct Answer
Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition. Switch discovery is not the same as authorization; auto-authorization has governance implications and a managed-mode transition may reboot the device. Verify the action with: Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
Incorrect Answers
Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces. This action is relevant to Single FortiGate and single FortiSwitch topology, not the controlling requirement in this case. FortiLink carries management and data traffic; a valid management handshake does not prove every user VLAN is forwarded. The targeted response is: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.
Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records. This action is relevant to LLDP neighbor discovery and location information, not the controlling requirement in this case. LLDP is an L2 discovery protocol and cannot prove the whole routed service path or phone emergency-location correctness by itself. The targeted response is: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.
Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards. This action is relevant to FortiSwitch multi-tier managed topology, not the controlling requirement in this case. A FortiGate controls each FortiSwitch through the managed Layer-2 topology, but downstream reachability depends on upstream FortiLink links. The targeted response is: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.