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 54

Question 530

A firewall-to-switch connection repeatedly flaps because each side assumes different negotiated speed. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Inspect hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect.
  2. Verify model-specific PoE class, total switch power budget and per-port policy before enabling new powered devices.
  3. Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters.
  4. Legitimate clients lease addresses while rogue DHCP servers connected to untrusted access ports cannot answer.
  5. Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds.

Explanation

Correct Answers

C:

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

E:

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

Incorrect Answers

A:

Inspect hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect. This step concerns FortiSwitch split port breakout mode and is not part of the required paired solution. The correct action and evidence are: Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds. Together with: Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters.

B:

Verify model-specific PoE class, total switch power budget and per-port policy before enabling new powered devices. This step concerns Power over Ethernet port controls and budgets and is not part of the required paired solution. The correct action and evidence are: Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds. Together with: Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters.

D:

Legitimate clients lease addresses while rogue DHCP servers connected to untrusted access ports cannot answer. This step concerns DHCP snooping trust-boundary enforcement and is not part of the required paired solution. The correct action and evidence are: Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds. Together with: Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters.

Question 531

A managed FortiSwitch learns an unauthorized DHCP server from a neighboring guest kiosk. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. A controlled peer or member failure maintains approved client VLAN access without a Layer-2 loop.
  2. Inspect DHCP server permitted list, Option 82 insertion/trust state, relay path, client bindings and lease evidence.
  3. Inspect frame-rate counters by class, threshold configuration, affected VLANs and protocol health under controlled load.
  4. Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings.
  5. Use documented trusted DHCP-server lists or Option 82 information where supported to enforce authorized address assignment.

Explanation

Correct Answers

B:

Inspect DHCP server permitted list, Option 82 insertion/trust state, relay path, client bindings and lease evidence. DHCP server allowlist and Option 82 metadata provide additional context but cannot correct a failed VLAN or missing upstream relay. The paired action is: Use documented trusted DHCP-server lists or Option 82 information where supported to enforce authorized address assignment. This is the diagnostic or verification half of the requested TWO-step pair.

E:

Use documented trusted DHCP-server lists or Option 82 information where supported to enforce authorized address assignment. DHCP server allowlist and Option 82 metadata provide additional context but cannot correct a failed VLAN or missing upstream relay. Verify the action with: Inspect DHCP server permitted list, Option 82 insertion/trust state, relay path, client bindings and lease evidence. This is the configuration or remediation half of the requested TWO-step pair.

Incorrect Answers

A:

A controlled peer or member failure maintains approved client VLAN access without a Layer-2 loop. This step concerns MCLAG multichassis access redundancy and is not part of the required paired solution. The correct action and evidence are: Use documented trusted DHCP-server lists or Option 82 information where supported to enforce authorized address assignment. Together with: Inspect DHCP server permitted list, Option 82 insertion/trust state, relay path, client bindings and lease evidence.

C:

Inspect frame-rate counters by class, threshold configuration, affected VLANs and protocol health under controlled load. This step concerns Storm-control thresholds and broadcast containment and is not part of the required paired solution. The correct action and evidence are: Use documented trusted DHCP-server lists or Option 82 information where supported to enforce authorized address assignment. Together with: Inspect DHCP server permitted list, Option 82 insertion/trust state, relay path, client bindings and lease evidence.

D:

Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings. This step concerns IPv4 source guard and binding-based packet filtering and is not part of the required paired solution. The correct action and evidence are: Use documented trusted DHCP-server lists or Option 82 information where supported to enforce authorized address assignment. Together with: Inspect DHCP server permitted list, Option 82 insertion/trust state, relay path, client bindings and lease evidence.

Question 532

A switch CLI patch fixes a VLAN temporarily but disappears after controller synchronization. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.
  2. Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting.
  3. The user VLAN reaches the authorized gateway without being placed on an unrelated physical FortiGate interface.
  4. Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration.
  5. Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure.

Explanation

Correct Answers

B:

Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting. Local changes on a FortiLink-managed switch can be discarded when the FortiGate controller reapplies its known configuration. Verify the action with: Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration. This is the configuration or remediation half of the requested TWO-step pair.

D:

Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration. Local changes on a FortiLink-managed switch can be discarded when the FortiGate controller reapplies its known configuration. The paired action is: Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

A:

Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status. This step concerns FortiSwitch multi-tier managed topology and is not part of the required paired solution. The correct action and evidence are: Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting. Together with: Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration.

C:

The user VLAN reaches the authorized gateway without being placed on an unrelated physical FortiGate interface. This step concerns FortiGate managed FortiSwitch VLAN interface placement and is not part of the required paired solution. The correct action and evidence are: Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting. Together with: Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration.

E:

Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure. 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: Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting. Together with: Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration.

Question 533

A firewall-to-switch connection repeatedly flaps because each side assumes different negotiated speed. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds.
  2. Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings.
  3. Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping.
  4. Choose supported Fortinet transceivers and link media based on switch capability, optical reach and wavelength.

Explanation

Correct Answer

A:

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

Incorrect Answers

B:

Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings. This action is relevant to FortiSwitch port mirroring to network analyzer, not the controlling requirement in this case. A mirrored stream is passive evidence and can be incomplete if analyzer bandwidth is lower than the observed traffic. The targeted response is: Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds.

C:

Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping. This action is relevant to FortiSwitch split port breakout mode, not the controlling requirement in this case. A physical QSFP cage does not guarantee that four independent Ethernet child ports can be enabled on every model. The targeted response is: Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds.

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: Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds.

Question 534

MAC addresses oscillate between two uplinks after a newly installed unmanaged bridge creates a loop. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. A controlled peer or member failure maintains approved client VLAN access without a Layer-2 loop.
  2. Known unicast traffic reaches the correct access port while unknown traffic is confined to the intended VLAN.
  3. Hosts can reach their intended SVI and authorized routed destinations without overlapping address space.
  4. Members receive subscribed streams while unsubscribed access ports are not flooded unnecessarily.

Explanation

Correct Answer

B:

Known unicast traffic reaches the correct access port while unknown traffic is confined to the intended VLAN. An L2 switch uses MAC destination and VLAN state for forwarding; a healthy SVI is not proof a host is on the proper port.

Incorrect Answers

A:

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: Known unicast traffic reaches the correct access port while unknown traffic is confined to the intended VLAN.

C:

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: Known unicast traffic reaches the correct access port while unknown traffic is confined to the intended VLAN.

D:

Members receive subscribed streams while unsubscribed access ports are not flooded unnecessarily. This result relates to IGMP snooping and multicast receivers, not the acceptance condition under test. The relevant result is: Known unicast traffic reaches the correct access port while unknown traffic is confined to the intended VLAN.

Question 535

A monitoring host receives no packets because the chosen mirror direction captures only ingress while the failing frames are egress. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect FortiGate FortiLink status, supported discovery port, LLDP frames, interface IP, link errors and switch serial.
  2. Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history.
  3. Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.
  4. Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.

Explanation

Correct Answer

C:

Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics. A mirrored stream is passive evidence and can be incomplete if analyzer bandwidth is lower than the observed traffic. The paired action is: Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings.

Incorrect Answers

A:

Inspect FortiGate FortiLink status, supported discovery port, LLDP frames, interface IP, link errors and switch serial. These observations are applicable to FortiLink discovery failure and physical uplink path, but would not isolate the main failure first. The decisive evidence is: Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.

B:

Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history. These observations are applicable to FortiSwitch diagnostic commands and logs, but would not isolate the main failure first. The decisive evidence is: Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.

D:

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 mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.

Question 536

An administrator gives every traffic class strict priority and then cannot explain which queue is actually served. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
  2. Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.
  3. Examine LLDP transmit state, port profile, neighbor TLVs, advertised VLAN and DSCP or 802.1p settings.
  4. Review queue maps, output drops, interface rate, strict versus weighted servicing and application latency.

Explanation

Correct Answer

D:

Review queue maps, output drops, interface rate, strict versus weighted servicing and application latency. QoS prioritizes scarce link capacity but cannot create bandwidth beyond the physical egress rate. The paired action is: Apply supported egress CoS queue policy to reduce latency under congestion without starving other required traffic.

Incorrect Answers

A:

Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility. These observations are applicable to Discovered versus authorized FortiSwitch state, but would not isolate the main failure first. The decisive evidence is: Review queue maps, output drops, interface rate, strict versus weighted servicing and application latency.

B:

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: Review queue maps, output drops, interface rate, strict versus weighted servicing and application latency.

C:

Examine LLDP transmit state, port profile, neighbor TLVs, advertised VLAN and DSCP or 802.1p settings. These observations are applicable to LLDP-MED voice network policy advertisements, but would not isolate the main failure first. The decisive evidence is: Review queue maps, output drops, interface rate, strict versus weighted servicing and application latency.

Question 537

A user authenticates successfully but its new RADIUS ACL never appears in switch policy state. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Apply a specific restricted VLAN or quarantine mechanism with explicit authorized remediation and monitoring expectations.
  2. Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints.
  3. Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links.
  4. Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices.

Explanation

Correct Answer

B:

Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints. DACLs install after successful authorization and documented release limits apply; a RADIUS response alone is not proof of forwarding enforcement. Verify the action with: Inspect RADIUS Filter-Id or downloadable ACL attribute, authenticated session state, installed hardware entries and ACL counters.

Incorrect Answers

A:

Apply a specific restricted VLAN or quarantine mechanism with explicit authorized remediation and monitoring expectations. This action is relevant to VLAN security policy and quarantine actions, not the controlling requirement in this case. Quarantine must be enforced at the right switch and VLAN path; a security-alert label alone does not remove access. The targeted response is: Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints.

C:

Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links. This action is relevant to DHCP snooping trust-boundary enforcement, not the controlling requirement in this case. Trusting every port defeats DHCP snooping and wrongly distrusting the server uplink may suppress all leases. The targeted response is: Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints.

D:

Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices. This action is relevant to Controller authorization and pending-switch state, not the controlling requirement in this case. Authorizing a switch is an administrative trust step; pending switch state is not evidence of a routing failure. The targeted response is: Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints.

Question 538

A QoS change trusts 802.1p tags from a server port that should be an untagged client interface. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location.
  2. Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues.
  3. Apply supported egress CoS queue policy to reduce latency under congestion without starving other required traffic.
  4. Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records.

Explanation

Correct Answer

B:

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

Incorrect Answers

A:

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: Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues.

C:

Apply supported egress CoS queue policy to reduce latency under congestion without starving other required traffic. This action is relevant to Egress priority scheduling and congestion visibility, not the controlling requirement in this case. QoS prioritizes scarce link capacity but cannot create bandwidth beyond the physical egress rate. The targeted response is: Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues.

D:

Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records. This action is relevant to LLDP neighbor discovery and location information, not the controlling requirement in this case. LLDP is an L2 discovery protocol and cannot prove the whole routed service path or phone emergency-location correctness by itself. The targeted response is: Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues.

Question 539

Two customer groups with overlapping subnet plans are connected as if VDOM segmentation automatically fixes routing collisions. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Each customer's tagged traffic reaches only its assigned service context without S-VLAN collision.
  2. The offending misassignment is corrected with both permitted traffic and forbidden cross-tenant traffic tested.
  3. Two tenants can use the supported shared port without accidental cross-tenant broadcasts or privilege escalation.
  4. A controlled failure test restores approved management and access connectivity through the designed redundant path.

Explanation

Correct Answer

C:

Two tenants can use the supported shared port without accidental cross-tenant broadcasts or privilege escalation. Shared physical ports can support some per-port controls across VDOMs, but feature support and tagging must be checked for the exact release.

Incorrect Answers

A:

Each customer's tagged traffic reaches only its assigned service context without S-VLAN collision. This result relates to QinQ outer and inner VLAN tenant mapping, not the acceptance condition under test. The relevant result is: Two tenants can use the supported shared port without accidental cross-tenant broadcasts or privilege escalation.

B:

The offending misassignment is corrected with both permitted traffic and forbidden cross-tenant traffic tested. This result relates to Managed tenant troubleshooting across controller and access layer, not the acceptance condition under test. The relevant result is: Two tenants can use the supported shared port without accidental cross-tenant broadcasts or privilege escalation.

D:

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: Two tenants can use the supported shared port without accidental cross-tenant broadcasts or privilege escalation.

Question 540

A manager wants all discovered switches automatically authorized even though the site uses untrusted wiring closets. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history.
  2. Inspect FortiGate HA active member, FortiLink aggregate state, ISL, MCLAG peer link, standby path and STP roles.
  3. Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode.
  4. Check switch quarantine status, ACL/security profile, allowed remediation services, NAC event and release criteria.

Explanation

Correct Answer

C:

Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode. Authorizing a switch is an administrative trust step; pending switch state is not evidence of a routing failure. The paired action is: Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices.

Incorrect Answers

A:

Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history. These observations are applicable to FortiSwitch diagnostic commands and logs, but would not isolate the main failure first. The decisive evidence is: Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode.

B:

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: Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode.

D:

Check switch quarantine status, ACL/security profile, allowed remediation services, NAC event and release criteria. These observations are applicable to VLAN security policy and quarantine actions, but would not isolate the main failure first. The decisive evidence is: Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode.

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