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 44

Question 430

A provider configures S-VLAN on a tenant VDOM rather than the VDOM where its FortiLink parent exists. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test.
  2. Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests.
  3. Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.
  4. Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.

Explanation

Correct Answer

D:

Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability. QinQ layering and VDOM assignment are separate controls; wrong outer tagging can mix customers even when inner VLAN IDs differ. The paired action is: Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.

Incorrect Answers

A:

Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test. These observations are applicable to RADIUS change of authorization and applied session policy, but would not isolate the main failure first. The decisive evidence is: Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.

B:

Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests. These observations are applicable to Multi-tenant change verification and rollback, but would not isolate the main failure first. The decisive evidence is: Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.

C:

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: Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.

Question 431

The only switch backup was taken before a year of VLAN changes and restore loses critical networks. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery.
  2. Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces.
  3. Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics.
  4. Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location.

Explanation

Correct Answer

A:

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

Incorrect Answers

B:

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: Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery.

C:

Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics. This action is relevant to Capture and confidentiality limits in incident response, not the controlling requirement in this case. A packet-capture tool may record payloads and credentials, so evidence handling is part of the network security process. The targeted response is: Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery.

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: Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery.

Question 432

A new tenant's DHCP VLAN is permitted but an old customer unexpectedly loses service due to a broad template overwrite. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. The user VLAN reaches the authorized gateway without being placed on an unrelated physical FortiGate interface.
  2. Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings.
  3. Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests.
  4. Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.
  5. Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence.

Explanation

Correct Answers

B:

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

C:

Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests. A change on shared physical transport can affect multiple VDOMs, even if each tenant's firewall policy is separate. The paired action is: Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

A:

The user VLAN reaches the authorized gateway without being placed on an unrelated physical FortiGate interface. This step concerns FortiGate managed FortiSwitch VLAN interface placement and is not part of the required paired solution. The correct action and evidence are: Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings. Together with: Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests.

D:

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: Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings. Together with: Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests.

E:

Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence. 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: Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings. Together with: Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests.

Question 433

An operator assumes that separate VLAN IDs automatically establish the intended FortiGate policy boundaries for tenants. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. A tenant reaches only its approved VDOM resources and does not inherit another tenant's policies.
  2. Expected members join the trunk and survive a member disconnect without loops or silent black holes.
  3. The intended tenant configuration changes while other tenants retain their segmentation and service.
  4. The switch successfully onboards to the intended FortiGate and retains a recoverable controller-managed baseline.

Explanation

Correct Answer

A:

A tenant reaches only its approved VDOM resources and does not inherit another tenant's policies. A VDOM creates a separate policy and routing context; it does not by itself make a shared physical switch port safe for all tenants.

Incorrect Answers

B:

Expected members join the trunk and survive a member disconnect without loops or silent black holes. This result relates to Link aggregation and port error recovery, not the acceptance condition under test. The relevant result is: A tenant reaches only its approved VDOM resources and does not inherit another tenant's policies.

C:

The intended tenant configuration changes while other tenants retain their segmentation and service. This result relates to Multi-tenant change verification and rollback, not the acceptance condition under test. The relevant result is: A tenant reaches only its approved VDOM resources and does not inherit another tenant's policies.

D:

The switch successfully onboards to the intended FortiGate and retains a recoverable controller-managed baseline. This result relates to Zero-touch provisioning and controller dependency checks, not the acceptance condition under test. The relevant result is: A tenant reaches only its approved VDOM resources and does not inherit another tenant's policies.

Question 434

A field engineer uses standalone CLI instructions on a FortiGate-managed switch and its interface settings revert. 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. Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links.
  3. Determine whether a switch is managed by FortiGate or standalone before setting interfaces, routes or admin policies.
  4. Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings.

Explanation

Correct Answer

C:

Determine whether a switch is managed by FortiGate or standalone before setting interfaces, routes or admin policies. Direct edits on a managed switch can be overridden; standalone configuration must be maintained and backed up independently. Verify the action with: Inspect FortiLink operational mode, controller ownership, current management address, VDOM and switch model support.

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: Determine whether a switch is managed by FortiGate or standalone before setting interfaces, routes or admin policies.

B:

Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links. This action is relevant to RPVST and supported STP mode interoperability, not the controlling requirement in this case. An STP mode change can change per-VLAN convergence behavior even if existing links remain physically up. The targeted response is: Determine whether a switch is managed by FortiGate or standalone before setting interfaces, routes or admin policies.

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: Determine whether a switch is managed by FortiGate or standalone before setting interfaces, routes or admin policies.

Question 435

A shared FortiSwitch port carries two tenants but the controller creates both VLANs inside the wrong VDOM. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. The impacted client can communicate on the permitted VLAN while unrelated tenant or guest VLANs remain separated.
  2. Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing.
  3. Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.
  4. Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings.
  5. Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure.

Explanation

Correct Answers

C:

Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation. 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 paired action is: Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure. This is the diagnostic or verification half of the requested TWO-step pair.

E:

Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure. A VDOM creates a separate policy and routing context; it does not by itself make a shared physical switch port safe for all tenants. Verify the action with: Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation. This is the configuration or remediation half of the requested TWO-step pair.

Incorrect Answers

A:

The impacted client can communicate on the permitted VLAN while unrelated tenant or guest VLANs remain separated. 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 FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure. Together with: Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.

B:

Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing. This step concerns Firmware and lifecycle preparation for FortiSwitch and is not part of the required paired solution. The correct action and evidence are: Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure. Together with: Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.

D:

Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings. This step concerns Multi-tenant change verification and rollback and is not part of the required paired solution. The correct action and evidence are: Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure. Together with: Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.

Question 436

A technician adds a slower interface to an existing aggregate without validating compatibility and member status. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect FortiLink interface type, split-interface setting, connected peer count, STP state and active management path.
  2. Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters.
  3. Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.
  4. Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing.

Explanation

Correct Answer

B:

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.

Incorrect Answers

A:

Inspect FortiLink interface type, split-interface setting, connected peer count, STP state and active management path. These observations are applicable to FortiLink split-interface and standby path design, but would not isolate the main failure first. The decisive evidence is: Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member 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: Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters.

D:

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: Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters.

Question 437

A relay receives mismatched Option 82 information and discards legitimate client renewals. 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. Only approved DHCP servers issue leases and the assigned endpoint identity or location remains traceable.
  3. Runaway flooding is contained without blocking legitimate broadcast-based onboarding or multicast subscribers.
  4. A session's effective access changes only when the authorization result is accepted and policy is installed on hardware.

Explanation

Correct Answer

B:

Only approved DHCP servers issue leases and the assigned endpoint identity or location remains traceable. DHCP server allowlist and Option 82 metadata provide additional context but cannot correct a failed VLAN or missing upstream relay.

Incorrect Answers

A:

The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions. This result relates to Managed switch port statistics and counter analysis, not the acceptance condition under test. The relevant result is: Only approved DHCP servers issue leases and the assigned endpoint identity or location remains traceable.

C:

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: Only approved DHCP servers issue leases and the assigned endpoint identity or location remains traceable.

D:

A session's effective access changes only when the authorization result is accepted and policy is installed on hardware. This result relates to RADIUS change of authorization and applied session policy, not the acceptance condition under test. The relevant result is: Only approved DHCP servers issue leases and the assigned endpoint identity or location remains traceable.

Question 438

A small branch has a single FortiSwitch connected to FortiGate but the user subnet is never assigned to ports. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate.
  2. Management control and authorized user traffic work over the direct connection without confusing them.
  3. Two tenants can use the supported shared port without accidental cross-tenant broadcasts or privilege escalation.
  4. The intended tenant configuration changes while other tenants retain their segmentation and service.

Explanation

Correct Answer

B:

Management control and authorized user traffic work over the direct connection without confusing them. FortiLink carries management and data traffic; a valid management handshake does not prove every user VLAN is forwarded.

Incorrect Answers

A:

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: Management control and authorized user traffic work over the direct connection without confusing them.

C:

Two tenants can use the supported shared port without accidental cross-tenant broadcasts or privilege escalation. This result relates to Shared port multi-VDOM policy boundaries, not the acceptance condition under test. The relevant result is: Management control and authorized user traffic work over the direct connection without confusing them.

D:

The intended tenant configuration changes while other tenants retain their segmentation and service. This result relates to Multi-tenant change verification and rollback, not the acceptance condition under test. The relevant result is: Management control and authorized user traffic work over the direct connection without confusing them.

Question 439

A technician plugs a managed FortiSwitch into an arbitrary WAN port and waits for it to register automatically. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting.
  2. Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces.
  3. Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch.
  4. Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints.

Explanation

Correct Answer

C:

Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch. A FortiGate port not configured for FortiLink cannot assume managed-switch ownership from physical connection alone. Verify the action with: Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.

Incorrect Answers

A:

Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting. This action is relevant to Managed switch configuration synchronization, not the controlling requirement in this case. Local changes on a FortiLink-managed switch can be discarded when the FortiGate controller reapplies its known configuration. The targeted response is: Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch.

B:

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: Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch.

D:

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: Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch.

Question 440

An unmanaged peer uses a static bundle while FortiSwitch expects active LACP negotiation. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Spoofed ARP replies are dropped while legitimate endpoints maintain gateway ARP resolution.
  2. An access host receives the right subnet while only approved tagged VLANs traverse the uplink.
  3. The handset and attached workstation use the intended separate networks and retain their authorized access.
  4. Approved aggregate members forward as one bundle while nonmatching links remain excluded.

Explanation

Correct Answer

D:

Approved aggregate members forward as one bundle while nonmatching links remain excluded. This is a measurable client, control-plane, or security outcome rather than a claim that configuration was entered. Passive LACP on both ends may not negotiate an active bundle, and individual green links do not prove aggregation.

Incorrect Answers

A:

Spoofed ARP replies are dropped while legitimate endpoints maintain gateway ARP resolution. This result relates to Dynamic ARP inspection with DHCP snooping bindings, not the acceptance condition under test. The relevant result is: Approved aggregate members forward as one bundle while nonmatching links remain excluded.

B:

An access host receives the right subnet while only approved tagged VLANs traverse the uplink. This result relates to FortiSwitch native VLAN versus allowed VLANs, not the acceptance condition under test. The relevant result is: Approved aggregate members forward as one bundle while nonmatching links remain excluded.

C:

The handset and attached workstation use the intended separate networks and retain their authorized access. This result relates to Voice and data VLAN separation on shared access ports, not the acceptance condition under test. The relevant result is: Approved aggregate members forward as one bundle while nonmatching links remain excluded.

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