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 46

Question 450

A FortiSwitch is asked to route between two user VLANs but the gateway addresses were configured only on hosts. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters.
  2. A moved device is traced to its current approved port and incorrect cross-connection is identified.
  3. Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it.
  4. Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context.
  5. Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway.

Explanation

Correct Answers

D:

Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context. Layer-3 SVI configuration and actual usable forwarding are separate from having a named Layer-2 VLAN. Verify the action with: Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway. This is the configuration or remediation half of the requested TWO-step pair.

E:

Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway. Layer-3 SVI configuration and actual usable forwarding are separate from having a named Layer-2 VLAN. The paired action is: Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

A:

Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters. This step concerns Switch port speed and duplex commissioning and is not part of the required paired solution. The correct action and evidence are: Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context. Together with: Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway.

B:

A moved device is traced to its current approved port and incorrect cross-connection is identified. This step concerns LLDP and MAC forwarding table extraction and is not part of the required paired solution. The correct action and evidence are: Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context. Together with: Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway.

C:

Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it. This step concerns IGMP snooping and multicast receivers and is not part of the required paired solution. The correct action and evidence are: Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context. Together with: Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway.

Question 451

An engineer blames firmware for a restart without inspecting system-event history or power loss indications. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes.
  2. Verify FortiLink management status and user VLAN reachability independently when a switch is authorized but clients fail.
  3. Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image.
  4. Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history.
  5. A redundant topology recovers after a link failure without simultaneous independent forwarding paths causing loops.

Explanation

Correct Answers

A:

Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes. A log message without source device, time and relevant state is not adequate to prove root cause. Verify the action with: Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history. This is the configuration or remediation half of the requested TWO-step pair.

D:

Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history. A log message without source device, time and relevant state is not adequate to prove root cause. The paired action is: Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

B:

Verify FortiLink management status and user VLAN reachability independently when a switch is authorized but clients fail. This step concerns FortiLink control and client VLAN transport separation and is not part of the required paired solution. The correct action and evidence are: Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes. Together with: Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history.

C:

Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image. This step concerns FortiLink synchronization and upgrade troubleshooting and is not part of the required paired solution. The correct action and evidence are: Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes. Together with: Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history.

E:

A redundant topology recovers after a link failure without simultaneous independent forwarding paths causing loops. This step concerns FortiLink split-interface and standby path design and is not part of the required paired solution. The correct action and evidence are: Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes. Together with: Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history.

Question 452

A landlord shares one uplink among tenant VDOMs without restricting customer-tagged VLANs. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters.
  2. Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.
  3. Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.
  4. Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test.

Explanation

Correct Answer

C:

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.

Incorrect Answers

A:

Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters. These observations are applicable to Managed tenant troubleshooting across controller and access layer, but would not isolate the main failure first. The decisive evidence is: Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.

B:

Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation. These observations are applicable to FortiGate VDOM-based FortiSwitch tenant assignment, but would not isolate the main failure first. The decisive evidence is: Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.

D:

Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test. These observations are applicable to Intra-VLAN blocking and isolation boundaries, but would not isolate the main failure first. The decisive evidence is: Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.

Question 453

Two service customers both use inner VLAN 10 but one S-VLAN is omitted during handoff. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.
  2. Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.
  3. Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.
  4. Known printers and IoT devices enter their restricted VLANs while unknown endpoints have no excessive access.
  5. Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.

Explanation

Correct Answers

A:

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

E:

Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic. QinQ layering and VDOM assignment are separate controls; wrong outer tagging can mix customers even when inner VLAN IDs differ. Verify the action with: Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability. This is the configuration or remediation half of the requested TWO-step pair.

Incorrect Answers

B:

Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards. This step concerns FortiSwitch multi-tier managed topology and is not part of the required paired solution. The correct action and evidence are: Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic. Together with: Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.

C:

Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability. This step concerns FortiLink management interface provisioning and is not part of the required paired solution. The correct action and evidence are: Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic. Together with: Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.

D:

Known printers and IoT devices enter their restricted VLANs while unknown endpoints have no excessive access. This step concerns NAC dynamic port policy device classification and is not part of the required paired solution. The correct action and evidence are: Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic. Together with: Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.

Question 454

A managed FortiSwitch loses VLAN policy after reboot because prior local CLI edits never entered FortiGate configuration. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers.
  2. Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps.
  3. Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions.
  4. Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image.

Explanation

Correct Answer

D:

Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image. Managed switches can be reachable at Layer 2 yet show stale policy after incompatible upgrade or failed controller push. The paired action is: Investigate managed switch offline or configuration mismatch after firmware upgrade or controller resynchronization using both endpoints.

Incorrect Answers

A:

Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers. These observations are applicable to DHCP snooping trust-boundary enforcement, but would not isolate the main failure first. The decisive evidence is: Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image.

B:

Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps. These observations are applicable to Managed switch port statistics and counter analysis, but would not isolate the main failure first. The decisive evidence is: Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image.

C:

Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions. These observations are applicable to Config backup and firmware inventory evidence, but would not isolate the main failure first. The decisive evidence is: Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image.

Question 455

A tenant laptop obtains a valid lease but cannot reach services because its gateway interface belongs to another VDOM. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?

  1. Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters.
  2. Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration.
  3. Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware.
  4. Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.

Explanation

Correct Answer

A:

Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters. A packet may be correctly switched but rejected by VDOM routing or firewall policy, or incorrectly admitted to another tenant at Layer 2. The paired action is: Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence.

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: Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters.

C:

Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware. These observations are applicable to FortiLink transport over nontrivial L2 or L3 paths, but would not isolate the main failure first. The decisive evidence is: Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters.

D:

Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters. These observations are applicable to Layer 2 MAC-learning and forwarding decisions, but would not isolate the main failure first. The decisive evidence is: Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters.

Question 456

An attacker spoofs an authorized IoT MAC to test whether the switch applies any additional restrictions. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof.
  2. Change managed switch VLAN membership through the FortiGate controller and verify the installed configuration stays consistent.
  3. Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence.
  4. Use supported intra-VLAN traffic controls when clients in the same broadcast domain must not communicate directly.

Explanation

Correct Answer

A:

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.

Incorrect Answers

B:

Change managed switch VLAN membership through the FortiGate controller and verify the installed configuration stays consistent. This action is relevant to VLAN configuration persistence and drift control, not the controlling requirement in this case. Directly editing a FortiLink-managed switch can cause drift because FortiGate remains the controller of record. The targeted response is: Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof.

C:

Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence. This action is relevant to Static port ACL forwarding decisions, not the controlling requirement in this case. Switch ACLs and FortiGate firewall policies operate at different enforcement points; a deny on one does not prove the other applied. The targeted response is: Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof.

D:

Use supported intra-VLAN traffic controls when clients in the same broadcast domain must not communicate directly. This action is relevant to Intra-VLAN blocking and isolation boundaries, not the controlling requirement in this case. Routing-level firewall rules may not inspect local Layer-2 forwarding unless intra-VLAN isolation is configured. The targeted response is: Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof.

Question 457

Two distribution switches have different MST region revisions and flood after a redundant connection is added. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path.
  2. Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy.
  3. Repair LACP member settings and physical port errors independently before increasing aggregate traffic.
  4. Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.
  5. Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy.

Explanation

Correct Answers

B:

Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy. Different MST configuration identifiers split regions even if switch ports are physically connected. Verify the action with: Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters. This is the configuration or remediation half of the requested TWO-step pair.

D:

Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters. Different MST configuration identifiers split regions even if switch ports are physically connected. The paired action is: Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

A:

Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path. This step concerns FortiGate managed FortiSwitch VLAN interface placement and is not part of the required paired solution. The correct action and evidence are: Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy. Together with: Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.

C:

Repair LACP member settings and physical port errors independently before increasing aggregate traffic. This step concerns Link aggregation and port error recovery and is not part of the required paired solution. The correct action and evidence are: Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy. Together with: Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.

E:

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: Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy. Together with: Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.

Question 458

An authorized replacement is still pending because the switch serial was entered incorrectly in controller inventory. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Management connectivity is established across the supported intermediate network without losing segmentation or authentication assumptions.
  2. Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices.
  3. Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.
  4. Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted.
  5. Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode.

Explanation

Correct Answers

B:

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

E:

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

Incorrect Answers

A:

Management connectivity is established across the supported intermediate network without losing segmentation or authentication assumptions. 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: Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices. Together with: Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode.

C:

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: Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices. Together with: Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode.

D:

Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted. This step concerns FortiGate one-arm sniffer across managed switching and is not part of the required paired solution. The correct action and evidence are: Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices. Together with: Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode.

Question 459

A team interprets seeing a DHCP Discover at the mirror as proof the server's Offer reached the requesting access port. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. The analyzer receives the intended copies while production forwarding remains unchanged.
  2. Both ends connect at compatible rates with stable errors and required throughput.
  3. The exact dropped direction or incorrect address binding is evidenced before changing a security feature.
  4. FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy.

Explanation

Correct Answer

D:

FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy. Sniffer placement determines visibility; absence of a packet at one observation point does not prove no packet existed elsewhere.

Incorrect Answers

A:

The analyzer receives the intended copies while production forwarding remains unchanged. This result relates to FortiSwitch port mirroring to network analyzer, not the acceptance condition under test. The relevant result is: FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy.

B:

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: FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy.

C:

The exact dropped direction or incorrect address binding is evidenced before changing a security feature. This result relates to Capture-based DHCP and ARP path isolation, not the acceptance condition under test. The relevant result is: FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy.

Question 460

A technician plugs a managed FortiSwitch into an arbitrary WAN port and waits for it to register automatically. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. A redundant topology recovers after a link failure without simultaneous independent forwarding paths causing loops.
  2. Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.
  3. Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch.
  4. Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.
  5. Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings.

Explanation

Correct Answers

C:

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

D:

Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability. A FortiGate port not configured for FortiLink cannot assume managed-switch ownership from physical connection alone. The paired action is: Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

A:

A redundant topology recovers after a link failure without simultaneous independent forwarding paths causing loops. This step concerns FortiLink split-interface and standby path design and is not part of the required paired solution. The correct action and evidence are: Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch. Together with: Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.

B:

Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity. This step concerns HA FortiGate pair managing switch topology and is not part of the required paired solution. The correct action and evidence are: Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch. Together with: Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.

E:

Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings. This step concerns Multi-tenant change verification and rollback and is not part of the required paired solution. The correct action and evidence are: Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch. Together with: Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.

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