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 72

Question 710

A school lab asks for device isolation yet only adds a policy between VLANs, leaving same-VLAN peers connected. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Runaway flooding is contained without blocking legitimate broadcast-based onboarding or multicast subscribers.
  2. Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy.
  3. Isolated clients can reach approved gateways while direct lateral traffic within the VLAN is blocked according to policy.
  4. The failed ISL or switch is isolated and recovered with all unaffected downstream switches remaining correctly managed.

Explanation

Correct Answer

C:

Isolated clients can reach approved gateways while direct lateral traffic within the VLAN is blocked according to policy. Routing-level firewall rules may not inspect local Layer-2 forwarding unless intra-VLAN isolation is configured.

Incorrect Answers

A:

Runaway flooding is contained without blocking legitimate broadcast-based onboarding or multicast subscribers. This result relates to Storm-control thresholds and broadcast containment, not the acceptance condition under test. The relevant result is: Isolated clients can reach approved gateways while direct lateral traffic within the VLAN is blocked according to policy.

B:

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: Isolated clients can reach approved gateways while direct lateral traffic within the VLAN is blocked according to policy.

D:

The failed ISL or switch is isolated and recovered with all unaffected downstream switches remaining correctly managed. This result relates to Stack failure isolation and switch-to-switch port roles, not the acceptance condition under test. The relevant result is: Isolated clients can reach approved gateways while direct lateral traffic within the VLAN is blocked according to policy.

Question 711

A new tenant's DHCP VLAN is permitted but an old customer unexpectedly loses service due to a broad template overwrite. 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. Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure.
  3. Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings.
  4. Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links.

Explanation

Correct Answer

C:

Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings. A change on shared physical transport can affect multiple VDOMs, even if each tenant's firewall policy is separate. Verify the action with: Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests.

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: Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings.

B:

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: Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings.

D:

Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links. This action is relevant to DHCP snooping trust-boundary enforcement, not the controlling requirement in this case. Trusting every port defeats DHCP snooping and wrongly distrusting the server uplink may suppress all leases. The targeted response is: Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings.

Question 712

An access switch accidentally becomes root because its bridge priority is lower than planned core devices. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.
  2. Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes.
  3. Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.
  4. Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.

Explanation

Correct Answer

D:

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

Incorrect Answers

A:

Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity. These observations are applicable to HA FortiGate pair managing switch topology, but would not isolate the main failure first. The decisive evidence is: Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.

B:

Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes. These observations are applicable to STP incident recovery with MAC flap evidence, but would not isolate the main failure first. The decisive evidence is: Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.

C:

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

Question 713

A technician changes the VLAN directly on a FortiLink-managed switch and loses it after reboot. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Change managed switch VLAN membership through the FortiGate controller and verify the installed configuration stays consistent.
  2. The managed switch retains the intended controller-pushed policy after a controlled synchronization and restart.
  3. Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.
  4. Trace MAC-learning and forwarding across the precise VLAN and repair only missing approved membership.
  5. Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior.

Explanation

Correct Answers

A:

Change managed switch VLAN membership through the FortiGate controller and verify the installed configuration stays consistent. Directly editing a FortiLink-managed switch can cause drift because FortiGate remains the controller of record. Verify the action with: Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior. This is the configuration or remediation half of the requested TWO-step pair.

E:

Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior. Directly editing a FortiLink-managed switch can cause drift because FortiGate remains the controller of record. The paired action is: Change managed switch VLAN membership through the FortiGate controller and verify the installed configuration stays consistent. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

B:

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: Change managed switch VLAN membership through the FortiGate controller and verify the installed configuration stays consistent. Together with: Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior.

C:

Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface. This step concerns FortiSwitch native VLAN versus allowed VLANs and is not part of the required paired solution. The correct action and evidence are: Change managed switch VLAN membership through the FortiGate controller and verify the installed configuration stays consistent. Together with: Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior.

D:

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: Change managed switch VLAN membership through the FortiGate controller and verify the installed configuration stays consistent. Together with: Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior.

Question 714

A security team sends a DACL for an unauthenticated session and assumes the switch applied its hardware entries. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. All expected child interfaces enumerate at supported speeds without disrupting unrelated uplinks.
  2. A session's effective access changes only when the authorization result is accepted and policy is installed on hardware.
  3. Approved legacy devices gain only restricted services while unknown or spoofed MAC addresses remain constrained.
  4. Unauthorized source IP packets fail while an approved host continues using its assigned IP and address policy.

Explanation

Correct Answer

B:

A session's effective access changes only when the authorization result is accepted and policy is installed on hardware. RADIUS authentication success is not proof that a downloadable ACL or CoA update was enforced; some modes have documented conditions.

Incorrect Answers

A:

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: A session's effective access changes only when the authorization result is accepted and policy is installed on hardware.

C:

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: A session's effective access changes only when the authorization result is accepted and policy is installed on hardware.

D:

Unauthorized source IP packets fail while an approved host continues using its assigned IP and address policy. This result relates to IPv4 source guard and binding-based packet filtering, not the acceptance condition under test. The relevant result is: A session's effective access changes only when the authorization result is accepted and policy is installed on hardware.

Question 715

An operator applies an edge-port policy to a FortiLink upstream interface and disrupts normal peer BPDUs. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Apply appropriate STP root or loop protection to preserve topology while analyzing missing BPDUs and unexpected root claims.
  2. Build FortiSwitch VLAN interfaces in the correct FortiLink context and assign ports through the managed switch controller.
  3. Enable supported BPDU guard only on true edge/client ports, and restore blocked ports after identifying unauthorized switching.
  4. Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings.

Explanation

Correct Answer

C:

Enable supported BPDU guard only on true edge/client ports, and restore blocked ports after identifying unauthorized switching. BPDU guard can disable an intended trunk if incorrectly treated as an end-station port. Verify the action with: Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy.

Incorrect Answers

A:

Apply appropriate STP root or loop protection to preserve topology while analyzing missing BPDUs and unexpected root claims. This action is relevant to Root guard and loop guard failure response, not the controlling requirement in this case. Root guard and loop guard mitigate different failure cases and should not be enabled indiscriminately on every uplink. The targeted response is: Enable supported BPDU guard only on true edge/client ports, and restore blocked ports after identifying unauthorized switching.

B:

Build FortiSwitch VLAN interfaces in the correct FortiLink context and assign ports through the managed switch controller. This action is relevant to FortiGate managed FortiSwitch VLAN interface placement, not the controlling requirement in this case. A named VLAN in FortiOS is not proof its switch-port membership and L3 policy are correct. The targeted response is: Enable supported BPDU guard only on true edge/client ports, and restore blocked ports after identifying unauthorized switching.

D:

Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings. This action is relevant to Multi-tenant change verification and rollback, not the controlling requirement in this case. A change on shared physical transport can affect multiple VDOMs, even if each tenant's firewall policy is separate. The targeted response is: Enable supported BPDU guard only on true edge/client ports, and restore blocked ports after identifying unauthorized switching.

Question 716

A distribution uplink carries VLAN 40 locally but the peer excludes VLAN 40 from its allowed list. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path.
  2. Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.
  3. Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover.
  4. Trace MAC-learning and forwarding across the precise VLAN and repair only missing approved membership.
  5. A moved device is traced to its current approved port and incorrect cross-connection is identified.

Explanation

Correct Answers

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

C:

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

Incorrect Answers

A:

Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path. This step concerns FortiGate managed FortiSwitch VLAN interface placement and is not part of the required paired solution. The correct action and evidence are: Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover. Together with: Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.

D:

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: Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover. Together with: Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.

E:

A moved device is traced to its current approved port and incorrect cross-connection is identified. This step concerns LLDP and MAC forwarding table extraction and is not part of the required paired solution. The correct action and evidence are: Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover. Together with: Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.

Question 717

An unmanaged peer uses a static bundle while FortiSwitch expects active LACP negotiation. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters.
  2. The switch successfully onboards to the intended FortiGate and retains a recoverable controller-managed baseline.
  3. Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic.
  4. Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation.
  5. Inspect transceiver SKU, supported compatibility table, Tx/Rx optical power, interface alarms and cable plant type.

Explanation

Correct Answers

A:

Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters. Passive LACP on both ends may not negotiate an active bundle, and individual green links do not prove aggregation. The paired action is: Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation. This is the diagnostic or verification half of the requested TWO-step pair.

D:

Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation. Passive LACP on both ends may not negotiate an active bundle, and individual green links do not prove aggregation. Verify the action with: Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters. This is the configuration or remediation half of the requested TWO-step pair.

Incorrect Answers

B:

The switch successfully onboards to the intended FortiGate and retains a recoverable controller-managed baseline. This step concerns Zero-touch provisioning and controller dependency checks and is not part of the required paired solution. The correct action and evidence are: Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation. Together with: Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters.

C:

Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic. This step concerns Static route and default gateway validation and is not part of the required paired solution. The correct action and evidence are: Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation. Together with: Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters.

E:

Inspect transceiver SKU, supported compatibility table, Tx/Rx optical power, interface alarms and cable plant type. This step concerns Optic compatibility and laser diagnostic evidence and is not part of the required paired solution. The correct action and evidence are: Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation. Together with: Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters.

Question 718

A pair of distribution FortiSwitch units has dual client uplinks but never formed an MCLAG peer group. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Use FortiLink split-interface or standby interfaces only for supported topology and verify active versus backup port behavior.
  2. Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology.
  3. Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.
  4. A tenant reaches only its approved VDOM resources and does not inherit another tenant's policies.
  5. Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles.

Explanation

Correct Answers

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

E:

Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles. MCLAG redundancy depends on supported peer-link and aggregate design; two cables alone do not constitute working multichassis aggregation. Verify the action with: Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology. This is the configuration or remediation half of the requested TWO-step pair.

Incorrect Answers

A:

Use FortiLink split-interface or standby interfaces only for supported topology and verify active versus backup port behavior. 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: Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles. Together with: Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology.

C:

Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters. This step concerns Layer 2 MAC-learning and forwarding decisions and is not part of the required paired solution. The correct action and evidence are: Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles. Together with: Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology.

D:

A tenant reaches only its approved VDOM resources and does not inherit another tenant's policies. This step concerns FortiGate VDOM-based FortiSwitch tenant assignment and is not part of the required paired solution. The correct action and evidence are: Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles. Together with: Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology.

Question 719

A PoE access switch can power legacy phones but sheds newer high-power access points after lunch. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage.
  2. Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints.
  3. Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs.
  4. Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues.

Explanation

Correct Answer

A:

Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage. Port count and Ethernet link state do not guarantee sufficient power for high-draw endpoints. Verify the action with: Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events.

Incorrect Answers

B:

Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints. This action is relevant to DACL RADIUS attribute and per-session enforcement, not the controlling requirement in this case. DACLs install after successful authorization and documented release limits apply; a RADIUS response alone is not proof of forwarding enforcement. The targeted response is: Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage.

C:

Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs. This action is relevant to Stack failure isolation and switch-to-switch port roles, not the controlling requirement in this case. A missing switch in a FortiLink managed chain may be caused by the upstream ISL even if its access ports still carry local traffic. The targeted response is: Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage.

D:

Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues. This action is relevant to QoS ingress classification and trust boundaries, not the controlling requirement in this case. A packet marking has no useful QoS effect until supported classification and scheduling map it consistently. The targeted response is: Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage.

Question 720

A newly patched uplink reports an unexpected LLDP peer from a separate customer zone. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
  2. Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths.
  3. Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy.
  4. Phones and access points receive stable allocated power while redundant PSU and priority policies remain within budget.
  5. Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes.

Explanation

Correct Answers

A:

Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map. LLDP provides adjacent-device identity, while MAC learning maps forwarding; neither is a full routed trace by itself. The paired action is: Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths. This is the diagnostic or verification half of the requested TWO-step pair.

B:

Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths. LLDP provides adjacent-device identity, while MAC learning maps forwarding; neither is a full routed trace by itself. Verify the action with: Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map. This is the configuration or remediation half of the requested TWO-step pair.

Incorrect Answers

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: Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths. Together with: Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.

D:

Phones and access points receive stable allocated power while redundant PSU and priority policies remain within budget. This step concerns PoE and LLDP-MED endpoint power coordination and is not part of the required paired solution. The correct action and evidence are: Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths. Together with: Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.

E:

Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes. This step concerns FortiSwitch diagnostic commands and logs and is not part of the required paired solution. The correct action and evidence are: Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths. Together with: Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.

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