McAfee Secure

Exam Code: NSE5_FSW_AD-7.6

Exam Name: Fortinet NSE 5 - FortiSwitch 7.6 Administrator

Certification Provider: Fortinet

Corresponding Certification: NSE5

Fortinet NSE5_FSW_AD-7.6 Questions & Answers

Study with Up-To-Date REAL Exam Questions and Answers from the ACTUAL Test

64 Questions & Answers with Testing Engine

"Fortinet NSE 5 - FortiSwitch 7.6 Administrator Exam", also known as NSE5_FSW_AD-7.6 exam, is a Fortinet certification exam.

Pass your tests with the always up-to-date NSE5_FSW_AD-7.6 Exam Engine. Your NSE5_FSW_AD-7.6 training materials keep you at the head of the pack!

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Was: $137.49
Now: $124.99

Fortinet NSE5_FSW_AD-7.6 Practice Test 42

Question 410

At the Redhaven campus infrastructure group, an access switch has uplinks to two FortiSwitch distribution peers but the peers lack an approved MCLAG configuration. What risk should the team identify as the primary issue?

  1. Overlay transport requires explicit compatibility and control reachability beyond a regular copper uplink
  2. Two physical uplinks to independent peers are not a coordinated aggregate by default
  3. The documented shared FortiSwitch port feature set does not include DHCP snooping
  4. Unreviewed automatic authorization can admit a connected switch before identity and installation are checked

Explanation

Correct Answer

B:

This identifies the root issue: two physical uplinks to independent peers are not a coordinated aggregate by default. At the Redhaven campus infrastructure group, the team should therefore deploy supported MCLAG peer and inter-chassis design before activating parallel uplinks.

Incorrect Answers

A:

The offered action is: Overlay transport requires explicit compatibility and control reachability beyond a regular copper uplink. It is associated with this separate technical condition: Overlay transport requires explicit compatibility and control reachability beyond a regular copper uplink. The actual incident concerns a different dependency: Two physical uplinks to independent peers are not a coordinated aggregate by default. The corresponding change is: Two physical uplinks to independent peers are not a coordinated aggregate by default.

C:

The offered alternative is: The documented shared FortiSwitch port feature set does not include DHCP snooping. It addresses this separate failure mode: The documented shared FortiSwitch port feature set does not include DHCP snooping. In the current case, the observed mechanism is: Two physical uplinks to independent peers are not a coordinated aggregate by default. The keyed action, Two physical uplinks to independent peers are not a coordinated aggregate by default., targets that condition more directly.

D:

Unreviewed automatic authorization can admit a connected switch before identity and installation are checked. That is not the mechanism that accounts for the stated failure at the Redhaven campus infrastructure group.

Question 411

At the Redhaven campus infrastructure group, an access switch has uplinks to two FortiSwitch distribution peers but the peers lack an approved MCLAG configuration. What is the strongest acceptance test for this change?

  1. A controlled primary-link outage moves operations to the standby link
  2. A two-tenant load test preserves the approved class treatment without leakage
  3. A lab review shows enforcement without assuming unsupported snooping on that shared port
  4. A peer failure preserves supported downstream forwarding without a Layer 2 loop

Explanation

Correct Answer

D:

The intended correction is to deploy supported MCLAG peer and inter-chassis design before activating parallel uplinks. The decisive verification is that a peer failure preserves supported downstream forwarding without a Layer 2 loop, rather than only confirming configuration was saved.

Incorrect Answers

A:

A controlled primary-link outage moves operations to the standby link. That result would test a control for this other failure: Split-interface redundancy intentionally limits active forwarding until a supported MCLAG state permits more. The question instead requires evidence for: Two physical uplinks to independent peers are not a coordinated aggregate by default. The direct outcome to verify is: A peer failure preserves supported downstream forwarding without a Layer 2 loop.

B:

At the Redhaven campus infrastructure group, a result about tenant per-port qos constraints would not show that the team corrected the failure where two physical uplinks to independent peers are not a coordinated aggregate by default.

C:

A lab review shows enforcement without assuming unsupported snooping on that shared port. That result would test a control for this other failure: The documented shared FortiSwitch port feature set does not include DHCP snooping. The question instead requires evidence for: Two physical uplinks to independent peers are not a coordinated aggregate by default. The direct outcome to verify is: A peer failure preserves supported downstream forwarding without a Layer 2 loop.

Question 412

At the Redhaven campus infrastructure group, an access switch has uplinks to two FortiSwitch distribution peers but the peers lack an approved MCLAG configuration. Which setting or practice should be reviewed in future?

  1. Audit routed management changes for unauthorized NAT
  2. Monitor MCLAG peer and member health
  3. Monitor time sync status after management network changes
  4. Review FortiGate administrator roles each quarter

Explanation

Correct Answer

B:

This control works beyond the initial remediation because it requires the team to monitor MCLAG peer and member health.

Incorrect Answers

A:

Audit routed management changes for unauthorized NAT is not the primary recurring safeguard for this problem. The team should monitor MCLAG peer and member health. For the Redhaven campus infrastructure group, the direct corrective action is to deploy supported MCLAG peer and inter-chassis design before activating parallel uplinks.

C:

The suggested preventive check is: Monitor time sync status after management network changes. Its technical scope concerns: Unsynchronized switch clocks make event correlation and certificate validation unreliable. This question asks how to sustain control over: Two physical uplinks to independent peers are not a coordinated aggregate by default. The more targeted safeguard is: Monitor MCLAG peer and member health.

D:

Review FortiGate administrator roles each quarter. That safeguard would help prevent recurrence of: Excess controller privileges allow unintended changes to managed switch configurations. The risk being reviewed here is instead: Two physical uplinks to independent peers are not a coordinated aggregate by default. The matching ongoing control is: Monitor MCLAG peer and member health.

Question 413

At the Dunbridge network security team, a redundant FortiLink aggregate connects to two switches and its operators assume standby traffic means a failed optic. Which corrective action best meets the requirement?

  1. Validate the specific FortiLink on VXLAN prerequisites and supported platform feature constraints
  2. Resize and validate the supported FortiLink management address pool or topology addressing plan
  3. Recreate or reassign supported tenant VLAN interfaces and switch-port ownership under a controlled migration
  4. Check whether the split interface is enabled and confirm the expected one-active-link topology

Explanation

Correct Answer

D:

For the Dunbridge network security team, the appropriate correction is to check whether the split interface is enabled and confirm the expected one-active-link topology. The decisive reason is that split-interface redundancy intentionally limits active forwarding until a supported MCLAG state permits more; acceptance evidence is that a controlled primary-link outage moves operations to the standby link.

Incorrect Answers

A:

The option addresses the separate situation where overlay transport requires explicit compatibility and control reachability beyond a regular copper uplink. For this case, the more appropriate response is to check whether the split interface is enabled and confirm the expected one-active-link topology. For the Dunbridge network security team, the direct corrective action is to check whether the split interface is enabled and confirm the expected one-active-link topology.

B:

The offered action is: Resize and validate the supported FortiLink management address pool or topology addressing plan. It is associated with this separate technical condition: Switch discovery and controller communication require nonconflicting usable management addresses. The actual incident concerns a different dependency: Split-interface redundancy intentionally limits active forwarding until a supported MCLAG state permits more. The corresponding change is: Check whether the split interface is enabled and confirm the expected one-active-link topology.

C:

Recreate or reassign supported tenant VLAN interfaces and switch-port ownership under a controlled migration can be useful for another FortiSwitch 7.6 administration workflow, but it leaves the immediate failure unresolved. Here the priority is to check whether the split interface is enabled and confirm the expected one-active-link topology. For the Dunbridge network security team, the direct corrective action is to check whether the split interface is enabled and confirm the expected one-active-link topology.

Question 414

At the Dunbridge network security team, a redundant FortiLink aggregate connects to two switches and its operators assume standby traffic means a failed optic. Which underlying issue most directly explains this situation?

  1. Multiple bridged management uplinks can create loops without supported topology constraints
  2. Unreviewed automatic authorization can admit a connected switch before identity and installation are checked
  3. Split-interface redundancy intentionally limits active forwarding until a supported MCLAG state permits more
  4. A stale VDOM port assignment leaves residual tenant access and operational ownership

Explanation

Correct Answer

C:

The strongest explanation is that split-interface redundancy intentionally limits active forwarding until a supported MCLAG state permits more. This accounts for the outcome and supports the action to check whether the split interface is enabled and confirm the expected one-active-link topology.

Incorrect Answers

A:

The offered principle is: Multiple bridged management uplinks can create loops without supported topology constraints. In the source material it is associated with: Multiple bridged management uplinks can create loops without supported topology constraints. This case has a different controlling cause: Split-interface redundancy intentionally limits active forwarding until a supported MCLAG state permits more. Its keyed mechanism is: Split-interface redundancy intentionally limits active forwarding until a supported MCLAG state permits more.

B:

Unreviewed automatic authorization can admit a connected switch before identity and installation are checked. That is not the mechanism that accounts for the stated failure at the Dunbridge network security team.

D:

Although a stale VDOM port assignment leaves residual tenant access and operational ownership, the presented symptoms do not support that as the primary cause; they indicate that split-interface redundancy intentionally limits active forwarding until a supported MCLAG state permits more. For the Dunbridge network security team, the direct corrective action is to check whether the split interface is enabled and confirm the expected one-active-link topology.

Question 415

At the Dunbridge network security team, a redundant FortiLink aggregate connects to two switches and its operators assume standby traffic means a failed optic. What evidence would justify considering this concern addressed?

  1. A controlled primary-link outage moves operations to the standby link
  2. A test discovers both switches over the corrected point-to-point transport
  3. A lab review shows enforcement without assuming unsupported snooping on that shared port
  4. Each tenant administrator sees and configures only ports assigned to its VDOM

Explanation

Correct Answer

A:

This tests the real business behavior: a controlled primary-link outage moves operations to the standby link. It specifically checks whether the risk that split-interface redundancy intentionally limits active forwarding until a supported MCLAG state permits more has been reduced.

Incorrect Answers

B:

The offered observation is: A test discovers both switches over the corrected point-to-point transport. It would support the separate mechanism: Mismatched provider tag EtherType can prevent expected encapsulated control traffic delivery. In this case the decisive dependency is: Split-interface redundancy intentionally limits active forwarding until a supported MCLAG state permits more. The original keyed verification is: A controlled primary-link outage moves operations to the standby link.

C:

A lab review shows enforcement without assuming unsupported snooping on that shared port. That result would test a control for this other failure: The documented shared FortiSwitch port feature set does not include DHCP snooping. The question instead requires evidence for: Split-interface redundancy intentionally limits active forwarding until a supported MCLAG state permits more. The direct outcome to verify is: A controlled primary-link outage moves operations to the standby link.

D:

The offered observation is: Each tenant administrator sees and configures only ports assigned to its VDOM. It would support the separate mechanism: Managed FortiSwitch physical port administration does not automatically follow a tenant VLAN name. In this case the decisive dependency is: Split-interface redundancy intentionally limits active forwarding until a supported MCLAG state permits more. The original keyed verification is: A controlled primary-link outage moves operations to the standby link.

Question 416

At the Dunbridge network security team, a redundant FortiLink aggregate connects to two switches and its operators assume standby traffic means a failed optic. How should the organization sustain the improvement?

  1. Review split interface behavior after changing aggregation
  2. Review L3 FortiLink limitations before adding islands
  3. Retest the shared-port feature matrix after version changes
  4. Run tenant isolation acceptance tests after shared-uplink changes

Explanation

Correct Answer

A:

The team should review split interface behavior after changing aggregation. That recurring practice targets the same weakness, namely that split-interface redundancy intentionally limits active forwarding until a supported MCLAG state permits more.

Incorrect Answers

B:

Review L3 FortiLink limitations before adding islands. That safeguard would help prevent recurrence of: FortiLink over Layer 3 does not create a continuous Layer 2 VLAN across the routed path. The risk being reviewed here is instead: Split-interface redundancy intentionally limits active forwarding until a supported MCLAG state permits more. The matching ongoing control is: Review split interface behavior after changing aggregation.

C:

That routine supports shared port security-policy support, but the relevant ongoing risk requires the team to review split interface behavior after changing aggregation. For the Dunbridge network security team, the direct corrective action is to check whether the split interface is enabled and confirm the expected one-active-link topology.

D:

Run tenant isolation acceptance tests after shared-uplink changes. That safeguard would help prevent recurrence of: Separate VLAN labels do not independently guarantee tenant Layer 3 policy isolation. The risk being reviewed here is instead: Split-interface redundancy intentionally limits active forwarding until a supported MCLAG state permits more. The matching ongoing control is: Review split interface behavior after changing aggregation.

Question 417

At the Quayford managed-network provider, two FortiSwitch devices need management connectivity across a non-Fortinet transparent wireless bridge. Which approach best resolves the described issue?

  1. Design supported FortiLink over Layer 3 with functional routing and separate local VLANs
  2. Use supported FortiLink point-to-point Layer 2 bridging and appropriate discovery handling
  3. Revoke the port export and safely reassign it only after wiping tenant access policy
  4. Create FortiGate administrative access profiles restricting switch operations to required responsibilities

Explanation

Correct Answer

B:

For the Quayford managed-network provider, the appropriate correction is to use supported FortiLink point-to-point Layer 2 bridging and appropriate discovery handling. The decisive reason is that some intermediate Layer 2 devices do not transport standard neighbor discovery frames; acceptance evidence is that both devices discover and exchange approved management and data through the bridge.

Incorrect Answers

A:

Design supported FortiLink over Layer 3 with functional routing and separate local VLANs can be useful for another FortiSwitch 7.6 administration workflow, but it leaves the immediate failure unresolved. Here the priority is to use supported FortiLink point-to-point Layer 2 bridging and appropriate discovery handling. For the Quayford managed-network provider, the direct corrective action is to use supported FortiLink point-to-point Layer 2 bridging and appropriate discovery handling.

C:

This alternative would be suitable where a stale VDOM port assignment leaves residual tenant access and operational ownership. It does not by itself resolve the need to use supported FortiLink point-to-point Layer 2 bridging and appropriate discovery handling. For the Quayford managed-network provider, the direct corrective action is to use supported FortiLink point-to-point Layer 2 bridging and appropriate discovery handling.

D:

Create FortiGate administrative access profiles restricting switch operations to required responsibilities addresses a different kind of problem: excess controller privileges allow unintended changes to managed switch configurations. Here the reported weakness is that some intermediate Layer 2 devices do not transport standard neighbor discovery frames. For the Quayford managed-network provider, the direct corrective action is to use supported FortiLink point-to-point Layer 2 bridging and appropriate discovery handling.

Question 418

At the Quayford managed-network provider, two FortiSwitch devices need management connectivity across a non-Fortinet transparent wireless bridge. Which explanation best accounts for the concern?

  1. Overlay transport requires explicit compatibility and control reachability beyond a regular copper uplink
  2. Physical port sharing and VLAN ownership across VDOMs require deliberate controller configuration
  3. An outer-tag EtherType mismatch can make customer VLAN frames unreadable across the service boundary
  4. Some intermediate Layer 2 devices do not transport standard neighbor discovery frames

Explanation

Correct Answer

D:

This identifies the root issue: some intermediate Layer 2 devices do not transport standard neighbor discovery frames. At the Quayford managed-network provider, the team should therefore use supported FortiLink point-to-point Layer 2 bridging and appropriate discovery handling.

Incorrect Answers

A:

The offered principle is: Overlay transport requires explicit compatibility and control reachability beyond a regular copper uplink. In the source material it is associated with: Overlay transport requires explicit compatibility and control reachability beyond a regular copper uplink. This case has a different controlling cause: Some intermediate Layer 2 devices do not transport standard neighbor discovery frames. Its keyed mechanism is: Some intermediate Layer 2 devices do not transport standard neighbor discovery frames.

B:

Although physical port sharing and VLAN ownership across VDOMs require deliberate controller configuration, the presented symptoms do not support that as the primary cause; they indicate that some intermediate Layer 2 devices do not transport standard neighbor discovery frames. For the Quayford managed-network provider, the direct corrective action is to use supported FortiLink point-to-point Layer 2 bridging and appropriate discovery handling.

C:

The offered principle is: An outer-tag EtherType mismatch can make customer VLAN frames unreadable across the service boundary. In the source material it is associated with: An outer-tag EtherType mismatch can make customer VLAN frames unreadable across the service boundary. This case has a different controlling cause: Some intermediate Layer 2 devices do not transport standard neighbor discovery frames. Its keyed mechanism is: Some intermediate Layer 2 devices do not transport standard neighbor discovery frames.

Question 419

At the Quayford managed-network provider, two FortiSwitch devices need management connectivity across a non-Fortinet transparent wireless bridge. Which test result best shows the requirement is met?

  1. Either peer can be disabled while the access test remains connected
  2. A test phone reaches its permitted voice subnet after policy synchronization
  3. Both devices discover and exchange approved management and data through the bridge
  4. A controlled restart retains the approved VLAN and management settings

Explanation

Correct Answer

C:

Because some intermediate Layer 2 devices do not transport standard neighbor discovery frames, the required evidence must show that both devices discover and exchange approved management and data through the bridge. A healthy endpoint status alone is insufficient.

Incorrect Answers

A:

Either peer can be disabled while the access test remains connected. That result would test a control for this other failure: Multi-chassis redundancy requires peers to exchange supported state over their inter-chassis connection. The question instead requires evidence for: Some intermediate Layer 2 devices do not transport standard neighbor discovery frames. The direct outcome to verify is: Both devices discover and exchange approved management and data through the bridge.

B:

The offered observation is: A test phone reaches its permitted voice subnet after policy synchronization. It would support the separate mechanism: A managed FortiSwitch port follows its controller configuration even when the connected phone appears physically healthy. In this case the decisive dependency is: Some intermediate Layer 2 devices do not transport standard neighbor discovery frames. The original keyed verification is: Both devices discover and exchange approved management and data through the bridge.

D:

At the Quayford managed-network provider, a result about fortiswitch standalone config persistence would not show that the team corrected the failure where some intermediate Layer 2 devices do not transport standard neighbor discovery frames.

Question 420

At the Quayford managed-network provider, two FortiSwitch devices need management connectivity across a non-Fortinet transparent wireless bridge. Which ongoing control best prevents this issue from recurring?

  1. Audit routed management changes for unauthorized NAT
  2. Document root and tenant responsibilities for VLAN changes
  3. Audit the management mode before every switch change
  4. Verify transparent bridge and FortiLink compatibility on replacement

Explanation

Correct Answer

D:

This control works beyond the initial remediation because it requires the team to verify transparent bridge and FortiLink compatibility on replacement.

Incorrect Answers

A:

That routine supports fortilink l3 nat unsupported, but the relevant ongoing risk requires the team to verify transparent bridge and FortiLink compatibility on replacement. For the Quayford managed-network provider, the direct corrective action is to use supported FortiLink point-to-point Layer 2 bridging and appropriate discovery handling.

B:

Document root and tenant responsibilities for VLAN changes. That safeguard would help prevent recurrence of: Tenant VLAN existence and FortiSwitch port export are distinct configuration requirements. The risk being reviewed here is instead: Some intermediate Layer 2 devices do not transport standard neighbor discovery frames. The matching ongoing control is: Verify transparent bridge and FortiLink compatibility on replacement.

C:

Audit the management mode before every switch change is not the primary recurring safeguard for this problem. The team should verify transparent bridge and FortiLink compatibility on replacement. For the Quayford managed-network provider, the direct corrective action is to use supported FortiLink point-to-point Layer 2 bridging and appropriate discovery handling.

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