Fortinet NSE5_FSW_AD-7.6 Practice Test 49
Question 480
A managed switch loses FortiLink only after an active FortiGate HA failover. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Identify FortiLink failures caused by split-interface, HA, MCLAG peer or ISL mismatches before changing unrelated ports.
- Troubleshoot FortiLink discovery from physical and logical interface configuration through LLDP and management addressing.
- Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted.
- Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging.
Explanation
Correct Answer
A:Identify FortiLink failures caused by split-interface, HA, MCLAG peer or ISL mismatches before changing unrelated ports. FortiGate HA, FortiLink split-interface and FortiSwitch MCLAG have distinct failover behaviors that cannot be inferred from link LEDs alone. Verify the action with: Inspect FortiGate HA active member, FortiLink aggregate state, ISL, MCLAG peer link, standby path and STP roles.
Incorrect Answers
B: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: Identify FortiLink failures caused by split-interface, HA, MCLAG peer or ISL mismatches before changing unrelated ports.
C: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: Identify FortiLink failures caused by split-interface, HA, MCLAG peer or ISL mismatches before changing unrelated ports.
D:Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging. This action is relevant to Shared port multi-VDOM policy boundaries, not the controlling requirement in this case. Shared physical ports can support some per-port controls across VDOMs, but feature support and tagging must be checked for the exact release. The targeted response is: Identify FortiLink failures caused by split-interface, HA, MCLAG peer or ISL mismatches before changing unrelated ports.
Question 481
A firewall-to-switch connection repeatedly flaps because each side assumes different negotiated speed. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters.
- Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy.
- Inspect transceiver SKU, supported compatibility table, Tx/Rx optical power, interface alarms and cable plant type.
- Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile.
Explanation
Correct Answer
A:Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters. Incorrect forced port speed or duplex can mimic application loss even when the VLAN configuration is valid. The paired action is: Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds.
Incorrect Answers
B:Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy. These observations are applicable to BPDU guard on endpoint-facing ports, but would not isolate the main failure first. The decisive evidence is: Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters.
C:Inspect transceiver SKU, supported compatibility table, Tx/Rx optical power, interface alarms and cable plant type. These observations are applicable to Optic compatibility and laser diagnostic evidence, but would not isolate the main failure first. The decisive evidence is: Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters.
D:Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile. These observations are applicable to FortiSwitch 802.1X port-based authentication, but would not isolate the main failure first. The decisive evidence is: Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters.
Question 482
A standby FortiLink port never takes over because its intended peer and discovery state were not prepared. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof.
- Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues.
- Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links.
- Use FortiLink split-interface or standby interfaces only for supported topology and verify active versus backup port behavior.
Explanation
Correct Answer
D:Use FortiLink split-interface or standby interfaces only for supported topology and verify active versus backup port behavior. FortiLink split-interface behavior depends on topology; enabling it blindly for same-peer LAG links can break intended aggregation. Verify the action with: Inspect FortiLink interface type, split-interface setting, connected peer count, STP state and active management path.
Incorrect Answers
A:Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof. This action is relevant to MAC-based authentication and restricted legacy devices, not the controlling requirement in this case. A MAC address can be cloned; MAC authentication must be combined with appropriate segmentation and monitoring. The targeted response is: Use FortiLink split-interface or standby interfaces only for supported topology and verify active versus backup port behavior.
B:Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues. This action is relevant to QoS ingress classification and trust boundaries, not the controlling requirement in this case. A packet marking has no useful QoS effect until supported classification and scheduling map it consistently. The targeted response is: Use FortiLink split-interface or standby interfaces only for supported topology and verify active versus backup port behavior.
C: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: Use FortiLink split-interface or standby interfaces only for supported topology and verify active versus backup port behavior.
Question 483
An engineer enables authorization during business hours without recognizing that the switch may reboot into FortiLink mode. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.
- 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.
- Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing.
Explanation
Correct Answer
B: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.
Incorrect Answers
A:Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters. These observations are applicable to Layer 2 MAC-learning and forwarding decisions, but would not isolate the main failure first. The decisive evidence is: Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
C: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: Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
D:Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing. These observations are applicable to Firmware and lifecycle preparation for FortiSwitch, but would not isolate the main failure first. The decisive evidence is: Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
Question 484
An operator receives an assigned IP address but assumes that proves the switch is already controller-authorized. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- A tenant reaches only its approved VDOM resources and does not inherit another tenant's policies.
- The offending misassignment is corrected with both permitted traffic and forbidden cross-tenant traffic tested.
- The switch successfully onboards to the intended FortiGate and retains a recoverable controller-managed baseline.
- A redundant topology recovers after a link failure without simultaneous independent forwarding paths causing loops.
Explanation
Correct Answer
C:The switch successfully onboards to the intended FortiGate and retains a recoverable controller-managed baseline. Zero-touch deployment works only when the necessary discovery path and identity checks function; a link LED is insufficient.
Incorrect Answers
A:A tenant reaches only its approved VDOM resources and does not inherit another tenant's policies. This result relates to FortiGate VDOM-based FortiSwitch tenant assignment, not the acceptance condition under test. The relevant result is: The switch successfully onboards to the intended FortiGate and retains a recoverable controller-managed baseline.
B:The offending misassignment is corrected with both permitted traffic and forbidden cross-tenant traffic tested. This result relates to Managed tenant troubleshooting across controller and access layer, not the acceptance condition under test. The relevant result is: The switch successfully onboards to the intended FortiGate and retains a recoverable controller-managed baseline.
D:A redundant topology recovers after a link failure without simultaneous independent forwarding paths causing loops. This result relates to FortiLink split-interface and standby path design, not the acceptance condition under test. The relevant result is: The switch successfully onboards to the intended FortiGate and retains a recoverable controller-managed baseline.
Question 485
A user moves between ports and the stale binding on the old port rejects the new legitimate lease. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy.
- The analyzer receives the intended copies while production forwarding remains unchanged.
- Unauthorized source IP packets fail while an approved host continues using its assigned IP and address policy.
- Runaway flooding is contained without blocking legitimate broadcast-based onboarding or multicast subscribers.
Explanation
Correct Answer
C:Unauthorized source IP packets fail while an approved host continues using its assigned IP and address policy. Source guard is an ingress source-binding check, not a full replacement for routed firewall policies or endpoint security.
Incorrect Answers
A:Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy. This result relates to FortiSwitch 802.1X port-based authentication, not the acceptance condition under test. The relevant result is: Unauthorized source IP packets fail while an approved host continues using its assigned IP and address policy.
B:The analyzer receives the intended copies while production forwarding remains unchanged. This result relates to FortiSwitch port mirroring to network analyzer, not the acceptance condition under test. The relevant result is: Unauthorized source IP packets fail while an approved host continues using its assigned IP and address policy.
D:Runaway flooding is contained without blocking legitimate broadcast-based onboarding or multicast subscribers. This result relates to Storm-control thresholds and broadcast containment, not the acceptance condition under test. The relevant result is: Unauthorized source IP packets fail while an approved host continues using its assigned IP and address policy.
Question 486
An old switch runs a different STP variant and the peer unexpectedly blocks the voice VLAN only. 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.
- FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy.
- Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy.
- Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.
- Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links.
Explanation
Correct Answers
D:Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history. An STP mode change can change per-VLAN convergence behavior even if existing links remain physically up. The paired action is: Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links. This is the diagnostic or verification half of the requested TWO-step pair.
E:Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links. An STP mode change can change per-VLAN convergence behavior even if existing links remain physically up. Verify the action with: Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history. This is the configuration or remediation half of the requested TWO-step pair.
Incorrect Answers
A:Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology. This step concerns MCLAG peer-link topology for managed access switches and is not part of the required paired solution. The correct action and evidence are: Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links. Together with: Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.
B:FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy. This step concerns FortiGate one-arm sniffer across managed switching and is not part of the required paired solution. The correct action and evidence are: Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links. Together with: Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.
C:Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy. This step concerns MSTP region consistency and designated root and is not part of the required paired solution. The correct action and evidence are: Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links. Together with: Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.
Question 487
A static-IP printer loses connectivity after DAI is turned on with no manual binding exception. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Inspect ARP inspection status, DHCP snooping binding database, source MAC/IP, trusted ports and violation logs.
- Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state.
- Use supported dynamic ARP inspection with valid switch bindings to reject spoofed IP-MAC claims at untrusted edges.
- The intended VLAN survives a switch restart without unexpected controller overwrite or unauthorized local change.
- Use documented trusted DHCP-server lists or Option 82 information where supported to enforce authorized address assignment.
Explanation
Correct Answers
A: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
B:Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state. This step concerns NAC dynamic port policy device classification 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:The intended VLAN survives a switch restart without unexpected controller overwrite or unauthorized local change. This step concerns VLAN configuration persistence and drift control 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:Use documented trusted DHCP-server lists or Option 82 information where supported to enforce authorized address assignment. This step concerns DHCP server allowlist and Option 82 validation 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 488
A new low storm-control threshold prevents otherwise healthy phones from obtaining DHCP leases. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect ARP inspection status, DHCP snooping binding database, source MAC/IP, trusted ports and violation logs.
- Inspect DHCP server permitted list, Option 82 insertion/trust state, relay path, client bindings and lease evidence.
- Inspect frame-rate counters by class, threshold configuration, affected VLANs and protocol health under controlled load.
- Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.
Explanation
Correct Answer
C:Inspect frame-rate counters by class, threshold configuration, affected VLANs and protocol health under controlled load. Overaggressive storm control can break DHCP, ARP or group discovery even when physical links remain healthy. The paired action is: Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols.
Incorrect Answers
A:Inspect ARP inspection status, DHCP snooping binding database, source MAC/IP, trusted ports and violation logs. These observations are applicable to Dynamic ARP inspection with DHCP snooping bindings, but would not isolate the main failure first. The decisive evidence is: Inspect frame-rate counters by class, threshold configuration, affected VLANs and protocol health under controlled load.
B:Inspect DHCP server permitted list, Option 82 insertion/trust state, relay path, client bindings and lease evidence. These observations are applicable to DHCP server allowlist and Option 82 validation, but would not isolate the main failure first. The decisive evidence is: Inspect frame-rate counters by class, threshold configuration, affected VLANs and protocol health under controlled load.
D:Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization. These observations are applicable to FortiLink ISL auto-discovery and stack cabling, but would not isolate the main failure first. The decisive evidence is: Inspect frame-rate counters by class, threshold configuration, affected VLANs and protocol health under controlled load.
Question 489
A manager wants all discovered switches automatically authorized even though the site uses untrusted wiring closets. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths.
- Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted.
- Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices.
- Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports.
Explanation
Correct Answer
C:Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices. Authorizing a switch is an administrative trust step; pending switch state is not evidence of a routing failure. Verify the action with: Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode.
Incorrect Answers
A: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: Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices.
B: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: Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices.
D:Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports. This action is relevant to Port MAC learning-limit and violation controls, not the controlling requirement in this case. Dynamic MAC learning limits reduce accidental fan-out but should be tuned for legitimate multi-device access designs. The targeted response is: Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices.
Question 490
A video stream reaches all desks even though only two phones subscribe to the multicast group. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.
- Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context.
- Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation.
- Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it.
Explanation
Correct Answer
D:Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it. A multicast VLAN alone does not indicate that IGMP receiver membership or querier operation is healthy. Verify the action with: Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port.
Incorrect Answers
A: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: Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it.
B:Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context. This action is relevant to FortiSwitch SVI routing and connected routes, not the controlling requirement in this case. Layer-3 SVI configuration and actual usable forwarding are separate from having a named Layer-2 VLAN. The targeted response is: Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it.
C:Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation. This action is relevant to LACP negotiation on FortiSwitch FortiLink trunks, not the controlling requirement in this case. Passive LACP on both ends may not negotiate an active bundle, and individual green links do not prove aggregation. The targeted response is: Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it.