Fortinet NSE5_FSW_AD-7.6 Practice Test 63
Question 620
A shared FortiSwitch port carries two tenants but the controller creates both VLANs inside the wrong VDOM. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure.
- Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end.
- Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.
- Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover.
Explanation
Correct Answer
A:Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure. A VDOM creates a separate policy and routing context; it does not by itself make a shared physical switch port safe for all tenants. Verify the action with: Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.
Incorrect Answers
B:Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end. This action is relevant to FortiLink transport over nontrivial L2 or L3 paths, not the controlling requirement in this case. FortiLink over intermediate networks requires topology-specific settings; ordinary IP reachability alone does not establish FortiLink discovery. The targeted response is: Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure.
C: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: Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure.
D:Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover. This action is relevant to FortiSwitch native VLAN versus allowed VLANs, not the controlling requirement in this case. Native VLAN handling and tagged VLAN membership are different controls; a working physical link does not validate VLAN carriage. The targeted response is: Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure.
Question 621
An attacker spoofs the default gateway MAC using gratuitous ARP on a guest user VLAN. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence.
- Inspect ARP inspection status, DHCP snooping binding database, source MAC/IP, trusted ports and violation logs.
- Use supported dynamic ARP inspection with valid switch bindings to reject spoofed IP-MAC claims at untrusted edges.
- Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN.
- The intended tenant configuration changes while other tenants retain their segmentation and service.
Explanation
Correct Answers
B:Inspect ARP inspection status, DHCP snooping binding database, source MAC/IP, trusted ports and violation logs. DAI validation needs a reliable binding or exception policy; enabling it blindly can interrupt static-IP devices. The paired action is: Use supported dynamic ARP inspection with valid switch bindings to reject spoofed IP-MAC claims at untrusted edges. This is the diagnostic or verification half of the requested TWO-step pair.
C:Use supported dynamic ARP inspection with valid switch bindings to reject spoofed IP-MAC claims at untrusted edges. DAI validation needs a reliable binding or exception policy; enabling it blindly can interrupt static-IP devices. Verify the action with: Inspect ARP inspection status, DHCP snooping binding database, source MAC/IP, trusted ports and violation logs. This is the configuration or remediation half of the requested TWO-step pair.
Incorrect Answers
A:Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence. This step concerns Static port ACL forwarding decisions and is not part of the required paired solution. The correct action and evidence are: Use supported dynamic ARP inspection with valid switch bindings to reject spoofed IP-MAC claims at untrusted edges. Together with: Inspect ARP inspection status, DHCP snooping binding database, source MAC/IP, trusted ports and violation logs.
D:Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN. This step concerns MAC-based authentication and restricted legacy devices and is not part of the required paired solution. The correct action and evidence are: Use supported dynamic ARP inspection with valid switch bindings to reject spoofed IP-MAC claims at untrusted edges. Together with: Inspect ARP inspection status, DHCP snooping binding database, source MAC/IP, trusted ports and violation logs.
E:The intended tenant configuration changes while other tenants retain their segmentation and service. This step concerns Multi-tenant change verification and rollback and is not part of the required paired solution. The correct action and evidence are: Use supported dynamic ARP inspection with valid switch bindings to reject spoofed IP-MAC claims at untrusted edges. Together with: Inspect ARP inspection status, DHCP snooping binding database, source MAC/IP, trusted ports and violation logs.
Question 622
A trunk expects double-tagged frames but the upstream switch strips the outer service tag. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards.
- Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.
- Review queue maps, output drops, interface rate, strict versus weighted servicing and application latency.
- Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.
Explanation
Correct Answer
B:Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability. QinQ layering and VDOM assignment are separate controls; wrong outer tagging can mix customers even when inner VLAN IDs differ. The paired action is: Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.
Incorrect Answers
A:Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards. These observations are applicable to MCLAG multichassis access redundancy, but would not isolate the main failure first. The decisive evidence is: Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.
C:Review queue maps, output drops, interface rate, strict versus weighted servicing and application latency. These observations are applicable to Egress priority scheduling and congestion visibility, but would not isolate the main failure first. The decisive evidence is: Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.
D:Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state. These observations are applicable to Shared port multi-VDOM policy boundaries, but would not isolate the main failure first. The decisive evidence is: Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.
Question 623
After an unmanaged bridge is added, the same endpoint MAC repeatedly moves between ports and the team checks only DHCP leases. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted.
- Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.
- Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths.
- Trace DHCP and ARP exchanges at ingress and uplink to distinguish missing requests from blocked or malformed responses.
Explanation
Correct Answer
C:Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths. LLDP provides adjacent-device identity, while MAC learning maps forwarding; neither is a full routed trace by itself. Verify the action with: Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
Incorrect Answers
A:Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted. This action is relevant to FortiGate one-arm sniffer across managed switching, not the controlling requirement in this case. Sniffer placement determines visibility; absence of a packet at one observation point does not prove no packet existed elsewhere. The targeted response is: Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths.
B:Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic. This action is relevant to QinQ outer and inner VLAN tenant mapping, not the controlling requirement in this case. QinQ layering and VDOM assignment are separate controls; wrong outer tagging can mix customers even when inner VLAN IDs differ. The targeted response is: Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths.
D:Trace DHCP and ARP exchanges at ingress and uplink to distinguish missing requests from blocked or malformed responses. This action is relevant to Capture-based DHCP and ARP path isolation, not the controlling requirement in this case. A DHCP lease failure can originate at the client, switch, relay or server; capturing at one side alone is not always conclusive. The targeted response is: Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths.
Question 624
A staff laptop fails EAP-TLS because its certificate chain differs from the identity-server trust store. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state.
- Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test.
- Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes.
- Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile.
Explanation
Correct Answer
D:Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile. A physical link can be up while 802.1X blocks traffic; the switch is the authenticator, not the authentication server. The paired action is: Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior.
Incorrect Answers
A:Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state. These observations are applicable to NAC dynamic port policy device classification, but would not isolate the main failure first. The decisive evidence is: Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile.
B:Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test. These observations are applicable to RADIUS change of authorization and applied session policy, but would not isolate the main failure first. The decisive evidence is: Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile.
C:Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes. These observations are applicable to STP incident recovery with MAC flap evidence, but would not isolate the main failure first. The decisive evidence is: Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile.
Question 625
A new guest VLAN works on one FortiSwitch but is omitted from the FortiLink interswitch path. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- A failed managed switch can be replaced with supported firmware and restored authorized port/VLAN behavior.
- Managed status remains healthy and user traffic uses only its intended FortiLink-carried VLANs.
- Accidental downstream switches are contained without disabling legitimate uplinks that should exchange BPDUs.
- Troubleshooting evidence is sufficient to establish the fault without exporting unnecessary private communications.
Explanation
Correct Answer
B:Managed status remains healthy and user traffic uses only its intended FortiLink-carried VLANs. FortiLink transports management and data; a successful controller heartbeat does not guarantee a user VLAN or firewall session is permitted.
Incorrect Answers
A:A failed managed switch can be replaced with supported firmware and restored authorized port/VLAN behavior. This result relates to Config backup and firmware inventory evidence, not the acceptance condition under test. The relevant result is: Managed status remains healthy and user traffic uses only its intended FortiLink-carried VLANs.
C:Accidental downstream switches are contained without disabling legitimate uplinks that should exchange BPDUs. This result relates to BPDU guard on endpoint-facing ports, not the acceptance condition under test. The relevant result is: Managed status remains healthy and user traffic uses only its intended FortiLink-carried VLANs.
D:Troubleshooting evidence is sufficient to establish the fault without exporting unnecessary private communications. This result relates to Capture and confidentiality limits in incident response, not the acceptance condition under test. The relevant result is: Managed status remains healthy and user traffic uses only its intended FortiLink-carried VLANs.
Question 626
A new conference phone reboots when its extra display turns on despite a stable Ethernet link. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority.
- Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy.
- Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch.
- Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage.
Explanation
Correct Answer
D:Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage. Port count and Ethernet link state do not guarantee sufficient power for high-draw endpoints. Verify the action with: Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events.
Incorrect Answers
A:Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority. This action is relevant to LLDP-MED voice network policy advertisements, not the controlling requirement in this case. LLDP-MED exchanges policy hints with compatible endpoints; it does not substitute for port membership and DHCP. The targeted response is: Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage.
B:Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy. This action is relevant to MSTP region consistency and designated root, not the controlling requirement in this case. Different MST configuration identifiers split regions even if switch ports are physically connected. The targeted response is: Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage.
C:Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch. This action is relevant to FortiLink management interface provisioning, not the controlling requirement in this case. A FortiGate port not configured for FortiLink cannot assume managed-switch ownership from physical connection alone. The targeted response is: Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage.
Question 627
A provider configures S-VLAN on a tenant VDOM rather than the VDOM where its FortiLink parent exists. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Known printers and IoT devices enter their restricted VLANs while unknown endpoints have no excessive access.
- Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence.
- Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.
- Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.
- Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests.
Explanation
Correct Answers
C:Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability. QinQ layering and VDOM assignment are separate controls; wrong outer tagging can mix customers even when inner VLAN IDs differ. The paired action is: Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic. This is the diagnostic or verification half of the requested TWO-step pair.
D:Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic. QinQ layering and VDOM assignment are separate controls; wrong outer tagging can mix customers even when inner VLAN IDs differ. Verify the action with: Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability. This is the configuration or remediation half of the requested TWO-step pair.
Incorrect Answers
A:Known printers and IoT devices enter their restricted VLANs while unknown endpoints have no excessive access. This step concerns NAC dynamic port policy device classification and is not part of the required paired solution. The correct action and evidence are: Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic. Together with: Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.
B:Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence. This step concerns Managed tenant troubleshooting across controller and access layer and is not part of the required paired solution. The correct action and evidence are: Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic. Together with: Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.
E:Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests. This step concerns Multi-tenant change verification and rollback and is not part of the required paired solution. The correct action and evidence are: Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic. Together with: Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.
Question 628
An MCLAG access uplink fails after a peer link replacement and the team tests only physical LEDs. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology.
- Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles.
- Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context.
- Check client MAC learning, VLAN database, switch uplink tags, gateway ARP and port assignment on every hop.
- Runaway flooding is contained without blocking legitimate broadcast-based onboarding or multicast subscribers.
Explanation
Correct Answers
A:Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology. MCLAG redundancy depends on supported peer-link and aggregate design; two cables alone do not constitute working multichassis aggregation. The paired action is: Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles. This is the diagnostic or verification half of the requested TWO-step pair.
B:Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles. MCLAG redundancy depends on supported peer-link and aggregate design; two cables alone do not constitute working multichassis aggregation. Verify the action with: Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology. This is the configuration or remediation half of the requested TWO-step pair.
Incorrect Answers
C:Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context. This step concerns FortiSwitch SVI routing and connected routes and is not part of the required paired solution. The correct action and evidence are: Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles. Together with: Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology.
D:Check client MAC learning, VLAN database, switch uplink tags, gateway ARP and port assignment on every hop. This step concerns VLAN access isolation and troubleshooting of membership and is not part of the required paired solution. The correct action and evidence are: Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles. Together with: Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology.
E:Runaway flooding is contained without blocking legitimate broadcast-based onboarding or multicast subscribers. This step concerns Storm-control thresholds and broadcast containment and is not part of the required paired solution. The correct action and evidence are: Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles. Together with: Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology.
Question 629
After an unmanaged bridge is added, the same endpoint MAC repeatedly moves between ports and the team checks only DHCP leases. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- A failed managed switch can be replaced with supported firmware and restored authorized port/VLAN behavior.
- A moved device is traced to its current approved port and incorrect cross-connection is identified.
- The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate.
- Only intended networks are reachable through the configured route and the return path remains valid.
Explanation
Correct Answer
B:A moved device is traced to its current approved port and incorrect cross-connection is identified. LLDP provides adjacent-device identity, while MAC learning maps forwarding; neither is a full routed trace by itself.
Incorrect Answers
A:A failed managed switch can be replaced with supported firmware and restored authorized port/VLAN behavior. This result relates to Config backup and firmware inventory evidence, not the acceptance condition under test. The relevant result is: A moved device is traced to its current approved port and incorrect cross-connection is identified.
C:The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate. This result relates to FortiSwitch diagnostic commands and logs, not the acceptance condition under test. The relevant result is: A moved device is traced to its current approved port and incorrect cross-connection is identified.
D:Only intended networks are reachable through the configured route and the return path remains valid. This result relates to Static route and default gateway validation, not the acceptance condition under test. The relevant result is: A moved device is traced to its current approved port and incorrect cross-connection is identified.
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.
- Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.
- Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.
- Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.
- 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.
Explanation
Correct Answers
B: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.
D: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
A: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.
C: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.
E: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.