Question 630
A rogue switch appears as discovered and an administrator considers enabling global auto-authorization without checking its identity. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
Explanation
Correct Answers
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. This is the configuration or remediation half of the requested TWO-step pair.
Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility. Switch discovery is not the same as authorization; auto-authorization has governance implications and a managed-mode transition may reboot the device. The paired action is: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic. This step concerns QinQ outer and inner VLAN tenant mapping and is not part of the required paired solution. The correct action and evidence are: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition. Together with: Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status. This step concerns FortiSwitch multi-tier managed topology and is not part of the required paired solution. The correct action and evidence are: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition. Together with: Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
Routes and interfaces are configured at the appropriate control plane and persist after synchronization or reboot. This step concerns FortiSwitch standalone versus FortiLink managed L3 ownership and is not part of the required paired solution. The correct action and evidence are: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition. Together with: Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.