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 48

Question 470

A phone and computer share one access port but the policy authenticates only the first observed MAC address. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure.
  2. Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links.
  3. Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols.
  4. Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof.

Explanation

Correct Answer

D:

Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof. A MAC address can be cloned; MAC authentication must be combined with appropriate segmentation and monitoring. Verify the action with: Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN.

Incorrect Answers

A:

Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure. This action is relevant to FortiGate VDOM-based FortiSwitch tenant assignment, not the controlling requirement in this case. A VDOM creates a separate policy and routing context; it does not by itself make a shared physical switch port safe for all tenants. The targeted response is: Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof.

B:

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: Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof.

C:

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: Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof.

Question 471

The configured FortiLink aggregate connects to a single switch but its split-interface setting does not match the topology. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests.
  2. Inspect RADIUS Filter-Id or downloadable ACL attribute, authenticated session state, installed hardware entries and ACL counters.
  3. Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.
  4. Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards.

Explanation

Correct Answer

C:

Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability. A FortiGate port not configured for FortiLink cannot assume managed-switch ownership from physical connection alone. The paired action is: Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch.

Incorrect Answers

A:

Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests. These observations are applicable to Multi-tenant change verification and rollback, but would not isolate the main failure first. The decisive evidence is: Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.

B:

Inspect RADIUS Filter-Id or downloadable ACL attribute, authenticated session state, installed hardware entries and ACL counters. These observations are applicable to DACL RADIUS attribute and per-session enforcement, but would not isolate the main failure first. The decisive evidence is: Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.

D:

Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards. These observations are applicable to MCLAG multichassis access redundancy, but would not isolate the main failure first. The decisive evidence is: Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.

Question 472

A relay receives mismatched Option 82 information and discards legitimate client renewals. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Use documented trusted DHCP-server lists or Option 82 information where supported to enforce authorized address assignment.
  2. A planned alternate link remains blocked and takes over predictably without a broadcast storm.
  3. Use supported dynamic ARP inspection with valid switch bindings to reject spoofed IP-MAC claims at untrusted edges.
  4. Inspect DHCP server permitted list, Option 82 insertion/trust state, relay path, client bindings and lease evidence.
  5. Inspect MAC table usage, configured learning limit, learned device count, port-security event and violation action.

Explanation

Correct Answers

A:

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.

D:

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.

Incorrect Answers

B:

A planned alternate link remains blocked and takes over predictably without a broadcast storm. This step concerns MSTP region consistency and designated root 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:

Use supported dynamic ARP inspection with valid switch bindings to reject spoofed IP-MAC claims at untrusted edges. This step concerns Dynamic ARP inspection with DHCP snooping bindings 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.

E:

Inspect MAC table usage, configured learning limit, learned device count, port-security event and violation action. This step concerns Port MAC learning-limit and violation controls 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 473

A campus extends two-tier managed switching across a narrow uplink and experiences unexpected bottlenecks. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure.
  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. Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs.

Explanation

Correct Answer

C:

Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards. A FortiGate controls each FortiSwitch through the managed Layer-2 topology, but downstream reachability depends on upstream FortiLink links. Verify the action with: Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.

Incorrect Answers

A:

Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure. This action is relevant to FortiGate VDOM-based FortiSwitch tenant assignment, not the controlling requirement in this case. A VDOM creates a separate policy and routing context; it does not by itself make a shared physical switch port safe for all tenants. The targeted response is: Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.

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: Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.

D:

Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs. This action is relevant to Stack failure isolation and switch-to-switch port roles, not the controlling requirement in this case. 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 targeted response is: Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.

Question 474

Two phones receive different QoS hints after being attached to ports using different LLDP profiles. 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. Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority.
  3. A capable handset reports the expected voice network policy and traffic uses the correct VLAN.
  4. The managed switch retains the intended controller-pushed policy after a controlled synchronization and restart.

Explanation

Correct Answer

C:

A capable handset reports the expected voice network policy and traffic uses the correct VLAN. LLDP-MED exchanges policy hints with compatible endpoints; it does not substitute for port membership and DHCP.

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: A capable handset reports the expected voice network policy and traffic uses the correct VLAN.

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: A capable handset reports the expected voice network policy and traffic uses the correct VLAN.

D:

The managed switch retains the intended controller-pushed policy after a controlled synchronization and restart. This result relates to Managed switch configuration synchronization, not the acceptance condition under test. The relevant result is: A capable handset reports the expected voice network policy and traffic uses the correct VLAN.

Question 475

Two distribution switches have different MST region revisions and flood after a redundant connection is added. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.
  2. Examine LLDP transmit state, port profile, neighbor TLVs, advertised VLAN and DSCP or 802.1p settings.
  3. Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards.
  4. Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port.

Explanation

Correct Answer

A:

Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters. Different MST configuration identifiers split regions even if switch ports are physically connected. The paired action is: Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy.

Incorrect Answers

B:

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 MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.

C:

Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards. These observations are applicable to MCLAG multichassis access redundancy, but would not isolate the main failure first. The decisive evidence is: Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.

D:

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: Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.

Question 476

A new guest VLAN works on one FortiSwitch but is omitted from the FortiLink interswitch path. 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. Inspect FortiLink management state, native/tagged VLANs, port membership, FortiGate interface and active firewall policy.
  3. Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.
  4. Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions.

Explanation

Correct Answer

B:

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

Incorrect Answers

A:

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 FortiLink management state, native/tagged VLANs, port membership, FortiGate interface and active firewall policy.

C:

Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path. These observations are applicable to Static route and default gateway validation, but would not isolate the main failure first. The decisive evidence is: Inspect FortiLink management state, native/tagged VLANs, port membership, FortiGate interface and active firewall policy.

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 FortiLink management state, native/tagged VLANs, port membership, FortiGate interface and active firewall policy.

Question 477

A manager wants all discovered switches automatically authorized even though the site uses untrusted wiring closets. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. The expected known switch becomes authorized and synchronizes without accepting an unrelated device.
  2. The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate.
  3. The intended switch appears in discovery after restoring the precise missing interface or transport prerequisite.
  4. Legitimate clients lease addresses while rogue DHCP servers connected to untrusted access ports cannot answer.

Explanation

Correct Answer

A:

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

B:

The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate. This result relates to FortiSwitch diagnostic commands and logs, not the acceptance condition under test. The relevant result is: The expected known switch becomes authorized and synchronizes without accepting an unrelated device.

C:

The intended switch appears in discovery after restoring the precise missing interface or transport prerequisite. This result relates to FortiLink discovery failure and physical uplink path, not the acceptance condition under test. The relevant result is: The expected known switch becomes authorized and synchronizes without accepting an unrelated device.

D:

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: The expected known switch becomes authorized and synchronizes without accepting an unrelated device.

Question 478

A new managed switch port allows link negotiation but users stay unauthenticated after a RADIUS server change. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Each customer's tagged traffic reaches only its assigned service context without S-VLAN collision.
  2. Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior.
  3. Verify that supported CoA or dynamic user security profiles are enforced on authenticated sessions under the deployed topology.
  4. Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.
  5. Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile.

Explanation

Correct Answers

B:

Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior. A physical link can be up while 802.1X blocks traffic; the switch is the authenticator, not the authentication server. Verify the action with: Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile. This is the configuration or remediation half of the requested TWO-step pair.

E:

Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile. A physical link can be up while 802.1X blocks traffic; the switch is the authenticator, not the authentication server. The paired action is: Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

A:

Each customer's tagged traffic reaches only its assigned service context without S-VLAN collision. This step concerns QinQ outer and inner VLAN tenant mapping and is not part of the required paired solution. The correct action and evidence are: Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior. Together with: Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile.

C:

Verify that supported CoA or dynamic user security profiles are enforced on authenticated sessions under the deployed topology. This step concerns RADIUS change of authorization and applied session policy and is not part of the required paired solution. The correct action and evidence are: Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior. Together with: Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile.

D:

Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path. This step concerns Static port ACL forwarding decisions and is not part of the required paired solution. The correct action and evidence are: Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior. Together with: Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile.

Question 479

A server sends untagged frames but its switch port expects only tagged frames and never learns the MAC in the intended VLAN. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Known unicast traffic reaches the correct access port while unknown traffic is confined to the intended VLAN.
  2. The analyzer receives the intended copies while production forwarding remains unchanged.
  3. Rapid MAC moves stop and normal forwarding returns with a verified alternate redundant path.
  4. Hosts can reach their intended SVI and authorized routed destinations without overlapping address space.

Explanation

Correct Answer

A:

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

B:

The analyzer receives the intended copies while production forwarding remains unchanged. This result relates to FortiSwitch port mirroring to network analyzer, not the acceptance condition under test. The relevant result is: Known unicast traffic reaches the correct access port while unknown traffic is confined to the intended VLAN.

C:

Rapid MAC moves stop and normal forwarding returns with a verified alternate redundant path. This result relates to STP incident recovery with MAC flap evidence, 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:

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.

Question 480

A managed switch loses FortiLink only after an active FortiGate HA failover. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Identify FortiLink failures caused by split-interface, HA, MCLAG peer or ISL mismatches before changing unrelated ports.
  2. Troubleshoot FortiLink discovery from physical and logical interface configuration through LLDP and management addressing.
  3. Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted.
  4. Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging.

Explanation

Correct Answer

A:

Identify FortiLink failures caused by split-interface, HA, MCLAG peer or ISL mismatches before changing unrelated ports. FortiGate HA, FortiLink split-interface and FortiSwitch MCLAG have distinct failover behaviors that cannot be inferred from link LEDs alone. Verify the action with: Inspect FortiGate HA active member, FortiLink aggregate state, ISL, MCLAG peer link, standby path and STP roles.

Incorrect Answers

B:

Troubleshoot FortiLink discovery from physical and logical interface configuration through LLDP and management addressing. This action is relevant to FortiLink discovery failure and physical uplink path, not the controlling requirement in this case. A green Ethernet link is necessary for many paths but does not prove the FortiLink management protocol or discovery is working. The targeted response is: Identify FortiLink failures caused by split-interface, HA, MCLAG peer or ISL mismatches before changing unrelated ports.

C:

Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted. This action is relevant to FortiGate one-arm sniffer across managed switching, not the controlling requirement in this case. Sniffer placement determines visibility; absence of a packet at one observation point does not prove no packet existed elsewhere. The targeted response is: Identify FortiLink failures caused by split-interface, HA, MCLAG peer or ISL mismatches before changing unrelated ports.

D:

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: Identify FortiLink failures caused by split-interface, HA, MCLAG peer or ISL mismatches before changing unrelated ports.

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