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 31

Question 300

A new replacement is visible in discovery but its ports do not receive policy because it is pending authorization. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.
  2. Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols.
  3. Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging.
  4. Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end.

Explanation

Correct Answer

A:

Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition. Switch discovery is not the same as authorization; auto-authorization has governance implications and a managed-mode transition may reboot the device. Verify the action with: Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.

Incorrect Answers

B:

Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols. This action is relevant to Storm-control thresholds and broadcast containment, not the controlling requirement in this case. Overaggressive storm control can break DHCP, ARP or group discovery even when physical links remain healthy. The targeted response is: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.

C:

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: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.

D:

Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end. This action is relevant to FortiLink transport over nontrivial L2 or L3 paths, not the controlling requirement in this case. FortiLink over intermediate networks requires topology-specific settings; ordinary IP reachability alone does not establish FortiLink discovery. The targeted response is: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.

Question 301

A user authenticates successfully but its new RADIUS ACL never appears in switch policy state. 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. Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.
  3. Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN.
  4. Inspect RADIUS Filter-Id or downloadable ACL attribute, authenticated session state, installed hardware entries and ACL counters.

Explanation

Correct Answer

D:

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

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: Inspect RADIUS Filter-Id or downloadable ACL attribute, authenticated session state, installed hardware entries and ACL counters.

B:

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 RADIUS Filter-Id or downloadable ACL attribute, authenticated session state, installed hardware entries and ACL counters.

C:

Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN. These observations are applicable to MAC-based authentication and restricted legacy devices, but would not isolate the main failure first. The decisive evidence is: Inspect RADIUS Filter-Id or downloadable ACL attribute, authenticated session state, installed hardware entries and ACL counters.

Question 302

An operator tries to configure 10G on a copper port lacking that interface capability. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics.
  2. Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping.
  3. Choose supported Fortinet transceivers and link media based on switch capability, optical reach and wavelength.
  4. Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds.

Explanation

Correct Answer

D:

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

A:

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

B:

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.

C:

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 303

An engineer removes an obsolete customer VLAN from a shared trunk without checking another tenant still uses it. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.
  2. Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests.
  3. Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters.
  4. Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers.

Explanation

Correct Answer

B:

Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests. A change on shared physical transport can affect multiple VDOMs, even if each tenant's firewall policy is separate. The paired action is: Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings.

Incorrect Answers

A:

Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state. These observations are applicable to Shared port multi-VDOM policy boundaries, but would not isolate the main failure first. The decisive evidence is: Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests.

C:

Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters. These observations are applicable to Managed tenant troubleshooting across controller and access layer, but would not isolate the main failure first. The decisive evidence is: Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests.

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 shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests.

Question 304

An administrator sets a static route to a next hop located behind an interface that is administratively down. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Review queue maps, output drops, interface rate, strict versus weighted servicing and application latency.
  2. The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions.
  3. Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.
  4. Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic.
  5. Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context.

Explanation

Correct Answers

C:

Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path. A default route cannot repair local VLAN tagging or a missing neighbor resolution condition. The paired action is: Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic. This is the diagnostic or verification half of the requested TWO-step pair.

D:

Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic. A default route cannot repair local VLAN tagging or a missing neighbor resolution condition. Verify the action with: Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path. This is the configuration or remediation half of the requested TWO-step pair.

Incorrect Answers

A:

Review queue maps, output drops, interface rate, strict versus weighted servicing and application latency. This step concerns Egress priority scheduling and congestion visibility and is not part of the required paired solution. The correct action and evidence are: Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic. Together with: Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.

B:

The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions. This step concerns Managed switch port statistics and counter analysis and is not part of the required paired solution. The correct action and evidence are: Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic. Together with: Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.

E:

Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context. This step concerns FortiSwitch SVI routing and connected routes and is not part of the required paired solution. The correct action and evidence are: Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic. Together with: Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.

Question 305

A mispatched access switch creates a broadcast storm that saturates multiple closets. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect DHCP server permitted list, Option 82 insertion/trust state, relay path, client bindings and lease evidence.
  2. Inspect frame-rate counters by class, threshold configuration, affected VLANs and protocol health under controlled load.
  3. Inspect MAC table usage, configured learning limit, learned device count, port-security event and violation action.
  4. Inspect FortiGate HA active member, FortiLink aggregate state, ISL, MCLAG peer link, standby path and STP roles.

Explanation

Correct Answer

B:

Inspect frame-rate counters by class, threshold configuration, affected VLANs and protocol health under controlled load. Overaggressive storm control can break DHCP, ARP or group discovery even when physical links remain healthy. The paired action is: Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols.

Incorrect Answers

A:

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: Inspect frame-rate counters by class, threshold configuration, affected VLANs and protocol health under controlled load.

C:

Inspect MAC table usage, configured learning limit, learned device count, port-security event and violation action. These observations are applicable to Port MAC learning-limit and violation controls, but would not isolate the main failure first. The decisive evidence is: Inspect frame-rate counters by class, threshold configuration, affected VLANs and protocol health under controlled load.

D:

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 frame-rate counters by class, threshold configuration, affected VLANs and protocol health under controlled load.

Question 306

An engineer removes an obsolete customer VLAN from a shared trunk without checking another tenant still uses it. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings.
  2. Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior.
  3. Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.
  4. Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.

Explanation

Correct Answer

A:

Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings. A change on shared physical transport can affect multiple VDOMs, even if each tenant's firewall policy is separate. Verify the action with: Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests.

Incorrect Answers

B:

Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior. This action is relevant to FortiSwitch 802.1X port-based authentication, not the controlling requirement in this case. A physical link can be up while 802.1X blocks traffic; the switch is the authenticator, not the authentication server. The targeted response is: Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings.

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: Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings.

D:

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: Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings.

Question 307

A branch uplink uses a multimode optic across a single-mode campus fiber run and never achieves light. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. A planned alternate link remains blocked and takes over predictably without a broadcast storm.
  2. Unauthorized source IP packets fail while an approved host continues using its assigned IP and address policy.
  3. Every relevant VLAN converges without loops and redundant paths unblock only when needed.
  4. The correct link establishes at expected negotiated rate without recurring loss-of-signal or CRC errors.

Explanation

Correct Answer

D:

The correct link establishes at expected negotiated rate without recurring loss-of-signal or CRC errors. This is a measurable client, control-plane, or security outcome rather than a claim that configuration was entered. Matching a mechanical optic cage is insufficient to prove optical or firmware compatibility.

Incorrect Answers

A:

A planned alternate link remains blocked and takes over predictably without a broadcast storm. This result relates to MSTP region consistency and designated root, not the acceptance condition under test. The relevant result is: The correct link establishes at expected negotiated rate without recurring loss-of-signal or CRC errors.

B:

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: The correct link establishes at expected negotiated rate without recurring loss-of-signal or CRC errors.

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: The correct link establishes at expected negotiated rate without recurring loss-of-signal or CRC errors.

Question 308

After an office renovation, broadcast rates spike and the same client MAC jumps between two access ports. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Authorized monitoring receives timely, interpretable switch evidence without exposing community strings or overwhelming CPU.
  2. Use STP state and MAC move evidence to isolate one bad bridging path and change only the proven element.
  3. Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links.
  4. Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy.
  5. Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes.

Explanation

Correct Answers

B:

Use STP state and MAC move evidence to isolate one bad bridging path and change only the proven element. Packet loss during a bridging loop can coexist with clean optical counters, so L1-only diagnostics miss the root cause. Verify the action with: Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes. This is the configuration or remediation half of the requested TWO-step pair.

E:

Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes. Packet loss during a bridging loop can coexist with clean optical counters, so L1-only diagnostics miss the root cause. The paired action is: Use STP state and MAC move evidence to isolate one bad bridging path and change only the proven element. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

A:

Authorized monitoring receives timely, interpretable switch evidence without exposing community strings or overwhelming CPU. This step concerns SNMP and sFlow monitoring configuration and is not part of the required paired solution. The correct action and evidence are: Use STP state and MAC move evidence to isolate one bad bridging path and change only the proven element. Together with: Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes.

C:

Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links. This step concerns RPVST and supported STP mode interoperability and is not part of the required paired solution. The correct action and evidence are: Use STP state and MAC move evidence to isolate one bad bridging path and change only the proven element. Together with: Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes.

D:

Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy. This step concerns BPDU guard on endpoint-facing ports and is not part of the required paired solution. The correct action and evidence are: Use STP state and MAC move evidence to isolate one bad bridging path and change only the proven element. Together with: Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes.

Question 309

A landlord shares one uplink among tenant VDOMs without restricting customer-tagged VLANs. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Latency-sensitive flows improve under representative load while other business services remain functional.
  2. A controlled FortiGate HA failover leaves managed switches authorized and required client access functioning.
  3. Management connectivity is established across the supported intermediate network without losing segmentation or authentication assumptions.
  4. Two tenants can use the supported shared port without accidental cross-tenant broadcasts or privilege escalation.

Explanation

Correct Answer

D:

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:

Latency-sensitive flows improve under representative load while other business services remain functional. This result relates to Egress priority scheduling and congestion visibility, 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:

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

C:

Management connectivity is established across the supported intermediate network without losing segmentation or authentication assumptions. This result relates to FortiLink transport over nontrivial L2 or L3 paths, 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 310

A second floor switch is cabled through an undocumented uplink and never appears in managed FortiSwitch inventory. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes.
  2. Build FortiSwitch VLAN interfaces in the correct FortiLink context and assign ports through the managed switch controller.
  3. Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.
  4. Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles.
  5. The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function.

Explanation

Correct Answers

C:

Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization. The FortiGate-managed FortiSwitch stack is a managed L2 topology, not automatically a single chassis or universal VSF-like control plane. The paired action is: Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles. This is the diagnostic or verification half of the requested TWO-step pair.

D:

Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles. The FortiGate-managed FortiSwitch stack is a managed L2 topology, not automatically a single chassis or universal VSF-like control plane. Verify the action with: Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization. This is the configuration or remediation half of the requested TWO-step pair.

Incorrect Answers

A:

Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes. This step concerns Voice and data VLAN separation on shared access ports and is not part of the required paired solution. The correct action and evidence are: Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles. Together with: Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.

B:

Build FortiSwitch VLAN interfaces in the correct FortiLink context and assign ports through the managed switch controller. This step concerns FortiGate managed FortiSwitch VLAN interface placement and is not part of the required paired solution. The correct action and evidence are: Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles. Together with: Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.

E:

The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function. This step concerns FortiLink management interface provisioning and is not part of the required paired solution. The correct action and evidence are: Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles. Together with: Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.

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