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 24

Question 230

An organization attempts to push an IPv6 DACL policy even though the supported FortiSwitch release documents only IPv4 DACL support. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Spoofed ARP replies are dropped while legitimate endpoints maintain gateway ARP resolution.
  2. Approved legacy devices gain only restricted services while unknown or spoofed MAC addresses remain constrained.
  3. The authenticated client receives the intended per-user or per-port restrictions and unauthenticated hosts do not inherit them.
  4. Phones and access points receive stable allocated power while redundant PSU and priority policies remain within budget.

Explanation

Correct Answer

C:

The authenticated client receives the intended per-user or per-port restrictions and unauthenticated hosts do not inherit them. DACLs install after successful authorization and documented release limits apply; a RADIUS response alone is not proof of forwarding enforcement.

Incorrect Answers

A:

Spoofed ARP replies are dropped while legitimate endpoints maintain gateway ARP resolution. This result relates to Dynamic ARP inspection with DHCP snooping bindings, not the acceptance condition under test. The relevant result is: The authenticated client receives the intended per-user or per-port restrictions and unauthenticated hosts do not inherit them.

B:

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: The authenticated client receives the intended per-user or per-port restrictions and unauthenticated hosts do not inherit them.

D:

Phones and access points receive stable allocated power while redundant PSU and priority policies remain within budget. This result relates to PoE and LLDP-MED endpoint power coordination, not the acceptance condition under test. The relevant result is: The authenticated client receives the intended per-user or per-port restrictions and unauthenticated hosts do not inherit them.

Question 231

A gigabit analyzer drops mirrored frames from multiple saturated 10G sources and the engineer misreads the capture as true link loss. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
  2. Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.
  3. Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings.
  4. Expected members join the trunk and survive a member disconnect without loops or silent black holes.
  5. Investigate managed switch offline or configuration mismatch after firmware upgrade or controller resynchronization using both endpoints.

Explanation

Correct Answers

B:

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. This is the diagnostic or verification half of the requested TWO-step pair.

C:

Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings. A mirrored stream is passive evidence and can be incomplete if analyzer bandwidth is lower than the observed traffic. Verify the action with: Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics. This is the configuration or remediation half of the requested TWO-step pair.

Incorrect Answers

A:

Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map. This step concerns LLDP and MAC forwarding table extraction and is not part of the required paired solution. The correct action and evidence are: Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings. Together with: Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.

D:

Expected members join the trunk and survive a member disconnect without loops or silent black holes. This step concerns Link aggregation and port error recovery and is not part of the required paired solution. The correct action and evidence are: Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings. Together with: Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.

E:

Investigate managed switch offline or configuration mismatch after firmware upgrade or controller resynchronization using both endpoints. This step concerns FortiLink synchronization and upgrade troubleshooting and is not part of the required paired solution. The correct action and evidence are: Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings. Together with: Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.

Question 232

A branch begins firmware rollout on every downstream switch without checking supported controller compatibility. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch.
  2. Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing.
  3. Spoofed ARP replies are dropped while legitimate endpoints maintain gateway ARP resolution.
  4. Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
  5. Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology.

Explanation

Correct Answers

B:

Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing. A successful image upload does not prove switch operation or controller compatibility after reboot. The paired action is: Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology. This is the diagnostic or verification half of the requested TWO-step pair.

E:

Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology. A successful image upload does not prove switch operation or controller compatibility after reboot. Verify the action with: Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing. This is the configuration or remediation half of the requested TWO-step pair.

Incorrect Answers

A:

Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch. This step concerns FortiLink management interface provisioning and is not part of the required paired solution. The correct action and evidence are: Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology. Together with: Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing.

C:

Spoofed ARP replies are dropped while legitimate endpoints maintain gateway ARP resolution. 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: Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology. Together with: Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing.

D:

Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility. This step concerns Discovered versus authorized FortiSwitch state and is not part of the required paired solution. The correct action and evidence are: Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology. Together with: Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing.

Question 233

A branch telephone gets a guest address because its access port native VLAN was changed during replacement. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Enable supported BPDU guard only on true edge/client ports, and restore blocked ports after identifying unauthorized switching.
  2. Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover.
  3. Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope.
  4. Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment.

Explanation

Correct Answer

B:

Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover. Native VLAN handling and tagged VLAN membership are different controls; a working physical link does not validate VLAN carriage. Verify the action with: Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.

Incorrect Answers

A:

Enable supported BPDU guard only on true edge/client ports, and restore blocked ports after identifying unauthorized switching. This action is relevant to BPDU guard on endpoint-facing ports, not the controlling requirement in this case. BPDU guard can disable an intended trunk if incorrectly treated as an end-station port. The targeted response is: Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover.

C:

Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope. This action is relevant to SNMP and sFlow monitoring configuration, not the controlling requirement in this case. Flow samples are estimates and counters vary by port; collecting telemetry cannot replace a controlled packet capture when headers are needed. The targeted response is: Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover.

D:

Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment. This action is relevant to Voice and data VLAN separation on shared access ports, not the controlling requirement in this case. Voice tagging is not secured merely because its VLAN ID differs from the workstation's native VLAN. The targeted response is: Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover.

Question 234

An administrator installs an ACL on the wrong ingress switch port and sees no change in affected traffic. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect RADIUS Filter-Id or downloadable ACL attribute, authenticated session state, installed hardware entries and ACL counters.
  2. Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
  3. Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.
  4. Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.

Explanation

Correct Answer

C:

Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path. Switch ACLs and FortiGate firewall policies operate at different enforcement points; a deny on one does not prove the other applied. The paired action is: Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence.

Incorrect Answers

A:

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: Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.

B:

Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map. These observations are applicable to LLDP and MAC forwarding table extraction, but would not isolate the main failure first. The decisive evidence is: Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.

D:

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: Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.

Question 235

A second floor switch is cabled through an undocumented uplink and never appears in managed FortiSwitch inventory. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters.
  2. Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events.
  3. Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.
  4. Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards.

Explanation

Correct Answer

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.

Incorrect Answers

A:

Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters. These observations are applicable to Switch port speed and duplex commissioning, but would not isolate the main failure first. The decisive evidence is: Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.

B:

Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events. These observations are applicable to PoE and LLDP-MED endpoint power coordination, but would not isolate the main failure first. The decisive evidence is: Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.

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 uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.

Question 236

A downstream switch advertises a superior bridge ID and tries to become campus root unexpectedly. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Repair LACP member settings and physical port errors independently before increasing aggregate traffic.
  2. Change managed switch VLAN membership through the FortiGate controller and verify the installed configuration stays consistent.
  3. Apply appropriate STP root or loop protection to preserve topology while analyzing missing BPDUs and unexpected root claims.
  4. Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests.

Explanation

Correct Answer

C:

Apply appropriate STP root or loop protection to preserve topology while analyzing missing BPDUs and unexpected root claims. Root guard and loop guard mitigate different failure cases and should not be enabled indiscriminately on every uplink. Verify the action with: Inspect guard role, BPDU reception, root-ID history, STP port role and loop-condition log.

Incorrect Answers

A:

Repair LACP member settings and physical port errors independently before increasing aggregate traffic. This action is relevant to Link aggregation and port error recovery, not the controlling requirement in this case. One healthy physical link is not proof an aggregate has balanced traffic or that the peer LACP policy matches. The targeted response is: Apply appropriate STP root or loop protection to preserve topology while analyzing missing BPDUs and unexpected root claims.

B:

Change managed switch VLAN membership through the FortiGate controller and verify the installed configuration stays consistent. This action is relevant to VLAN configuration persistence and drift control, not the controlling requirement in this case. Directly editing a FortiLink-managed switch can cause drift because FortiGate remains the controller of record. The targeted response is: Apply appropriate STP root or loop protection to preserve topology while analyzing missing BPDUs and unexpected root claims.

D:

Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests. This action is relevant to HA FortiGate pair managing switch topology, not the controlling requirement in this case. FortiGate HA design and FortiSwitch stacking/MCLAG are separate mechanisms; their failure paths must both be evaluated. The targeted response is: Apply appropriate STP root or loop protection to preserve topology while analyzing missing BPDUs and unexpected root claims.

Question 237

One access port has increasing CRC errors while its neighbor carries clean traffic under similar load. 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. Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery.
  3. Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location.
  4. Use documented peer-group and downstream trunk configuration for MCLAG rather than creating ad hoc parallel Ethernet links.

Explanation

Correct Answer

C:

Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location. A port-up indicator or one successful ping is not proof that a congested or errored uplink is healthy. Verify the action with: Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps.

Incorrect Answers

A:

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: Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location.

B:

Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery. This action is relevant to Config backup and firmware inventory evidence, not the controlling requirement in this case. Backups require correct model/version and an actual restore procedure; a saved file name is not proof a recovered switch will work. The targeted response is: Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location.

D:

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: Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location.

Question 238

A cabinet with many cameras exceeds its switch PoE watt budget although enough physical ports exist. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links.
  2. Verify model-specific PoE class, total switch power budget and per-port policy before enabling new powered devices.
  3. Repair LACP member settings and physical port errors independently before increasing aggregate traffic.
  4. Verify that supported CoA or dynamic user security profiles are enforced on authenticated sessions under the deployed topology.

Explanation

Correct Answer

B:

Verify model-specific PoE class, total switch power budget and per-port policy before enabling new powered devices. Not every FortiSwitch model or port supports identical PoE allocation or every attached device's peak draw. Verify the action with: Inspect power supply reserve, current draw, negotiated PoE class, priority shedding and port events.

Incorrect Answers

A:

Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links. This action is relevant to RPVST and supported STP mode interoperability, not the controlling requirement in this case. An STP mode change can change per-VLAN convergence behavior even if existing links remain physically up. The targeted response is: Verify model-specific PoE class, total switch power budget and per-port policy before enabling new powered devices.

C:

Repair LACP member settings and physical port errors independently before increasing aggregate traffic. This action is relevant to Link aggregation and port error recovery, not the controlling requirement in this case. One healthy physical link is not proof an aggregate has balanced traffic or that the peer LACP policy matches. The targeted response is: Verify model-specific PoE class, total switch power budget and per-port policy before enabling new powered devices.

D:

Verify that supported CoA or dynamic user security profiles are enforced on authenticated sessions under the deployed topology. This action is relevant to RADIUS change of authorization and applied session policy, not the controlling requirement in this case. RADIUS authentication success is not proof that a downloadable ACL or CoA update was enforced; some modes have documented conditions. The targeted response is: Verify model-specific PoE class, total switch power budget and per-port policy before enabling new powered devices.

Question 239

A managed switch's controller connection stays up while a trunk change removes the voice VLAN. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Spoofed ARP replies are dropped while legitimate endpoints maintain gateway ARP resolution.
  2. The expected known switch becomes authorized and synchronizes without accepting an unrelated device.
  3. Managed status remains healthy and user traffic uses only its intended FortiLink-carried VLANs.
  4. FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy.

Explanation

Correct Answer

C:

Managed status remains healthy and user traffic uses only its intended FortiLink-carried VLANs. FortiLink transports management and data; a successful controller heartbeat does not guarantee a user VLAN or firewall session is permitted.

Incorrect Answers

A:

Spoofed ARP replies are dropped while legitimate endpoints maintain gateway ARP resolution. This result relates to Dynamic ARP inspection with DHCP snooping bindings, not the acceptance condition under test. The relevant result is: Managed status remains healthy and user traffic uses only its intended FortiLink-carried VLANs.

B:

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

D:

FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy. This result relates to FortiGate one-arm sniffer across managed switching, not the acceptance condition under test. The relevant result is: Managed status remains healthy and user traffic uses only its intended FortiLink-carried VLANs.

Question 240

A high-power access point boots but shuts down once its additional radio activates. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Critical telephony and wireless endpoints receive continuous intended power without overrunning PSU capacity.
  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. FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy.

Explanation

Correct Answer

A:

Critical telephony and wireless endpoints receive continuous intended power without overrunning PSU capacity. Not every FortiSwitch model or port supports identical PoE allocation or every attached device's peak draw.

Incorrect Answers

B:

Known unicast traffic reaches the correct access port while unknown traffic is confined to the intended VLAN. This result relates to Layer 2 MAC-learning and forwarding decisions, not the acceptance condition under test. The relevant result is: Critical telephony and wireless endpoints receive continuous intended power without overrunning PSU capacity.

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: Critical telephony and wireless endpoints receive continuous intended power without overrunning PSU capacity.

D:

FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy. This result relates to FortiGate one-arm sniffer across managed switching, not the acceptance condition under test. The relevant result is: Critical telephony and wireless endpoints receive continuous intended power without overrunning PSU capacity.

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