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 79

Question 780

Two MCLAG peers disagree on allowed client VLANs and the same client reaches different gateways depending on active link. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy.
  2. A downstream dual-homed switch retains service on one peer failure without duplicate independent forwarding loops.
  3. A rogue root candidate is blocked or a looped path remains safely contained without wiping all STP configuration.
  4. The user VLAN reaches the authorized gateway without being placed on an unrelated physical FortiGate interface.

Explanation

Correct Answer

B:

A downstream dual-homed switch retains service on one peer failure without duplicate independent forwarding loops. MCLAG redundancy depends on supported peer-link and aggregate design; two cables alone do not constitute working multichassis aggregation.

Incorrect Answers

A:

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: A downstream dual-homed switch retains service on one peer failure without duplicate independent forwarding loops.

C:

A rogue root candidate is blocked or a looped path remains safely contained without wiping all STP configuration. This result relates to Root guard and loop guard failure response, not the acceptance condition under test. The relevant result is: A downstream dual-homed switch retains service on one peer failure without duplicate independent forwarding loops.

D:

The user VLAN reaches the authorized gateway without being placed on an unrelated physical FortiGate interface. This result relates to FortiGate managed FortiSwitch VLAN interface placement, not the acceptance condition under test. The relevant result is: A downstream dual-homed switch retains service on one peer failure without duplicate independent forwarding loops.

Question 781

Two distribution switches report an unexpected LLDP neighbor after a contractor reroutes patch cables. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology.
  2. A controlled FortiGate HA failover leaves managed switches authorized and required client access functioning.
  3. Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records.
  4. Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority.
  5. Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.

Explanation

Correct Answers

C:

Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records. LLDP is an L2 discovery protocol and cannot prove the whole routed service path or phone emergency-location correctness by itself. Verify the action with: Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings. This is the configuration or remediation half of the requested TWO-step pair.

E:

Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings. LLDP is an L2 discovery protocol and cannot prove the whole routed service path or phone emergency-location correctness by itself. The paired action is: Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

A:

Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology. This step concerns MCLAG peer-link topology for managed access switches and is not part of the required paired solution. The correct action and evidence are: Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records. Together with: Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.

B:

A controlled FortiGate HA failover leaves managed switches authorized and required client access functioning. This step concerns HA FortiGate pair managing switch topology and is not part of the required paired solution. The correct action and evidence are: Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records. Together with: Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.

D:

Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority. This step concerns LLDP-MED voice network policy advertisements and is not part of the required paired solution. The correct action and evidence are: Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records. Together with: Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.

Question 782

A desk phone and PC are daisy-chained, yet both obtain addresses from the guest subnet. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior.
  2. Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history.
  3. Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes.
  4. Inspect hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect.

Explanation

Correct Answer

C:

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.

Incorrect Answers

A:

Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior. These observations are applicable to VLAN configuration persistence and drift control, but would not isolate the main failure first. The decisive evidence is: Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes.

B:

Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history. These observations are applicable to FortiSwitch diagnostic commands and logs, but would not isolate the main failure first. The decisive evidence is: Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes.

D:

Inspect hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect. These observations are applicable to FortiSwitch split port breakout mode, but would not isolate the main failure first. The decisive evidence is: Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes.

Question 783

FortiSwitch reaches its maximum combined static and dynamic ACL entry budget and silently leaves some intended policy uninstalled. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Inspect RADIUS Filter-Id or downloadable ACL attribute, authenticated session state, installed hardware entries and ACL counters.
  2. Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings.
  3. The managed switch retains the intended controller-pushed policy after a controlled synchronization and restart.
  4. Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints.
  5. Inspect MAC table usage, configured learning limit, learned device count, port-security event and violation action.

Explanation

Correct Answers

A:

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

D:

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

Incorrect Answers

B:

Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings. This step concerns IPv4 source guard and binding-based packet filtering and is not part of the required paired solution. The correct action and evidence are: Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints. Together with: Inspect RADIUS Filter-Id or downloadable ACL attribute, authenticated session state, installed hardware entries and ACL counters.

C:

The managed switch retains the intended controller-pushed policy after a controlled synchronization and restart. This step concerns Managed switch configuration synchronization and is not part of the required paired solution. The correct action and evidence are: Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints. Together with: Inspect RADIUS Filter-Id or downloadable ACL attribute, authenticated session state, installed hardware entries and ACL counters.

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: Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints. Together with: Inspect RADIUS Filter-Id or downloadable ACL attribute, authenticated session state, installed hardware entries and ACL counters.

Question 784

A data closet trunk sends untagged management frames into a partner's tagged-only management VLAN. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. A downstream dual-homed switch retains service on one peer failure without duplicate independent forwarding loops.
  2. Rapid MAC moves stop and normal forwarding returns with a verified alternate redundant path.
  3. An access host receives the right subnet while only approved tagged VLANs traverse the uplink.
  4. A trace shows the expected ingress/egress control packets without collecting unrelated sensitive network traffic.

Explanation

Correct Answer

C:

An access host receives the right subnet while only approved tagged VLANs traverse the uplink. Native VLAN handling and tagged VLAN membership are different controls; a working physical link does not validate VLAN carriage.

Incorrect Answers

A:

A downstream dual-homed switch retains service on one peer failure without duplicate independent forwarding loops. This result relates to MCLAG peer-link topology for managed access switches, not the acceptance condition under test. The relevant result is: An access host receives the right subnet while only approved tagged VLANs traverse the uplink.

B:

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: An access host receives the right subnet while only approved tagged VLANs traverse the uplink.

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: An access host receives the right subnet while only approved tagged VLANs traverse the uplink.

Question 785

A school lab asks for device isolation yet only adds a policy between VLANs, leaving same-VLAN peers connected. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test.
  2. Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test.
  3. Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events.
  4. Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile.

Explanation

Correct Answer

A:

Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test. Routing-level firewall rules may not inspect local Layer-2 forwarding unless intra-VLAN isolation is configured. The paired action is: Use supported intra-VLAN traffic controls when clients in the same broadcast domain must not communicate directly.

Incorrect Answers

B:

Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test. These observations are applicable to RADIUS change of authorization and applied session policy, but would not isolate the main failure first. The decisive evidence is: Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test.

C:

Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events. These observations are applicable to Stack failure isolation and switch-to-switch port roles, but would not isolate the main failure first. The decisive evidence is: Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test.

D:

Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile. These observations are applicable to FortiSwitch 802.1X port-based authentication, but would not isolate the main failure first. The decisive evidence is: Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test.

Question 786

A managed switch loses FortiLink only after an active FortiGate HA failover. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  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. Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy.
  4. Inspect FortiGate HA active member, FortiLink aggregate state, ISL, MCLAG peer link, standby path and STP roles.
  5. The offending misassignment is corrected with both permitted traffic and forbidden cross-tenant traffic tested.

Explanation

Correct Answers

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

D:

Inspect FortiGate HA active member, FortiLink aggregate state, ISL, MCLAG peer link, standby path and STP roles. FortiGate HA, FortiLink split-interface and FortiSwitch MCLAG have distinct failover behaviors that cannot be inferred from link LEDs alone. The paired action is: Identify FortiLink failures caused by split-interface, HA, MCLAG peer or ISL mismatches before changing unrelated ports. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

B:

Troubleshoot FortiLink discovery from physical and logical interface configuration through LLDP and management addressing. This step concerns FortiLink discovery failure and physical uplink path and is not part of the required paired solution. The correct action and evidence are: Identify FortiLink failures caused by split-interface, HA, MCLAG peer or ISL mismatches before changing unrelated ports. Together with: Inspect FortiGate HA active member, FortiLink aggregate state, ISL, MCLAG peer link, standby path and STP roles.

C:

Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy. This step concerns SNMP and sFlow monitoring configuration and is not part of the required paired solution. The correct action and evidence are: Identify FortiLink failures caused by split-interface, HA, MCLAG peer or ISL mismatches before changing unrelated ports. Together with: Inspect FortiGate HA active member, FortiLink aggregate state, ISL, MCLAG peer link, standby path and STP roles.

E:

The offending misassignment is corrected with both permitted traffic and forbidden cross-tenant traffic tested. This step concerns Managed tenant troubleshooting across controller and access layer and is not part of the required paired solution. The correct action and evidence are: Identify FortiLink failures caused by split-interface, HA, MCLAG peer or ISL mismatches before changing unrelated ports. Together with: Inspect FortiGate HA active member, FortiLink aggregate state, ISL, MCLAG peer link, standby path and STP roles.

Question 787

A replacement switch is installed without checking whether its old firmware supports the current FortiLink controller. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery.
  2. Runaway flooding is contained without blocking legitimate broadcast-based onboarding or multicast subscribers.
  3. Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions.
  4. Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings.
  5. Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.

Explanation

Correct Answers

A:

Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery. Backups require correct model/version and an actual restore procedure; a saved file name is not proof a recovered switch will work. Verify the action with: Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions. This is the configuration or remediation half of the requested TWO-step pair.

C:

Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions. Backups require correct model/version and an actual restore procedure; a saved file name is not proof a recovered switch will work. The paired action is: Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

B:

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: Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery. Together with: Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions.

D:

Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings. This step concerns FortiSwitch port mirroring to network analyzer and is not part of the required paired solution. The correct action and evidence are: Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery. Together with: Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions.

E:

Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction. 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: Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery. Together with: Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions.

Question 788

One FortiSwitch reboot causes adjacent units to move between discovered and authorized states. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology.
  2. Verify model-specific PoE class, total switch power budget and per-port policy before enabling new powered devices.
  3. Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs.
  4. Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles.

Explanation

Correct Answer

C:

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

Incorrect Answers

A:

Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology. This action is relevant to Firmware and lifecycle preparation for FortiSwitch, not the controlling requirement in this case. A successful image upload does not prove switch operation or controller compatibility after reboot. The targeted response is: Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs.

B:

Verify model-specific PoE class, total switch power budget and per-port policy before enabling new powered devices. This action is relevant to Power over Ethernet port controls and budgets, not the controlling requirement in this case. Not every FortiSwitch model or port supports identical PoE allocation or every attached device's peak draw. The targeted response is: Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs.

D:

Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles. This action is relevant to MCLAG peer-link topology for managed access switches, not the controlling requirement in this case. MCLAG redundancy depends on supported peer-link and aggregate design; two cables alone do not constitute working multichassis aggregation. The targeted response is: Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs.

Question 789

A branch turns off 802.1X to fix an outage and inadvertently permits visitors onto production VLANs. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile.
  2. Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior.
  3. Inspect RADIUS Filter-Id or downloadable ACL attribute, authenticated session state, installed hardware entries and ACL counters.
  4. Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof.
  5. Every relevant VLAN converges without loops and redundant paths unblock only when needed.

Explanation

Correct Answers

A:

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.

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.

Incorrect Answers

C:

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

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: 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.

E:

Every relevant VLAN converges without loops and redundant paths unblock only when needed. This step concerns RPVST and supported STP mode interoperability 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 790

Two aggregation switches have two uplinks to an access device but lack a configured FortiSwitch MCLAG pair. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware.
  2. Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards.
  3. Review queue maps, output drops, interface rate, strict versus weighted servicing and application latency.
  4. Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.

Explanation

Correct Answer

B:

Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards. MCLAG requires peer coordination and correct downstream aggregation; it is not equivalent to connecting independent switches in parallel. The paired action is: Use documented peer-group and downstream trunk configuration for MCLAG rather than creating ad hoc parallel Ethernet links.

Incorrect Answers

A:

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 group, peer-link status, LACP members, VLAN consistency and split-brain safeguards.

C:

Review queue maps, output drops, interface rate, strict versus weighted servicing and application latency. These observations are applicable to Egress priority scheduling and congestion visibility, but would not isolate the main failure first. The decisive evidence is: Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards.

D:

Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation. These observations are applicable to FortiGate VDOM-based FortiSwitch tenant assignment, but would not isolate the main failure first. The decisive evidence is: Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards.

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