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 77

Question 760

A team claims an ACL encrypts traffic instead of recognizing its supported forwarding/filtering actions. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Only intended traffic is accepted or rejected at the switch while allowed application sessions remain functional.
  2. The authenticated client receives the intended per-user or per-port restrictions and unauthenticated hosts do not inherit them.
  3. Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy.
  4. The correct link establishes at expected negotiated rate without recurring loss-of-signal or CRC errors.

Explanation

Correct Answer

A:

Only intended traffic is accepted or rejected at the switch while allowed application sessions remain functional. Switch ACLs and FortiGate firewall policies operate at different enforcement points; a deny on one does not prove the other applied.

Incorrect Answers

B:

The authenticated client receives the intended per-user or per-port restrictions and unauthenticated hosts do not inherit them. This result relates to DACL RADIUS attribute and per-session enforcement, not the acceptance condition under test. The relevant result is: Only intended traffic is accepted or rejected at the switch while allowed application sessions remain functional.

C:

Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy. This result relates to FortiSwitch 802.1X port-based authentication, not the acceptance condition under test. The relevant result is: Only intended traffic is accepted or rejected at the switch while allowed application sessions remain functional.

D:

The correct link establishes at expected negotiated rate without recurring loss-of-signal or CRC errors. This result relates to Optic compatibility and laser diagnostic evidence, not the acceptance condition under test. The relevant result is: Only intended traffic is accepted or rejected at the switch while allowed application sessions remain functional.

Question 761

An automated branch rollout fails because its bootstrap port sits on a VLAN that cannot contact the controller. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.
  2. Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure.
  3. Apply supported egress CoS queue policy to reduce latency under congestion without starving other required traffic.
  4. Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure.

Explanation

Correct Answer

B:

Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure. Zero-touch deployment works only when the necessary discovery path and identity checks function; a link LED is insufficient. Verify the action with: Inspect factory-default mode, DHCP or discovery exchange, upstream native VLAN, FortiLink enablement, NTP and controller authorization.

Incorrect Answers

A:

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

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

D:

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

Question 762

An approved static-IP server is blocked because its switch port lacks a binding entry after enabling source guard. 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. Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters.
  3. Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet.
  4. Inspect MAC table usage, configured learning limit, learned device count, port-security event and violation action.

Explanation

Correct Answer

C:

Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet. Source guard is an ingress source-binding check, not a full replacement for routed firewall policies or endpoint security. The paired action is: Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings.

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: Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet.

B:

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: Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet.

D:

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: Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet.

Question 763

One managed port uses a stale security profile because an override did not synchronize from FortiGate. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Use supported intra-VLAN traffic controls when clients in the same broadcast domain must not communicate directly.
  2. Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence.
  3. All subtending managed switches remain discoverable and user service survives expected single-link failures where supported.
  4. Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.
  5. Check switch quarantine status, ACL/security profile, allowed remediation services, NAC event and release criteria.

Explanation

Correct Answers

B:

Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence. A named security profile sitting in configuration is not proof that it was applied to the intended hardware port. Verify the action with: Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls. This is the configuration or remediation half of the requested TWO-step pair.

D:

Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls. A named security profile sitting in configuration is not proof that it was applied to the intended hardware port. The paired action is: Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

A:

Use supported intra-VLAN traffic controls when clients in the same broadcast domain must not communicate directly. This step concerns Intra-VLAN blocking and isolation boundaries and is not part of the required paired solution. The correct action and evidence are: Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence. Together with: Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.

C:

All subtending managed switches remain discoverable and user service survives expected single-link failures where supported. This step concerns FortiSwitch multi-tier managed topology and is not part of the required paired solution. The correct action and evidence are: Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence. Together with: Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.

E:

Check switch quarantine status, ACL/security profile, allowed remediation services, NAC event and release criteria. This step concerns VLAN security policy and quarantine actions and is not part of the required paired solution. The correct action and evidence are: Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence. Together with: Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.

Question 764

When a distribution uplink fails, three downstream switches disappear from the FortiGate controller together. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters.
  2. Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events.
  3. Inspect DHCP server permitted list, Option 82 insertion/trust state, relay path, client bindings and lease evidence.
  4. Inspect FortiLink interface type, split-interface setting, connected peer count, STP state and active management path.

Explanation

Correct Answer

B:

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

Incorrect Answers

A:

Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters. These observations are applicable to LACP negotiation on FortiSwitch FortiLink trunks, but would not isolate the main failure first. The decisive evidence is: Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events.

C:

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: Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events.

D:

Inspect FortiLink interface type, split-interface setting, connected peer count, STP state and active management path. These observations are applicable to FortiLink split-interface and standby path design, but would not isolate the main failure first. The decisive evidence is: Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events.

Question 765

A voice rollout advertises the new voice VLAN but its DHCP scope is still unreachable from the phone segment. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment.
  2. Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes.
  3. Trace MAC-learning and forwarding across the precise VLAN and repair only missing approved membership.
  4. Inspect FortiLink interface type, split-interface setting, connected peer count, STP state and active management path.
  5. The suspect device is restricted without interrupting unrelated tenants and can be restored after review.

Explanation

Correct Answers

A:

Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment. Voice tagging is not secured merely because its VLAN ID differs from the workstation's native VLAN. Verify the action with: Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes. This is the configuration or remediation half of the requested TWO-step pair.

B:

Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes. Voice tagging is not secured merely because its VLAN ID differs from the workstation's native VLAN. The paired action is: Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

C:

Trace MAC-learning and forwarding across the precise VLAN and repair only missing approved membership. This step concerns VLAN access isolation and troubleshooting of membership and is not part of the required paired solution. The correct action and evidence are: Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment. Together with: Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes.

D:

Inspect FortiLink interface type, split-interface setting, connected peer count, STP state and active management path. This step concerns FortiLink split-interface and standby path design and is not part of the required paired solution. The correct action and evidence are: Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment. Together with: Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes.

E:

The suspect device is restricted without interrupting unrelated tenants and can be restored after review. This step concerns VLAN security policy and quarantine actions and is not part of the required paired solution. The correct action and evidence are: Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment. Together with: Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes.

Question 766

A dynamic port-policy rule intended for printers matches all newly connected laptops due to a broad condition. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Known printers and IoT devices enter their restricted VLANs while unknown endpoints have no excessive access.
  2. Approved legacy devices gain only restricted services while unknown or spoofed MAC addresses remain constrained.
  3. An unexpected additional device is restricted or signaled without knocking out approved business equipment.
  4. The analyzer receives the intended copies while production forwarding remains unchanged.

Explanation

Correct Answer

A:

Known printers and IoT devices enter their restricted VLANs while unknown endpoints have no excessive access. NAC assignment relies on reliable detection and a defined precedence; a class label is not a substitute for switch-port policy.

Incorrect Answers

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: Known printers and IoT devices enter their restricted VLANs while unknown endpoints have no excessive access.

C:

An unexpected additional device is restricted or signaled without knocking out approved business equipment. This result relates to Port MAC learning-limit and violation controls, not the acceptance condition under test. The relevant result is: Known printers and IoT devices enter their restricted VLANs while unknown endpoints have no excessive access.

D:

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 printers and IoT devices enter their restricted VLANs while unknown endpoints have no excessive access.

Question 767

A data closet trunk sends untagged management frames into a partner's tagged-only management VLAN. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters.
  2. Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.
  3. Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
  4. Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path.

Explanation

Correct Answer

B:

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

Incorrect Answers

A:

Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters. These observations are applicable to LACP negotiation on FortiSwitch FortiLink trunks, but would not isolate the main failure first. The decisive evidence is: Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.

C:

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: Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.

D:

Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path. These observations are applicable to FortiGate managed FortiSwitch VLAN interface placement, but would not isolate the main failure first. The decisive evidence is: Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.

Question 768

A team posts complete captures containing authentication tokens into a public support thread. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Management connectivity is established across the supported intermediate network without losing segmentation or authentication assumptions.
  2. Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics.
  3. Inspect FortiGate HA active member, FortiLink aggregate state, ISL, MCLAG peer link, standby path and STP roles.
  4. Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices.
  5. Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions.

Explanation

Correct Answers

B:

Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics. A packet-capture tool may record payloads and credentials, so evidence handling is part of the network security process. Verify the action with: Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions. This is the configuration or remediation half of the requested TWO-step pair.

E:

Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions. A packet-capture tool may record payloads and credentials, so evidence handling is part of the network security process. The paired action is: Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

A:

Management connectivity is established across the supported intermediate network without losing segmentation or authentication assumptions. This step concerns FortiLink transport over nontrivial L2 or L3 paths and is not part of the required paired solution. The correct action and evidence are: Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics. Together with: Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions.

C:

Inspect FortiGate HA active member, FortiLink aggregate state, ISL, MCLAG peer link, standby path and STP roles. This step concerns FortiLink HA and MCLAG topology faults and is not part of the required paired solution. The correct action and evidence are: Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics. Together with: Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions.

D:

Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices. This step concerns Controller authorization and pending-switch state and is not part of the required paired solution. The correct action and evidence are: Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics. Together with: Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions.

Question 769

An approved static-IP server is blocked because its switch port lacks a binding entry after enabling source guard. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols.
  2. Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers.
  3. Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings.
  4. The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate.
  5. Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet.

Explanation

Correct Answers

C:

Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings. Source guard is an ingress source-binding check, not a full replacement for routed firewall policies or endpoint security. Verify the action with: Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet. This is the configuration or remediation half of the requested TWO-step pair.

E:

Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet. Source guard is an ingress source-binding check, not a full replacement for routed firewall policies or endpoint security. The paired action is: Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

A:

Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols. This step concerns Storm-control thresholds and broadcast containment and is not part of the required paired solution. The correct action and evidence are: Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings. Together with: Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet.

B:

Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers. This step concerns DHCP snooping trust-boundary enforcement and is not part of the required paired solution. The correct action and evidence are: Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings. Together with: Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet.

D:

The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate. This step concerns FortiSwitch diagnostic commands and logs and is not part of the required paired solution. The correct action and evidence are: Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings. Together with: Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet.

Question 770

An administrator enables DHCP snooping without checking whether the expected relay path is exempted correctly. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links.
  2. Use documented trusted DHCP-server lists or Option 82 information where supported to enforce authorized address assignment.
  3. Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery.
  4. Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes.

Explanation

Correct Answer

A:

Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links. Trusting every port defeats DHCP snooping and wrongly distrusting the server uplink may suppress all leases. Verify the action with: Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers.

Incorrect Answers

B:

Use documented trusted DHCP-server lists or Option 82 information where supported to enforce authorized address assignment. This action is relevant to DHCP server allowlist and Option 82 validation, not the controlling requirement in this case. DHCP server allowlist and Option 82 metadata provide additional context but cannot correct a failed VLAN or missing upstream relay. The targeted response is: Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links.

C:

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: Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links.

D:

Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes. This action is relevant to NAC dynamic port policy device classification, not the controlling requirement in this case. NAC assignment relies on reliable detection and a defined precedence; a class label is not a substitute for switch-port policy. The targeted response is: Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links.

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