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 39

Question 380

At the Marshport infrastructure service operator, a large switch fleet receives different security and access settings because each unit is configured manually. How should the organization sustain the improvement?

  1. Monitor managed-switch PoE consumption by site
  2. Document every downstream dependency when replacing an upstream switch
  3. Audit template drift during firmware and topology changes
  4. Exercise link-loss scenarios after ring changes

Explanation

Correct Answer

C:

The continuing safeguard is to audit template drift during firmware and topology changes. It helps avoid the original condition: per-device changes can diverge from an approved baseline and complicate mass maintenance.

Incorrect Answers

A:

The suggested preventive check is: Monitor managed-switch PoE consumption by site. Its technical scope concerns: The shared switch power limit can be exceeded even when the switch has enough physical Ethernet ports. This question asks how to sustain control over: Per-device changes can diverge from an approved baseline and complicate mass maintenance. The more targeted safeguard is: Audit template drift during firmware and topology changes.

B:

Document every downstream dependency when replacing an upstream switch. That safeguard would help prevent recurrence of: Second-tier management depends on the operational first-tier inter-switch path. The risk being reviewed here is instead: Per-device changes can diverge from an approved baseline and complicate mass maintenance. The matching ongoing control is: Audit template drift during firmware and topology changes.

D:

Exercise link-loss scenarios after ring changes. That safeguard would help prevent recurrence of: A linear FortiLink chain has single-link failure dependencies for devices beyond the break. The risk being reviewed here is instead: Per-device changes can diverge from an approved baseline and complicate mass maintenance. The matching ongoing control is: Audit template drift during firmware and topology changes.

Question 381

At the Greystone campus infrastructure group, a new downstream switch is powered before its upstream managed ISL is authorized and cannot be discovered. Which approach best resolves the described issue?

  1. Bring up and validate the supported upstream FortiLink path before onboarding dependent devices
  2. Configure its supported management IP route and permitted administrative access services
  3. Choose a supported topology or alternate guardrail because DHCP snooping is unavailable on shared ports
  4. Map customer VLAN tags and service VLAN tags using supported QinQ controls

Explanation

Correct Answer

A:

The reported facts support this change rather than a general platform replacement. The team should bring up and validate the supported upstream FortiLink path before onboarding dependent devices because downstream management discovery depends on operational and permitted upstream switching paths. A suitable test confirms that the intended downstream serial appears after the upstream connection is correctly provisioned.

Incorrect Answers

B:

The offered action is: Configure its supported management IP route and permitted administrative access services. It is associated with this separate technical condition: Management-plane routing and access controls are separate from user data forwarding. The actual incident concerns a different dependency: Downstream management discovery depends on operational and permitted upstream switching paths. The corresponding change is: Bring up and validate the supported upstream FortiLink path before onboarding dependent devices.

C:

This alternative would be suitable where the documented shared FortiSwitch port feature set does not include DHCP snooping. It does not by itself resolve the need to bring up and validate the supported upstream FortiLink path before onboarding dependent devices. For the Greystone campus infrastructure group, the direct corrective action is to bring up and validate the supported upstream FortiLink path before onboarding dependent devices.

D:

Map customer VLAN tags and service VLAN tags using supported QinQ controls addresses a different kind of problem: an outer service VLAN alone cannot classify every intended tenant inner VLAN path. Here the reported weakness is that downstream management discovery depends on operational and permitted upstream switching paths. For the Greystone campus infrastructure group, the direct corrective action is to bring up and validate the supported upstream FortiLink path before onboarding dependent devices.

Question 382

At the Greystone campus infrastructure group, a new downstream switch is powered before its upstream managed ISL is authorized and cannot be discovered. Which explanation best accounts for the concern?

  1. Downstream management discovery depends on operational and permitted upstream switching paths
  2. Per-device changes can diverge from an approved baseline and complicate mass maintenance
  3. Managed FortiSwitch physical port administration does not automatically follow a tenant VLAN name
  4. Multi-chassis redundancy requires peers to exchange supported state over their inter-chassis connection

Explanation

Correct Answer

A:

The strongest explanation is that downstream management discovery depends on operational and permitted upstream switching paths. This accounts for the outcome and supports the action to bring up and validate the supported upstream FortiLink path before onboarding dependent devices.

Incorrect Answers

B:

Although per-device changes can diverge from an approved baseline and complicate mass maintenance, the presented symptoms do not support that as the primary cause; they indicate that downstream management discovery depends on operational and permitted upstream switching paths. For the Greystone campus infrastructure group, the direct corrective action is to bring up and validate the supported upstream FortiLink path before onboarding dependent devices.

C:

The offered principle is: Managed FortiSwitch physical port administration does not automatically follow a tenant VLAN name. In the source material it is associated with: Managed FortiSwitch physical port administration does not automatically follow a tenant VLAN name. This case has a different controlling cause: Downstream management discovery depends on operational and permitted upstream switching paths. Its keyed mechanism is: Downstream management discovery depends on operational and permitted upstream switching paths.

D:

Multi-chassis redundancy requires peers to exchange supported state over their inter-chassis connection. That may occur elsewhere, but the evidence at the Greystone campus infrastructure group instead points to the fact that downstream management discovery depends on operational and permitted upstream switching paths.

Question 383

At the Greystone campus infrastructure group, a new downstream switch is powered before its upstream managed ISL is authorized and cannot be discovered. Which test result best shows the requirement is met?

  1. A monitor-only account can view status but cannot change port VLANs
  2. The root controller sees the physical unit and tenant sees only exported resources
  3. The intended downstream serial appears after the upstream connection is correctly provisioned
  4. All island members report the same intended FortiGate controller identity

Explanation

Correct Answer

C:

Because downstream management discovery depends on operational and permitted upstream switching paths, the required evidence must show that the intended downstream serial appears after the upstream connection is correctly provisioned. A healthy endpoint status alone is insufficient.

Incorrect Answers

A:

A monitor-only account can view status but cannot change port VLANs. That result would test a control for this other failure: Excess controller privileges allow unintended changes to managed switch configurations. The question instead requires evidence for: Downstream management discovery depends on operational and permitted upstream switching paths. The direct outcome to verify is: The intended downstream serial appears after the upstream connection is correctly provisioned.

B:

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: Downstream management discovery depends on operational and permitted upstream switching paths. The original keyed verification is: The intended downstream serial appears after the upstream connection is correctly provisioned.

D:

At the Greystone campus infrastructure group, a result about fortilink island split controller would not show that the team corrected the failure where downstream management discovery depends on operational and permitted upstream switching paths.

Question 384

At the Greystone campus infrastructure group, a new downstream switch is powered before its upstream managed ISL is authorized and cannot be discovered. Which ongoing control best prevents this issue from recurring?

  1. Update serial inventory after every device RMA
  2. Document root and tenant responsibilities for VLAN changes
  3. Check documented QinQ feature exclusions before new tenant policies
  4. Verify provisioning sequence in site rollout playbooks

Explanation

Correct Answer

D:

This control works beyond the initial remediation because it requires the team to verify provisioning sequence in site rollout playbooks.

Incorrect Answers

A:

That routine supports controller switch identity replacement, but the relevant ongoing risk requires the team to verify provisioning sequence in site rollout playbooks. For the Greystone campus infrastructure group, the direct corrective action is to bring up and validate the supported upstream FortiLink path before onboarding dependent devices.

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: Downstream management discovery depends on operational and permitted upstream switching paths. The matching ongoing control is: Verify provisioning sequence in site rollout playbooks.

C:

Check documented QinQ feature exclusions before new tenant policies is not the primary recurring safeguard for this problem. The team should verify provisioning sequence in site rollout playbooks. For the Greystone campus infrastructure group, the direct corrective action is to bring up and validate the supported upstream FortiLink path before onboarding dependent devices.

Question 385

At the Lindenport network security team, a standalone switch has inconsistent log timestamps after operators omit its NTP configuration. Which implementation choice best addresses the situation?

  1. Deauthorize the retired hardware and adopt the replacement through the supported managed-switch process
  2. Use only supported per-port CoS egress queue policies and verify capability on the exact model
  3. Verify owning root VDOM controller scope and export the permitted resources rather than recreating the switch
  4. Configure the supported trusted time source and validate time synchronization

Explanation

Correct Answer

D:

The primary failure mode is that unsynchronized switch clocks make event correlation and certificate validation unreliable. The proposed action directly fixes it by requiring the team to configure the supported trusted time source and validate time synchronization; afterward, verify that the switch clock matches the trusted reference and logs align with FortiGate events.

Incorrect Answers

A:

This alternative would be suitable where managed-switch configuration is associated with device identity and may not migrate automatically to a new serial. It does not by itself resolve the need to configure the supported trusted time source and validate time synchronization. For the Lindenport network security team, the direct corrective action is to configure the supported trusted time source and validate time synchronization.

B:

Use only supported per-port CoS egress queue policies and verify capability on the exact model addresses a different kind of problem: not all advanced switch features are available on shared tenant ports. Here the reported weakness is that unsynchronized switch clocks make event correlation and certificate validation unreliable. For the Lindenport network security team, the direct corrective action is to configure the supported trusted time source and validate time synchronization.

C:

The option addresses the separate situation where physical managed FortiSwitch inventory may reside in the controlling VDOM rather than every tenant. For this case, the more appropriate response is to configure the supported trusted time source and validate time synchronization. For the Lindenport network security team, the direct corrective action is to configure the supported trusted time source and validate time synchronization.

Question 386

At the Lindenport network security team, a standalone switch has inconsistent log timestamps after operators omit its NTP configuration. What risk should the team identify as the primary issue?

  1. Unsynchronized switch clocks make event correlation and certificate validation unreliable
  2. Unreviewed automatic authorization can admit a connected switch before identity and installation are checked
  3. A configured backup interface does not prove switch management survives an upstream path outage
  4. Two physical uplinks to independent peers are not a coordinated aggregate by default

Explanation

Correct Answer

A:

The situation shows that unsynchronized switch clocks make event correlation and certificate validation unreliable, rather than merely a monitoring or presentation issue. Remediation is to configure the supported trusted time source and validate time synchronization.

Incorrect Answers

B:

Unreviewed automatic authorization can admit a connected switch before identity and installation are checked. That may occur elsewhere, but the evidence at the Lindenport network security team instead points to the fact that unsynchronized switch clocks make event correlation and certificate validation unreliable.

C:

The offered alternative is: A configured backup interface does not prove switch management survives an upstream path outage. It addresses this separate failure mode: A configured backup interface does not prove switch management survives an upstream path outage. In the current case, the observed mechanism is: Unsynchronized switch clocks make event correlation and certificate validation unreliable. The keyed action, Unsynchronized switch clocks make event correlation and certificate validation unreliable., targets that condition more directly.

D:

Two physical uplinks to independent peers are not a coordinated aggregate by default. That is not the mechanism that accounts for the stated failure at the Lindenport network security team.

Question 387

At the Lindenport network security team, a standalone switch has inconsistent log timestamps after operators omit its NTP configuration. What is the strongest acceptance test for this change?

  1. The intended downstream serial appears after the upstream connection is correctly provisioned
  2. Two tenants carry the same inner VLAN ID without exchanging frames
  3. The switch clock matches the trusted reference and logs align with FortiGate events
  4. The retired tenant cannot access the port and the replacement tenant gets a clean configuration

Explanation

Correct Answer

C:

This tests the real business behavior: the switch clock matches the trusted reference and logs align with FortiGate events. It specifically checks whether the risk that unsynchronized switch clocks make event correlation and certificate validation unreliable has been reduced.

Incorrect Answers

A:

The intended downstream serial appears after the upstream connection is correctly provisioned. That result would test a control for this other failure: Downstream management discovery depends on operational and permitted upstream switching paths. The question instead requires evidence for: Unsynchronized switch clocks make event correlation and certificate validation unreliable. The direct outcome to verify is: The switch clock matches the trusted reference and logs align with FortiGate events.

B:

At the Lindenport network security team, a result about vdom qinq outer vlan would not show that the team corrected the failure where unsynchronized switch clocks make event correlation and certificate validation unreliable.

D:

The offered observation is: The retired tenant cannot access the port and the replacement tenant gets a clean configuration. It would support the separate mechanism: A stale VDOM port assignment leaves residual tenant access and operational ownership. In this case the decisive dependency is: Unsynchronized switch clocks make event correlation and certificate validation unreliable. The original keyed verification is: The switch clock matches the trusted reference and logs align with FortiGate events.

Question 388

At the Lindenport network security team, a standalone switch has inconsistent log timestamps after operators omit its NTP configuration. Which setting or practice should be reviewed in future?

  1. Monitor time sync status after management network changes
  2. Update serial inventory after every device RMA
  3. Review L3 FortiLink limitations before adding islands
  4. Document control-plane visibility versus tenant access boundaries

Explanation

Correct Answer

A:

After implementation, the team should monitor time sync status after management network changes as the appropriate recurring safeguard against the identified issue.

Incorrect Answers

B:

Update serial inventory after every device RMA. That safeguard would help prevent recurrence of: Managed-switch configuration is associated with device identity and may not migrate automatically to a new serial. The risk being reviewed here is instead: Unsynchronized switch clocks make event correlation and certificate validation unreliable. The matching ongoing control is: Monitor time sync status after management network changes.

C:

The suggested preventive check is: Review L3 FortiLink limitations before adding islands. Its technical scope concerns: FortiLink over Layer 3 does not create a continuous Layer 2 VLAN across the routed path. This question asks how to sustain control over: Unsynchronized switch clocks make event correlation and certificate validation unreliable. The more targeted safeguard is: Monitor time sync status after management network changes.

D:

Document control-plane visibility versus tenant access boundaries. That safeguard would help prevent recurrence of: Physical managed FortiSwitch inventory may reside in the controlling VDOM rather than every tenant. The risk being reviewed here is instead: Unsynchronized switch clocks make event correlation and certificate validation unreliable. The matching ongoing control is: Monitor time sync status after management network changes.

Question 389

At the Zincbridge managed-network provider, operators expose switch HTTPS and SSH management directly to guest networks for convenience. Which corrective action best meets the requirement?

  1. Configure its supported management IP route and permitted administrative access services
  2. Validate FortiGate VDOM policy and routing isolation for each tenant VLAN path
  3. Verify owning root VDOM controller scope and export the permitted resources rather than recreating the switch
  4. Restrict supported administrative services to the approved management path and accounts

Explanation

Correct Answer

D:

For the Zincbridge managed-network provider, the appropriate correction is to restrict supported administrative services to the approved management path and accounts. The decisive reason is that open management access from untrusted segments broadens credential attack surface; acceptance evidence is that guest access is blocked while an authorized administrator can manage the switch.

Incorrect Answers

A:

The option addresses the separate situation where management-plane routing and access controls are separate from user data forwarding. For this case, the more appropriate response is to restrict supported administrative services to the approved management path and accounts. For the Zincbridge managed-network provider, the direct corrective action is to restrict supported administrative services to the approved management path and accounts.

B:

The offered action is: Validate FortiGate VDOM policy and routing isolation for each tenant VLAN path. It is associated with this separate technical condition: Separate VLAN labels do not independently guarantee tenant Layer 3 policy isolation. The actual incident concerns a different dependency: Open management access from untrusted segments broadens credential attack surface. The corresponding change is: Restrict supported administrative services to the approved management path and accounts.

C:

Verify owning root VDOM controller scope and export the permitted resources rather than recreating the switch can be useful for another FortiSwitch 7.6 administration workflow, but it leaves the immediate failure unresolved. Here the priority is to restrict supported administrative services to the approved management path and accounts. For the Zincbridge managed-network provider, the direct corrective action is to restrict supported administrative services to the approved management path and accounts.

Question 390

At the Zincbridge managed-network provider, operators expose switch HTTPS and SSH management directly to guest networks for convenience. Which underlying issue most directly explains this situation?

  1. A normal LAN interface does not automatically provide the control plane expected by FortiLink discovery
  2. Physical port sharing and VLAN ownership across VDOMs require deliberate controller configuration
  3. Open management access from untrusted segments broadens credential attack surface
  4. Mixed FortiGate ownership within one routed FortiSwitch island violates the topology limitation

Explanation

Correct Answer

C:

The strongest explanation is that open management access from untrusted segments broadens credential attack surface. This accounts for the outcome and supports the action to restrict supported administrative services to the approved management path and accounts.

Incorrect Answers

A:

The offered principle is: A normal LAN interface does not automatically provide the control plane expected by FortiLink discovery. In the source material it is associated with: A normal LAN interface does not automatically provide the control plane expected by FortiLink discovery. This case has a different controlling cause: Open management access from untrusted segments broadens credential attack surface. Its keyed mechanism is: Open management access from untrusted segments broadens credential attack surface.

B:

Physical port sharing and VLAN ownership across VDOMs require deliberate controller configuration. That is not the mechanism that accounts for the stated failure at the Zincbridge managed-network provider.

D:

Although mixed FortiGate ownership within one routed FortiSwitch island violates the topology limitation, the presented symptoms do not support that as the primary cause; they indicate that open management access from untrusted segments broadens credential attack surface. For the Zincbridge managed-network provider, the direct corrective action is to restrict supported administrative services to the approved management path and accounts.

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