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 4

Question 30

A campus extends two-tier managed switching across a narrow uplink and experiences unexpected bottlenecks. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests.
  2. Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing.
  3. Inspect DHCP server permitted list, Option 82 insertion/trust state, relay path, client bindings and lease evidence.
  4. Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.

Explanation

Correct Answer

D:

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:

Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests. These observations are applicable to Multi-tenant change verification and rollback, 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:

Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing. These observations are applicable to Firmware and lifecycle preparation for FortiSwitch, 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.

C:

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

Question 31

A core maintenance event disconnects one MCLAG peer link and the operator checks only client ping. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence.
  2. Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.
  3. Apply appropriate STP root or loop protection to preserve topology while analyzing missing BPDUs and unexpected root claims.
  4. Use documented peer-group and downstream trunk configuration for MCLAG rather than creating ad hoc parallel Ethernet links.

Explanation

Correct Answer

D:

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

Incorrect Answers

A:

Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence. This action is relevant to Managed tenant troubleshooting across controller and access layer, not the controlling requirement in this case. A packet may be correctly switched but rejected by VDOM routing or firewall policy, or incorrectly admitted to another tenant at Layer 2. The targeted response is: Use documented peer-group and downstream trunk configuration for MCLAG rather than creating ad hoc parallel Ethernet links.

B:

Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition. This action is relevant to Discovered versus authorized FortiSwitch state, not the controlling requirement in this case. Switch discovery is not the same as authorization; auto-authorization has governance implications and a managed-mode transition may reboot the device. The targeted response is: Use documented peer-group and downstream trunk configuration for MCLAG rather than creating ad hoc parallel Ethernet links.

C:

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 documented peer-group and downstream trunk configuration for MCLAG rather than creating ad hoc parallel Ethernet links.

Question 32

A redundant uplink stops receiving expected BPDUs and becomes a potential loop hazard. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority.
  2. The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate.
  3. Every relevant VLAN converges without loops and redundant paths unblock only when needed.
  4. A rogue root candidate is blocked or a looped path remains safely contained without wiping all STP configuration.

Explanation

Correct Answer

D:

A rogue root candidate is blocked or a looped path remains safely contained without wiping all STP configuration. Root guard and loop guard mitigate different failure cases and should not be enabled indiscriminately on every uplink.

Incorrect Answers

A:

Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority. This result relates to QoS ingress classification and trust boundaries, not the acceptance condition under test. The relevant result is: A rogue root candidate is blocked or a looped path remains safely contained without wiping all STP configuration.

B:

The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate. This result relates to FortiSwitch diagnostic commands and logs, not the acceptance condition under test. The relevant result is: A rogue root candidate is blocked or a looped path remains safely contained without wiping all STP configuration.

C:

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

Question 33

A multicast paging VLAN disappears after a template update allowed only the corporate user VLAN. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Hosts can reach their intended SVI and authorized routed destinations without overlapping address space.
  2. Switches reconnect to FortiLink and preserve approved VLAN/role configuration after the planned upgrade.
  3. The impacted client can communicate on the permitted VLAN while unrelated tenant or guest VLANs remain separated.
  4. Expected members join the trunk and survive a member disconnect without loops or silent black holes.

Explanation

Correct Answer

C:

The impacted client can communicate on the permitted VLAN while unrelated tenant or guest VLANs remain separated. Link up and successful traffic in one VLAN do not prove every VLAN is correctly provisioned on the path.

Incorrect Answers

A:

Hosts can reach their intended SVI and authorized routed destinations without overlapping address space. This result relates to FortiSwitch SVI routing and connected routes, not the acceptance condition under test. The relevant result is: The impacted client can communicate on the permitted VLAN while unrelated tenant or guest VLANs remain separated.

B:

Switches reconnect to FortiLink and preserve approved VLAN/role configuration after the planned upgrade. This result relates to Firmware and lifecycle preparation for FortiSwitch, not the acceptance condition under test. The relevant result is: The impacted client can communicate on the permitted VLAN while unrelated tenant or guest VLANs remain separated.

D:

Expected members join the trunk and survive a member disconnect without loops or silent black holes. This result relates to Link aggregation and port error recovery, not the acceptance condition under test. The relevant result is: The impacted client can communicate on the permitted VLAN while unrelated tenant or guest VLANs remain separated.

Question 34

A user changes departments and the RADIUS server issues CoA but the switch continues enforcing the old access role. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Approved legacy devices gain only restricted services while unknown or spoofed MAC addresses remain constrained.
  2. An unexpected additional device is restricted or signaled without knocking out approved business equipment.
  3. A session's effective access changes only when the authorization result is accepted and policy is installed on hardware.
  4. The current neighboring device and optional endpoint location are visible and match approved cabling documentation.

Explanation

Correct Answer

C:

A session's effective access changes only when the authorization result is accepted and policy is installed on hardware. RADIUS authentication success is not proof that a downloadable ACL or CoA update was enforced; some modes have documented conditions.

Incorrect Answers

A:

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: A session's effective access changes only when the authorization result is accepted and policy is installed on hardware.

B:

An unexpected additional device is restricted or signaled without knocking out approved business equipment. This result relates to Port MAC learning-limit and violation controls, not the acceptance condition under test. The relevant result is: A session's effective access changes only when the authorization result is accepted and policy is installed on hardware.

D:

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: A session's effective access changes only when the authorization result is accepted and policy is installed on hardware.

Question 35

An untrusted edge switch discards a valid server Offer and the fault is blamed on DHCP service uptime. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. All subtending managed switches remain discoverable and user service survives expected single-link failures where supported.
  2. The analyzer receives the intended copies while production forwarding remains unchanged.
  3. The exact dropped direction or incorrect address binding is evidenced before changing a security feature.
  4. Troubleshooting evidence is sufficient to establish the fault without exporting unnecessary private communications.

Explanation

Correct Answer

C:

The exact dropped direction or incorrect address binding is evidenced before changing a security feature. A DHCP lease failure can originate at the client, switch, relay or server; capturing at one side alone is not always conclusive.

Incorrect Answers

A:

All subtending managed switches remain discoverable and user service survives expected single-link failures where supported. This result relates to FortiSwitch multi-tier managed topology, not the acceptance condition under test. The relevant result is: The exact dropped direction or incorrect address binding is evidenced before changing a security feature.

B:

The analyzer receives the intended copies while production forwarding remains unchanged. This result relates to FortiSwitch port mirroring to network analyzer, not the acceptance condition under test. The relevant result is: The exact dropped direction or incorrect address binding is evidenced before changing a security feature.

D:

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: The exact dropped direction or incorrect address binding is evidenced before changing a security feature.

Question 36

A direct switch connection works until the FortiGate port is repurposed into another software-switch aggregate. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Switches reconnect to FortiLink and preserve approved VLAN/role configuration after the planned upgrade.
  2. Management control and authorized user traffic work over the direct connection without confusing them.
  3. The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions.
  4. The intended tenant configuration changes while other tenants retain their segmentation and service.

Explanation

Correct Answer

B:

Management control and authorized user traffic work over the direct connection without confusing them. FortiLink carries management and data traffic; a valid management handshake does not prove every user VLAN is forwarded.

Incorrect Answers

A:

Switches reconnect to FortiLink and preserve approved VLAN/role configuration after the planned upgrade. This result relates to Firmware and lifecycle preparation for FortiSwitch, not the acceptance condition under test. The relevant result is: Management control and authorized user traffic work over the direct connection without confusing them.

C:

The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions. This result relates to Managed switch port statistics and counter analysis, not the acceptance condition under test. The relevant result is: Management control and authorized user traffic work over the direct connection without confusing them.

D:

The intended tenant configuration changes while other tenants retain their segmentation and service. This result relates to Multi-tenant change verification and rollback, not the acceptance condition under test. The relevant result is: Management control and authorized user traffic work over the direct connection without confusing them.

Question 37

A trunk member reports no traffic despite all LACP member LEDs appearing green. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location.
  2. Approved legacy devices gain only restricted services while unknown or spoofed MAC addresses remain constrained.
  3. Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps.
  4. Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.
  5. Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery.

Explanation

Correct Answers

A:

Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location. A port-up indicator or one successful ping is not proof that a congested or errored uplink is healthy. Verify the action with: Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps. This is the configuration or remediation half of the requested TWO-step pair.

C:

Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps. A port-up indicator or one successful ping is not proof that a congested or errored uplink is healthy. The paired action is: Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

B:

Approved legacy devices gain only restricted services while unknown or spoofed MAC addresses remain constrained. This step concerns MAC-based authentication and restricted legacy devices and is not part of the required paired solution. The correct action and evidence are: Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location. Together with: Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps.

D:

Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction. This step concerns FortiGate one-arm sniffer across managed switching and is not part of the required paired solution. The correct action and evidence are: Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location. Together with: Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps.

E:

Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery. This step concerns Config backup and firmware inventory evidence and is not part of the required paired solution. The correct action and evidence are: Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location. Together with: Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps.

Question 38

An operations platform sees no FortiSwitch traffic samples because the configured sFlow collector address is wrong. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology.
  2. Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy.
  3. Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image.
  4. Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions.

Explanation

Correct Answer

B:

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

Incorrect Answers

A:

Inspect 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: Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy.

C:

Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image. These observations are applicable to FortiLink synchronization and upgrade troubleshooting, but would not isolate the main failure first. The decisive evidence is: Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy.

D:

Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions. These observations are applicable to Capture and confidentiality limits in incident response, but would not isolate the main failure first. The decisive evidence is: Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy.

Question 39

A campus extends two-tier managed switching across a narrow uplink and experiences unexpected bottlenecks. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. All subtending managed switches remain discoverable and user service survives expected single-link failures where supported.
  2. A capable handset reports the expected voice network policy and traffic uses the correct VLAN.
  3. Switches reconnect to FortiLink and preserve approved VLAN/role configuration after the planned upgrade.
  4. The intended tenant configuration changes while other tenants retain their segmentation and service.

Explanation

Correct Answer

A:

All subtending managed switches remain discoverable and user service survives expected single-link failures where supported. A FortiGate controls each FortiSwitch through the managed Layer-2 topology, but downstream reachability depends on upstream FortiLink links.

Incorrect Answers

B:

A capable handset reports the expected voice network policy and traffic uses the correct VLAN. This result relates to LLDP-MED voice network policy advertisements, not the acceptance condition under test. The relevant result is: All subtending managed switches remain discoverable and user service survives expected single-link failures where supported.

C:

Switches reconnect to FortiLink and preserve approved VLAN/role configuration after the planned upgrade. This result relates to Firmware and lifecycle preparation for FortiSwitch, not the acceptance condition under test. The relevant result is: All subtending managed switches remain discoverable and user service survives expected single-link failures where supported.

D:

The intended tenant configuration changes while other tenants retain their segmentation and service. This result relates to Multi-tenant change verification and rollback, not the acceptance condition under test. The relevant result is: All subtending managed switches remain discoverable and user service survives expected single-link failures where supported.

Question 40

An administrator assumes a new FortiSwitch model accepts the same firmware image as an older campus model. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging.
  2. Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology.
  3. Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.
  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:

Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology. A successful image upload does not prove switch operation or controller compatibility after reboot. Verify the action with: Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing.

Incorrect Answers

A:

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: Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology.

C:

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: Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology.

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: Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology.

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