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 21

Question 200

Two service customers both use inner VLAN 10 but one S-VLAN is omitted during handoff. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.
  2. Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile.
  3. Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.
  4. Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.

Explanation

Correct Answer

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.

Incorrect Answers

A:

Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation. These observations are applicable to FortiGate VDOM-based FortiSwitch tenant assignment, 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.

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 customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.

D:

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: Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.

Question 201

A trunk expects double-tagged frames but the upstream switch strips the outer service tag. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.
  2. Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings.
  3. Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging.
  4. Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch.

Explanation

Correct Answer

A:

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.

Incorrect Answers

B:

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: Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.

C:

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: Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.

D:

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: Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.

Question 202

An operator applies an edge-port policy to a FortiLink upstream interface and disrupts normal peer BPDUs. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. The current neighboring device and optional endpoint location are visible and match approved cabling documentation.
  2. Accidental downstream switches are contained without disabling legitimate uplinks that should exchange BPDUs.
  3. The expected known switch becomes authorized and synchronizes without accepting an unrelated device.
  4. The handset and attached workstation use the intended separate networks and retain their authorized access.

Explanation

Correct Answer

B:

Accidental downstream switches are contained without disabling legitimate uplinks that should exchange BPDUs. BPDU guard can disable an intended trunk if incorrectly treated as an end-station port.

Incorrect Answers

A:

The current neighboring device and optional endpoint location are visible and match approved cabling documentation. This result relates to LLDP neighbor discovery and location information, not the acceptance condition under test. The relevant result is: Accidental downstream switches are contained without disabling legitimate uplinks that should exchange BPDUs.

C:

The expected known switch becomes authorized and synchronizes without accepting an unrelated device. This result relates to Controller authorization and pending-switch state, not the acceptance condition under test. The relevant result is: Accidental downstream switches are contained without disabling legitimate uplinks that should exchange BPDUs.

D:

The handset and attached workstation use the intended separate networks and retain their authorized access. This result relates to Voice and data VLAN separation on shared access ports, not the acceptance condition under test. The relevant result is: Accidental downstream switches are contained without disabling legitimate uplinks that should exchange BPDUs.

Question 203

An organization disconnects FortiLink to deploy standalone management but fails to assign a reachable management IP and default route. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters.
  2. Inspect incoming 802.1p and DSCP markings, trust mode, QoS map, physical port and classification counters.
  3. Inspect FortiLink operational mode, controller ownership, current management address, VDOM and switch model support.
  4. Inspect FortiGate HA active member, FortiLink aggregate state, ISL, MCLAG peer link, standby path and STP roles.

Explanation

Correct Answer

C:

Inspect FortiLink operational mode, controller ownership, current management address, VDOM and switch model support. Direct edits on a managed switch can be overridden; standalone configuration must be maintained and backed up independently. The paired action is: Determine whether a switch is managed by FortiGate or standalone before setting interfaces, routes or admin policies.

Incorrect Answers

A:

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 FortiLink operational mode, controller ownership, current management address, VDOM and switch model support.

B:

Inspect incoming 802.1p and DSCP markings, trust mode, QoS map, physical port and classification counters. These observations are applicable to QoS ingress classification and trust boundaries, but would not isolate the main failure first. The decisive evidence is: Inspect FortiLink operational mode, controller ownership, current management address, VDOM and switch model support.

D:

Inspect FortiGate HA active member, FortiLink aggregate state, ISL, MCLAG peer link, standby path and STP roles. These observations are applicable to FortiLink HA and MCLAG topology faults, but would not isolate the main failure first. The decisive evidence is: Inspect FortiLink operational mode, controller ownership, current management address, VDOM and switch model support.

Question 204

A voice ACL blocks the signaling network because a new permit rule was placed after a broader deny. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy.
  2. Only intended traffic is accepted or rejected at the switch while allowed application sessions remain functional.
  3. Approved legacy devices gain only restricted services while unknown or spoofed MAC addresses remain constrained.
  4. The managed switch retains the intended controller-pushed policy after a controlled synchronization and restart.

Explanation

Correct Answer

B:

Only intended traffic is accepted or rejected at the switch while allowed application sessions remain functional. Switch ACLs and FortiGate firewall policies operate at different enforcement points; a deny on one does not prove the other applied.

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: Only intended traffic is accepted or rejected at the switch while allowed application sessions remain functional.

C:

Approved legacy devices gain only restricted services while unknown or spoofed MAC addresses remain constrained. This result relates to MAC-based authentication and restricted legacy devices, not the acceptance condition under test. The relevant result is: Only intended traffic is accepted or rejected at the switch while allowed application sessions remain functional.

D:

The managed switch retains the intended controller-pushed policy after a controlled synchronization and restart. This result relates to Managed switch configuration synchronization, not the acceptance condition under test. The relevant result is: Only intended traffic is accepted or rejected at the switch while allowed application sessions remain functional.

Question 205

A core maintenance event disconnects one MCLAG peer link and the operator checks only client ping. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect FortiLink mode, physical or aggregate link state, switch authorization, VLAN interfaces and test-client path.
  2. Inspect Discover/Offer/Request/Ack sequence, ARP requests/replies, VLAN tags, DHCP snooping and DAI counters.
  3. Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards.
  4. Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.

Explanation

Correct Answer

C:

Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards. MCLAG requires peer coordination and correct downstream aggregation; it is not equivalent to connecting independent switches in parallel. The paired action is: Use documented peer-group and downstream trunk configuration for MCLAG rather than creating ad hoc parallel Ethernet links.

Incorrect Answers

A:

Inspect FortiLink mode, physical or aggregate link state, switch authorization, VLAN interfaces and test-client path. These observations are applicable to Single FortiGate and single FortiSwitch topology, but would not isolate the main failure first. The decisive evidence is: Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards.

B:

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 MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards.

D:

Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity. These observations are applicable to HA FortiGate pair managing switch topology, but would not isolate the main failure first. The decisive evidence is: Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards.

Question 206

A rogue laptop runs a DHCP server and offers incorrect gateways to clients on an access switch. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN.
  2. Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers.
  3. Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile.
  4. Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.

Explanation

Correct Answer

B:

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

Incorrect Answers

A:

Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN. These observations are applicable to MAC-based authentication and restricted legacy devices, but would not isolate the main failure first. The decisive evidence is: Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers.

C:

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 trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers.

D:

Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status. These observations are applicable to FortiSwitch multi-tier managed topology, but would not isolate the main failure first. The decisive evidence is: Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers.

Question 207

An administrator leaves FortiLink split-interface enabled while connecting an aggregate to one managed switch. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs.
  2. Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.
  3. Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping.
  4. 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:

Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs. This action is relevant to Stack failure isolation and switch-to-switch port roles, not the controlling requirement in this case. A missing switch in a FortiLink managed chain may be caused by the upstream ISL even if its access ports still carry local traffic. The targeted response is: Use FortiLink split-interface or standby interfaces only for supported topology and verify active versus backup port behavior.

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: Use FortiLink split-interface or standby interfaces only for supported topology and verify active versus backup port behavior.

C:

Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping. This action is relevant to FortiSwitch split port breakout mode, not the controlling requirement in this case. A physical QSFP cage does not guarantee that four independent Ethernet child ports can be enabled on every model. The targeted response is: Use FortiLink split-interface or standby interfaces only for supported topology and verify active versus backup port behavior.

Question 208

A new low storm-control threshold prevents otherwise healthy phones from obtaining DHCP leases. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes.
  2. Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings.
  3. Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols.
  4. Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints.

Explanation

Correct Answer

C:

Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols. Overaggressive storm control can break DHCP, ARP or group discovery even when physical links remain healthy. Verify the action with: Inspect frame-rate counters by class, threshold configuration, affected VLANs and protocol health under controlled load.

Incorrect Answers

A:

Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes. This action is relevant to NAC dynamic port policy device classification, not the controlling requirement in this case. NAC assignment relies on reliable detection and a defined precedence; a class label is not a substitute for switch-port policy. The targeted response is: Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols.

B:

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: Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols.

D:

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: Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols.

Question 209

A video stream reaches all desks even though only two phones subscribe to the multicast group. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port.
  2. Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.
  3. Inspect FortiGate FortiLink status, supported discovery port, LLDP frames, interface IP, link errors and switch serial.
  4. Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.

Explanation

Correct Answer

A:

Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port. A multicast VLAN alone does not indicate that IGMP receiver membership or querier operation is healthy. The paired action is: Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it.

Incorrect Answers

B:

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: Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port.

C:

Inspect FortiGate FortiLink status, supported discovery port, LLDP frames, interface IP, link errors and switch serial. These observations are applicable to FortiLink discovery failure and physical uplink path, but would not isolate the main failure first. The decisive evidence is: Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port.

D:

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: Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port.

Question 210

An old switch runs a different STP variant and the peer unexpectedly blocks the voice VLAN only. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Only intended traffic is accepted or rejected at the switch while allowed application sessions remain functional.
  2. Every relevant VLAN converges without loops and redundant paths unblock only when needed.
  3. A rogue root candidate is blocked or a looped path remains safely contained without wiping all STP configuration.
  4. Rapid MAC moves stop and normal forwarding returns with a verified alternate redundant path.

Explanation

Correct Answer

B:

Every relevant VLAN converges without loops and redundant paths unblock only when needed. An STP mode change can change per-VLAN convergence behavior even if existing links remain physically up.

Incorrect Answers

A:

Only intended traffic is accepted or rejected at the switch while allowed application sessions remain functional. This result relates to Static port ACL forwarding decisions, not the acceptance condition under test. The relevant result is: Every relevant VLAN converges without loops and redundant paths unblock only when needed.

C:

A rogue root candidate is blocked or a looped path remains safely contained without wiping all STP configuration. This result relates to Root guard and loop guard failure response, not the acceptance condition under test. The relevant result is: Every relevant VLAN converges without loops and redundant paths unblock only when needed.

D:

Rapid MAC moves stop and normal forwarding returns with a verified alternate redundant path. This result relates to STP incident recovery with MAC flap evidence, not the acceptance condition under test. The relevant result is: Every relevant VLAN converges without loops and redundant paths unblock only when needed.

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