Fortinet NSE5_FSW_AD-7.6 Practice Test 65
Question 640
An installer assumes any FortiSwitch port will auto-discover FortiLink despite model-specific discovery defaults. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.
- Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image.
- Review queue maps, output drops, interface rate, strict versus weighted servicing and application latency.
- Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.
Explanation
Correct Answer
A:Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization. The FortiGate-managed FortiSwitch stack is a managed L2 topology, not automatically a single chassis or universal VSF-like control plane. The paired action is: Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles.
Incorrect Answers
B:Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image. These observations are applicable to FortiLink synchronization and upgrade troubleshooting, but would not isolate the main failure first. The decisive evidence is: Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.
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: Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.
D:Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings. These observations are applicable to LLDP neighbor discovery and location information, but would not isolate the main failure first. The decisive evidence is: Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.
Question 641
A branch uplink uses a multimode optic across a single-mode campus fiber run and never achieves light. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage.
- Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes.
- The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate.
- Inspect transceiver SKU, supported compatibility table, Tx/Rx optical power, interface alarms and cable plant type.
- Choose supported Fortinet transceivers and link media based on switch capability, optical reach and wavelength.
Explanation
Correct Answers
D:Inspect transceiver SKU, supported compatibility table, Tx/Rx optical power, interface alarms and cable plant type. Matching a mechanical optic cage is insufficient to prove optical or firmware compatibility. The paired action is: Choose supported Fortinet transceivers and link media based on switch capability, optical reach and wavelength. This is the diagnostic or verification half of the requested TWO-step pair.
E:Choose supported Fortinet transceivers and link media based on switch capability, optical reach and wavelength. Matching a mechanical optic cage is insufficient to prove optical or firmware compatibility. Verify the action with: Inspect transceiver SKU, supported compatibility table, Tx/Rx optical power, interface alarms and cable plant type. This is the configuration or remediation half of the requested TWO-step pair.
Incorrect Answers
A:Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage. This step concerns PoE and LLDP-MED endpoint power coordination and is not part of the required paired solution. The correct action and evidence are: Choose supported Fortinet transceivers and link media based on switch capability, optical reach and wavelength. Together with: Inspect transceiver SKU, supported compatibility table, Tx/Rx optical power, interface alarms and cable plant type.
B:Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes. This step concerns STP incident recovery with MAC flap evidence and is not part of the required paired solution. The correct action and evidence are: Choose supported Fortinet transceivers and link media based on switch capability, optical reach and wavelength. Together with: Inspect transceiver SKU, supported compatibility table, Tx/Rx optical power, interface alarms and cable plant type.
C:The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate. This step concerns FortiSwitch diagnostic commands and logs and is not part of the required paired solution. The correct action and evidence are: Choose supported Fortinet transceivers and link media based on switch capability, optical reach and wavelength. Together with: Inspect transceiver SKU, supported compatibility table, Tx/Rx optical power, interface alarms and cable plant type.
Question 642
A phone is moved to another floor but its advertised LLDP-MED location still references the old closet. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters.
- All subtending managed switches remain discoverable and user service survives expected single-link failures where supported.
- Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records.
- Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping.
- Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.
Explanation
Correct Answers
C:Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records. LLDP is an L2 discovery protocol and cannot prove the whole routed service path or phone emergency-location correctness by itself. Verify the action with: Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings. This is the configuration or remediation half of the requested TWO-step pair.
E:Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings. LLDP is an L2 discovery protocol and cannot prove the whole routed service path or phone emergency-location correctness by itself. The paired action is: Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
A:Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters. This step concerns Switch port speed and duplex commissioning and is not part of the required paired solution. The correct action and evidence are: Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records. Together with: Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.
B:All subtending managed switches remain discoverable and user service survives expected single-link failures where supported. This step concerns FortiSwitch multi-tier managed topology and is not part of the required paired solution. The correct action and evidence are: Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records. Together with: Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.
D:Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping. This step concerns FortiSwitch split port breakout mode and is not part of the required paired solution. The correct action and evidence are: Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records. Together with: Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.
Question 643
A switch CLI patch fixes a VLAN temporarily but disappears after controller synchronization. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration.
- Inspect hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect.
- Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
- Inspect factory-default mode, DHCP or discovery exchange, upstream native VLAN, FortiLink enablement, NTP and controller authorization.
Explanation
Correct Answer
A:Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration. Local changes on a FortiLink-managed switch can be discarded when the FortiGate controller reapplies its known configuration. The paired action is: Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting.
Incorrect Answers
B:Inspect hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect. These observations are applicable to FortiSwitch split port breakout mode, but would not isolate the main failure first. The decisive evidence is: Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration.
C:Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility. These observations are applicable to Discovered versus authorized FortiSwitch state, but would not isolate the main failure first. The decisive evidence is: Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration.
D:Inspect factory-default mode, DHCP or discovery exchange, upstream native VLAN, FortiLink enablement, NTP and controller authorization. These observations are applicable to Zero-touch provisioning and controller dependency checks, but would not isolate the main failure first. The decisive evidence is: Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration.
Question 644
An operator puts a VLAN under a WAN interface instead of the FortiLink interface used by the branch switches. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover.
- Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path.
- All subtending managed switches remain discoverable and user service survives expected single-link failures where supported.
- Inspect transceiver SKU, supported compatibility table, Tx/Rx optical power, interface alarms and cable plant type.
- Build FortiSwitch VLAN interfaces in the correct FortiLink context and assign ports through the managed switch controller.
Explanation
Correct Answers
B:Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path. A named VLAN in FortiOS is not proof its switch-port membership and L3 policy are correct. The paired action is: Build FortiSwitch VLAN interfaces in the correct FortiLink context and assign ports through the managed switch controller. This is the diagnostic or verification half of the requested TWO-step pair.
E:Build FortiSwitch VLAN interfaces in the correct FortiLink context and assign ports through the managed switch controller. A named VLAN in FortiOS is not proof its switch-port membership and L3 policy are correct. Verify the action with: Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path. This is the configuration or remediation half of the requested TWO-step pair.
Incorrect Answers
A:Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover. This step concerns FortiSwitch native VLAN versus allowed VLANs and is not part of the required paired solution. The correct action and evidence are: Build FortiSwitch VLAN interfaces in the correct FortiLink context and assign ports through the managed switch controller. Together with: Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path.
C:All subtending managed switches remain discoverable and user service survives expected single-link failures where supported. This step concerns FortiSwitch multi-tier managed topology and is not part of the required paired solution. The correct action and evidence are: Build FortiSwitch VLAN interfaces in the correct FortiLink context and assign ports through the managed switch controller. Together with: Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path.
D:Inspect transceiver SKU, supported compatibility table, Tx/Rx optical power, interface alarms and cable plant type. This step concerns Optic compatibility and laser diagnostic evidence and is not part of the required paired solution. The correct action and evidence are: Build FortiSwitch VLAN interfaces in the correct FortiLink context and assign ports through the managed switch controller. Together with: Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path.
Question 645
A switch has a supported breakout cable yet its configured phy-mode and child speeds do not match the attached peers. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping.
- Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting.
- Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage.
- Choose supported Fortinet transceivers and link media based on switch capability, optical reach and wavelength.
Explanation
Correct Answer
A:Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping. A physical QSFP cage does not guarantee that four independent Ethernet child ports can be enabled on every model. Verify the action with: Inspect hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect.
Incorrect Answers
B:Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting. This action is relevant to Managed switch configuration synchronization, not the controlling requirement in this case. Local changes on a FortiLink-managed switch can be discarded when the FortiGate controller reapplies its known configuration. The targeted response is: Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping.
C:Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage. This action is relevant to PoE and LLDP-MED endpoint power coordination, not the controlling requirement in this case. Port count and Ethernet link state do not guarantee sufficient power for high-draw endpoints. The targeted response is: Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping.
D:Choose supported Fortinet transceivers and link media based on switch capability, optical reach and wavelength. This action is relevant to Optic compatibility and laser diagnostic evidence, not the controlling requirement in this case. Matching a mechanical optic cage is insufficient to prove optical or firmware compatibility. The targeted response is: Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping.
Question 646
A FortiSwitch is asked to route between two user VLANs but the gateway addresses were configured only on hosts. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links.
- Verify model-specific PoE class, total switch power budget and per-port policy before enabling new powered devices.
- Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices.
- Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context.
Explanation
Correct Answer
D:Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context. Layer-3 SVI configuration and actual usable forwarding are separate from having a named Layer-2 VLAN. Verify the action with: Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway.
Incorrect Answers
A:Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links. This action is relevant to RPVST and supported STP mode interoperability, not the controlling requirement in this case. An STP mode change can change per-VLAN convergence behavior even if existing links remain physically up. The targeted response is: Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context.
B:Verify model-specific PoE class, total switch power budget and per-port policy before enabling new powered devices. This action is relevant to Power over Ethernet port controls and budgets, not the controlling requirement in this case. Not every FortiSwitch model or port supports identical PoE allocation or every attached device's peak draw. The targeted response is: Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context.
C:Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices. This action is relevant to Controller authorization and pending-switch state, not the controlling requirement in this case. Authorizing a switch is an administrative trust step; pending switch state is not evidence of a routing failure. The targeted response is: Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context.
Question 647
A firewall analyst captures only the routed interface while the failure occurs between two hosts in one switch VLAN. 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.
- Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location.
- Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings.
- Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths.
Explanation
Correct Answer
A:Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted. Sniffer placement determines visibility; absence of a packet at one observation point does not prove no packet existed elsewhere. Verify the action with: Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.
Incorrect Answers
B:Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location. This action is relevant to Managed switch port statistics and counter analysis, not the controlling requirement in this case. A port-up indicator or one successful ping is not proof that a congested or errored uplink is healthy. The targeted response is: Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted.
C:Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings. This action is relevant to Multi-tenant change verification and rollback, not the controlling requirement in this case. A change on shared physical transport can affect multiple VDOMs, even if each tenant's firewall policy is separate. The targeted response is: Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted.
D:Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths. This action is relevant to LLDP and MAC forwarding table extraction, not the controlling requirement in this case. LLDP provides adjacent-device identity, while MAC learning maps forwarding; neither is a full routed trace by itself. The targeted response is: Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted.
Question 648
A managed FortiSwitch loses VLAN policy after reboot because prior local CLI edits never entered FortiGate configuration. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings.
- Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices.
- Troubleshoot FortiLink discovery from physical and logical interface configuration through LLDP and management addressing.
- Investigate managed switch offline or configuration mismatch after firmware upgrade or controller resynchronization using both endpoints.
Explanation
Correct Answer
D:Investigate managed switch offline or configuration mismatch after firmware upgrade or controller resynchronization using both endpoints. Managed switches can be reachable at Layer 2 yet show stale policy after incompatible upgrade or failed controller push. Verify the action with: Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image.
Incorrect Answers
A:Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings. This action is relevant to IPv4 source guard and binding-based packet filtering, not the controlling requirement in this case. Source guard is an ingress source-binding check, not a full replacement for routed firewall policies or endpoint security. The targeted response is: Investigate managed switch offline or configuration mismatch after firmware upgrade or controller resynchronization using both endpoints.
B:Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices. This action is relevant to Controller authorization and pending-switch state, not the controlling requirement in this case. Authorizing a switch is an administrative trust step; pending switch state is not evidence of a routing failure. The targeted response is: Investigate managed switch offline or configuration mismatch after firmware upgrade or controller resynchronization using both endpoints.
C:Troubleshoot FortiLink discovery from physical and logical interface configuration through LLDP and management addressing. This action is relevant to FortiLink discovery failure and physical uplink path, not the controlling requirement in this case. A green Ethernet link is necessary for many paths but does not prove the FortiLink management protocol or discovery is working. The targeted response is: Investigate managed switch offline or configuration mismatch after firmware upgrade or controller resynchronization using both endpoints.
Question 649
A technician adds a slower interface to an existing aggregate without validating compatibility and member status. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- The correct link establishes at expected negotiated rate without recurring loss-of-signal or CRC errors.
- Approved aggregate members forward as one bundle while nonmatching links remain excluded.
- Switches reconnect to FortiLink and preserve approved VLAN/role configuration after the planned upgrade.
- The impacted client can communicate on the permitted VLAN while unrelated tenant or guest VLANs remain separated.
Explanation
Correct Answer
B:Approved aggregate members forward as one bundle while nonmatching links remain excluded. This is a measurable client, control-plane, or security outcome rather than a claim that configuration was entered. Passive LACP on both ends may not negotiate an active bundle, and individual green links do not prove aggregation.
Incorrect Answers
A:The correct link establishes at expected negotiated rate without recurring loss-of-signal or CRC errors. This result relates to Optic compatibility and laser diagnostic evidence, not the acceptance condition under test. The relevant result is: Approved aggregate members forward as one bundle while nonmatching links remain excluded.
C:Switches reconnect to FortiLink and preserve approved VLAN/role configuration after the planned upgrade. This result relates to Firmware and lifecycle preparation for FortiSwitch, not the acceptance condition under test. The relevant result is: Approved aggregate members forward as one bundle while nonmatching links remain excluded.
D:The impacted client can communicate on the permitted VLAN while unrelated tenant or guest VLANs remain separated. This result relates to VLAN access isolation and troubleshooting of membership, not the acceptance condition under test. The relevant result is: Approved aggregate members forward as one bundle while nonmatching links remain excluded.
Question 650
A managed switch's controller connection stays up while a trunk change removes the voice VLAN. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect FortiLink management state, native/tagged VLANs, port membership, FortiGate interface and active firewall policy.
- Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image.
- Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.
- Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions.
Explanation
Correct Answer
A:Inspect FortiLink management state, native/tagged VLANs, port membership, FortiGate interface and active firewall policy. FortiLink transports management and data; a successful controller heartbeat does not guarantee a user VLAN or firewall session is permitted. The paired action is: Verify FortiLink management status and user VLAN reachability independently when a switch is authorized but clients fail.
Incorrect Answers
B:Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image. These observations are applicable to FortiLink synchronization and upgrade troubleshooting, but would not isolate the main failure first. The decisive evidence is: Inspect FortiLink management state, native/tagged VLANs, port membership, FortiGate interface and active firewall policy.
C:Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings. These observations are applicable to LLDP neighbor discovery and location information, but would not isolate the main failure first. The decisive evidence is: Inspect FortiLink management state, native/tagged VLANs, port membership, FortiGate interface and active firewall policy.
D:Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions. These observations are applicable to Config backup and firmware inventory evidence, but would not isolate the main failure first. The decisive evidence is: Inspect FortiLink management state, native/tagged VLANs, port membership, FortiGate interface and active firewall policy.