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 61

Question 600

A rogue switch appears as discovered and an administrator considers enabling global auto-authorization without checking its identity. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces.
  2. Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.
  3. Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records.
  4. Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.

Explanation

Correct Answer

B:

Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition. Switch discovery is not the same as authorization; auto-authorization has governance implications and a managed-mode transition may reboot the device. Verify the action with: Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.

Incorrect Answers

A:

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: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.

C:

Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records. This action is relevant to LLDP neighbor discovery and location information, not the controlling requirement in this case. LLDP is an L2 discovery protocol and cannot prove the whole routed service path or phone emergency-location correctness by itself. The targeted response is: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.

D:

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: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.

Question 601

A multicast paging VLAN disappears after a template update allowed only the corporate user VLAN. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Trace MAC-learning and forwarding across the precise VLAN and repair only missing approved membership.
  2. Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery.
  3. Use STP state and MAC move evidence to isolate one bad bridging path and change only the proven element.
  4. Repair LACP member settings and physical port errors independently before increasing aggregate traffic.

Explanation

Correct Answer

A:

Trace MAC-learning and forwarding across the precise VLAN and repair only missing approved membership. Link up and successful traffic in one VLAN do not prove every VLAN is correctly provisioned on the path. Verify the action with: Check client MAC learning, VLAN database, switch uplink tags, gateway ARP and port assignment on every hop.

Incorrect Answers

B:

Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery. This action is relevant to Config backup and firmware inventory evidence, not the controlling requirement in this case. Backups require correct model/version and an actual restore procedure; a saved file name is not proof a recovered switch will work. The targeted response is: Trace MAC-learning and forwarding across the precise VLAN and repair only missing approved membership.

C:

Use STP state and MAC move evidence to isolate one bad bridging path and change only the proven element. This action is relevant to STP incident recovery with MAC flap evidence, not the controlling requirement in this case. Packet loss during a bridging loop can coexist with clean optical counters, so L1-only diagnostics miss the root cause. The targeted response is: Trace MAC-learning and forwarding across the precise VLAN and repair only missing approved membership.

D:

Repair LACP member settings and physical port errors independently before increasing aggregate traffic. This action is relevant to Link aggregation and port error recovery, not the controlling requirement in this case. One healthy physical link is not proof an aggregate has balanced traffic or that the peer LACP policy matches. The targeted response is: Trace MAC-learning and forwarding across the precise VLAN and repair only missing approved membership.

Question 602

A technician changes the VLAN directly on a FortiLink-managed switch and loses it after reboot. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. An access host receives the right subnet while only approved tagged VLANs traverse the uplink.
  2. Accidental downstream switches are contained without disabling legitimate uplinks that should exchange BPDUs.
  3. The intended VLAN survives a switch restart without unexpected controller overwrite or unauthorized local change.
  4. The suspect device is restricted without interrupting unrelated tenants and can be restored after review.

Explanation

Correct Answer

C:

The intended VLAN survives a switch restart without unexpected controller overwrite or unauthorized local change. Directly editing a FortiLink-managed switch can cause drift because FortiGate remains the controller of record.

Incorrect Answers

A:

An access host receives the right subnet while only approved tagged VLANs traverse the uplink. This result relates to FortiSwitch native VLAN versus allowed VLANs, not the acceptance condition under test. The relevant result is: The intended VLAN survives a switch restart without unexpected controller overwrite or unauthorized local change.

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: The intended VLAN survives a switch restart without unexpected controller overwrite or unauthorized local change.

D:

The suspect device is restricted without interrupting unrelated tenants and can be restored after review. This result relates to VLAN security policy and quarantine actions, not the acceptance condition under test. The relevant result is: The intended VLAN survives a switch restart without unexpected controller overwrite or unauthorized local change.

Question 603

An old switch runs a different STP variant and the peer unexpectedly blocks the voice VLAN only. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes.
  2. Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links.
  3. Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds.
  4. Apply appropriate STP root or loop protection to preserve topology while analyzing missing BPDUs and unexpected root claims.

Explanation

Correct Answer

B:

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.

Incorrect Answers

A:

Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes. This action is relevant to FortiSwitch diagnostic commands and logs, not the controlling requirement in this case. A log message without source device, time and relevant state is not adequate to prove root cause. The targeted response is: Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links.

C:

Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds. This action is relevant to Switch port speed and duplex commissioning, not the controlling requirement in this case. Incorrect forced port speed or duplex can mimic application loss even when the VLAN configuration is valid. The targeted response is: Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links.

D:

Apply appropriate STP root or loop protection to preserve topology while analyzing missing BPDUs and unexpected root claims. This action is relevant to Root guard and loop guard failure response, not the controlling requirement in this case. Root guard and loop guard mitigate different failure cases and should not be enabled indiscriminately on every uplink. The targeted response is: Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links.

Question 604

An operator tries to configure 10G on a copper port lacking that interface capability. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds.
  2. Inspect guard role, BPDU reception, root-ID history, STP port role and loop-condition log.
  3. Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters.
  4. Exactly the intended serial joins managed inventory and receives approved controller settings after authorization.
  5. Repair LACP member settings and physical port errors independently before increasing aggregate traffic.

Explanation

Correct Answers

A:

Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds. Incorrect forced port speed or duplex can mimic application loss even when the VLAN configuration is valid. Verify the action with: Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters. This is the configuration or remediation half of the requested TWO-step pair.

C:

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

Incorrect Answers

B:

Inspect guard role, BPDU reception, root-ID history, STP port role and loop-condition log. 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: Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds. Together with: Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters.

D:

Exactly the intended serial joins managed inventory and receives approved controller settings after authorization. This step concerns Discovered versus authorized FortiSwitch state and is not part of the required paired solution. The correct action and evidence are: Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds. Together with: Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters.

E:

Repair LACP member settings and physical port errors independently before increasing aggregate traffic. This step concerns Link aggregation and port error recovery and is not part of the required paired solution. The correct action and evidence are: Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds. Together with: Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters.

Question 605

A wireless bridge carries a FortiLink interswitch segment but does not forward expected discovery multicast frames. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware.
  2. Inspect MAC table usage, configured learning limit, learned device count, port-security event and violation action.
  3. Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.
  4. Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.

Explanation

Correct Answer

A:

Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware. FortiLink over intermediate networks requires topology-specific settings; ordinary IP reachability alone does not establish FortiLink discovery. The paired action is: Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end.

Incorrect Answers

B:

Inspect MAC table usage, configured learning limit, learned device count, port-security event and violation action. These observations are applicable to Port MAC learning-limit and violation controls, but would not isolate the main failure first. The decisive evidence is: Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware.

C:

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 supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware.

D:

Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state. These observations are applicable to Shared port multi-VDOM policy boundaries, but would not isolate the main failure first. The decisive evidence is: Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware.

Question 606

An engineer blames firmware for a restart without inspecting system-event history or power loss indications. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope.
  2. Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes.
  3. Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy.
  4. Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location.

Explanation

Correct Answer

B:

Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes. A log message without source device, time and relevant state is not adequate to prove root cause. Verify the action with: Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history.

Incorrect Answers

A:

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: Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes.

C:

Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy. This action is relevant to MSTP region consistency and designated root, not the controlling requirement in this case. Different MST configuration identifiers split regions even if switch ports are physically connected. The targeted response is: Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes.

D:

Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location. This action is relevant to Managed switch port statistics and counter analysis, not the controlling requirement in this case. A port-up indicator or one successful ping is not proof that a congested or errored uplink is healthy. The targeted response is: Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes.

Question 607

A QoS change trusts 802.1p tags from a server port that should be an untagged client interface. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy.
  2. Inspect incoming 802.1p and DSCP markings, trust mode, QoS map, physical port and classification counters.
  3. Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.
  4. Review queue maps, output drops, interface rate, strict versus weighted servicing and application latency.

Explanation

Correct Answer

B:

Inspect incoming 802.1p and DSCP markings, trust mode, QoS map, physical port and classification counters. A packet marking has no useful QoS effect until supported classification and scheduling map it consistently. The paired action is: Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues.

Incorrect Answers

A:

Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy. These observations are applicable to SNMP and sFlow monitoring configuration, but would not isolate the main failure first. The decisive evidence is: Inspect incoming 802.1p and DSCP markings, trust mode, QoS map, physical port and classification counters.

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 incoming 802.1p and DSCP markings, trust mode, QoS map, physical port and classification counters.

D:

Review queue maps, output drops, interface rate, strict versus weighted servicing and application latency. These observations are applicable to Egress priority scheduling and congestion visibility, but would not isolate the main failure first. The decisive evidence is: Inspect incoming 802.1p and DSCP markings, trust mode, QoS map, physical port and classification counters.

Question 608

A branch cascades managed switches but connects a ring without checking the supported FortiLink stacking design. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.
  2. The exact dropped direction or incorrect address binding is evidenced before changing a security feature.
  3. Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes.
  4. Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles.
  5. Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic.

Explanation

Correct Answers

A:

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

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

Incorrect Answers

B:

The exact dropped direction or incorrect address binding is evidenced before changing a security feature. This step concerns Capture-based DHCP and ARP path isolation and is not part of the required paired solution. The correct action and evidence are: Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles. Together with: Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.

C:

Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes. This step concerns STP incident recovery with MAC flap evidence and is not part of the required paired solution. The correct action and evidence are: Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles. Together with: Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.

E:

Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic. This step concerns Static route and default gateway validation and is not part of the required paired solution. The correct action and evidence are: Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles. Together with: Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.

Question 609

After an office renovation, broadcast rates spike and the same client MAC jumps between two access ports. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect DHCP server permitted list, Option 82 insertion/trust state, relay path, client bindings and lease evidence.
  2. Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path.
  3. Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway.
  4. Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes.

Explanation

Correct Answer

D:

Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes. Packet loss during a bridging loop can coexist with clean optical counters, so L1-only diagnostics miss the root cause. The paired action is: Use STP state and MAC move evidence to isolate one bad bridging path and change only the proven element.

Incorrect Answers

A:

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: Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes.

B:

Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path. These observations are applicable to FortiGate managed FortiSwitch VLAN interface placement, but would not isolate the main failure first. The decisive evidence is: Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes.

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: Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes.

Question 610

An operations platform sees no FortiSwitch traffic samples because the configured sFlow collector address is wrong. 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. Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.
  3. Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope.
  4. Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes.

Explanation

Correct Answer

C:

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

Incorrect Answers

A:

Verify FortiLink management status and user VLAN reachability independently when a switch is authorized but clients fail. This action is relevant to FortiLink control and client VLAN transport separation, not the controlling requirement in this case. FortiLink transports management and data; a successful controller heartbeat does not guarantee a user VLAN or firewall session is permitted. The targeted response is: Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope.

B:

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: Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope.

D:

Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes. This action is relevant to FortiSwitch diagnostic commands and logs, not the controlling requirement in this case. A log message without source device, time and relevant state is not adequate to prove root cause. The targeted response is: Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope.

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