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 59

Question 580

The only switch backup was taken before a year of VLAN changes and restore loses critical networks. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect FortiGate HA active member, FortiLink aggregate state, ISL, MCLAG peer link, standby path and STP roles.
  2. Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions.
  3. Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.
  4. Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode.

Explanation

Correct Answer

B:

Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions. Backups require correct model/version and an actual restore procedure; a saved file name is not proof a recovered switch will work. The paired action is: Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery.

Incorrect Answers

A:

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: Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions.

C:

Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls. These observations are applicable to FortiSwitch security profile application and precedence, but would not isolate the main failure first. The decisive evidence is: Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions.

D:

Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode. These observations are applicable to Controller authorization and pending-switch state, but would not isolate the main failure first. The decisive evidence is: Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions.

Question 581

A new VLAN is mapped into a different MST instance on one switch and topology behavior diverges. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues.
  2. Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.
  3. The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions.
  4. Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy.
  5. Examine LLDP transmit state, port profile, neighbor TLVs, advertised VLAN and DSCP or 802.1p settings.

Explanation

Correct Answers

B:

Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters. Different MST configuration identifiers split regions even if switch ports are physically connected. The paired action is: Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy. This is the diagnostic or verification half of the requested TWO-step pair.

D:

Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy. Different MST configuration identifiers split regions even if switch ports are physically connected. Verify the action with: Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters. This is the configuration or remediation half of the requested TWO-step pair.

Incorrect Answers

A:

Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues. This step concerns QoS ingress classification and trust boundaries and is not part of the required paired solution. The correct action and evidence are: Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy. Together with: Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.

C:

The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions. This step concerns Managed switch port statistics and counter analysis and is not part of the required paired solution. The correct action and evidence are: Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy. Together with: Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.

E:

Examine LLDP transmit state, port profile, neighbor TLVs, advertised VLAN and DSCP or 802.1p settings. This step concerns LLDP-MED voice network policy advertisements and is not part of the required paired solution. The correct action and evidence are: Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy. Together with: Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.

Question 582

A new routed VLAN exists but its SVI stays down because no participating port is operational. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway.
  2. Inspect MAC table usage, configured learning limit, learned device count, port-security event and violation action.
  3. Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port.
  4. Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes.

Explanation

Correct Answer

A:

Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway. Layer-3 SVI configuration and actual usable forwarding are separate from having a named Layer-2 VLAN. The paired action is: Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context.

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 SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway.

C:

Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port. These observations are applicable to IGMP snooping and multicast receivers, but would not isolate the main failure first. The decisive evidence is: Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway.

D:

Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes. These observations are applicable to Voice and data VLAN separation on shared access ports, but would not isolate the main failure first. The decisive evidence is: Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway.

Question 583

A new VLAN is mapped into a different MST instance on one switch and topology behavior diverges. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.
  2. Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN.
  3. Check client MAC learning, VLAN database, switch uplink tags, gateway ARP and port assignment on every hop.
  4. Inspect guard role, BPDU reception, root-ID history, STP port role and loop-condition log.

Explanation

Correct Answer

A:

Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters. Different MST configuration identifiers split regions even if switch ports are physically connected. The paired action is: Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy.

Incorrect Answers

B:

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: Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.

C:

Check client MAC learning, VLAN database, switch uplink tags, gateway ARP and port assignment on every hop. These observations are applicable to VLAN access isolation and troubleshooting of membership, but would not isolate the main failure first. The decisive evidence is: Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.

D:

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: Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.

Question 584

A FortiGate template updates native VLANs but a switch shows an outdated port mapping after synchronization. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet.
  2. Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy.
  3. Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior.
  4. Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes.

Explanation

Correct Answer

C:

Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior. Directly editing a FortiLink-managed switch can cause drift because FortiGate remains the controller of record. The paired action is: Change managed switch VLAN membership through the FortiGate controller and verify the installed configuration stays consistent.

Incorrect Answers

A:

Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet. These observations are applicable to IPv4 source guard and binding-based packet filtering, but would not isolate the main failure first. The decisive evidence is: Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior.

B:

Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy. These observations are applicable to BPDU guard on endpoint-facing ports, but would not isolate the main failure first. The decisive evidence is: Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior.

D:

Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes. These observations are applicable to Voice and data VLAN separation on shared access ports, but would not isolate the main failure first. The decisive evidence is: Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior.

Question 585

An operator receives an assigned IP address but assumes that proves the switch is already controller-authorized. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Use documented peer-group and downstream trunk configuration for MCLAG rather than creating ad hoc parallel Ethernet links.
  2. Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting.
  3. Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure.
  4. Choose supported Fortinet transceivers and link media based on switch capability, optical reach and wavelength.

Explanation

Correct Answer

C:

Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure. Zero-touch deployment works only when the necessary discovery path and identity checks function; a link LED is insufficient. Verify the action with: Inspect factory-default mode, DHCP or discovery exchange, upstream native VLAN, FortiLink enablement, NTP and controller authorization.

Incorrect Answers

A:

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: Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure.

B:

Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting. This action is relevant to Managed switch configuration synchronization, not the controlling requirement in this case. Local changes on a FortiLink-managed switch can be discarded when the FortiGate controller reapplies its known configuration. The targeted response is: Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure.

D:

Choose supported Fortinet transceivers and link media based on switch capability, optical reach and wavelength. This action is relevant to Optic compatibility and laser diagnostic evidence, not the controlling requirement in this case. Matching a mechanical optic cage is insufficient to prove optical or firmware compatibility. The targeted response is: Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure.

Question 586

A contractor creates an unapproved second ring path, then calls every STP blocked port an outage. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters.
  2. Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware.
  3. Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.
  4. Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy.

Explanation

Correct Answer

C:

Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status. A FortiGate controls each FortiSwitch through the managed Layer-2 topology, but downstream reachability depends on upstream FortiLink links. The paired action is: Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.

Incorrect Answers

A:

Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters. These observations are applicable to Managed tenant troubleshooting across controller and access layer, but would not isolate the main failure first. The decisive evidence is: Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.

B:

Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware. These observations are applicable to FortiLink transport over nontrivial L2 or L3 paths, but would not isolate the main failure first. The decisive evidence is: Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.

D:

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: Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.

Question 587

A mirrored switch port feeds FortiGate but the sniffer filter incorrectly excludes double-tagged frames. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. The intended switch appears in discovery after restoring the precise missing interface or transport prerequisite.
  2. A moved device is traced to its current approved port and incorrect cross-connection is identified.
  3. Known unicast traffic reaches the correct access port while unknown traffic is confined to the intended VLAN.
  4. FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy.

Explanation

Correct Answer

D:

FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy. Sniffer placement determines visibility; absence of a packet at one observation point does not prove no packet existed elsewhere.

Incorrect Answers

A:

The intended switch appears in discovery after restoring the precise missing interface or transport prerequisite. This result relates to FortiLink discovery failure and physical uplink path, not the acceptance condition under test. The relevant result is: FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy.

B:

A moved device is traced to its current approved port and incorrect cross-connection is identified. This result relates to LLDP and MAC forwarding table extraction, not the acceptance condition under test. The relevant result is: FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy.

C:

Known unicast traffic reaches the correct access port while unknown traffic is confined to the intended VLAN. This result relates to Layer 2 MAC-learning and forwarding decisions, not the acceptance condition under test. The relevant result is: FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy.

Question 588

A third-party optic fits the switch but platform logs report it as unsupported after a firmware change. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.
  2. Inspect transceiver SKU, supported compatibility table, Tx/Rx optical power, interface alarms and cable plant type.
  3. The switch successfully onboards to the intended FortiGate and retains a recoverable controller-managed baseline.
  4. Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing.
  5. Choose supported Fortinet transceivers and link media based on switch capability, optical reach and wavelength.

Explanation

Correct Answers

B:

Inspect transceiver SKU, supported compatibility table, Tx/Rx optical power, interface alarms and cable plant type. Matching a mechanical optic cage is insufficient to prove optical or firmware compatibility. The paired action is: Choose supported Fortinet transceivers and link media based on switch capability, optical reach and wavelength. This is the diagnostic or verification half of the requested TWO-step pair.

E:

Choose supported Fortinet transceivers and link media based on switch capability, optical reach and wavelength. Matching a mechanical optic cage is insufficient to prove optical or firmware compatibility. Verify the action with: Inspect transceiver SKU, supported compatibility table, Tx/Rx optical power, interface alarms and cable plant type. This is the configuration or remediation half of the requested TWO-step pair.

Incorrect Answers

A:

Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path. This step concerns Static route and default gateway validation and is not part of the required paired solution. The correct action and evidence are: Choose supported Fortinet transceivers and link media based on switch capability, optical reach and wavelength. Together with: Inspect transceiver SKU, supported compatibility table, Tx/Rx optical power, interface alarms and cable plant type.

C:

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: Choose supported Fortinet transceivers and link media based on switch capability, optical reach and wavelength. Together with: Inspect transceiver SKU, supported compatibility table, Tx/Rx optical power, interface alarms and cable plant type.

D:

Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing. This step concerns Layer 2 MAC-learning and forwarding decisions and is not part of the required paired solution. The correct action and evidence are: Choose supported Fortinet transceivers and link media based on switch capability, optical reach and wavelength. Together with: Inspect transceiver SKU, supported compatibility table, Tx/Rx optical power, interface alarms and cable plant type.

Question 589

A switch shows repeated FortiLink disconnects after a configuration push and the team reads only client DHCP logs. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history.
  2. Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode.
  3. Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes.
  4. Approved aggregate members forward as one bundle while nonmatching links remain excluded.
  5. Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope.

Explanation

Correct Answers

A:

Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history. A log message without source device, time and relevant state is not adequate to prove root cause. The paired action is: Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes. This is the diagnostic or verification half of the requested TWO-step pair.

C:

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

Incorrect Answers

B:

Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode. This step concerns Controller authorization and pending-switch state and is not part of the required paired solution. The correct action and evidence are: Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes. Together with: Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history.

D:

Approved aggregate members forward as one bundle while nonmatching links remain excluded. This step concerns LACP negotiation on FortiSwitch FortiLink trunks and is not part of the required paired solution. The correct action and evidence are: Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes. Together with: Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history.

E:

Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope. This step concerns SNMP and sFlow monitoring configuration and is not part of the required paired solution. The correct action and evidence are: Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes. Together with: Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history.

Question 590

A branch cascades managed switches but connects a ring without checking the supported FortiLink stacking design. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect incoming 802.1p and DSCP markings, trust mode, QoS map, physical port and classification counters.
  2. Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN.
  3. Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.
  4. Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology.

Explanation

Correct Answer

C:

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.

Incorrect Answers

A:

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: Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.

B:

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: Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.

D:

Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology. These observations are applicable to MCLAG peer-link topology for managed access switches, but would not isolate the main failure first. The decisive evidence is: Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.

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