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 5

Question 40

An administrator assumes a new FortiSwitch model accepts the same firmware image as an older campus model. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging.
  2. Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology.
  3. Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.
  4. Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location.

Explanation

Correct Answer

B:

Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology. A successful image upload does not prove switch operation or controller compatibility after reboot. Verify the action with: Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing.

Incorrect Answers

A:

Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging. This action is relevant to Shared port multi-VDOM policy boundaries, not the controlling requirement in this case. Shared physical ports can support some per-port controls across VDOMs, but feature support and tagging must be checked for the exact release. The targeted response is: Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology.

C:

Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic. This action is relevant to QinQ outer and inner VLAN tenant mapping, not the controlling requirement in this case. QinQ layering and VDOM assignment are separate controls; wrong outer tagging can mix customers even when inner VLAN IDs differ. The targeted response is: Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology.

D:

Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location. This action is relevant to Managed switch port statistics and counter analysis, not the controlling requirement in this case. A port-up indicator or one successful ping is not proof that a congested or errored uplink is healthy. The targeted response is: Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology.

Question 41

A FortiGate template updates native VLANs but a switch shows an outdated port mapping after synchronization. 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 offending misassignment is corrected with both permitted traffic and forbidden cross-tenant traffic tested.
  3. Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior.
  4. Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment.
  5. Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path.

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.

C:

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

Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment. This step concerns Voice and data VLAN separation on shared access ports 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.

E:

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

A replacement switch reboots with old port settings because the controller still associates the serial with a previous group. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure.
  2. Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting.
  3. Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope.
  4. Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces.

Explanation

Correct Answer

B:

Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting. Local changes on a FortiLink-managed switch can be discarded when the FortiGate controller reapplies its known configuration. Verify the action with: Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration.

Incorrect Answers

A:

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: Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting.

C:

Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope. This action is relevant to SNMP and sFlow monitoring configuration, not the controlling requirement in this case. Flow samples are estimates and counters vary by port; collecting telemetry cannot replace a controlled packet capture when headers are needed. The targeted response is: Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting.

D:

Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces. This action is relevant to Single FortiGate and single FortiSwitch topology, not the controlling requirement in this case. FortiLink carries management and data traffic; a valid management handshake does not prove every user VLAN is forwarded. The targeted response is: Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting.

Question 43

Two MCLAG peers disagree on allowed client VLANs and the same client reaches different gateways depending on active link. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Use FortiLink split-interface or standby interfaces only for supported topology and verify active versus backup port behavior.
  2. Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles.
  3. Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records.
  4. Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols.

Explanation

Correct Answer

B:

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.

Incorrect Answers

A:

Use FortiLink split-interface or standby interfaces only for supported topology and verify active versus backup port behavior. This action is relevant to FortiLink split-interface and standby path design, not the controlling requirement in this case. FortiLink split-interface behavior depends on topology; enabling it blindly for same-peer LAG links can break intended aggregation. The targeted response is: Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles.

C:

Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records. This action is relevant to LLDP neighbor discovery and location information, not the controlling requirement in this case. LLDP is an L2 discovery protocol and cannot prove the whole routed service path or phone emergency-location correctness by itself. The targeted response is: Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles.

D:

Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols. This action is relevant to Storm-control thresholds and broadcast containment, not the controlling requirement in this case. Overaggressive storm control can break DHCP, ARP or group discovery even when physical links remain healthy. The targeted response is: Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles.

Question 44

A replacement switch reboots with old port settings because the controller still associates the serial with a previous group. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.
  2. Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing.
  3. Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.
  4. Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration.

Explanation

Correct Answer

D:

Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration. Local changes on a FortiLink-managed switch can be discarded when the FortiGate controller reapplies its known configuration. The paired action is: Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting.

Incorrect Answers

A:

Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction. These observations are applicable to FortiGate one-arm sniffer across managed switching, but would not isolate the main failure first. The decisive evidence is: Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration.

B:

Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing. These observations are applicable to Firmware and lifecycle preparation for FortiSwitch, but would not isolate the main failure first. The decisive evidence is: Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration.

C:

Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability. These observations are applicable to QinQ outer and inner VLAN tenant mapping, but would not isolate the main failure first. The decisive evidence is: Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration.

Question 45

A small branch has a single FortiSwitch connected to FortiGate but the user subnet is never assigned to ports. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure.
  2. Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces.
  3. Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence.
  4. Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location.

Explanation

Correct Answer

B:

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:

Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure. This action is relevant to Zero-touch provisioning and controller dependency checks, not the controlling requirement in this case. Zero-touch deployment works only when the necessary discovery path and identity checks function; a link LED is insufficient. The targeted response is: Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces.

C:

Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence. This action is relevant to Managed tenant troubleshooting across controller and access layer, not the controlling requirement in this case. A packet may be correctly switched but rejected by VDOM routing or firewall policy, or incorrectly admitted to another tenant at Layer 2. The targeted response is: Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces.

D:

Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location. This action is relevant to Managed switch port statistics and counter analysis, not the controlling requirement in this case. A port-up indicator or one successful ping is not proof that a congested or errored uplink is healthy. The targeted response is: Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces.

Question 46

A contractor creates an unapproved second ring path, then calls every STP blocked port an outage. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.
  2. Apply appropriate STP root or loop protection to preserve topology while analyzing missing BPDUs and unexpected root claims.
  3. Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.
  4. Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end.

Explanation

Correct Answer

C:

Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards. A FortiGate controls each FortiSwitch through the managed Layer-2 topology, but downstream reachability depends on upstream FortiLink links. Verify the action with: Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.

Incorrect Answers

A:

Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic. This action is relevant to QinQ outer and inner VLAN tenant mapping, not the controlling requirement in this case. QinQ layering and VDOM assignment are separate controls; wrong outer tagging can mix customers even when inner VLAN IDs differ. The targeted response is: Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.

B:

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: Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.

D:

Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end. This action is relevant to FortiLink transport over nontrivial L2 or L3 paths, not the controlling requirement in this case. FortiLink over intermediate networks requires topology-specific settings; ordinary IP reachability alone does not establish FortiLink discovery. The targeted response is: Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.

Question 47

A device dashboard shows an average rate that hides short bursts of dropped voice traffic. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions.
  2. A trace shows the expected ingress/egress control packets without collecting unrelated sensitive network traffic.
  3. Managed status remains healthy and user traffic uses only its intended FortiLink-carried VLANs.
  4. The offending misassignment is corrected with both permitted traffic and forbidden cross-tenant traffic tested.

Explanation

Correct Answer

A:

The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions. A port-up indicator or one successful ping is not proof that a congested or errored uplink is healthy.

Incorrect Answers

B:

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: The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions.

C:

Managed status remains healthy and user traffic uses only its intended FortiLink-carried VLANs. This result relates to FortiLink control and client VLAN transport separation, not the acceptance condition under test. The relevant result is: The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions.

D:

The offending misassignment is corrected with both permitted traffic and forbidden cross-tenant traffic tested. This result relates to Managed tenant troubleshooting across controller and access layer, not the acceptance condition under test. The relevant result is: The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions.

Question 48

An unknown switch appears discovered after a contractor accidentally connected equipment to the FortiLink port. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode.
  2. Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps.
  3. Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices.
  4. Only intended networks are reachable through the configured route and the return path remains valid.
  5. Investigate managed switch offline or configuration mismatch after firmware upgrade or controller resynchronization using both endpoints.

Explanation

Correct Answers

A:

Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode. Authorizing a switch is an administrative trust step; pending switch state is not evidence of a routing failure. The paired action is: Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices. This is the diagnostic or verification half of the requested TWO-step pair.

C:

Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices. Authorizing a switch is an administrative trust step; pending switch state is not evidence of a routing failure. Verify the action with: Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode. This is the configuration or remediation half of the requested TWO-step pair.

Incorrect Answers

B:

Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps. This step concerns Managed switch port statistics and counter analysis and is not part of the required paired solution. The correct action and evidence are: Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices. Together with: Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode.

D:

Only intended networks are reachable through the configured route and the return path remains valid. This step concerns Static route and default gateway validation and is not part of the required paired solution. The correct action and evidence are: Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices. Together with: Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode.

E:

Investigate managed switch offline or configuration mismatch after firmware upgrade or controller resynchronization using both endpoints. This step concerns FortiLink synchronization and upgrade troubleshooting and is not part of the required paired solution. The correct action and evidence are: Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices. Together with: Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode.

Question 49

Two distribution switches report an unexpected LLDP neighbor after a contractor reroutes patch cables. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.
  2. Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.
  3. Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port.
  4. Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events.

Explanation

Correct Answer

B:

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.

Incorrect Answers

A:

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: Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.

C:

Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port. These observations are applicable to IGMP snooping and multicast receivers, but would not isolate the main failure first. The decisive evidence is: Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.

D:

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: Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.

Question 50

A contractor creates an unapproved second ring path, then calls every STP blocked port an outage. 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. A controlled peer or member failure maintains approved client VLAN access without a Layer-2 loop.
  3. All subtending managed switches remain discoverable and user service survives expected single-link failures where supported.
  4. A controlled FortiGate HA failover leaves managed switches authorized and required client access functioning.

Explanation

Correct Answer

C:

All subtending managed switches remain discoverable and user service survives expected single-link failures where supported. A FortiGate controls each FortiSwitch through the managed Layer-2 topology, but downstream reachability depends on upstream FortiLink links.

Incorrect Answers

A:

Legitimate clients lease addresses while rogue DHCP servers connected to untrusted access ports cannot answer. This result relates to DHCP snooping trust-boundary enforcement, not the acceptance condition under test. The relevant result is: All subtending managed switches remain discoverable and user service survives expected single-link failures where supported.

B:

A controlled peer or member failure maintains approved client VLAN access without a Layer-2 loop. This result relates to MCLAG multichassis access redundancy, not the acceptance condition under test. The relevant result is: All subtending managed switches remain discoverable and user service survives expected single-link failures where supported.

D:

A controlled FortiGate HA failover leaves managed switches authorized and required client access functioning. This result relates to HA FortiGate pair managing switch topology, not the acceptance condition under test. The relevant result is: All subtending managed switches remain discoverable and user service survives expected single-link failures where supported.

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