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 32

Question 310

A second floor switch is cabled through an undocumented uplink and never appears in managed FortiSwitch inventory. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes.
  2. Build FortiSwitch VLAN interfaces in the correct FortiLink context and assign ports through the managed switch controller.
  3. Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.
  4. Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles.
  5. The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function.

Explanation

Correct Answers

C:

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

D:

Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles. The FortiGate-managed FortiSwitch stack is a managed L2 topology, not automatically a single chassis or universal VSF-like control plane. Verify the action with: Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization. This is the configuration or remediation half of the requested TWO-step pair.

Incorrect Answers

A:

Review phone tagging capabilities, voice VLAN identifier, LLDP-MED policy, access port configuration and DHCP scopes. 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: Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles. Together with: Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.

B:

Build FortiSwitch VLAN interfaces in the correct FortiLink context and assign ports through the managed switch controller. This step concerns FortiGate managed FortiSwitch VLAN interface placement and is not part of the required paired solution. The correct action and evidence are: Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles. Together with: Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.

E:

The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function. This step concerns FortiLink management interface provisioning and is not part of the required paired solution. The correct action and evidence are: Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles. Together with: Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.

Question 311

A second floor switch is cabled through an undocumented uplink and never appears in managed FortiSwitch inventory. 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. Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation.
  3. Apply supported egress CoS queue policy to reduce latency under congestion without starving other required traffic.
  4. Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles.

Explanation

Correct Answer

D:

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

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: Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles.

B:

Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation. This action is relevant to LACP negotiation on FortiSwitch FortiLink trunks, not the controlling requirement in this case. Passive LACP on both ends may not negotiate an active bundle, and individual green links do not prove aggregation. The targeted response is: Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles.

C:

Apply supported egress CoS queue policy to reduce latency under congestion without starving other required traffic. This action is relevant to Egress priority scheduling and congestion visibility, not the controlling requirement in this case. QoS prioritizes scarce link capacity but cannot create bandwidth beyond the physical egress rate. The targeted response is: Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles.

Question 312

A phone is moved to another floor but its advertised LLDP-MED location still references the old closet. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Latency-sensitive flows improve under representative load while other business services remain functional.
  2. Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority.
  3. Authorized monitoring receives timely, interpretable switch evidence without exposing community strings or overwhelming CPU.
  4. The current neighboring device and optional endpoint location are visible and match approved cabling documentation.

Explanation

Correct Answer

D:

The current neighboring device and optional endpoint location are visible and match approved cabling documentation. LLDP is an L2 discovery protocol and cannot prove the whole routed service path or phone emergency-location correctness by itself.

Incorrect Answers

A:

Latency-sensitive flows improve under representative load while other business services remain functional. This result relates to Egress priority scheduling and congestion visibility, not the acceptance condition under test. The relevant result is: The current neighboring device and optional endpoint location are visible and match approved cabling documentation.

B:

Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority. This result relates to QoS ingress classification and trust boundaries, not the acceptance condition under test. The relevant result is: The current neighboring device and optional endpoint location are visible and match approved cabling documentation.

C:

Authorized monitoring receives timely, interpretable switch evidence without exposing community strings or overwhelming CPU. This result relates to SNMP and sFlow monitoring configuration, not the acceptance condition under test. The relevant result is: The current neighboring device and optional endpoint location are visible and match approved cabling documentation.

Question 313

A long full-packet trace fills the device RAM disk and discards the earliest evidence during an incident. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics.
  2. Enable supported BPDU guard only on true edge/client ports, and restore blocked ports after identifying unauthorized switching.
  3. Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames.
  4. Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted.

Explanation

Correct Answer

C:

Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames. Packet captures are interface and filter scoped, and platform buffer limits differ; a capture file is not proof of all traffic on every switch port. Verify the action with: Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers.

Incorrect Answers

A:

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: Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames.

B:

Enable supported BPDU guard only on true edge/client ports, and restore blocked ports after identifying unauthorized switching. This action is relevant to BPDU guard on endpoint-facing ports, not the controlling requirement in this case. BPDU guard can disable an intended trunk if incorrectly treated as an end-station port. The targeted response is: Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames.

D:

Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted. This action is relevant to FortiGate one-arm sniffer across managed switching, not the controlling requirement in this case. Sniffer placement determines visibility; absence of a packet at one observation point does not prove no packet existed elsewhere. The targeted response is: Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames.

Question 314

A server sends untagged frames but its switch port expects only tagged frames and never learns the MAC in the intended VLAN. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Management control and authorized user traffic work over the direct connection without confusing them.
  2. Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing.
  3. Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.
  4. Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port.
  5. Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context.

Explanation

Correct Answers

B:

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.

C:

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

A:

Management control and authorized user traffic work over the direct connection without confusing them. This step concerns Single FortiGate and single FortiSwitch topology 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:

Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port. This step concerns IGMP snooping and multicast receivers 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:

Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context. This step concerns FortiSwitch SVI routing and connected routes 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 315

A team posts complete captures containing authentication tokens into a public support thread. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics.
  2. Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted.
  3. Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths.
  4. Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles.

Explanation

Correct Answer

A:

Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics. A packet-capture tool may record payloads and credentials, so evidence handling is part of the network security process. Verify the action with: Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions.

Incorrect Answers

B:

Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted. This action is relevant to FortiGate one-arm sniffer across managed switching, not the controlling requirement in this case. Sniffer placement determines visibility; absence of a packet at one observation point does not prove no packet existed elsewhere. The targeted response is: Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics.

C:

Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths. This action is relevant to LLDP and MAC forwarding table extraction, not the controlling requirement in this case. LLDP provides adjacent-device identity, while MAC learning maps forwarding; neither is a full routed trace by itself. The targeted response is: Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics.

D:

Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles. This action is relevant to FortiLink ISL auto-discovery and stack cabling, not the controlling requirement in this case. The FortiGate-managed FortiSwitch stack is a managed L2 topology, not automatically a single chassis or universal VSF-like control plane. The targeted response is: Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics.

Question 316

A standalone FortiSwitch has local management access but cannot reach its NTP server off-subnet. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Determine whether a switch is managed by FortiGate or standalone before setting interfaces, routes or admin policies.
  2. A controlled failure test restores approved management and access connectivity through the designed redundant path.
  3. Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.
  4. Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.
  5. Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic.

Explanation

Correct Answers

D:

Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path. A default route cannot repair local VLAN tagging or a missing neighbor resolution condition. The paired action is: Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic. This is the diagnostic or verification half of the requested TWO-step pair.

E:

Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic. A default route cannot repair local VLAN tagging or a missing neighbor resolution condition. Verify the action with: Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path. This is the configuration or remediation half of the requested TWO-step pair.

Incorrect Answers

A:

Determine whether a switch is managed by FortiGate or standalone before setting interfaces, routes or admin policies. 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: Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic. Together with: Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.

B:

A controlled failure test restores approved management and access connectivity through the designed redundant path. This step concerns FortiLink HA and MCLAG topology faults and is not part of the required paired solution. The correct action and evidence are: Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic. Together with: Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.

C:

Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters. This step concerns MSTP region consistency and designated root and is not part of the required paired solution. The correct action and evidence are: Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic. Together with: Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.

Question 317

The network plan assumes every port-security feature is supported for a multi-VDOM shared port on every model. 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. Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests.
  3. Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging.
  4. Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation.

Explanation

Correct Answer

C:

Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging. Shared physical ports can support some per-port controls across VDOMs, but feature support and tagging must be checked for the exact release. Verify the action with: Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.

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: Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging.

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: Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging.

D:

Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation. This action is relevant to LACP negotiation on FortiSwitch FortiLink trunks, not the controlling requirement in this case. Passive LACP on both ends may not negotiate an active bundle, and individual green links do not prove aggregation. The targeted response is: Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging.

Question 318

A client manually assigns a privileged subnet address and tries to send packets through an access port. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Only approved DHCP servers issue leases and the assigned endpoint identity or location remains traceable.
  2. Unauthorized source IP packets fail while an approved host continues using its assigned IP and address policy.
  3. The handset and attached workstation use the intended separate networks and retain their authorized access.
  4. Spoofed ARP replies are dropped while legitimate endpoints maintain gateway ARP resolution.

Explanation

Correct Answer

B:

Unauthorized source IP packets fail while an approved host continues using its assigned IP and address policy. Source guard is an ingress source-binding check, not a full replacement for routed firewall policies or endpoint security.

Incorrect Answers

A:

Only approved DHCP servers issue leases and the assigned endpoint identity or location remains traceable. This result relates to DHCP server allowlist and Option 82 validation, not the acceptance condition under test. The relevant result is: Unauthorized source IP packets fail while an approved host continues using its assigned IP and address policy.

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: Unauthorized source IP packets fail while an approved host continues using its assigned IP and address policy.

D:

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: Unauthorized source IP packets fail while an approved host continues using its assigned IP and address policy.

Question 319

An HA failover succeeds for firewall traffic while downstream switch management disconnects because standby wiring is incomplete. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.
  2. Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing.
  3. Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests.
  4. Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end.
  5. The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate.

Explanation

Correct Answers

A:

Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity. FortiGate HA design and FortiSwitch stacking/MCLAG are separate mechanisms; their failure paths must both be evaluated. The paired action is: Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests. This is the diagnostic or verification half of the requested TWO-step pair.

C:

Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests. FortiGate HA design and FortiSwitch stacking/MCLAG are separate mechanisms; their failure paths must both be evaluated. Verify the action with: Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity. This is the configuration or remediation half of the requested TWO-step pair.

Incorrect Answers

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: Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests. Together with: Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.

D:

Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end. This step concerns FortiLink transport over nontrivial L2 or L3 paths and is not part of the required paired solution. The correct action and evidence are: Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests. Together with: Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.

E:

The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate. This step concerns FortiSwitch diagnostic commands and logs and is not part of the required paired solution. The correct action and evidence are: Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests. Together with: Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.

Question 320

An organization disconnects FortiLink to deploy standalone management but fails to assign a reachable management IP and default route. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Both ends connect at compatible rates with stable errors and required throughput.
  2. Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy.
  3. Routes and interfaces are configured at the appropriate control plane and persist after synchronization or reboot.
  4. Hosts can reach their intended SVI and authorized routed destinations without overlapping address space.

Explanation

Correct Answer

C:

Routes and interfaces are configured at the appropriate control plane and persist after synchronization or reboot. Direct edits on a managed switch can be overridden; standalone configuration must be maintained and backed up independently.

Incorrect Answers

A:

Both ends connect at compatible rates with stable errors and required throughput. This result relates to Switch port speed and duplex commissioning, not the acceptance condition under test. The relevant result is: Routes and interfaces are configured at the appropriate control plane and persist after synchronization or reboot.

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: Routes and interfaces are configured at the appropriate control plane and persist after synchronization or reboot.

D:

Hosts can reach their intended SVI and authorized routed destinations without overlapping address space. This result relates to FortiSwitch SVI routing and connected routes, not the acceptance condition under test. The relevant result is: Routes and interfaces are configured at the appropriate control plane and persist after synchronization or reboot.

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