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 33

Question 320

At the Pinewick campus infrastructure group, a protected edge port remains inactive after an 802.1X or security violation even though its cable is healthy. How should the organization sustain the improvement?

  1. Monitor repeated violations rather than clearing the state blindly
  2. Monitor collision or CRC trends after physical changes
  3. Monitor MCLAG peer and ICL status during maintenance
  4. Revalidate static route next hops when WAN routers change

Explanation

Correct Answer

A:

The team should monitor repeated violations rather than clearing the state blindly. That recurring practice targets the same weakness, namely that a switch safety action can disable forwarding independently of physical link health.

Incorrect Answers

B:

Monitor collision or CRC trends after physical changes. That safeguard would help prevent recurrence of: A speed or duplex mismatch can create retransmissions despite an illuminated link. The risk being reviewed here is instead: A switch safety action can disable forwarding independently of physical link health. The matching ongoing control is: Monitor repeated violations rather than clearing the state blindly.

C:

That routine supports mclag inter chassis configuration, but the relevant ongoing risk requires the team to monitor repeated violations rather than clearing the state blindly. For the Pinewick campus infrastructure group, the direct corrective action is to identify the violation reason and follow the supported recovery process after correcting policy.

D:

Revalidate static route next hops when WAN routers change. That safeguard would help prevent recurrence of: A route pointing at an unreachable neighbor cannot forward outside connected subnets. The risk being reviewed here is instead: A switch safety action can disable forwarding independently of physical link health. The matching ongoing control is: Monitor repeated violations rather than clearing the state blindly.

Question 321

At the Birchhaven infrastructure service operator, an uplink shows intermittent drops and operators reboot the switch before checking interface diagnostic data. Which approach best resolves the described issue?

  1. Consult the version-specific FortiSwitch feature matrix and compatible transceiver list for the exact hardware
  2. Trace QoS classification and remarking along the FortiSwitch forwarding path
  3. Restore supported STP or a valid aggregated topology instead of creating unrestricted redundant Layer 2 paths
  4. Inspect link state transceiver counters and supported loopback or cable diagnostics first

Explanation

Correct Answer

D:

Inspect link state transceiver counters and supported loopback or cable diagnostics first is the best response because physical port faults cannot be distinguished from configuration causes by restart alone. A focused validation would establish that a targeted diagnostic identifies the failing component and forwarding recovers after repair.

Incorrect Answers

A:

Consult the version-specific FortiSwitch feature matrix and compatible transceiver list for the exact hardware can be useful for another FortiSwitch 7.6 administration workflow, but it leaves the immediate failure unresolved. Here the priority is to inspect link state transceiver counters and supported loopback or cable diagnostics first. For the Birchhaven infrastructure service operator, the direct corrective action is to inspect link state transceiver counters and supported loopback or cable diagnostics first.

B:

The offered action is: Trace QoS classification and remarking along the FortiSwitch forwarding path. It is associated with this separate technical condition: A later hop can undo correct ingress classifications and move packets to the wrong class. The actual incident concerns a different dependency: Physical port faults cannot be distinguished from configuration causes by restart alone. The corresponding change is: Inspect link state transceiver counters and supported loopback or cable diagnostics first.

C:

This alternative would be suitable where parallel unmanaged forwarding paths can cause persistent Ethernet loops. It does not by itself resolve the need to inspect link state transceiver counters and supported loopback or cable diagnostics first. For the Birchhaven infrastructure service operator, the direct corrective action is to inspect link state transceiver counters and supported loopback or cable diagnostics first.

Question 322

At the Birchhaven infrastructure service operator, an uplink shows intermittent drops and operators reboot the switch before checking interface diagnostic data. Which explanation best accounts for the concern?

  1. A speed or duplex mismatch can create retransmissions despite an illuminated link
  2. The same department traffic can enter different broadcast domains when trunk identifiers disagree
  3. Physical port faults cannot be distinguished from configuration causes by restart alone
  4. Configured intent may not match the route actually selected for forwarding

Explanation

Correct Answer

C:

The situation shows that physical port faults cannot be distinguished from configuration causes by restart alone, rather than merely a monitoring or presentation issue. Remediation is to inspect link state transceiver counters and supported loopback or cable diagnostics first.

Incorrect Answers

A:

The offered principle is: A speed or duplex mismatch can create retransmissions despite an illuminated link. In the source material it is associated with: A speed or duplex mismatch can create retransmissions despite an illuminated link. This case has a different controlling cause: Physical port faults cannot be distinguished from configuration causes by restart alone. Its keyed mechanism is: Physical port faults cannot be distinguished from configuration causes by restart alone.

B:

Although the same department traffic can enter different broadcast domains when trunk identifiers disagree, the presented symptoms do not support that as the primary cause; they indicate that physical port faults cannot be distinguished from configuration causes by restart alone. For the Birchhaven infrastructure service operator, the direct corrective action is to inspect link state transceiver counters and supported loopback or cable diagnostics first.

D:

Configured intent may not match the route actually selected for forwarding. That may occur elsewhere, but the evidence at the Birchhaven infrastructure service operator instead points to the fact that physical port faults cannot be distinguished from configuration causes by restart alone.

Question 323

At the Birchhaven infrastructure service operator, an uplink shows intermittent drops and operators reboot the switch before checking interface diagnostic data. Which test result best shows the requirement is met?

  1. A targeted diagnostic identifies the failing component and forwarding recovers after repair
  2. A test storm is bounded while ordinary ARP and DHCP still succeed
  3. All planned member ports enter the active trunk and survive one-link loss
  4. A staged ring test retains switch management and does not form a loop

Explanation

Correct Answer

A:

At the Birchhaven infrastructure service operator, evidence that a targeted diagnostic identifies the failing component and forwarding recovers after repair directly validates the correction, instead of testing a neighboring service.

Incorrect Answers

B:

The offered observation is: A test storm is bounded while ordinary ARP and DHCP still succeed. It would support the separate mechanism: Excess broadcasts can consume shared switching bandwidth and CPU resources. In this case the decisive dependency is: Physical port faults cannot be distinguished from configuration causes by restart alone. The original keyed verification is: A targeted diagnostic identifies the failing component and forwarding recovers after repair.

C:

All planned member ports enter the active trunk and survive one-link loss. That result would test a control for this other failure: Mismatched LACP negotiation can exclude ports from the intended logical trunk. The question instead requires evidence for: Physical port faults cannot be distinguished from configuration causes by restart alone. The direct outcome to verify is: A targeted diagnostic identifies the failing component and forwarding recovers after repair.

D:

At the Birchhaven infrastructure service operator, a result about stp fortilink managed topology would not show that the team corrected the failure where physical port faults cannot be distinguished from configuration causes by restart alone.

Question 324

At the Birchhaven infrastructure service operator, an uplink shows intermittent drops and operators reboot the switch before checking interface diagnostic data. Which ongoing control best prevents this issue from recurring?

  1. Maintain a supported optics and fiber inventory
  2. Reevaluate protocol selector mappings after industrial firmware upgrades
  3. Trend port health and hardware errors before the next outage
  4. Document the control and failure domains of each stack member

Explanation

Correct Answer

C:

After implementation, the team should trend port health and hardware errors before the next outage as the appropriate recurring safeguard against the identified issue.

Incorrect Answers

A:

That routine supports sfp wavelength pairing, but the relevant ongoing risk requires the team to trend port health and hardware errors before the next outage. For the Birchhaven infrastructure service operator, the direct corrective action is to inspect link state transceiver counters and supported loopback or cable diagnostics first.

B:

Reevaluate protocol selector mappings after industrial firmware upgrades. That safeguard would help prevent recurrence of: Simple native VLAN handling cannot distinguish service traffic by defined protocol selectors. The risk being reviewed here is instead: Physical port faults cannot be distinguished from configuration causes by restart alone. The matching ongoing control is: Trend port health and hardware errors before the next outage.

D:

Document the control and failure domains of each stack member. That safeguard would help prevent recurrence of: FortiGate manages every member separately even when the switches form one Layer 2 managed stack. The risk being reviewed here is instead: Physical port faults cannot be distinguished from configuration causes by restart alone. The matching ongoing control is: Trend port health and hardware errors before the next outage.

Question 325

At the Oakport enterprise network team, a team configures FortiSwitch ports directly while the FortiGate controller later overwrites the changes. Which implementation choice best addresses the situation?

  1. Create FortiGate administrative access profiles restricting switch operations to required responsibilities
  2. Make persistent managed-switch configuration through the owning FortiGate switch controller instead of local CLI
  3. Rework the LAG to the supported single intermediary or supported alternative topology
  4. Recreate or reassign supported tenant VLAN interfaces and switch-port ownership under a controlled migration

Explanation

Correct Answer

B:

Make persistent managed-switch configuration through the owning FortiGate switch controller instead of local CLI is the best response because a FortiLink-managed FortiSwitch receives authoritative configuration from its FortiGate controller. A focused validation would establish that the setting persists after synchronization and a controlled switch restart.

Incorrect Answers

A:

This alternative would be suitable where excess controller privileges allow unintended changes to managed switch configurations. It does not by itself resolve the need to make persistent managed-switch configuration through the owning FortiGate switch controller instead of local CLI. For the Oakport enterprise network team, the direct corrective action is to make persistent managed-switch configuration through the owning FortiGate switch controller instead of local CLI.

C:

The option addresses the separate situation where the documented Layer 3 FortiLink in-band LAG cannot span separate intermediary routers. For this case, the more appropriate response is to make persistent managed-switch configuration through the owning FortiGate switch controller instead of local CLI. For the Oakport enterprise network team, the direct corrective action is to make persistent managed-switch configuration through the owning FortiGate switch controller instead of local CLI.

D:

The offered alternative is: Recreate or reassign supported tenant VLAN interfaces and switch-port ownership under a controlled migration. It addresses this separate failure mode: Changing VDOM ownership can leave obsolete VLAN references and inaccessible management objects. In the current case, the observed mechanism is: A FortiLink-managed FortiSwitch receives authoritative configuration from its FortiGate controller. The keyed action, Make persistent managed-switch configuration through the owning FortiGate switch controller instead of local CLI., targets that condition more directly.

Question 326

At the Oakport enterprise network team, a team configures FortiSwitch ports directly while the FortiGate controller later overwrites the changes. What risk should the team identify as the primary issue?

  1. Excess controller privileges allow unintended changes to managed switch configurations
  2. A FortiLink-managed FortiSwitch receives authoritative configuration from its FortiGate controller
  3. The GUI does not expose every cross-VDOM native VLAN assignment supported by FortiOS
  4. Changing VDOM ownership can leave obsolete VLAN references and inaccessible management objects

Explanation

Correct Answer

B:

This identifies the root issue: a FortiLink-managed FortiSwitch receives authoritative configuration from its FortiGate controller. At the Oakport enterprise network team, the team should therefore make persistent managed-switch configuration through the owning FortiGate switch controller instead of local CLI.

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: A FortiLink-managed FortiSwitch receives authoritative configuration from its FortiGate controller. The corresponding change is: A FortiLink-managed FortiSwitch receives authoritative configuration from its FortiGate controller.

C:

The offered alternative is: The GUI does not expose every cross-VDOM native VLAN assignment supported by FortiOS. It addresses this separate failure mode: The GUI does not expose every cross-VDOM native VLAN assignment supported by FortiOS. In the current case, the observed mechanism is: A FortiLink-managed FortiSwitch receives authoritative configuration from its FortiGate controller. The keyed action, A FortiLink-managed FortiSwitch receives authoritative configuration from its FortiGate controller., targets that condition more directly.

D:

Changing VDOM ownership can leave obsolete VLAN references and inaccessible management objects. That is not the mechanism that accounts for the stated failure at the Oakport enterprise network team.

Question 327

At the Oakport enterprise network team, a team configures FortiSwitch ports directly while the FortiGate controller later overwrites the changes. What is the strongest acceptance test for this change?

  1. The intended downstream serial appears after the upstream connection is correctly provisioned
  2. The setting persists after synchronization and a controlled switch restart
  3. The tenant retains permitted connectivity and no orphaned port allocation remains
  4. A tenant endpoint gets its authorized subnet from the correct exported port

Explanation

Correct Answer

B:

The team can confirm the fix by showing that the setting persists after synchronization and a controlled switch restart. This aligns with the corrective design to make persistent managed-switch configuration through the owning FortiGate switch controller instead of local CLI.

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: A FortiLink-managed FortiSwitch receives authoritative configuration from its FortiGate controller. The direct outcome to verify is: The setting persists after synchronization and a controlled switch restart.

C:

The tenant retains permitted connectivity and no orphaned port allocation remains. That result would test a control for this other failure: Changing VDOM ownership can leave obsolete VLAN references and inaccessible management objects. The question instead requires evidence for: A FortiLink-managed FortiSwitch receives authoritative configuration from its FortiGate controller. The direct outcome to verify is: The setting persists after synchronization and a controlled switch restart.

D:

The offered observation is: A tenant endpoint gets its authorized subnet from the correct exported port. It would support the separate mechanism: Tenant VLAN existence and FortiSwitch port export are distinct configuration requirements. In this case the decisive dependency is: A FortiLink-managed FortiSwitch receives authoritative configuration from its FortiGate controller. The original keyed verification is: The setting persists after synchronization and a controlled switch restart.

Question 328

At the Oakport enterprise network team, a team configures FortiSwitch ports directly while the FortiGate controller later overwrites the changes. Which setting or practice should be reviewed in future?

  1. Monitor time sync status after management network changes
  2. Audit service and customer tag assignments during onboarding
  3. Validate port-specific topology constraints before branch construction
  4. Audit the management mode before every switch change

Explanation

Correct Answer

D:

For the Oakport enterprise network team, this maintenance action preserves the fix: audit the management mode before every switch change. It should be revisited as the workload evolves.

Incorrect Answers

A:

Monitor time sync status after management network changes is not the primary recurring safeguard for this problem. The team should audit the management mode before every switch change. For the Oakport enterprise network team, the direct corrective action is to make persistent managed-switch configuration through the owning FortiGate switch controller instead of local CLI.

B:

Audit service and customer tag assignments during onboarding. That safeguard would help prevent recurrence of: Overlapping customer VLAN IDs require a segregating outer service tag across shared infrastructure. The risk being reviewed here is instead: A FortiLink-managed FortiSwitch receives authoritative configuration from its FortiGate controller. The matching ongoing control is: Audit the management mode before every switch change.

C:

The suggested preventive check is: Validate port-specific topology constraints before branch construction. Its technical scope concerns: The documented out-of-band mgmt-port Layer 3 mode supports a single FortiSwitch island member. This question asks how to sustain control over: A FortiLink-managed FortiSwitch receives authoritative configuration from its FortiGate controller. The more targeted safeguard is: Audit the management mode before every switch change.

Question 329

At the Claremont network modernization program, a newly cabled FortiSwitch is discovered by FortiGate but stays unauthorized and does not receive production VLANs. Which corrective action best meets the requirement?

  1. Use supported managed-switch templates or controller policy objects for compatible site groups
  2. Provide a supported non-NAT routed management path for the FortiLink over Layer 3 deployment
  3. Rework the LAG to the supported single intermediary or supported alternative topology
  4. Authorize the intended switch serial number through the FortiGate controller after confirming physical identity

Explanation

Correct Answer

D:

For the Claremont network modernization program, the appropriate correction is to authorize the intended switch serial number through the FortiGate controller after confirming physical identity. The decisive reason is that fortiLink discovery does not itself guarantee the switch is authorized to receive configuration; acceptance evidence is that the approved serial number shows authorized managed status and correct assigned ports.

Incorrect Answers

A:

The option addresses the separate situation where per-device changes can diverge from an approved baseline and complicate mass maintenance. For this case, the more appropriate response is to authorize the intended switch serial number through the FortiGate controller after confirming physical identity. For the Claremont network modernization program, the direct corrective action is to authorize the intended switch serial number through the FortiGate controller after confirming physical identity.

B:

The offered action is: Provide a supported non-NAT routed management path for the FortiLink over Layer 3 deployment. It is associated with this separate technical condition: NAT between FortiSwitch and FortiGate is not supported for FortiLink Layer 3 management. The actual incident concerns a different dependency: FortiLink discovery does not itself guarantee the switch is authorized to receive configuration. The corresponding change is: Authorize the intended switch serial number through the FortiGate controller after confirming physical identity.

C:

Rework the LAG to the supported single intermediary or supported alternative topology can be useful for another FortiSwitch 7.6 administration workflow, but it leaves the immediate failure unresolved. Here the priority is to authorize the intended switch serial number through the FortiGate controller after confirming physical identity. For the Claremont network modernization program, the direct corrective action is to authorize the intended switch serial number through the FortiGate controller after confirming physical identity.

Question 330

At the Claremont network modernization program, a newly cabled FortiSwitch is discovered by FortiGate but stays unauthorized and does not receive production VLANs. Which underlying issue most directly explains this situation?

  1. A FortiLink-managed FortiSwitch receives authoritative configuration from its FortiGate controller
  2. A port exported to a pool may need a tenant claim step before use
  3. FortiLink discovery does not itself guarantee the switch is authorized to receive configuration
  4. A stale VDOM port assignment leaves residual tenant access and operational ownership

Explanation

Correct Answer

C:

The strongest explanation is that fortiLink discovery does not itself guarantee the switch is authorized to receive configuration. This accounts for the outcome and supports the action to authorize the intended switch serial number through the FortiGate controller after confirming physical identity.

Incorrect Answers

A:

The offered principle is: A FortiLink-managed FortiSwitch receives authoritative configuration from its FortiGate controller. In the source material it is associated with: A FortiLink-managed FortiSwitch receives authoritative configuration from its FortiGate controller. This case has a different controlling cause: FortiLink discovery does not itself guarantee the switch is authorized to receive configuration. Its keyed mechanism is: FortiLink discovery does not itself guarantee the switch is authorized to receive configuration.

B:

A port exported to a pool may need a tenant claim step before use. That is not the mechanism that accounts for the stated failure at the Claremont network modernization program.

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 fortiLink discovery does not itself guarantee the switch is authorized to receive configuration. For the Claremont network modernization program, the direct corrective action is to authorize the intended switch serial number through the FortiGate controller after confirming physical identity.

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