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 64

Question 630

A rogue switch appears as discovered and an administrator considers enabling global auto-authorization without checking its identity. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.
  2. Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.
  3. Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.
  4. Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
  5. Routes and interfaces are configured at the appropriate control plane and persist after synchronization or reboot.

Explanation

Correct Answers

B:

Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition. Switch discovery is not the same as authorization; auto-authorization has governance implications and a managed-mode transition may reboot the device. Verify the action with: Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility. This is the configuration or remediation half of the requested TWO-step pair.

D:

Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility. Switch discovery is not the same as authorization; auto-authorization has governance implications and a managed-mode transition may reboot the device. The paired action is: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

A:

Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic. This step concerns QinQ outer and inner VLAN tenant mapping and is not part of the required paired solution. The correct action and evidence are: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition. Together with: Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.

C:

Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status. This step concerns FortiSwitch multi-tier managed topology and is not part of the required paired solution. The correct action and evidence are: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition. Together with: Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.

E:

Routes and interfaces are configured at the appropriate control plane and persist after synchronization or reboot. This step concerns FortiSwitch standalone versus FortiLink managed L3 ownership and is not part of the required paired solution. The correct action and evidence are: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition. Together with: Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.

Question 631

A technician adds a slower interface to an existing aggregate without validating compatibility and member status. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation.
  2. Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage.
  3. Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes.
  4. Determine whether a switch is managed by FortiGate or standalone before setting interfaces, routes or admin policies.

Explanation

Correct Answer

A:

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.

Incorrect Answers

B:

Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage. This action is relevant to PoE and LLDP-MED endpoint power coordination, not the controlling requirement in this case. Port count and Ethernet link state do not guarantee sufficient power for high-draw endpoints. The targeted response is: Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation.

C:

Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes. This action is relevant to NAC dynamic port policy device classification, not the controlling requirement in this case. NAC assignment relies on reliable detection and a defined precedence; a class label is not a substitute for switch-port policy. The targeted response is: Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation.

D:

Determine whether a switch is managed by FortiGate or standalone before setting interfaces, routes or admin policies. This action is relevant to FortiSwitch standalone versus FortiLink managed L3 ownership, not the controlling requirement in this case. Direct edits on a managed switch can be overridden; standalone configuration must be maintained and backed up independently. The targeted response is: Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation.

Question 632

A phone uplink starts receiving unexpected bridge-control frames after someone adds a looped desktop switch. 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. Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events.
  3. Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy.
  4. Review queue maps, output drops, interface rate, strict versus weighted servicing and application latency.

Explanation

Correct Answer

C:

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

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: Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy.

B:

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: Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy.

D:

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: Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy.

Question 633

A rogue switch appears as discovered and an administrator considers enabling global auto-authorization without checking its identity. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
  2. Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy.
  3. Inspect FortiLink mode, physical or aggregate link state, switch authorization, VLAN interfaces and test-client path.
  4. Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.

Explanation

Correct Answer

A:

Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility. Switch discovery is not the same as authorization; auto-authorization has governance implications and a managed-mode transition may reboot the device. The paired action is: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.

Incorrect Answers

B:

Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy. These observations are applicable to BPDU guard on endpoint-facing ports, but would not isolate the main failure first. The decisive evidence is: Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.

C:

Inspect FortiLink mode, physical or aggregate link state, switch authorization, VLAN interfaces and test-client path. These observations are applicable to Single FortiGate and single FortiSwitch topology, but would not isolate the main failure first. The decisive evidence is: Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.

D:

Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability. These observations are applicable to FortiLink management interface provisioning, but would not isolate the main failure first. The decisive evidence is: Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.

Question 634

A port inventory lists a downstream switch whose LLDP entry has expired and no longer reflects current wiring. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. The exact dropped direction or incorrect address binding is evidenced before changing a security feature.
  2. Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records.
  3. Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.
  4. Verify model-specific PoE class, total switch power budget and per-port policy before enabling new powered devices.
  5. Inspect guard role, BPDU reception, root-ID history, STP port role and loop-condition log.

Explanation

Correct Answers

B:

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.

C:

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:

The exact dropped direction or incorrect address binding is evidenced before changing a security feature. This step concerns Capture-based DHCP and ARP path isolation 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:

Verify model-specific PoE class, total switch power budget and per-port policy before enabling new powered devices. This step concerns Power over Ethernet port controls and budgets 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.

E:

Inspect guard role, BPDU reception, root-ID history, STP port role and loop-condition log. This step concerns Root guard and loop guard failure response 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 635

An administrator enables DHCP snooping without checking whether the expected relay path is exempted correctly. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Legitimate clients lease addresses while rogue DHCP servers connected to untrusted access ports cannot answer.
  2. Approved legacy devices gain only restricted services while unknown or spoofed MAC addresses remain constrained.
  3. An unexpected additional device is restricted or signaled without knocking out approved business equipment.
  4. The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate.

Explanation

Correct Answer

A:

Legitimate clients lease addresses while rogue DHCP servers connected to untrusted access ports cannot answer. Trusting every port defeats DHCP snooping and wrongly distrusting the server uplink may suppress all leases.

Incorrect Answers

B:

Approved legacy devices gain only restricted services while unknown or spoofed MAC addresses remain constrained. This result relates to MAC-based authentication and restricted legacy devices, not the acceptance condition under test. The relevant result is: Legitimate clients lease addresses while rogue DHCP servers connected to untrusted access ports cannot answer.

C:

An unexpected additional device is restricted or signaled without knocking out approved business equipment. This result relates to Port MAC learning-limit and violation controls, not the acceptance condition under test. The relevant result is: Legitimate clients lease addresses while rogue DHCP servers connected to untrusted access ports cannot answer.

D:

The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate. This result relates to FortiSwitch diagnostic commands and logs, not the acceptance condition under test. The relevant result is: Legitimate clients lease addresses while rogue DHCP servers connected to untrusted access ports cannot answer.

Question 636

A direct switch connection works until the FortiGate port is repurposed into another software-switch aggregate. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links.
  2. Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests.
  3. Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces.
  4. Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.

Explanation

Correct Answer

C:

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.

Incorrect Answers

A:

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: Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces.

B:

Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests. This action is relevant to HA FortiGate pair managing switch topology, not the controlling requirement in this case. FortiGate HA design and FortiSwitch stacking/MCLAG are separate mechanisms; their failure paths must both be evaluated. The targeted response is: Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces.

D:

Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards. This action is relevant to FortiSwitch multi-tier managed topology, not the controlling requirement in this case. A FortiGate controls each FortiSwitch through the managed Layer-2 topology, but downstream reachability depends on upstream FortiLink links. The targeted response is: Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces.

Question 637

A printer is moved to a new patch panel but its MAC keeps appearing on an old trunk member. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing.
  2. Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.
  3. Two tenants can use the supported shared port without accidental cross-tenant broadcasts or privilege escalation.
  4. Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues.
  5. Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.

Explanation

Correct Answers

A:

Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing. An L2 switch uses MAC destination and VLAN state for forwarding; a healthy SVI is not proof a host is on the proper port. Verify the action with: Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters. This is the configuration or remediation half of the requested TWO-step pair.

B:

Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters. An L2 switch uses MAC destination and VLAN state for forwarding; a healthy SVI is not proof a host is on the proper port. The paired action is: Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

C:

Two tenants can use the supported shared port without accidental cross-tenant broadcasts or privilege escalation. This step concerns Shared port multi-VDOM policy boundaries and is not part of the required paired solution. The correct action and evidence are: Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing. Together with: Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.

D:

Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues. This step concerns QoS ingress classification and trust boundaries and is not part of the required paired solution. The correct action and evidence are: Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing. Together with: Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.

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: Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing. Together with: Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.

Question 638

A mirrored switch port feeds FortiGate but the sniffer filter incorrectly excludes double-tagged frames. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps.
  2. Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.
  3. Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions.
  4. Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters.

Explanation

Correct Answer

B:

Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction. Sniffer placement determines visibility; absence of a packet at one observation point does not prove no packet existed elsewhere. The paired action is: Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted.

Incorrect Answers

A:

Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps. These observations are applicable to Managed switch port statistics and counter analysis, but would not isolate the main failure first. The decisive evidence is: Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.

C:

Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions. These observations are applicable to Capture and confidentiality limits in incident response, but would not isolate the main failure first. The decisive evidence is: Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.

D:

Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters. These observations are applicable to Managed tenant troubleshooting across controller and access layer, but would not isolate the main failure first. The decisive evidence is: Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.

Question 639

An automated branch rollout fails because its bootstrap port sits on a VLAN that cannot contact the controller. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Only approved DHCP servers issue leases and the assigned endpoint identity or location remains traceable.
  2. Inspect factory-default mode, DHCP or discovery exchange, upstream native VLAN, FortiLink enablement, NTP and controller authorization.
  3. Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.
  4. Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure.
  5. Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces.

Explanation

Correct Answers

B:

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

D:

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

Incorrect Answers

A:

Only approved DHCP servers issue leases and the assigned endpoint identity or location remains traceable. This step concerns DHCP server allowlist and Option 82 validation and is not part of the required paired solution. The correct action and evidence are: Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure. Together with: Inspect factory-default mode, DHCP or discovery exchange, upstream native VLAN, FortiLink enablement, NTP and controller authorization.

C:

Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity. This step concerns HA FortiGate pair managing switch topology and is not part of the required paired solution. The correct action and evidence are: Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure. Together with: Inspect factory-default mode, DHCP or discovery exchange, upstream native VLAN, FortiLink enablement, NTP and controller authorization.

E:

Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces. This step concerns Single FortiGate and single FortiSwitch topology and is not part of the required paired solution. The correct action and evidence are: Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure. Together with: Inspect factory-default mode, DHCP or discovery exchange, upstream native VLAN, FortiLink enablement, NTP and controller authorization.

Question 640

An installer assumes any FortiSwitch port will auto-discover FortiLink despite model-specific discovery defaults. 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. Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image.
  3. Review queue maps, output drops, interface rate, strict versus weighted servicing and application latency.
  4. Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.

Explanation

Correct Answer

A:

Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization. The FortiGate-managed FortiSwitch stack is a managed L2 topology, not automatically a single chassis or universal VSF-like control plane. The paired action is: Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles.

Incorrect Answers

B:

Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image. These observations are applicable to FortiLink synchronization and upgrade troubleshooting, but would not isolate the main failure first. The decisive evidence is: Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.

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

D:

Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings. These observations are applicable to LLDP neighbor discovery and location information, but would not isolate the main failure first. The decisive evidence is: Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.

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