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 35

Question 340

A firewall analyst captures only the routed interface while the failure occurs between two hosts in one switch VLAN. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Trace DHCP and ARP exchanges at ingress and uplink to distinguish missing requests from blocked or malformed responses.
  2. Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions.
  3. Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.
  4. Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy.
  5. Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted.

Explanation

Correct Answers

C:

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

E:

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

Incorrect Answers

A:

Trace DHCP and ARP exchanges at ingress and uplink to distinguish missing requests from blocked or malformed responses. This step concerns Capture-based DHCP and ARP path isolation and is not part of the required paired solution. The correct action and evidence are: Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted. Together with: Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.

B:

Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions. 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: Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted. Together with: Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.

D:

Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy. 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 a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted. Together with: Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.

Question 341

Two customer groups with overlapping subnet plans are connected as if VDOM segmentation automatically fixes routing collisions. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.
  2. Accidental downstream switches are contained without disabling legitimate uplinks that should exchange BPDUs.
  3. Inspect FortiLink mode, physical or aggregate link state, switch authorization, VLAN interfaces and test-client path.
  4. Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging.
  5. Use documented peer-group and downstream trunk configuration for MCLAG rather than creating ad hoc parallel Ethernet links.

Explanation

Correct Answers

A:

Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state. Shared physical ports can support some per-port controls across VDOMs, but feature support and tagging must be checked for the exact release. The paired action is: Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging. This is the diagnostic or verification half of the requested TWO-step pair.

D:

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

Incorrect Answers

B:

Accidental downstream switches are contained without disabling legitimate uplinks that should exchange BPDUs. This step concerns BPDU guard on endpoint-facing ports and is not part of the required paired solution. The correct action and evidence are: Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging. Together with: Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.

C:

Inspect FortiLink mode, physical or aggregate link state, switch authorization, VLAN interfaces and test-client path. This step concerns Single FortiGate and single FortiSwitch topology and is not part of the required paired solution. The correct action and evidence are: Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging. Together with: Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.

E:

Use documented peer-group and downstream trunk configuration for MCLAG rather than creating ad hoc parallel Ethernet links. This step concerns MCLAG multichassis access redundancy and is not part of the required paired solution. The correct action and evidence are: Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging. Together with: Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.

Question 342

Both ends of a branch trunk are set to passive LACP and none of the physical ports aggregate. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Approved aggregate members forward as one bundle while nonmatching links remain excluded.
  2. Each intended managed switch appears with valid upstream connectivity and no unintended layer-2 loop.
  3. Every relevant VLAN converges without loops and redundant paths unblock only when needed.
  4. The switch successfully onboards to the intended FortiGate and retains a recoverable controller-managed baseline.

Explanation

Correct Answer

A:

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

B:

Each intended managed switch appears with valid upstream connectivity and no unintended layer-2 loop. This result relates to FortiLink ISL auto-discovery and stack cabling, not the acceptance condition under test. The relevant result is: Approved aggregate members forward as one bundle while nonmatching links remain excluded.

C:

Every relevant VLAN converges without loops and redundant paths unblock only when needed. This result relates to RPVST and supported STP mode interoperability, not the acceptance condition under test. The relevant result is: Approved aggregate members forward as one bundle while nonmatching links remain excluded.

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: Approved aggregate members forward as one bundle while nonmatching links remain excluded.

Question 343

A replacement switch is installed without checking whether its old firmware supports the current FortiLink controller. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions.
  2. Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy.
  3. Check per-member speed, partner identity, state, optical counters, VLAN tags and aggregate distribution.
  4. Inspect FortiGate FortiLink status, supported discovery port, LLDP frames, interface IP, link errors and switch serial.

Explanation

Correct Answer

A:

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

Incorrect Answers

B:

Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy. These observations are applicable to SNMP and sFlow monitoring configuration, but would not isolate the main failure first. The decisive evidence is: Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions.

C:

Check per-member speed, partner identity, state, optical counters, VLAN tags and aggregate distribution. These observations are applicable to Link aggregation and port error recovery, but would not isolate the main failure first. The decisive evidence is: Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions.

D:

Inspect FortiGate FortiLink status, supported discovery port, LLDP frames, interface IP, link errors and switch serial. These observations are applicable to FortiLink discovery failure and physical uplink path, but would not isolate the main failure first. The decisive evidence is: Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions.

Question 344

Two phones receive different QoS hints after being attached to ports using different LLDP profiles. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.
  2. Examine LLDP transmit state, port profile, neighbor TLVs, advertised VLAN and DSCP or 802.1p settings.
  3. Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.
  4. Inspect FortiLink interface type, split-interface setting, connected peer count, STP state and active management path.

Explanation

Correct Answer

B:

Examine LLDP transmit state, port profile, neighbor TLVs, advertised VLAN and DSCP or 802.1p settings. LLDP-MED exchanges policy hints with compatible endpoints; it does not substitute for port membership and DHCP. The paired action is: Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority.

Incorrect Answers

A:

Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings. These observations are applicable to LLDP neighbor discovery and location information, but would not isolate the main failure first. The decisive evidence is: Examine LLDP transmit state, port profile, neighbor TLVs, advertised VLAN and DSCP or 802.1p settings.

C:

Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status. These observations are applicable to FortiSwitch multi-tier managed topology, but would not isolate the main failure first. The decisive evidence is: Examine LLDP transmit state, port profile, neighbor TLVs, advertised VLAN and DSCP or 802.1p settings.

D:

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: Examine LLDP transmit state, port profile, neighbor TLVs, advertised VLAN and DSCP or 802.1p settings.

Question 345

A device dashboard shows an average rate that hides short bursts of dropped voice traffic. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Investigate managed switch offline or configuration mismatch after firmware upgrade or controller resynchronization using both endpoints.
  2. Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.
  3. Rapid MAC moves stop and normal forwarding returns with a verified alternate redundant path.
  4. Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location.
  5. Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps.

Explanation

Correct Answers

D:

Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location. A port-up indicator or one successful ping is not proof that a congested or errored uplink is healthy. Verify the action with: Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps. This is the configuration or remediation half of the requested TWO-step pair.

E:

Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps. A port-up indicator or one successful ping is not proof that a congested or errored uplink is healthy. The paired action is: Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

A:

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: Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location. Together with: Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps.

B:

Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics. This step concerns FortiSwitch port mirroring to network analyzer and is not part of the required paired solution. The correct action and evidence are: Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location. Together with: Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps.

C:

Rapid MAC moves stop and normal forwarding returns with a verified alternate redundant path. This step concerns STP incident recovery with MAC flap evidence and is not part of the required paired solution. The correct action and evidence are: Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location. Together with: Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps.

Question 346

A shared FortiSwitch port carries two tenants but the controller creates both VLANs inside the wrong VDOM. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.
  2. Check client MAC learning, VLAN database, switch uplink tags, gateway ARP and port assignment on every hop.
  3. Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.
  4. Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.

Explanation

Correct Answer

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.

Incorrect Answers

A:

Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status. These observations are applicable to FortiSwitch multi-tier managed topology, but would not isolate the main failure first. The decisive evidence is: Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.

B:

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 controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.

D:

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 controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.

Question 347

A security team sends a DACL for an unauthenticated session and assumes the switch applied its hardware entries. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state.
  2. Inspect power supply reserve, current draw, negotiated PoE class, priority shedding and port events.
  3. Check switch quarantine status, ACL/security profile, allowed remediation services, NAC event and release criteria.
  4. Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test.

Explanation

Correct Answer

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.

Incorrect Answers

A:

Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state. These observations are applicable to NAC dynamic port policy device classification, but would not isolate the main failure first. The decisive evidence is: Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test.

B:

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: Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test.

C:

Check switch quarantine status, ACL/security profile, allowed remediation services, NAC event and release criteria. These observations are applicable to VLAN security policy and quarantine actions, but would not isolate the main failure first. The decisive evidence is: Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test.

Question 348

A branch begins firmware rollout on every downstream switch without checking supported controller compatibility. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing.
  2. Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration.
  3. Inspect DHCP server permitted list, Option 82 insertion/trust state, relay path, client bindings and lease evidence.
  4. Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.

Explanation

Correct Answer

A:

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

Incorrect Answers

B:

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

C:

Inspect DHCP server permitted list, Option 82 insertion/trust state, relay path, client bindings and lease evidence. These observations are applicable to DHCP server allowlist and Option 82 validation, but would not isolate the main failure first. The decisive evidence is: Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing.

D:

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: Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing.

Question 349

A broad profile overrides a more specific guest device rule and grants a larger VLAN scope than planned. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints.
  2. Authorized monitoring receives timely, interpretable switch evidence without exposing community strings or overwhelming CPU.
  3. Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence.
  4. Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state.
  5. Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.

Explanation

Correct Answers

C:

Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence. A named security profile sitting in configuration is not proof that it was applied to the intended hardware port. Verify the action with: Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls. This is the configuration or remediation half of the requested TWO-step pair.

E:

Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls. A named security profile sitting in configuration is not proof that it was applied to the intended hardware port. The paired action is: Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

A:

Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints. This step concerns DACL RADIUS attribute and per-session enforcement and is not part of the required paired solution. The correct action and evidence are: Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence. Together with: Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.

B:

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: Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence. Together with: Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.

D:

Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state. This step concerns NAC dynamic port policy device classification and is not part of the required paired solution. The correct action and evidence are: Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence. Together with: Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.

Question 350

A receiver moved to another port stops getting a stream because its membership reports are not observed. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles.
  2. Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it.
  3. Use STP state and MAC move evidence to isolate one bad bridging path and change only the proven element.
  4. Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure.

Explanation

Correct Answer

B:

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

Incorrect Answers

A:

Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles. This action is relevant to MCLAG peer-link topology for managed access switches, not the controlling requirement in this case. MCLAG redundancy depends on supported peer-link and aggregate design; two cables alone do not constitute working multichassis aggregation. The targeted response is: Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it.

C:

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: Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it.

D:

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: Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it.

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