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 6

Question 50

A contractor creates an unapproved second ring path, then calls every STP blocked port an outage. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Legitimate clients lease addresses while rogue DHCP servers connected to untrusted access ports cannot answer.
  2. A controlled peer or member failure maintains approved client VLAN access without a Layer-2 loop.
  3. All subtending managed switches remain discoverable and user service survives expected single-link failures where supported.
  4. A controlled FortiGate HA failover leaves managed switches authorized and required client access functioning.

Explanation

Correct Answer

C:

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

A:

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: All subtending managed switches remain discoverable and user service survives expected single-link failures where supported.

B:

A controlled peer or member failure maintains approved client VLAN access without a Layer-2 loop. This result relates to MCLAG multichassis access redundancy, 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:

A controlled FortiGate HA failover leaves managed switches authorized and required client access functioning. This result relates to HA FortiGate pair managing switch topology, 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 51

A VLAN on the firewall has an IP but no approved intra-VLAN or inter-VLAN policy for the intended client traffic. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.
  2. Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path.
  3. Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port.
  4. Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior.

Explanation

Correct Answer

B:

Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path. A named VLAN in FortiOS is not proof its switch-port membership and L3 policy are correct. The paired action is: Build FortiSwitch VLAN interfaces in the correct FortiLink context and assign ports through the managed switch controller.

Incorrect Answers

A:

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 FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path.

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: Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path.

D:

Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior. These observations are applicable to VLAN configuration persistence and drift control, but would not isolate the main failure first. The decisive evidence is: Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path.

Question 52

A capture filter excludes ARP and the team incorrectly concludes the gateway has no address resolution activity. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers.
  2. Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps.
  3. Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.
  4. Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.

Explanation

Correct Answer

A:

Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers. Packet captures are interface and filter scoped, and platform buffer limits differ; a capture file is not proof of all traffic on every switch port. The paired action is: Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames.

Incorrect Answers

B:

Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps. These observations are applicable to Managed switch port statistics and counter analysis, but would not isolate the main failure first. The decisive evidence is: Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers.

C:

Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters. These observations are applicable to Layer 2 MAC-learning and forwarding decisions, but would not isolate the main failure first. The decisive evidence is: Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers.

D:

Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics. These observations are applicable to FortiSwitch port mirroring to network analyzer, but would not isolate the main failure first. The decisive evidence is: Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers.

Question 53

An untrusted edge switch discards a valid server Offer and the fault is blamed on DHCP service uptime. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.
  2. Inspect Discover/Offer/Request/Ack sequence, ARP requests/replies, VLAN tags, DHCP snooping and DAI counters.
  3. Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions.
  4. Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers.

Explanation

Correct Answer

B:

Inspect Discover/Offer/Request/Ack sequence, ARP requests/replies, VLAN tags, DHCP snooping and DAI counters. A DHCP lease failure can originate at the client, switch, relay or server; capturing at one side alone is not always conclusive. The paired action is: Trace DHCP and ARP exchanges at ingress and uplink to distinguish missing requests from blocked or malformed responses.

Incorrect Answers

A:

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 Discover/Offer/Request/Ack sequence, ARP requests/replies, VLAN tags, DHCP snooping and DAI counters.

C:

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 Discover/Offer/Request/Ack sequence, ARP requests/replies, VLAN tags, DHCP snooping and DAI counters.

D:

Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers. These observations are applicable to FortiSwitch local packet-capture profile and filters, but would not isolate the main failure first. The decisive evidence is: Inspect Discover/Offer/Request/Ack sequence, ARP requests/replies, VLAN tags, DHCP snooping and DAI counters.

Question 54

An HA failover succeeds for firewall traffic while downstream switch management disconnects because standby wiring is incomplete. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports.
  2. Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings.
  3. Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.
  4. Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests.

Explanation

Correct Answer

D:

Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests. FortiGate HA design and FortiSwitch stacking/MCLAG are separate mechanisms; their failure paths must both be evaluated. Verify the action with: Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.

Incorrect Answers

A:

Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports. This action is relevant to Port MAC learning-limit and violation controls, not the controlling requirement in this case. Dynamic MAC learning limits reduce accidental fan-out but should be tuned for legitimate multi-device access designs. The targeted response is: Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests.

B:

Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings. This action is relevant to Multi-tenant change verification and rollback, not the controlling requirement in this case. A change on shared physical transport can affect multiple VDOMs, even if each tenant's firewall policy is separate. The targeted response is: Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests.

C:

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: Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests.

Question 55

A replacement switch reboots with old port settings because the controller still associates the serial with a previous group. 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. FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy.
  3. The managed switch retains the intended controller-pushed policy after a controlled synchronization and restart.
  4. The switch successfully onboards to the intended FortiGate and retains a recoverable controller-managed baseline.

Explanation

Correct Answer

C:

The managed switch retains the intended controller-pushed policy after a controlled synchronization and restart. Local changes on a FortiLink-managed switch can be discarded when the FortiGate controller reapplies its known configuration.

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: The managed switch retains the intended controller-pushed policy after a controlled synchronization and restart.

B:

FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy. This result relates to FortiGate one-arm sniffer across managed switching, not the acceptance condition under test. The relevant result is: The managed switch retains the intended controller-pushed policy after a controlled synchronization and restart.

D:

The switch successfully onboards to the intended FortiGate and retains a recoverable controller-managed baseline. This result relates to Zero-touch provisioning and controller dependency checks, not the acceptance condition under test. The relevant result is: The managed switch retains the intended controller-pushed policy after a controlled synchronization and restart.

Question 56

An administrator sets a static route to a next hop located behind an interface that is administratively down. 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. The current neighboring device and optional endpoint location are visible and match approved cabling documentation.
  3. Only intended networks are reachable through the configured route and the return path remains valid.
  4. Only approved DHCP servers issue leases and the assigned endpoint identity or location remains traceable.

Explanation

Correct Answer

C:

Only intended networks are reachable through the configured route and the return path remains valid. A default route cannot repair local VLAN tagging or a missing neighbor resolution condition.

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: Only intended networks are reachable through the configured route and the return path remains valid.

B:

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: Only intended networks are reachable through the configured route and the return path remains valid.

D:

Only approved DHCP servers issue leases and the assigned endpoint identity or location remains traceable. This result relates to DHCP server allowlist and Option 82 validation, not the acceptance condition under test. The relevant result is: Only intended networks are reachable through the configured route and the return path remains valid.

Question 57

Two remote sites share overlapping prefixes and a broad static route inadvertently sends traffic to the wrong location. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. A rogue root candidate is blocked or a looped path remains safely contained without wiping all STP configuration.
  2. Only intended networks are reachable through the configured route and the return path remains valid.
  3. Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy.
  4. Accidental downstream switches are contained without disabling legitimate uplinks that should exchange BPDUs.

Explanation

Correct Answer

B:

Only intended networks are reachable through the configured route and the return path remains valid. A default route cannot repair local VLAN tagging or a missing neighbor resolution condition.

Incorrect Answers

A:

A rogue root candidate is blocked or a looped path remains safely contained without wiping all STP configuration. This result relates to Root guard and loop guard failure response, not the acceptance condition under test. The relevant result is: Only intended networks are reachable through the configured route and the return path remains valid.

C:

Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy. This result relates to FortiSwitch 802.1X port-based authentication, not the acceptance condition under test. The relevant result is: Only intended networks are reachable through the configured route and the return path remains valid.

D:

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: Only intended networks are reachable through the configured route and the return path remains valid.

Question 58

A new guest VLAN works on one FortiSwitch but is omitted from the FortiLink interswitch path. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Change managed switch VLAN membership through the FortiGate controller and verify the installed configuration stays consistent.
  2. Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery.
  3. Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes.
  4. Verify FortiLink management status and user VLAN reachability independently when a switch is authorized but clients fail.

Explanation

Correct Answer

D:

Verify FortiLink management status and user VLAN reachability independently when a switch is authorized but clients fail. FortiLink transports management and data; a successful controller heartbeat does not guarantee a user VLAN or firewall session is permitted. Verify the action with: Inspect FortiLink management state, native/tagged VLANs, port membership, FortiGate interface and active firewall policy.

Incorrect Answers

A:

Change managed switch VLAN membership through the FortiGate controller and verify the installed configuration stays consistent. This action is relevant to VLAN configuration persistence and drift control, not the controlling requirement in this case. Directly editing a FortiLink-managed switch can cause drift because FortiGate remains the controller of record. The targeted response is: Verify FortiLink management status and user VLAN reachability independently when a switch is authorized but clients fail.

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: Verify FortiLink management status and user VLAN reachability independently when a switch is authorized but clients fail.

C:

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: Verify FortiLink management status and user VLAN reachability independently when a switch is authorized but clients fail.

Question 59

A new conference phone reboots when its extra display turns on despite a stable Ethernet link. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Only intended networks are reachable through the configured route and the return path remains valid.
  2. Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority.
  3. FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy.
  4. Phones and access points receive stable allocated power while redundant PSU and priority policies remain within budget.

Explanation

Correct Answer

D:

Phones and access points receive stable allocated power while redundant PSU and priority policies remain within budget. Port count and Ethernet link state do not guarantee sufficient power for high-draw endpoints.

Incorrect Answers

A:

Only intended networks are reachable through the configured route and the return path remains valid. This result relates to Static route and default gateway validation, not the acceptance condition under test. The relevant result is: Phones and access points receive stable allocated power while redundant PSU and priority policies remain within budget.

B:

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: Phones and access points receive stable allocated power while redundant PSU and priority policies remain within budget.

C:

FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy. This result relates to FortiGate one-arm sniffer across managed switching, not the acceptance condition under test. The relevant result is: Phones and access points receive stable allocated power while redundant PSU and priority policies remain within budget.

Question 60

A handset supports LLDP-MED but the access switch is configured only to receive LLDP and not advertise local policy. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.
  2. Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues.
  3. Use FortiLink split-interface or standby interfaces only for supported topology and verify active versus backup port behavior.
  4. Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority.

Explanation

Correct Answer

D:

Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority. LLDP-MED exchanges policy hints with compatible endpoints; it does not substitute for port membership and DHCP. Verify the action with: Examine LLDP transmit state, port profile, neighbor TLVs, advertised VLAN and DSCP or 802.1p settings.

Incorrect Answers

A:

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: Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority.

B:

Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues. This action is relevant to QoS ingress classification and trust boundaries, not the controlling requirement in this case. A packet marking has no useful QoS effect until supported classification and scheduling map it consistently. The targeted response is: Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority.

C:

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: Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority.

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