cert
cert-1
cert-2

Pass Fortinet NSE5_FSW_AD-7.6 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
NSE5_FSW_AD-7.6 Exam - Verified By Experts
NSE5_FSW_AD-7.6 Premium File

NSE5_FSW_AD-7.6 Premium File

$69.99
$76.99
  • Premium File 64 Questions & Answers. Last Update: Nov 15, 2026

Whats Included:

  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
 
$76.99
$69.99
accept 42 downloads in the last 7 days
block-screenshots
Fortinet NSE5_FSW_AD-7.6 Practice Test 66

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?

  1. Inspect FortiLink management state, native/tagged VLANs, port membership, FortiGate interface and active firewall policy.
  2. Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image.
  3. Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.
  4. 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.

Question 651

A QoS change trusts 802.1p tags from a server port that should be an untagged client interface. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function.
  2. Accidental downstream switches are contained without disabling legitimate uplinks that should exchange BPDUs.
  3. Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority.
  4. Members receive subscribed streams while unsubscribed access ports are not flooded unnecessarily.

Explanation

Correct Answer

C:

Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority. A packet marking has no useful QoS effect until supported classification and scheduling map it consistently.

Incorrect Answers

A:

The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function. This result relates to FortiLink management interface provisioning, not the acceptance condition under test. The relevant result is: Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority.

B:

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: Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority.

D:

Members receive subscribed streams while unsubscribed access ports are not flooded unnecessarily. This result relates to IGMP snooping and multicast receivers, not the acceptance condition under test. The relevant result is: Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority.

Question 652

A redundant uplink stops receiving expected BPDUs and becomes a potential loop hazard. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect.
  2. Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.
  3. Inspect Discover/Offer/Request/Ack sequence, ARP requests/replies, VLAN tags, DHCP snooping and DAI counters.
  4. Inspect guard role, BPDU reception, root-ID history, STP port role and loop-condition log.

Explanation

Correct Answer

D:

Inspect guard role, BPDU reception, root-ID history, STP port role and loop-condition log. Root guard and loop guard mitigate different failure cases and should not be enabled indiscriminately on every uplink. The paired action is: Apply appropriate STP root or loop protection to preserve topology while analyzing missing BPDUs and unexpected root claims.

Incorrect Answers

A:

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: Inspect guard role, BPDU reception, root-ID history, STP port role and loop-condition log.

B:

Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path. These observations are applicable to Static route and default gateway validation, but would not isolate the main failure first. The decisive evidence is: Inspect guard role, BPDU reception, root-ID history, STP port role and loop-condition log.

C:

Inspect Discover/Offer/Request/Ack sequence, ARP requests/replies, VLAN tags, DHCP snooping and DAI counters. These observations are applicable to Capture-based DHCP and ARP path isolation, but would not isolate the main failure first. The decisive evidence is: Inspect guard role, BPDU reception, root-ID history, STP port role and loop-condition log.

Question 653

A client manually assigns a privileged subnet address and tries to send packets through an access port. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. A rogue root candidate is blocked or a looped path remains safely contained without wiping all STP configuration.
  2. Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers.
  3. Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet.
  4. Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols.
  5. Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings.

Explanation

Correct Answers

C:

Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet. Source guard is an ingress source-binding check, not a full replacement for routed firewall policies or endpoint security. The paired action is: Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings. This is the diagnostic or verification half of the requested TWO-step pair.

E:

Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings. Source guard is an ingress source-binding check, not a full replacement for routed firewall policies or endpoint security. Verify the action with: Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet. This is the configuration or remediation half of the requested TWO-step pair.

Incorrect Answers

A:

A rogue root candidate is blocked or a looped path remains safely contained without wiping all STP configuration. This step concerns Root guard and loop guard failure response and is not part of the required paired solution. The correct action and evidence are: Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings. Together with: Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet.

B:

Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers. This step concerns DHCP snooping trust-boundary enforcement and is not part of the required paired solution. The correct action and evidence are: Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings. Together with: Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet.

D:

Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols. This step concerns Storm-control thresholds and broadcast containment and is not part of the required paired solution. The correct action and evidence are: Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings. Together with: Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet.

Question 654

A newly patched uplink reports an unexpected LLDP peer from a separate customer zone. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices.
  2. Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths.
  3. Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope.
  4. Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging.

Explanation

Correct Answer

B:

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:

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: Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths.

C:

Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope. This action is relevant to SNMP and sFlow monitoring configuration, not the controlling requirement in this case. Flow samples are estimates and counters vary by port; collecting telemetry cannot replace a controlled packet capture when headers are needed. The targeted response is: Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths.

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: Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths.

Question 655

All phones lose leases after the uplink carrying approved DHCP offers was marked untrusted. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths.
  2. Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols.
  3. Use supported dynamic ARP inspection with valid switch bindings to reject spoofed IP-MAC claims at untrusted edges.
  4. Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links.

Explanation

Correct Answer

D:

Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links. Trusting every port defeats DHCP snooping and wrongly distrusting the server uplink may suppress all leases. Verify the action with: Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers.

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: Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links.

B:

Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols. This action is relevant to Storm-control thresholds and broadcast containment, not the controlling requirement in this case. Overaggressive storm control can break DHCP, ARP or group discovery even when physical links remain healthy. The targeted response is: Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links.

C:

Use supported dynamic ARP inspection with valid switch bindings to reject spoofed IP-MAC claims at untrusted edges. This action is relevant to Dynamic ARP inspection with DHCP snooping bindings, not the controlling requirement in this case. DAI validation needs a reliable binding or exception policy; enabling it blindly can interrupt static-IP devices. The targeted response is: Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links.

Question 656

An engineer enables legacy public read-write SNMP community strings to save time and exposes management data. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
  2. Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy.
  3. Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters.
  4. Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps.

Explanation

Correct Answer

B:

Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy. Flow samples are estimates and counters vary by port; collecting telemetry cannot replace a controlled packet capture when headers are needed. The paired action is: Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope.

Incorrect Answers

A:

Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map. These observations are applicable to LLDP and MAC forwarding table extraction, but would not isolate the main failure first. The decisive evidence is: Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy.

C:

Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters. These observations are applicable to LACP negotiation on FortiSwitch FortiLink trunks, but would not isolate the main failure first. The decisive evidence is: Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy.

D:

Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps. These observations are applicable to Managed switch port statistics and counter analysis, but would not isolate the main failure first. The decisive evidence is: Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy.

Question 657

A data closet trunk sends untagged management frames into a partner's tagged-only management VLAN. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment.
  2. The switch successfully onboards to the intended FortiGate and retains a recoverable controller-managed baseline.
  3. Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.
  4. Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover.
  5. Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.

Explanation

Correct Answers

C:

Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface. Native VLAN handling and tagged VLAN membership are different controls; a working physical link does not validate VLAN carriage. The paired action is: Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover. This is the diagnostic or verification half of the requested TWO-step pair.

D:

Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover. Native VLAN handling and tagged VLAN membership are different controls; a working physical link does not validate VLAN carriage. Verify the action with: Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface. This is the configuration or remediation half of the requested TWO-step pair.

Incorrect Answers

A:

Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment. This step concerns Voice and data VLAN separation on shared access ports and is not part of the required paired solution. The correct action and evidence are: Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover. Together with: Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.

B:

The switch successfully onboards to the intended FortiGate and retains a recoverable controller-managed baseline. This step concerns Zero-touch provisioning and controller dependency checks and is not part of the required paired solution. The correct action and evidence are: Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover. Together with: Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.

E:

Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings. This step concerns LLDP neighbor discovery and location information and is not part of the required paired solution. The correct action and evidence are: Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover. Together with: Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.

Question 658

A relay receives mismatched Option 82 information and discards legitimate client renewals. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof.
  2. Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints.
  3. Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces.
  4. Use documented trusted DHCP-server lists or Option 82 information where supported to enforce authorized address assignment.

Explanation

Correct Answer

D:

Use documented trusted DHCP-server lists or Option 82 information where supported to enforce authorized address assignment. DHCP server allowlist and Option 82 metadata provide additional context but cannot correct a failed VLAN or missing upstream relay. Verify the action with: Inspect DHCP server permitted list, Option 82 insertion/trust state, relay path, client bindings and lease evidence.

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 documented trusted DHCP-server lists or Option 82 information where supported to enforce authorized address assignment.

B:

Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints. This action is relevant to DACL RADIUS attribute and per-session enforcement, not the controlling requirement in this case. DACLs install after successful authorization and documented release limits apply; a RADIUS response alone is not proof of forwarding enforcement. The targeted response is: Use documented trusted DHCP-server lists or Option 82 information where supported to enforce authorized address assignment.

C:

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: Use documented trusted DHCP-server lists or Option 82 information where supported to enforce authorized address assignment.

Question 659

An office switch is online in FortiGate but every new employee receives the wrong VLAN. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Verify FortiLink management status and user VLAN reachability independently when a switch is authorized but clients fail.
  2. Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths.
  3. Use documented peer-group and downstream trunk configuration for MCLAG rather than creating ad hoc parallel Ethernet links.
  4. Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames.

Explanation

Correct Answer

A:

Verify FortiLink management status and user VLAN reachability independently when a switch is authorized but clients fail. FortiLink transports management and data; a successful controller heartbeat does not guarantee a user VLAN or firewall session is permitted. Verify the action with: Inspect FortiLink management state, native/tagged VLANs, port membership, FortiGate interface and active firewall policy.

Incorrect Answers

B:

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: Verify FortiLink management status and user VLAN reachability independently when a switch is authorized but clients fail.

C:

Use documented peer-group and downstream trunk configuration for MCLAG rather than creating ad hoc parallel Ethernet links. This action is relevant to MCLAG multichassis access redundancy, not the controlling requirement in this case. MCLAG requires peer coordination and correct downstream aggregation; it is not equivalent to connecting independent switches in parallel. The targeted response is: Verify FortiLink management status and user VLAN reachability independently when a switch is authorized but clients fail.

D:

Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames. This action is relevant to FortiSwitch local packet-capture profile and filters, not the controlling requirement in this case. Packet captures are interface and filter scoped, and platform buffer limits differ; a capture file is not proof of all traffic on every switch port. The targeted response is: Verify FortiLink management status and user VLAN reachability independently when a switch is authorized but clients fail.

Question 660

An administrator raises MAC limits on every port instead of diagnosing one device creating random source addresses. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect MAC table usage, configured learning limit, learned device count, port-security event and violation action.
  2. Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile.
  3. Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test.
  4. Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes.

Explanation

Correct Answer

A:

Inspect MAC table usage, configured learning limit, learned device count, port-security event and violation action. Dynamic MAC learning limits reduce accidental fan-out but should be tuned for legitimate multi-device access designs. The paired action is: Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports.

Incorrect Answers

B:

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: Inspect MAC table usage, configured learning limit, learned device count, port-security event and violation action.

C:

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 MAC table usage, configured learning limit, learned device count, port-security event and violation action.

D:

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 MAC table usage, configured learning limit, learned device count, port-security event and violation action.

Fortinet NSE 5 - FortiSwitch 7.6 Administrator (NSE5_FSW_AD-7.6) Practice Tests