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 56

Question 550

A branch cascades managed switches but connects a ring without checking the supported FortiLink stacking design. 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. Use FortiLink split-interface or standby interfaces only for supported topology and verify active versus backup port behavior.
  3. Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage.
  4. Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles.

Explanation

Correct Answer

D:

Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles. The FortiGate-managed FortiSwitch stack is a managed L2 topology, not automatically a single chassis or universal VSF-like control plane. Verify the action with: Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.

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: Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles.

B:

Use FortiLink split-interface or standby interfaces only for supported topology and verify active versus backup port behavior. This action is relevant to FortiLink split-interface and standby path design, not the controlling requirement in this case. FortiLink split-interface behavior depends on topology; enabling it blindly for same-peer LAG links can break intended aggregation. The targeted response is: Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles.

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: Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles.

Question 551

A technician disables STP on one interswitch uplink because it shows blocking during normal redundancy. 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. Inspect guard role, BPDU reception, root-ID history, STP port role and loop-condition log.
  3. Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.
  4. Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy.

Explanation

Correct Answer

C:

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.

Incorrect Answers

A:

Inspect FortiLink management state, native/tagged VLANs, port membership, FortiGate interface and active firewall policy. These observations are applicable to FortiLink control and client VLAN transport separation, but would not isolate the main failure first. The decisive evidence is: Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.

B:

Inspect guard role, BPDU reception, root-ID history, STP port role and loop-condition log. These observations are applicable to Root guard and loop guard failure response, but would not isolate the main failure first. The decisive evidence is: Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.

D:

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: Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.

Question 552

All phones lose leases after the uplink carrying approved DHCP offers was marked untrusted. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Accidental downstream switches are contained without disabling legitimate uplinks that should exchange BPDUs.
  2. Use supported dynamic ARP inspection with valid switch bindings to reject spoofed IP-MAC claims at untrusted edges.
  3. Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers.
  4. Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile.
  5. Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links.

Explanation

Correct Answers

C:

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. This is the diagnostic or verification half of the requested TWO-step pair.

E:

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. This is the configuration or remediation half of the requested TWO-step pair.

Incorrect Answers

A:

Accidental downstream switches are contained without disabling legitimate uplinks that should exchange BPDUs. This step concerns BPDU guard on endpoint-facing ports and is not part of the required paired solution. The correct action and evidence are: Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links. Together with: Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers.

B:

Use supported dynamic ARP inspection with valid switch bindings to reject spoofed IP-MAC claims at untrusted edges. This step concerns Dynamic ARP inspection with DHCP snooping bindings and is not part of the required paired solution. The correct action and evidence are: Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links. Together with: Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers.

D:

Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile. This step concerns FortiSwitch 802.1X port-based authentication and is not part of the required paired solution. The correct action and evidence are: Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links. Together with: Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers.

Question 553

MAC addresses oscillate between two uplinks after a newly installed unmanaged bridge creates a loop. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Check switch quarantine status, ACL/security profile, allowed remediation services, NAC event and release criteria.
  2. Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.
  3. Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway.
  4. Inspect FortiLink operational mode, controller ownership, current management address, VDOM and switch model support.

Explanation

Correct Answer

B:

Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters. An L2 switch uses MAC destination and VLAN state for forwarding; a healthy SVI is not proof a host is on the proper port. The paired action is: Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing.

Incorrect Answers

A:

Check switch quarantine status, ACL/security profile, allowed remediation services, NAC event and release criteria. These observations are applicable to VLAN security policy and quarantine actions, but would not isolate the main failure first. The decisive evidence is: Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.

C:

Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway. These observations are applicable to FortiSwitch SVI routing and connected routes, but would not isolate the main failure first. The decisive evidence is: Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.

D:

Inspect FortiLink operational mode, controller ownership, current management address, VDOM and switch model support. These observations are applicable to FortiSwitch standalone versus FortiLink managed L3 ownership, but would not isolate the main failure first. The decisive evidence is: Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.

Question 554

The network plan assumes every port-security feature is supported for a multi-VDOM shared port on every model. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.
  2. Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.
  3. Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.
  4. Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.

Explanation

Correct Answer

D:

Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state. Shared physical ports can support some per-port controls across VDOMs, but feature support and tagging must be checked for the exact release. The paired action is: Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging.

Incorrect Answers

A:

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: Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.

B:

Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction. These observations are applicable to FortiGate one-arm sniffer across managed switching, but would not isolate the main failure first. The decisive evidence is: Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.

C:

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: Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.

Question 555

An operations platform sees no FortiSwitch traffic samples because the configured sFlow collector address is wrong. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. The exact dropped direction or incorrect address binding is evidenced before changing a security feature.
  2. Troubleshooting evidence is sufficient to establish the fault without exporting unnecessary private communications.
  3. Approved aggregate members forward as one bundle while nonmatching links remain excluded.
  4. Authorized monitoring receives timely, interpretable switch evidence without exposing community strings or overwhelming CPU.

Explanation

Correct Answer

D:

Authorized monitoring receives timely, interpretable switch evidence without exposing community strings or overwhelming CPU. Flow samples are estimates and counters vary by port; collecting telemetry cannot replace a controlled packet capture when headers are needed.

Incorrect Answers

A:

The exact dropped direction or incorrect address binding is evidenced before changing a security feature. This result relates to Capture-based DHCP and ARP path isolation, not the acceptance condition under test. The relevant result is: Authorized monitoring receives timely, interpretable switch evidence without exposing community strings or overwhelming CPU.

B:

Troubleshooting evidence is sufficient to establish the fault without exporting unnecessary private communications. This result relates to Capture and confidentiality limits in incident response, not the acceptance condition under test. The relevant result is: Authorized monitoring receives timely, interpretable switch evidence without exposing community strings or overwhelming CPU.

C:

Approved aggregate members forward as one bundle while nonmatching links remain excluded. This result relates to LACP negotiation on FortiSwitch FortiLink trunks, not the acceptance condition under test. The relevant result is: Authorized monitoring receives timely, interpretable switch evidence without exposing community strings or overwhelming CPU.

Question 556

A voice ACL blocks the signaling network because a new permit rule was placed after a broader deny. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Each customer's tagged traffic reaches only its assigned service context without S-VLAN collision.
  2. Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence.
  3. Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test.
  4. Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence.
  5. Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.

Explanation

Correct Answers

D:

Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence. Switch ACLs and FortiGate firewall policies operate at different enforcement points; a deny on one does not prove the other applied. Verify the action with: Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path. This is the configuration or remediation half of the requested TWO-step pair.

E:

Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path. Switch ACLs and FortiGate firewall policies operate at different enforcement points; a deny on one does not prove the other applied. The paired action is: Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

A:

Each customer's tagged traffic reaches only its assigned service context without S-VLAN collision. This step concerns QinQ outer and inner VLAN tenant mapping and is not part of the required paired solution. The correct action and evidence are: Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence. Together with: Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.

B:

Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence. This step concerns FortiSwitch security profile application and precedence and is not part of the required paired solution. The correct action and evidence are: Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence. Together with: Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.

C:

Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test. This step concerns Intra-VLAN blocking and isolation boundaries and is not part of the required paired solution. The correct action and evidence are: Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence. Together with: Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.

Question 557

A mirrored switch port feeds FortiGate but the sniffer filter incorrectly excludes double-tagged frames. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted.
  2. Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy.
  3. Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.
  4. Verify FortiLink management status and user VLAN reachability independently when a switch is authorized but clients fail.
  5. A controlled peer or member failure maintains approved client VLAN access without a Layer-2 loop.

Explanation

Correct Answers

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. This is the configuration or remediation half of the requested TWO-step pair.

C:

Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction. Sniffer placement determines visibility; absence of a packet at one observation point does not prove no packet existed elsewhere. The paired action is: Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

B:

Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy. This step concerns SNMP and sFlow monitoring configuration and is not part of the required paired solution. The correct action and evidence are: Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted. Together with: Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.

D:

Verify FortiLink management status and user VLAN reachability independently when a switch is authorized but clients fail. This step concerns FortiLink control and client VLAN transport separation and is not part of the required paired solution. The correct action and evidence are: Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted. Together with: Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.

E:

A controlled peer or member failure maintains approved client VLAN access without a Layer-2 loop. This step concerns MCLAG multichassis access redundancy and is not part of the required paired solution. The correct action and evidence are: Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted. Together with: Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.

Question 558

One managed port uses a stale security profile because an override did not synchronize from FortiGate. 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 port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.
  3. Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.
  4. Inspect frame-rate counters by class, threshold configuration, affected VLANs and protocol health under controlled load.

Explanation

Correct Answer

B:

Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls. A named security profile sitting in configuration is not proof that it was applied to the intended hardware port. The paired action is: Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence.

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 port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.

C:

Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface. These observations are applicable to FortiSwitch native VLAN versus allowed VLANs, but would not isolate the main failure first. The decisive evidence is: Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.

D:

Inspect frame-rate counters by class, threshold configuration, affected VLANs and protocol health under controlled load. These observations are applicable to Storm-control thresholds and broadcast containment, but would not isolate the main failure first. The decisive evidence is: Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.

Question 559

A downstream switch advertises a superior bridge ID and tries to become campus root unexpectedly. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.
  2. Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.
  3. Inspect guard role, BPDU reception, root-ID history, STP port role and loop-condition log.
  4. Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.

Explanation

Correct Answer

C:

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 the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface. These observations are applicable to FortiSwitch native VLAN versus allowed VLANs, 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:

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

D:

Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history. These observations are applicable to RPVST and supported STP mode interoperability, 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 560

An operator tries to configure 10G on a copper port lacking that interface capability. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. The correct link establishes at expected negotiated rate without recurring loss-of-signal or CRC errors.
  2. Legitimate clients lease addresses while rogue DHCP servers connected to untrusted access ports cannot answer.
  3. Latency-sensitive flows improve under representative load while other business services remain functional.
  4. Both ends connect at compatible rates with stable errors and required throughput.

Explanation

Correct Answer

D:

Both ends connect at compatible rates with stable errors and required throughput. Incorrect forced port speed or duplex can mimic application loss even when the VLAN configuration is valid.

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: Both ends connect at compatible rates with stable errors and required throughput.

B:

Legitimate clients lease addresses while rogue DHCP servers connected to untrusted access ports cannot answer. This result relates to DHCP snooping trust-boundary enforcement, not the acceptance condition under test. The relevant result is: Both ends connect at compatible rates with stable errors and required throughput.

C:

Latency-sensitive flows improve under representative load while other business services remain functional. This result relates to Egress priority scheduling and congestion visibility, not the acceptance condition under test. The relevant result is: Both ends connect at compatible rates with stable errors and required throughput.

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