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 37

Question 360

At the Thornfield network modernization program, a rollout team hand-configures every FortiSwitch although the environment supports FortiLink discovery and provisioning. Which ongoing control best prevents this issue from recurring?

  1. Review zero-touch profiles when sites are introduced
  2. Audit auto-authorization settings and new switch registrations
  3. Verify peer group configuration after firmware upgrades
  4. Review tenant device forecasts before increasing limits

Explanation

Correct Answer

A:

The continuing safeguard is to review zero-touch profiles when sites are introduced. It helps avoid the original condition: manual per-device setup increases configuration drift and delays consistent provisioning.

Incorrect Answers

B:

Audit auto-authorization settings and new switch registrations. That safeguard would help prevent recurrence of: Unreviewed automatic authorization can admit a connected switch before identity and installation are checked. The risk being reviewed here is instead: Manual per-device setup increases configuration drift and delays consistent provisioning. The matching ongoing control is: Review zero-touch profiles when sites are introduced.

C:

Verify peer group configuration after firmware upgrades is not the primary recurring safeguard for this problem. The team should review zero-touch profiles when sites are introduced. For the Thornfield network modernization program, the direct corrective action is to use the supported Fortinet zero-touch management process with controlled authorizations and approved port templates.

D:

Review tenant device forecasts before increasing limits. That safeguard would help prevent recurrence of: Unbounded MAC learning can strain forwarding resources and cross-tenant expectations. The risk being reviewed here is instead: Manual per-device setup increases configuration drift and delays consistent provisioning. The matching ongoing control is: Review zero-touch profiles when sites are introduced.

Question 361

At the Highbridge managed-network provider, a failed FortiSwitch is replaced with a new unit but the old serial remains tied to production port configuration. Which implementation choice best addresses the situation?

  1. Restrict supported administrative services to the approved management path and accounts
  2. Deauthorize the retired hardware and adopt the replacement through the supported managed-switch process
  3. Budget physical PoE headroom across both tenant port allocations and enforce supported priorities
  4. Use only supported per-port CoS egress queue policies and verify capability on the exact model

Explanation

Correct Answer

B:

Deauthorize the retired hardware and adopt the replacement through the supported managed-switch process is the best response because managed-switch configuration is associated with device identity and may not migrate automatically to a new serial. A focused validation would establish that the new switch receives intended VLAN and port policies while the old unit is revoked.

Incorrect Answers

A:

This alternative would be suitable where open management access from untrusted segments broadens credential attack surface. It does not by itself resolve the need to deauthorize the retired hardware and adopt the replacement through the supported managed-switch process. For the Highbridge managed-network provider, the direct corrective action is to deauthorize the retired hardware and adopt the replacement through the supported managed-switch process.

C:

The option addresses the separate situation where virtual tenant separation does not create independent physical power supplies. For this case, the more appropriate response is to deauthorize the retired hardware and adopt the replacement through the supported managed-switch process. For the Highbridge managed-network provider, the direct corrective action is to deauthorize the retired hardware and adopt the replacement through the supported managed-switch process.

D:

The offered alternative is: Use only supported per-port CoS egress queue policies and verify capability on the exact model. It addresses this separate failure mode: Not all advanced switch features are available on shared tenant ports. In the current case, the observed mechanism is: Managed-switch configuration is associated with device identity and may not migrate automatically to a new serial. The keyed action, Deauthorize the retired hardware and adopt the replacement through the supported managed-switch process., targets that condition more directly.

Question 362

At the Highbridge managed-network provider, a failed FortiSwitch is replaced with a new unit but the old serial remains tied to production port configuration. What risk should the team identify as the primary issue?

  1. Excess controller privileges allow unintended changes to managed switch configurations
  2. Multi-VDOM shared ports expose a defined subset of switch security capabilities
  3. A linear FortiLink chain has single-link failure dependencies for devices beyond the break
  4. Managed-switch configuration is associated with device identity and may not migrate automatically to a new serial

Explanation

Correct Answer

D:

The architectural weakness is that managed-switch configuration is associated with device identity and may not migrate automatically to a new serial. It can be addressed through the controlled change to deauthorize the retired hardware and adopt the replacement through the supported managed-switch process.

Incorrect Answers

A:

The offered action is: Excess controller privileges allow unintended changes to managed switch configurations. It is associated with this separate technical condition: Excess controller privileges allow unintended changes to managed switch configurations. The actual incident concerns a different dependency: Managed-switch configuration is associated with device identity and may not migrate automatically to a new serial. The corresponding change is: Managed-switch configuration is associated with device identity and may not migrate automatically to a new serial.

B:

Multi-VDOM shared ports expose a defined subset of switch security capabilities. That may occur elsewhere, but the evidence at the Highbridge managed-network provider instead points to the fact that managed-switch configuration is associated with device identity and may not migrate automatically to a new serial.

C:

The offered alternative is: A linear FortiLink chain has single-link failure dependencies for devices beyond the break. It addresses this separate failure mode: A linear FortiLink chain has single-link failure dependencies for devices beyond the break. In the current case, the observed mechanism is: Managed-switch configuration is associated with device identity and may not migrate automatically to a new serial. The keyed action, Managed-switch configuration is associated with device identity and may not migrate automatically to a new serial., targets that condition more directly.

Question 363

At the Highbridge managed-network provider, a failed FortiSwitch is replaced with a new unit but the old serial remains tied to production port configuration. What is the strongest acceptance test for this change?

  1. The new switch receives intended VLAN and port policies while the old unit is revoked
  2. Two pilot switches apply the same approved baseline while retaining permitted exceptions
  3. Either peer can be disabled while the access test remains connected
  4. The root controller sees the physical unit and tenant sees only exported resources

Explanation

Correct Answer

A:

Because managed-switch configuration is associated with device identity and may not migrate automatically to a new serial, the required evidence must show that the new switch receives intended VLAN and port policies while the old unit is revoked. A healthy endpoint status alone is insufficient.

Incorrect Answers

B:

At the Highbridge managed-network provider, a result about controller switch profile inheritance would not show that the team corrected the failure where managed-switch configuration is associated with device identity and may not migrate automatically to a new serial.

C:

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: Managed-switch configuration is associated with device identity and may not migrate automatically to a new serial. The direct outcome to verify is: The new switch receives intended VLAN and port policies while the old unit is revoked.

D:

The offered observation is: The root controller sees the physical unit and tenant sees only exported resources. It would support the separate mechanism: Physical managed FortiSwitch inventory may reside in the controlling VDOM rather than every tenant. In this case the decisive dependency is: Managed-switch configuration is associated with device identity and may not migrate automatically to a new serial. The original keyed verification is: The new switch receives intended VLAN and port policies while the old unit is revoked.

Question 364

At the Highbridge managed-network provider, a failed FortiSwitch is replaced with a new unit but the old serial remains tied to production port configuration. Which setting or practice should be reviewed in future?

  1. Monitor managed-switch PoE consumption by site
  2. Recheck cross-VDOM VLAN settings after firmware upgrades
  3. Update serial inventory after every device RMA
  4. Review tenant device forecasts before increasing limits

Explanation

Correct Answer

C:

The team should update serial inventory after every device RMA. That recurring practice targets the same weakness, namely that managed-switch configuration is associated with device identity and may not migrate automatically to a new serial.

Incorrect Answers

A:

Monitor managed-switch PoE consumption by site is not the primary recurring safeguard for this problem. The team should update serial inventory after every device RMA. For the Highbridge managed-network provider, the direct corrective action is to deauthorize the retired hardware and adopt the replacement through the supported managed-switch process.

B:

Recheck cross-VDOM VLAN settings after firmware upgrades. That safeguard would help prevent recurrence of: The GUI does not expose every cross-VDOM native VLAN assignment supported by FortiOS. The risk being reviewed here is instead: Managed-switch configuration is associated with device identity and may not migrate automatically to a new serial. The matching ongoing control is: Update serial inventory after every device RMA.

D:

Review tenant device forecasts before increasing limits. That safeguard would help prevent recurrence of: Unbounded MAC learning can strain forwarding resources and cross-tenant expectations. The risk being reviewed here is instead: Managed-switch configuration is associated with device identity and may not migrate automatically to a new serial. The matching ongoing control is: Update serial inventory after every device RMA.

Question 365

At the Brookfield branch IT department, a standalone FortiSwitch works after a change but reboots into the previous configuration. Which corrective action best meets the requirement?

  1. Save the validated running configuration to the supported persistent startup state
  2. Use supported managed-switch templates or controller policy objects for compatible site groups
  3. Use supported FortiLink point-to-point Layer 2 bridging and appropriate discovery handling
  4. Verify owning root VDOM controller scope and export the permitted resources rather than recreating the switch

Explanation

Correct Answer

A:

This is the direct FortiSwitch 7.6 administration remedy: save the validated running configuration to the supported persistent startup state. The observed risk is that unsaved changes in active configuration can disappear during restart; a passing acceptance check would show that a controlled restart retains the approved VLAN and management settings.

Incorrect Answers

B:

The offered action is: Use supported managed-switch templates or controller policy objects for compatible site groups. It is associated with this separate technical condition: Per-device changes can diverge from an approved baseline and complicate mass maintenance. The actual incident concerns a different dependency: Unsaved changes in active configuration can disappear during restart. The corresponding change is: Save the validated running configuration to the supported persistent startup state.

C:

Use supported FortiLink point-to-point Layer 2 bridging and appropriate discovery handling can be useful for another FortiSwitch 7.6 administration workflow, but it leaves the immediate failure unresolved. Here the priority is to save the validated running configuration to the supported persistent startup state. For the Brookfield branch IT department, the direct corrective action is to save the validated running configuration to the supported persistent startup state.

D:

The offered alternative is: Verify owning root VDOM controller scope and export the permitted resources rather than recreating the switch. It addresses this separate failure mode: Physical managed FortiSwitch inventory may reside in the controlling VDOM rather than every tenant. In the current case, the observed mechanism is: Unsaved changes in active configuration can disappear during restart. The keyed action, Save the validated running configuration to the supported persistent startup state., targets that condition more directly.

Question 366

At the Brookfield branch IT department, a standalone FortiSwitch works after a change but reboots into the previous configuration. Which underlying issue most directly explains this situation?

  1. Switch discovery and controller communication require nonconflicting usable management addresses
  2. Multi-chassis redundancy requires peers to exchange supported state over their inter-chassis connection
  3. Unsaved changes in active configuration can disappear during restart
  4. FortiSwitch NAC is not supported in the documented FortiLink over Layer 3 island design

Explanation

Correct Answer

C:

The strongest explanation is that unsaved changes in active configuration can disappear during restart. This accounts for the outcome and supports the action to save the validated running configuration to the supported persistent startup state.

Incorrect Answers

A:

The offered principle is: Switch discovery and controller communication require nonconflicting usable management addresses. In the source material it is associated with: Switch discovery and controller communication require nonconflicting usable management addresses. This case has a different controlling cause: Unsaved changes in active configuration can disappear during restart. Its keyed mechanism is: Unsaved changes in active configuration can disappear during restart.

B:

Multi-chassis redundancy requires peers to exchange supported state over their inter-chassis connection. That is not the mechanism that accounts for the stated failure at the Brookfield branch IT department.

D:

Although fortiSwitch NAC is not supported in the documented FortiLink over Layer 3 island design, the presented symptoms do not support that as the primary cause; they indicate that unsaved changes in active configuration can disappear during restart. For the Brookfield branch IT department, the direct corrective action is to save the validated running configuration to the supported persistent startup state.

Question 367

At the Brookfield branch IT department, a standalone FortiSwitch works after a change but reboots into the previous configuration. What evidence would justify considering this concern addressed?

  1. The approved serial number shows authorized managed status and correct assigned ports
  2. A controlled restart retains the approved VLAN and management settings
  3. A supported test topology brings the intended switch online without unsupported downstream stacking
  4. Each tenant administrator sees and configures only ports assigned to its VDOM

Explanation

Correct Answer

B:

The intended correction is to save the validated running configuration to the supported persistent startup state. The decisive verification is that a controlled restart retains the approved VLAN and management settings, rather than only confirming configuration was saved.

Incorrect Answers

A:

The approved serial number shows authorized managed status and correct assigned ports. That result would test a control for this other failure: FortiLink discovery does not itself guarantee the switch is authorized to receive configuration. The question instead requires evidence for: Unsaved changes in active configuration can disappear during restart. The direct outcome to verify is: A controlled restart retains the approved VLAN and management settings.

C:

A supported test topology brings the intended switch online without unsupported downstream stacking. That result would test a control for this other failure: The documented out-of-band mgmt-port Layer 3 mode supports a single FortiSwitch island member. The question instead requires evidence for: Unsaved changes in active configuration can disappear during restart. The direct outcome to verify is: A controlled restart retains the approved VLAN and management settings.

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: Unsaved changes in active configuration can disappear during restart. The original keyed verification is: A controlled restart retains the approved VLAN and management settings.

Question 368

At the Brookfield branch IT department, a standalone FortiSwitch works after a change but reboots into the previous configuration. How should the organization sustain the improvement?

  1. Synchronize switch port inventory after moves
  2. Recheck cross-VDOM VLAN settings after firmware upgrades
  3. Document every downstream dependency when replacing an upstream switch
  4. Require save and backup checks before closing standalone changes

Explanation

Correct Answer

D:

The needed prevention is to require save and backup checks before closing standalone changes. It directly sustains the original change to save the validated running configuration to the supported persistent startup state.

Incorrect Answers

A:

The suggested preventive check is: Synchronize switch port inventory after moves. Its technical scope concerns: Missing port identity makes correct endpoint provisioning and incident isolation harder. This question asks how to sustain control over: Unsaved changes in active configuration can disappear during restart. The more targeted safeguard is: Require save and backup checks before closing standalone changes.

B:

Recheck cross-VDOM VLAN settings after firmware upgrades. That safeguard would help prevent recurrence of: The GUI does not expose every cross-VDOM native VLAN assignment supported by FortiOS. The risk being reviewed here is instead: Unsaved changes in active configuration can disappear during restart. The matching ongoing control is: Require save and backup checks before closing standalone changes.

C:

That routine supports fortiswitch two-tier uplink dependency, but the relevant ongoing risk requires the team to require save and backup checks before closing standalone changes. For the Brookfield branch IT department, the direct corrective action is to save the validated running configuration to the supported persistent startup state.

Question 369

At the Jasperfield data network services firm, helpdesk staff receive full switch-controller rights despite needing only monitoring access. Which approach best resolves the described issue?

  1. Update managed-switch port descriptions and verify them against cabling records
  2. Use the supported single FortiGate to single FortiSwitch FortiLink topology with clear uplink role
  3. Create FortiGate administrative access profiles restricting switch operations to required responsibilities
  4. Deploy supported MCLAG peer and inter-chassis design before activating parallel uplinks

Explanation

Correct Answer

C:

This solution addresses the stated limitation: excess controller privileges allow unintended changes to managed switch configurations. Implementing it means the team should create FortiGate administrative access profiles restricting switch operations to required responsibilities, then verify that a monitor-only account can view status but cannot change port VLANs.

Incorrect Answers

A:

Update managed-switch port descriptions and verify them against cabling records can be useful for another FortiSwitch 7.6 administration workflow, but it leaves the immediate failure unresolved. Here the priority is to create FortiGate administrative access profiles restricting switch operations to required responsibilities. For the Jasperfield data network services firm, the direct corrective action is to create FortiGate administrative access profiles restricting switch operations to required responsibilities.

B:

The offered action is: Use the supported single FortiGate to single FortiSwitch FortiLink topology with clear uplink role. It is associated with this separate technical condition: A simple managed site can be operated without unnecessary high-availability interconnections. The actual incident concerns a different dependency: Excess controller privileges allow unintended changes to managed switch configurations. The corresponding change is: Create FortiGate administrative access profiles restricting switch operations to required responsibilities.

D:

Deploy supported MCLAG peer and inter-chassis design before activating parallel uplinks addresses a different kind of problem: two physical uplinks to independent peers are not a coordinated aggregate by default. Here the reported weakness is that excess controller privileges allow unintended changes to managed switch configurations. For the Jasperfield data network services firm, the direct corrective action is to create FortiGate administrative access profiles restricting switch operations to required responsibilities.

Question 370

At the Jasperfield data network services firm, helpdesk staff receive full switch-controller rights despite needing only monitoring access. Which explanation best accounts for the concern?

  1. Managed-switch configuration is associated with device identity and may not migrate automatically to a new serial
  2. A stale VDOM port assignment leaves residual tenant access and operational ownership
  3. Excess controller privileges allow unintended changes to managed switch configurations
  4. FortiLink over Layer 3 does not create a continuous Layer 2 VLAN across the routed path

Explanation

Correct Answer

C:

The situation shows that excess controller privileges allow unintended changes to managed switch configurations, rather than merely a monitoring or presentation issue. Remediation is to create FortiGate administrative access profiles restricting switch operations to required responsibilities.

Incorrect Answers

A:

The offered principle is: Managed-switch configuration is associated with device identity and may not migrate automatically to a new serial. In the source material it is associated with: Managed-switch configuration is associated with device identity and may not migrate automatically to a new serial. This case has a different controlling cause: Excess controller privileges allow unintended changes to managed switch configurations. Its keyed mechanism is: Excess controller privileges allow unintended changes to managed switch configurations.

B:

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 excess controller privileges allow unintended changes to managed switch configurations. For the Jasperfield data network services firm, the direct corrective action is to create FortiGate administrative access profiles restricting switch operations to required responsibilities.

D:

FortiLink over Layer 3 does not create a continuous Layer 2 VLAN across the routed path. That may occur elsewhere, but the evidence at the Jasperfield data network services firm instead points to the fact that excess controller privileges allow unintended changes to managed switch configurations.

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