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 51

Question 500

An administrator installs an ACL on the wrong ingress switch port and sees no change in affected traffic. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence.
  2. Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.
  3. Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.
  4. Rapid MAC moves stop and normal forwarding returns with a verified alternate redundant path.
  5. Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints.

Explanation

Correct Answers

A:

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

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

Incorrect Answers

B:

Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls. This step concerns FortiSwitch security profile application and precedence and is not part of the required paired solution. The correct action and evidence are: Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence. Together with: Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.

D:

Rapid MAC moves stop and normal forwarding returns with a verified alternate redundant path. This step concerns STP incident recovery with MAC flap evidence and is not part of the required paired solution. The correct action and evidence are: Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence. Together with: Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.

E:

Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints. This step concerns DACL RADIUS attribute and per-session enforcement and is not part of the required paired solution. The correct action and evidence are: Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence. Together with: Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.

Question 501

A newly patched uplink reports an unexpected LLDP peer from a separate customer zone. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Rapid MAC moves stop and normal forwarding returns with a verified alternate redundant path.
  2. Managed status remains healthy and user traffic uses only its intended FortiLink-carried VLANs.
  3. A moved device is traced to its current approved port and incorrect cross-connection is identified.
  4. A trace shows the expected ingress/egress control packets without collecting unrelated sensitive network traffic.

Explanation

Correct Answer

C:

A moved device is traced to its current approved port and incorrect cross-connection is identified. LLDP provides adjacent-device identity, while MAC learning maps forwarding; neither is a full routed trace by itself.

Incorrect Answers

A:

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: A moved device is traced to its current approved port and incorrect cross-connection is identified.

B:

Managed status remains healthy and user traffic uses only its intended FortiLink-carried VLANs. This result relates to FortiLink control and client VLAN transport separation, not the acceptance condition under test. The relevant result is: A moved device is traced to its current approved port and incorrect cross-connection is identified.

D:

A trace shows the expected ingress/egress control packets without collecting unrelated sensitive network traffic. This result relates to FortiSwitch local packet-capture profile and filters, not the acceptance condition under test. The relevant result is: A moved device is traced to its current approved port and incorrect cross-connection is identified.

Question 502

A technician changes a phone port to a trunk but fails to restrict unrelated management VLANs. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover.
  2. Troubleshooting evidence is sufficient to establish the fault without exporting unnecessary private communications.
  3. Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment.
  4. Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes.
  5. Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.

Explanation

Correct Answers

C:

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.

D:

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

A:

Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover. This step concerns FortiSwitch native VLAN versus allowed VLANs 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.

B:

Troubleshooting evidence is sufficient to establish the fault without exporting unnecessary private communications. This step concerns Capture and confidentiality limits in incident response 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:

Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization. This step concerns FortiLink ISL auto-discovery and stack cabling 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 503

Two MCLAG peers disagree on allowed client VLANs and the same client reaches different gateways depending on active link. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.
  2. Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology.
  3. Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware.
  4. Inspect FortiLink interface type, split-interface setting, connected peer count, STP state and active management path.

Explanation

Correct Answer

B:

Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology. MCLAG redundancy depends on supported peer-link and aggregate design; two cables alone do not constitute working multichassis aggregation. The paired action is: Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles.

Incorrect Answers

A:

Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization. These observations are applicable to FortiLink ISL auto-discovery and stack cabling, but would not isolate the main failure first. The decisive evidence is: Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology.

C:

Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware. These observations are applicable to FortiLink transport over nontrivial L2 or L3 paths, but would not isolate the main failure first. The decisive evidence is: Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology.

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: Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology.

Question 504

A long full-packet trace fills the device RAM disk and discards the earliest evidence during an incident. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Inspect FortiLink management state, native/tagged VLANs, port membership, FortiGate interface and active firewall policy.
  2. Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames.
  3. Runaway flooding is contained without blocking legitimate broadcast-based onboarding or multicast subscribers.
  4. Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted.
  5. Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers.

Explanation

Correct Answers

B:

Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames. Packet captures are interface and filter scoped, and platform buffer limits differ; a capture file is not proof of all traffic on every switch port. Verify the action with: Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers. This is the configuration or remediation half of the requested TWO-step pair.

E:

Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers. Packet captures are interface and filter scoped, and platform buffer limits differ; a capture file is not proof of all traffic on every switch port. The paired action is: Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

A:

Inspect FortiLink management state, native/tagged VLANs, port membership, FortiGate interface and active firewall policy. This step concerns FortiLink control and client VLAN transport separation and is not part of the required paired solution. The correct action and evidence are: Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames. Together with: Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers.

C:

Runaway flooding is contained without blocking legitimate broadcast-based onboarding or multicast subscribers. This step concerns Storm-control thresholds and broadcast containment and is not part of the required paired solution. The correct action and evidence are: Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames. Together with: Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers.

D:

Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted. This step concerns FortiGate one-arm sniffer across managed switching and is not part of the required paired solution. The correct action and evidence are: Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames. Together with: Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers.

Question 505

A mispatched access switch creates a broadcast storm that saturates multiple closets. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.
  2. Both ends connect at compatible rates with stable errors and required throughput.
  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.
  5. Inspect frame-rate counters by class, threshold configuration, affected VLANs and protocol health under controlled load.

Explanation

Correct Answers

C:

Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols. Overaggressive storm control can break DHCP, ARP or group discovery even when physical links remain healthy. Verify the action with: Inspect frame-rate counters by class, threshold configuration, affected VLANs and protocol health under controlled load. This is the configuration or remediation half of the requested TWO-step pair.

E:

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

Incorrect Answers

A:

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: Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols. Together with: Inspect frame-rate counters by class, threshold configuration, affected VLANs and protocol health under controlled load.

B:

Both ends connect at compatible rates with stable errors and required throughput. This step concerns Switch port speed and duplex commissioning and is not part of the required paired solution. The correct action and evidence are: Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols. Together with: Inspect frame-rate counters by class, threshold configuration, affected VLANs and protocol health under controlled load.

D:

Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof. This step concerns MAC-based authentication and restricted legacy devices and is not part of the required paired solution. The correct action and evidence are: Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols. Together with: Inspect frame-rate counters by class, threshold configuration, affected VLANs and protocol health under controlled load.

Question 506

A redundant aggregation port changes from discarding to forwarding before the expected blocked port transitions safely. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Every relevant VLAN converges without loops and redundant paths unblock only when needed.
  2. Rapid MAC moves stop and normal forwarding returns with a verified alternate redundant path.
  3. Members receive subscribed streams while unsubscribed access ports are not flooded unnecessarily.
  4. Known printers and IoT devices enter their restricted VLANs while unknown endpoints have no excessive access.

Explanation

Correct Answer

B:

Rapid MAC moves stop and normal forwarding returns with a verified alternate redundant path. Packet loss during a bridging loop can coexist with clean optical counters, so L1-only diagnostics miss the root cause.

Incorrect Answers

A:

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: Rapid MAC moves stop and normal forwarding returns with a verified alternate redundant path.

C:

Members receive subscribed streams while unsubscribed access ports are not flooded unnecessarily. This result relates to IGMP snooping and multicast receivers, not the acceptance condition under test. The relevant result is: Rapid MAC moves stop and normal forwarding returns with a verified alternate redundant path.

D:

Known printers and IoT devices enter their restricted VLANs while unknown endpoints have no excessive access. This result relates to NAC dynamic port policy device classification, not the acceptance condition under test. The relevant result is: Rapid MAC moves stop and normal forwarding returns with a verified alternate redundant path.

Question 507

A cabinet with many cameras exceeds its switch PoE watt budget although enough physical ports exist. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Both ends connect at compatible rates with stable errors and required throughput.
  2. The impacted client can communicate on the permitted VLAN while unrelated tenant or guest VLANs remain separated.
  3. Critical telephony and wireless endpoints receive continuous intended power without overrunning PSU capacity.
  4. A tenant reaches only its approved VDOM resources and does not inherit another tenant's policies.

Explanation

Correct Answer

C:

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

A:

Both ends connect at compatible rates with stable errors and required throughput. This result relates to Switch port speed and duplex commissioning, not the acceptance condition under test. The relevant result is: Critical telephony and wireless endpoints receive continuous intended power without overrunning PSU capacity.

B:

The impacted client can communicate on the permitted VLAN while unrelated tenant or guest VLANs remain separated. This result relates to VLAN access isolation and troubleshooting of membership, not the acceptance condition under test. The relevant result is: Critical telephony and wireless endpoints receive continuous intended power without overrunning PSU capacity.

D:

A tenant reaches only its approved VDOM resources and does not inherit another tenant's policies. This result relates to FortiGate VDOM-based FortiSwitch tenant assignment, not the acceptance condition under test. The relevant result is: Critical telephony and wireless endpoints receive continuous intended power without overrunning PSU capacity.

Question 508

When a distribution uplink fails, three downstream switches disappear from the FortiGate controller together. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Routes and interfaces are configured at the appropriate control plane and persist after synchronization or reboot.
  2. All expected child interfaces enumerate at supported speeds without disrupting unrelated uplinks.
  3. The failed ISL or switch is isolated and recovered with all unaffected downstream switches remaining correctly managed.
  4. The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function.

Explanation

Correct Answer

C:

The failed ISL or switch is isolated and recovered with all unaffected downstream switches remaining correctly managed. A missing switch in a FortiLink managed chain may be caused by the upstream ISL even if its access ports still carry local traffic.

Incorrect Answers

A:

Routes and interfaces are configured at the appropriate control plane and persist after synchronization or reboot. This result relates to FortiSwitch standalone versus FortiLink managed L3 ownership, not the acceptance condition under test. The relevant result is: The failed ISL or switch is isolated and recovered with all unaffected downstream switches remaining correctly managed.

B:

All expected child interfaces enumerate at supported speeds without disrupting unrelated uplinks. This result relates to FortiSwitch split port breakout mode, not the acceptance condition under test. The relevant result is: The failed ISL or switch is isolated and recovered with all unaffected downstream switches remaining correctly managed.

D:

The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function. This result relates to FortiLink management interface provisioning, not the acceptance condition under test. The relevant result is: The failed ISL or switch is isolated and recovered with all unaffected downstream switches remaining correctly managed.

Question 509

A direct switch connection works until the FortiGate port is repurposed into another software-switch aggregate. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end.
  2. Accidental downstream switches are contained without disabling legitimate uplinks that should exchange BPDUs.
  3. Inspect FortiLink mode, physical or aggregate link state, switch authorization, VLAN interfaces and test-client path.
  4. Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards.
  5. Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces.

Explanation

Correct Answers

C:

Inspect FortiLink mode, physical or aggregate link state, switch authorization, VLAN interfaces and test-client path. FortiLink carries management and data traffic; a valid management handshake does not prove every user VLAN is forwarded. The paired action is: Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces. This is the diagnostic or verification half of the requested TWO-step pair.

E:

Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces. FortiLink carries management and data traffic; a valid management handshake does not prove every user VLAN is forwarded. Verify the action with: Inspect FortiLink mode, physical or aggregate link state, switch authorization, VLAN interfaces and test-client path. This is the configuration or remediation half of the requested TWO-step pair.

Incorrect Answers

A:

Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end. 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 a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces. Together with: Inspect FortiLink mode, physical or aggregate link state, switch authorization, VLAN interfaces and test-client path.

B:

Accidental downstream switches are contained without disabling legitimate uplinks that should exchange BPDUs. 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 a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces. Together with: Inspect FortiLink mode, physical or aggregate link state, switch authorization, VLAN interfaces and test-client path.

D:

Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards. This step concerns MCLAG multichassis access redundancy and is not part of the required paired solution. The correct action and evidence are: Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces. Together with: Inspect FortiLink mode, physical or aggregate link state, switch authorization, VLAN interfaces and test-client path.

Question 510

A trunk member reports no traffic despite all LACP member LEDs appearing green. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Verify FortiLink management status and user VLAN reachability independently when a switch is authorized but clients fail.
  2. Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices.
  3. Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location.
  4. Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover.

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:

Verify FortiLink management status and user VLAN reachability independently when a switch is authorized but clients fail. This action is relevant to FortiLink control and client VLAN transport separation, not the controlling requirement in this case. FortiLink transports management and data; a successful controller heartbeat does not guarantee a user VLAN or firewall session is permitted. 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:

Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices. This action is relevant to Controller authorization and pending-switch state, not the controlling requirement in this case. Authorizing a switch is an administrative trust step; pending switch state is not evidence of a routing failure. The targeted response is: Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location.

D:

Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover. This action is relevant to FortiSwitch native VLAN versus allowed VLANs, not the controlling requirement in this case. Native VLAN handling and tagged VLAN membership are different controls; a working physical link does not validate VLAN carriage. The targeted response is: Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location.

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