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 30

Question 290

A security team sends a DACL for an unauthenticated session and assumes the switch applied its hardware entries. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings.
  2. The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions.
  3. Verify that supported CoA or dynamic user security profiles are enforced on authenticated sessions under the deployed topology.
  4. Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test.
  5. Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers.

Explanation

Correct Answers

C:

Verify that supported CoA or dynamic user security profiles are enforced on authenticated sessions under the deployed topology. RADIUS authentication success is not proof that a downloadable ACL or CoA update was enforced; some modes have documented conditions. Verify the action with: Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test. This is the configuration or remediation half of the requested TWO-step pair.

D:

Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test. RADIUS authentication success is not proof that a downloadable ACL or CoA update was enforced; some modes have documented conditions. The paired action is: Verify that supported CoA or dynamic user security profiles are enforced on authenticated sessions under the deployed topology. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

A:

Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings. This step concerns IPv4 source guard and binding-based packet filtering and is not part of the required paired solution. The correct action and evidence are: Verify that supported CoA or dynamic user security profiles are enforced on authenticated sessions under the deployed topology. Together with: Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test.

B:

The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions. 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: Verify that supported CoA or dynamic user security profiles are enforced on authenticated sessions under the deployed topology. Together with: Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test.

E:

Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers. This step concerns DHCP snooping trust-boundary enforcement and is not part of the required paired solution. The correct action and evidence are: Verify that supported CoA or dynamic user security profiles are enforced on authenticated sessions under the deployed topology. Together with: Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test.

Question 291

A core upgrade reelects root for one VLAN but not others, disrupting a downstream aggregation path. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Check client MAC learning, VLAN database, switch uplink tags, gateway ARP and port assignment on every hop.
  2. Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.
  3. Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.
  4. Inspect incoming 802.1p and DSCP markings, trust mode, QoS map, physical port and classification counters.

Explanation

Correct Answer

C:

Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history. An STP mode change can change per-VLAN convergence behavior even if existing links remain physically up. The paired action is: Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links.

Incorrect Answers

A:

Check client MAC learning, VLAN database, switch uplink tags, gateway ARP and port assignment on every hop. These observations are applicable to VLAN access isolation and troubleshooting of membership, but would not isolate the main failure first. The decisive evidence is: Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.

B:

Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state. These observations are applicable to Shared port multi-VDOM policy boundaries, but would not isolate the main failure first. The decisive evidence is: Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.

D:

Inspect incoming 802.1p and DSCP markings, trust mode, QoS map, physical port and classification counters. These observations are applicable to QoS ingress classification and trust boundaries, but would not isolate the main failure first. The decisive evidence is: Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.

Question 292

An MCLAG peer reports a keepalive or peer-link fault even though all physical uplink ports remain up. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect FortiGate HA active member, FortiLink aggregate state, ISL, MCLAG peer link, standby path and STP roles.
  2. Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.
  3. Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image.
  4. Review queue maps, output drops, interface rate, strict versus weighted servicing and application latency.

Explanation

Correct Answer

A:

Inspect FortiGate HA active member, FortiLink aggregate state, ISL, MCLAG peer link, standby path and STP roles. FortiGate HA, FortiLink split-interface and FortiSwitch MCLAG have distinct failover behaviors that cannot be inferred from link LEDs alone. The paired action is: Identify FortiLink failures caused by split-interface, HA, MCLAG peer or ISL mismatches before changing unrelated ports.

Incorrect Answers

B:

Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics. These observations are applicable to FortiSwitch port mirroring to network analyzer, but would not isolate the main failure first. The decisive evidence is: Inspect FortiGate HA active member, FortiLink aggregate state, ISL, MCLAG peer link, standby path and STP roles.

C:

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: Inspect FortiGate HA active member, FortiLink aggregate state, ISL, MCLAG peer link, standby path and STP roles.

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: Inspect FortiGate HA active member, FortiLink aggregate state, ISL, MCLAG peer link, standby path and STP roles.

Question 293

A phone and computer share one access port but the policy authenticates only the first observed MAC address. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile.
  2. Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN.
  3. Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof.
  4. Members receive subscribed streams while unsubscribed access ports are not flooded unnecessarily.
  5. Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports.

Explanation

Correct Answers

B:

Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN. A MAC address can be cloned; MAC authentication must be combined with appropriate segmentation and monitoring. The paired action is: Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof. This is the diagnostic or verification half of the requested TWO-step pair.

C:

Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof. A MAC address can be cloned; MAC authentication must be combined with appropriate segmentation and monitoring. Verify the action with: Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN. This is the configuration or remediation half of the requested TWO-step pair.

Incorrect Answers

A:

Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile. This step concerns FortiSwitch 802.1X port-based authentication and is not part of the required paired solution. The correct action and evidence are: Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof. Together with: Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN.

D:

Members receive subscribed streams while unsubscribed access ports are not flooded unnecessarily. This step concerns IGMP snooping and multicast receivers and is not part of the required paired solution. The correct action and evidence are: Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof. Together with: Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN.

E:

Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports. This step concerns Port MAC learning-limit and violation controls and is not part of the required paired solution. The correct action and evidence are: Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof. Together with: Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN.

Question 294

An operator receives an assigned IP address but assumes that proves the switch is already controller-authorized. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology.
  2. Troubleshooting evidence is sufficient to establish the fault without exporting unnecessary private communications.
  3. Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
  4. Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure.
  5. Inspect factory-default mode, DHCP or discovery exchange, upstream native VLAN, FortiLink enablement, NTP and controller authorization.

Explanation

Correct Answers

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.

E:

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.

Incorrect Answers

A:

Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology. This step concerns Firmware and lifecycle preparation for FortiSwitch 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.

B:

Troubleshooting evidence is sufficient to establish the fault without exporting unnecessary private communications. This step concerns Capture and confidentiality limits in incident response 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:

Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility. This step concerns Discovered versus authorized FortiSwitch state 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 295

A tenant laptop obtains a valid lease but cannot reach services because its gateway interface belongs to another VDOM. 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. The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function.
  3. The offending misassignment is corrected with both permitted traffic and forbidden cross-tenant traffic tested.
  4. All subtending managed switches remain discoverable and user service survives expected single-link failures where supported.

Explanation

Correct Answer

C:

The offending misassignment is corrected with both permitted traffic and forbidden cross-tenant traffic tested. A packet may be correctly switched but rejected by VDOM routing or firewall policy, or incorrectly admitted to another tenant at Layer 2.

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 offending misassignment is corrected with both permitted traffic and forbidden cross-tenant traffic tested.

B:

The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function. This result relates to FortiLink management interface provisioning, not the acceptance condition under test. The relevant result is: The offending misassignment is corrected with both permitted traffic and forbidden cross-tenant traffic tested.

D:

All subtending managed switches remain discoverable and user service survives expected single-link failures where supported. This result relates to FortiSwitch multi-tier managed topology, not the acceptance condition under test. The relevant result is: The offending misassignment is corrected with both permitted traffic and forbidden cross-tenant traffic tested.

Question 296

A receiver moved to another port stops getting a stream because its membership reports are not observed. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect power supply reserve, current draw, negotiated PoE class, priority shedding and port events.
  2. Inspect guard role, BPDU reception, root-ID history, STP port role and loop-condition log.
  3. Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
  4. Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port.

Explanation

Correct Answer

D:

Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port. A multicast VLAN alone does not indicate that IGMP receiver membership or querier operation is healthy. The paired action is: Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it.

Incorrect Answers

A:

Inspect power supply reserve, current draw, negotiated PoE class, priority shedding and port events. These observations are applicable to Power over Ethernet port controls and budgets, but would not isolate the main failure first. The decisive evidence is: Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port.

B:

Inspect guard role, BPDU reception, root-ID history, STP port role and loop-condition log. These observations are applicable to Root guard and loop guard failure response, but would not isolate the main failure first. The decisive evidence is: Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port.

C:

Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map. These observations are applicable to LLDP and MAC forwarding table extraction, but would not isolate the main failure first. The decisive evidence is: Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port.

Question 297

An organization attempts to push an IPv6 DACL policy even though the supported FortiSwitch release documents only IPv4 DACL support. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test.
  2. Inspect RADIUS Filter-Id or downloadable ACL attribute, authenticated session state, installed hardware entries and ACL counters.
  3. Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints.
  4. Authorized monitoring receives timely, interpretable switch evidence without exposing community strings or overwhelming CPU.
  5. Apply a specific restricted VLAN or quarantine mechanism with explicit authorized remediation and monitoring expectations.

Explanation

Correct Answers

B:

Inspect RADIUS Filter-Id or downloadable ACL attribute, authenticated session state, installed hardware entries and ACL counters. DACLs install after successful authorization and documented release limits apply; a RADIUS response alone is not proof of forwarding enforcement. The paired action is: Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints. This is the diagnostic or verification half of the requested TWO-step pair.

C:

Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints. DACLs install after successful authorization and documented release limits apply; a RADIUS response alone is not proof of forwarding enforcement. Verify the action with: Inspect RADIUS Filter-Id or downloadable ACL attribute, authenticated session state, installed hardware entries and ACL counters. This is the configuration or remediation half of the requested TWO-step pair.

Incorrect Answers

A:

Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test. This step concerns Intra-VLAN blocking and isolation boundaries and is not part of the required paired solution. The correct action and evidence are: Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints. Together with: Inspect RADIUS Filter-Id or downloadable ACL attribute, authenticated session state, installed hardware entries and ACL counters.

D:

Authorized monitoring receives timely, interpretable switch evidence without exposing community strings or overwhelming CPU. This step concerns SNMP and sFlow monitoring configuration and is not part of the required paired solution. The correct action and evidence are: Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints. Together with: Inspect RADIUS Filter-Id or downloadable ACL attribute, authenticated session state, installed hardware entries and ACL counters.

E:

Apply a specific restricted VLAN or quarantine mechanism with explicit authorized remediation and monitoring expectations. This step concerns VLAN security policy and quarantine actions and is not part of the required paired solution. The correct action and evidence are: Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints. Together with: Inspect RADIUS Filter-Id or downloadable ACL attribute, authenticated session state, installed hardware entries and ACL counters.

Question 298

The receive optical power is below specification and the team keeps modifying VLANs instead of fixing fiber attenuation. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping.
  2. Choose supported Fortinet transceivers and link media based on switch capability, optical reach and wavelength.
  3. Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes.
  4. Use STP state and MAC move evidence to isolate one bad bridging path and change only the proven element.

Explanation

Correct Answer

B:

Choose supported Fortinet transceivers and link media based on switch capability, optical reach and wavelength. Matching a mechanical optic cage is insufficient to prove optical or firmware compatibility. Verify the action with: Inspect transceiver SKU, supported compatibility table, Tx/Rx optical power, interface alarms and cable plant type.

Incorrect Answers

A:

Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping. This action is relevant to FortiSwitch split port breakout mode, not the controlling requirement in this case. A physical QSFP cage does not guarantee that four independent Ethernet child ports can be enabled on every model. The targeted response is: Choose supported Fortinet transceivers and link media based on switch capability, optical reach and wavelength.

C:

Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes. This action is relevant to FortiSwitch diagnostic commands and logs, not the controlling requirement in this case. A log message without source device, time and relevant state is not adequate to prove root cause. The targeted response is: Choose supported Fortinet transceivers and link media based on switch capability, optical reach and wavelength.

D:

Use STP state and MAC move evidence to isolate one bad bridging path and change only the proven element. This action is relevant to STP incident recovery with MAC flap evidence, not the controlling requirement in this case. Packet loss during a bridging loop can coexist with clean optical counters, so L1-only diagnostics miss the root cause. The targeted response is: Choose supported Fortinet transceivers and link media based on switch capability, optical reach and wavelength.

Question 299

FortiSwitch reaches its maximum combined static and dynamic ACL entry budget and silently leaves some intended policy uninstalled. 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. Hosts can reach their intended SVI and authorized routed destinations without overlapping address space.
  3. A session's effective access changes only when the authorization result is accepted and policy is installed on hardware.
  4. The authenticated client receives the intended per-user or per-port restrictions and unauthenticated hosts do not inherit them.

Explanation

Correct Answer

D:

The authenticated client receives the intended per-user or per-port restrictions and unauthenticated hosts do not inherit them. DACLs install after successful authorization and documented release limits apply; a RADIUS response alone is not proof of forwarding enforcement.

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: The authenticated client receives the intended per-user or per-port restrictions and unauthenticated hosts do not inherit them.

B:

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: The authenticated client receives the intended per-user or per-port restrictions and unauthenticated hosts do not inherit them.

C:

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: The authenticated client receives the intended per-user or per-port restrictions and unauthenticated hosts do not inherit them.

Question 300

A new replacement is visible in discovery but its ports do not receive policy because it is pending authorization. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.
  2. Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols.
  3. Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging.
  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

A:

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.

Incorrect Answers

B:

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: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.

C:

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: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.

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: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.

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