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 68

Question 670

A FortiGate template updates native VLANs but a switch shows an outdated port mapping after synchronization. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. The handset and attached workstation use the intended separate networks and retain their authorized access.
  2. The suspect device is restricted without interrupting unrelated tenants and can be restored after review.
  3. The intended VLAN survives a switch restart without unexpected controller overwrite or unauthorized local change.
  4. A rogue root candidate is blocked or a looped path remains safely contained without wiping all STP configuration.

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:

The handset and attached workstation use the intended separate networks and retain their authorized access. This result relates to Voice and data VLAN separation on shared access 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.

B:

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.

D:

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

Question 671

A phone uplink starts receiving unexpected bridge-control frames after someone adds a looped desktop switch. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Use STP state and MAC move evidence to isolate one bad bridging path and change only the proven element.
  2. Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy.
  3. Enable supported BPDU guard only on true edge/client ports, and restore blocked ports after identifying unauthorized switching.
  4. Identify FortiLink failures caused by split-interface, HA, MCLAG peer or ISL mismatches before changing unrelated ports.

Explanation

Correct Answer

C:

Enable supported BPDU guard only on true edge/client ports, and restore blocked ports after identifying unauthorized switching. BPDU guard can disable an intended trunk if incorrectly treated as an end-station port. Verify the action with: Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy.

Incorrect Answers

A:

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: Enable supported BPDU guard only on true edge/client ports, and restore blocked ports after identifying unauthorized switching.

B:

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: Enable supported BPDU guard only on true edge/client ports, and restore blocked ports after identifying unauthorized switching.

D:

Identify FortiLink failures caused by split-interface, HA, MCLAG peer or ISL mismatches before changing unrelated ports. This action is relevant to FortiLink HA and MCLAG topology faults, not the controlling requirement in this case. FortiGate HA, FortiLink split-interface and FortiSwitch MCLAG have distinct failover behaviors that cannot be inferred from link LEDs alone. The targeted response is: Enable supported BPDU guard only on true edge/client ports, and restore blocked ports after identifying unauthorized switching.

Question 672

A switch has a supported breakout cable yet its configured phy-mode and child speeds do not match the attached peers. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.
  2. Review queue maps, output drops, interface rate, strict versus weighted servicing and application latency.
  3. Inspect hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect.
  4. Inspect power supply reserve, current draw, negotiated PoE class, priority shedding and port events.

Explanation

Correct Answer

C:

Inspect hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect. A physical QSFP cage does not guarantee that four independent Ethernet child ports can be enabled on every model. The paired action is: Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping.

Incorrect Answers

A:

Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability. These observations are applicable to QinQ outer and inner VLAN tenant mapping, but would not isolate the main failure first. The decisive evidence is: Inspect hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect.

B:

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 hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect.

D:

Inspect power supply reserve, current draw, negotiated PoE class, priority shedding and port events. These observations are applicable to Power over Ethernet port controls and budgets, but would not isolate the main failure first. The decisive evidence is: Inspect hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect.

Question 673

One FortiSwitch reboot causes adjacent units to move between discovered and authorized states. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. The intended tenant configuration changes while other tenants retain their segmentation and service.
  2. Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs.
  3. Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles.
  4. Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.
  5. Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events.

Explanation

Correct Answers

B:

Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs. A missing switch in a FortiLink managed chain may be caused by the upstream ISL even if its access ports still carry local traffic. Verify the action with: Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events. This is the configuration or remediation half of the requested TWO-step pair.

E:

Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events. A missing switch in a FortiLink managed chain may be caused by the upstream ISL even if its access ports still carry local traffic. The paired action is: Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

A:

The intended tenant configuration changes while other tenants retain their segmentation and service. This step concerns Multi-tenant change verification and rollback and is not part of the required paired solution. The correct action and evidence are: Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs. Together with: Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events.

C:

Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles. This step concerns MCLAG peer-link topology for managed access switches and is not part of the required paired solution. The correct action and evidence are: Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs. Together with: Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events.

D:

Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters. This step concerns MSTP region consistency and designated root and is not part of the required paired solution. The correct action and evidence are: Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs. Together with: Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events.

Question 674

An unknown switch appears discovered after a contractor accidentally connected equipment to the FortiLink port. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Managed status remains healthy and user traffic uses only its intended FortiLink-carried VLANs.
  2. A controlled failure test restores approved management and access connectivity through the designed redundant path.
  3. The expected known switch becomes authorized and synchronizes without accepting an unrelated device.
  4. Exactly the intended serial joins managed inventory and receives approved controller settings after authorization.

Explanation

Correct Answer

C:

The expected known switch becomes authorized and synchronizes without accepting an unrelated device. Authorizing a switch is an administrative trust step; pending switch state is not evidence of a routing failure.

Incorrect Answers

A:

Managed status remains healthy and user traffic uses only its intended FortiLink-carried VLANs. This result relates to FortiLink control and client VLAN transport separation, not the acceptance condition under test. The relevant result is: The expected known switch becomes authorized and synchronizes without accepting an unrelated device.

B:

A controlled failure test restores approved management and access connectivity through the designed redundant path. This result relates to FortiLink HA and MCLAG topology faults, not the acceptance condition under test. The relevant result is: The expected known switch becomes authorized and synchronizes without accepting an unrelated device.

D:

Exactly the intended serial joins managed inventory and receives approved controller settings after authorization. This result relates to Discovered versus authorized FortiSwitch state, not the acceptance condition under test. The relevant result is: The expected known switch becomes authorized and synchronizes without accepting an unrelated device.

Question 675

A previously used standalone switch never auto-discovers because its old configuration prevents expected default provisioning. 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. Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure.
  3. Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings.
  4. Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics.

Explanation

Correct Answer

B:

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.

C:

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

D:

Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics. This action is relevant to Capture and confidentiality limits in incident response, not the controlling requirement in this case. A packet-capture tool may record payloads and credentials, so evidence handling is part of the network security process. The targeted response is: Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure.

Question 676

A new managed switch port allows link negotiation but users stay unauthenticated after a RADIUS server change. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Unauthorized source IP packets fail while an approved host continues using its assigned IP and address policy.
  2. Managed status remains healthy and user traffic uses only its intended FortiLink-carried VLANs.
  3. Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy.
  4. Approved legacy devices gain only restricted services while unknown or spoofed MAC addresses remain constrained.

Explanation

Correct Answer

C:

Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy. A physical link can be up while 802.1X blocks traffic; the switch is the authenticator, not the authentication server.

Incorrect Answers

A:

Unauthorized source IP packets fail while an approved host continues using its assigned IP and address policy. This result relates to IPv4 source guard and binding-based packet filtering, not the acceptance condition under test. The relevant result is: Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy.

B:

Managed status remains healthy and user traffic uses only its intended FortiLink-carried VLANs. This result relates to FortiLink control and client VLAN transport separation, not the acceptance condition under test. The relevant result is: Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy.

D:

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: Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy.

Question 677

Both ends of a branch trunk are set to passive LACP and none of the physical ports aggregate. 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. A controlled FortiGate HA failover leaves managed switches authorized and required client access functioning.
  3. Inspect incoming 802.1p and DSCP markings, trust mode, QoS map, physical port and classification counters.
  4. Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation.
  5. Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters.

Explanation

Correct Answers

D:

Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation. Passive LACP on both ends may not negotiate an active bundle, and individual green links do not prove aggregation. Verify the action with: Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters. This is the configuration or remediation half of the requested TWO-step pair.

E:

Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters. Passive LACP on both ends may not negotiate an active bundle, and individual green links do not prove aggregation. The paired action is: Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

A:

Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds. This step concerns Switch port speed and duplex commissioning and is not part of the required paired solution. The correct action and evidence are: Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation. Together with: Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters.

B:

A controlled FortiGate HA failover leaves managed switches authorized and required client access functioning. This step concerns HA FortiGate pair managing switch topology and is not part of the required paired solution. The correct action and evidence are: Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation. Together with: Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters.

C:

Inspect incoming 802.1p and DSCP markings, trust mode, QoS map, physical port and classification counters. This step concerns QoS ingress classification and trust boundaries and is not part of the required paired solution. The correct action and evidence are: Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation. Together with: Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters.

Question 678

A phone ignores a newly created voice VLAN because the switch advertises an obsolete LLDP-MED network policy. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect power supply reserve, current draw, negotiated PoE class, priority shedding and port events.
  2. Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway.
  3. Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test.
  4. Examine LLDP transmit state, port profile, neighbor TLVs, advertised VLAN and DSCP or 802.1p settings.

Explanation

Correct Answer

D:

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

Incorrect Answers

A:

Inspect power supply reserve, current draw, negotiated PoE class, priority shedding and port events. These observations are applicable to Power over Ethernet port controls and budgets, but would not isolate the main failure first. The decisive evidence is: Examine LLDP transmit state, port profile, neighbor TLVs, advertised VLAN and DSCP or 802.1p settings.

B:

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: Examine LLDP transmit state, port profile, neighbor TLVs, advertised VLAN and DSCP or 802.1p settings.

C:

Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test. These observations are applicable to Intra-VLAN blocking and isolation boundaries, but would not isolate the main failure first. The decisive evidence is: Examine LLDP transmit state, port profile, neighbor TLVs, advertised VLAN and DSCP or 802.1p settings.

Question 679

A managed switch belongs to a common FortiLink while new customer VLANs are assigned to an unrelated FortiGate VDOM. 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. Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure.
  3. Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues.
  4. Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence.

Explanation

Correct Answer

B:

Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure. A VDOM creates a separate policy and routing context; it does not by itself make a shared physical switch port safe for all tenants. Verify the action with: Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.

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: Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure.

C:

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: Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure.

D:

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: Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure.

Question 680

A voice client obtains an address yet keeps receiving ARP replies for the wrong gateway MAC. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.
  2. Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.
  3. Inspect Discover/Offer/Request/Ack sequence, ARP requests/replies, VLAN tags, DHCP snooping and DAI counters.
  4. Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions.

Explanation

Correct Answer

C:

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

B:

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

D:

Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions. These observations are applicable to Config backup and firmware inventory evidence, 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.

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