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 9

Question 80

At the Northport campus infrastructure group, an operations team assumes every attached endpoint honors LLDP-MED voice network policies. How should the organization sustain the improvement?

  1. Reconcile neighbor inventories during scheduled patch-panel audits
  2. Maintain an inventory of endpoint discovery and policy capabilities
  3. Review uplink capacity and discovery state after topology expansion
  4. Compare uplink profiles with an approved baseline before cabling changes

Explanation

Correct Answer

B:

For the Northport campus infrastructure group, this maintenance action preserves the fix: maintain an inventory of endpoint discovery and policy capabilities. It should be revisited as the workload evolves.

Incorrect Answers

A:

The suggested preventive check is: Reconcile neighbor inventories during scheduled patch-panel audits. Its technical scope concerns: Port labels may become stale when cables move and must be reconciled with observed neighbors. This question asks how to sustain control over: Ordinary LLDP support does not prove an endpoint applies LLDP-MED network policy TLVs. The more targeted safeguard is: Maintain an inventory of endpoint discovery and policy capabilities.

C:

That routine supports two tier managed topology, but the relevant ongoing risk requires the team to maintain an inventory of endpoint discovery and policy capabilities. For the Northport campus infrastructure group, the direct corrective action is to verify LLDP-MED support and use an approved alternate assignment method for devices without that capability.

D:

Compare uplink profiles with an approved baseline before cabling changes. That safeguard would help prevent recurrence of: An access-style port assignment can discard tagged traffic expected by upstream switches. The risk being reviewed here is instead: Ordinary LLDP support does not prove an endpoint applies LLDP-MED network policy TLVs. The matching ongoing control is: Maintain an inventory of endpoint discovery and policy capabilities.

Question 81

At the Maplehaven infrastructure service operator, a network inventory loses neighbor topology after hardening changes suppress LLDP on infrastructure ports. Which approach best resolves the described issue?

  1. Apply supported ingress rate limiting or policing to the guest traffic class with appropriate thresholds
  2. Enable approved LLDP transmit and receive on required trusted infrastructure interfaces
  3. Enable supported edge-port protection such as BPDU guard where downstream switches are prohibited
  4. Inspect link state transceiver counters and supported loopback or cable diagnostics first

Explanation

Correct Answer

B:

For the Maplehaven infrastructure service operator, the appropriate correction is to enable approved LLDP transmit and receive on required trusted infrastructure interfaces. The decisive reason is that neighbor discovery cannot build topology when needed LLDP frames are not transmitted or accepted; acceptance evidence is that the correct adjacent chassis and port appear in the discovery table.

Incorrect Answers

A:

Apply supported ingress rate limiting or policing to the guest traffic class with appropriate thresholds can be useful for another FortiSwitch 7.6 administration workflow, but it leaves the immediate failure unresolved. Here the priority is to enable approved LLDP transmit and receive on required trusted infrastructure interfaces. For the Maplehaven infrastructure service operator, the direct corrective action is to enable approved LLDP transmit and receive on required trusted infrastructure interfaces.

C:

This alternative would be suitable where unexpected bridge protocol frames on an edge port indicate a possible unauthorized loop. It does not by itself resolve the need to enable approved LLDP transmit and receive on required trusted infrastructure interfaces. For the Maplehaven infrastructure service operator, the direct corrective action is to enable approved LLDP transmit and receive on required trusted infrastructure interfaces.

D:

Inspect link state transceiver counters and supported loopback or cable diagnostics first addresses a different kind of problem: physical port faults cannot be distinguished from configuration causes by restart alone. Here the reported weakness is that neighbor discovery cannot build topology when needed LLDP frames are not transmitted or accepted. For the Maplehaven infrastructure service operator, the direct corrective action is to enable approved LLDP transmit and receive on required trusted infrastructure interfaces.

Question 82

At the Maplehaven infrastructure service operator, a network inventory loses neighbor topology after hardening changes suppress LLDP on infrastructure ports. Which explanation best accounts for the concern?

  1. Unrestricted low-priority demand can fill shared switch buffers during contention
  2. Neighbor discovery cannot build topology when needed LLDP frames are not transmitted or accepted
  3. IGMP snooping in one VLAN does not build a routed multicast path between subnet boundaries
  4. Physical port faults cannot be distinguished from configuration causes by restart alone

Explanation

Correct Answer

B:

The problem stems from the fact that neighbor discovery cannot build topology when needed LLDP frames are not transmitted or accepted. A correct solution would enable approved LLDP transmit and receive on required trusted infrastructure interfaces and check that the correct adjacent chassis and port appear in the discovery table.

Incorrect Answers

A:

The offered principle is: Unrestricted low-priority demand can fill shared switch buffers during contention. In the source material it is associated with: Unrestricted low-priority demand can fill shared switch buffers during contention. This case has a different controlling cause: Neighbor discovery cannot build topology when needed LLDP frames are not transmitted or accepted. Its keyed mechanism is: Neighbor discovery cannot build topology when needed LLDP frames are not transmitted or accepted.

C:

The offered principle is: IGMP snooping in one VLAN does not build a routed multicast path between subnet boundaries. In the source material it is associated with: IGMP snooping in one VLAN does not build a routed multicast path between subnet boundaries. This case has a different controlling cause: Neighbor discovery cannot build topology when needed LLDP frames are not transmitted or accepted. Its keyed mechanism is: Neighbor discovery cannot build topology when needed LLDP frames are not transmitted or accepted.

D:

Physical port faults cannot be distinguished from configuration causes by restart alone. That may occur elsewhere, but the evidence at the Maplehaven infrastructure service operator instead points to the fact that neighbor discovery cannot build topology when needed LLDP frames are not transmitted or accepted.

Question 83

At the Maplehaven infrastructure service operator, a network inventory loses neighbor topology after hardening changes suppress LLDP on infrastructure ports. Which test result best shows the requirement is met?

  1. The correct adjacent chassis and port appear in the discovery table
  2. Observed LLDP chassis and port identifiers match the verified cable map
  3. A controlled power limit preserves critical phones and sheds approved lower-priority loads
  4. A targeted diagnostic identifies the failing component and forwarding recovers after repair

Explanation

Correct Answer

A:

At the Maplehaven infrastructure service operator, evidence that the correct adjacent chassis and port appear in the discovery table directly validates the correction, instead of testing a neighboring service.

Incorrect Answers

B:

The offered observation is: Observed LLDP chassis and port identifiers match the verified cable map. It would support the separate mechanism: Port labels may become stale when cables move and must be reconciled with observed neighbors. In this case the decisive dependency is: Neighbor discovery cannot build topology when needed LLDP frames are not transmitted or accepted. The original keyed verification is: The correct adjacent chassis and port appear in the discovery table.

C:

A controlled power limit preserves critical phones and sheds approved lower-priority loads. That result would test a control for this other failure: Default power allocation order may not protect the most important devices during shortage. The question instead requires evidence for: Neighbor discovery cannot build topology when needed LLDP frames are not transmitted or accepted. The direct outcome to verify is: The correct adjacent chassis and port appear in the discovery table.

D:

At the Maplehaven infrastructure service operator, a result about loopback test and port health would not show that the team corrected the failure where neighbor discovery cannot build topology when needed LLDP frames are not transmitted or accepted.

Question 84

At the Maplehaven infrastructure service operator, a network inventory loses neighbor topology after hardening changes suppress LLDP on infrastructure ports. Which ongoing control best prevents this issue from recurring?

  1. Test discovery paths before introducing inline desk devices
  2. Reassess loop-control compatibility after adding switch models
  3. Retest root guard on distribution boundary ports after cabling changes
  4. Check LLDP operational status during interface template reviews

Explanation

Correct Answer

D:

This control works beyond the initial remediation because it requires the team to check LLDP operational status during interface template reviews.

Incorrect Answers

A:

That routine supports voice vlan via lldp link mismatch, but the relevant ongoing risk requires the team to check LLDP operational status during interface template reviews. For the Maplehaven infrastructure service operator, the direct corrective action is to enable approved LLDP transmit and receive on required trusted infrastructure interfaces.

B:

Reassess loop-control compatibility after adding switch models. That safeguard would help prevent recurrence of: Redundant physical links need controlled forwarding to prevent Layer 2 loops. The risk being reviewed here is instead: Neighbor discovery cannot build topology when needed LLDP frames are not transmitted or accepted. The matching ongoing control is: Check LLDP operational status during interface template reviews.

C:

Retest root guard on distribution boundary ports after cabling changes is not the primary recurring safeguard for this problem. The team should check LLDP operational status during interface template reviews. For the Maplehaven infrastructure service operator, the direct corrective action is to enable approved LLDP transmit and receive on required trusted infrastructure interfaces.

Question 85

At the Ashbourne enterprise network team, network staff claim their voice priority rule works but cannot show queue traffic or drops during a busy period. Which implementation choice best addresses the situation?

  1. Map approved 802.1p CoS priorities to supported FortiSwitch traffic classes and egress queues
  2. Use supported loop guard protection or correct the failing link to avoid unsafe forwarding
  3. Identify the violation reason and follow the supported recovery process after correcting policy
  4. Inspect FortiSwitch QoS class counters and egress scheduling under representative load

Explanation

Correct Answer

D:

The primary failure mode is that a saved QoS policy does not prove that the intended packets actually match its queue. The proposed action directly fixes it by requiring the team to inspect FortiSwitch QoS class counters and egress scheduling under representative load; afterward, verify that observed voice packets use the assigned class with acceptable loss and delay.

Incorrect Answers

A:

This alternative would be suitable where an 802.1Q priority field does not guarantee desired scheduling without a matching QoS policy. It does not by itself resolve the need to inspect FortiSwitch QoS class counters and egress scheduling under representative load. For the Ashbourne enterprise network team, the direct corrective action is to inspect FortiSwitch QoS class counters and egress scheduling under representative load.

B:

Use supported loop guard protection or correct the failing link to avoid unsafe forwarding addresses a different kind of problem: a unidirectional control-plane failure can make a redundant path appear safe when it is not. Here the reported weakness is that a saved QoS policy does not prove that the intended packets actually match its queue. For the Ashbourne enterprise network team, the direct corrective action is to inspect FortiSwitch QoS class counters and egress scheduling under representative load.

C:

The option addresses the separate situation where a switch safety action can disable forwarding independently of physical link health. For this case, the more appropriate response is to inspect FortiSwitch QoS class counters and egress scheduling under representative load. For the Ashbourne enterprise network team, the direct corrective action is to inspect FortiSwitch QoS class counters and egress scheduling under representative load.

Question 86

At the Ashbourne enterprise network team, network staff claim their voice priority rule works but cannot show queue traffic or drops during a busy period. What risk should the team identify as the primary issue?

  1. Link availability alone cannot establish whether the powered endpoint receives sufficient negotiated watts
  2. A saved QoS policy does not prove that the intended packets actually match its queue
  3. One spanning tree forwarding topology cannot distribute different VLAN groups over selected independent paths
  4. An available Ethernet port does not mean the power supply has spare PoE capacity

Explanation

Correct Answer

B:

This identifies the root issue: a saved QoS policy does not prove that the intended packets actually match its queue. At the Ashbourne enterprise network team, the team should therefore inspect FortiSwitch QoS class counters and egress scheduling under representative load.

Incorrect Answers

A:

The offered action is: Link availability alone cannot establish whether the powered endpoint receives sufficient negotiated watts. It is associated with this separate technical condition: Link availability alone cannot establish whether the powered endpoint receives sufficient negotiated watts. The actual incident concerns a different dependency: A saved QoS policy does not prove that the intended packets actually match its queue. The corresponding change is: A saved QoS policy does not prove that the intended packets actually match its queue.

C:

The offered alternative is: One spanning tree forwarding topology cannot distribute different VLAN groups over selected independent paths. It addresses this separate failure mode: One spanning tree forwarding topology cannot distribute different VLAN groups over selected independent paths. In the current case, the observed mechanism is: A saved QoS policy does not prove that the intended packets actually match its queue. The keyed action, A saved QoS policy does not prove that the intended packets actually match its queue., targets that condition more directly.

D:

An available Ethernet port does not mean the power supply has spare PoE capacity. That is not the mechanism that accounts for the stated failure at the Ashbourne enterprise network team.

Question 87

At the Ashbourne enterprise network team, network staff claim their voice priority rule works but cannot show queue traffic or drops during a busy period. What is the strongest acceptance test for this change?

  1. Observed voice packets use the assigned class with acceptable loss and delay
  2. A capture at the far end shows approved DSCP values preserved
  3. The known device enters its approved VLAN and an unknown MAC follows the fallback policy
  4. All approved breakout child interfaces come up at their target speeds

Explanation

Correct Answer

A:

Because a saved QoS policy does not prove that the intended packets actually match its queue, the required evidence must show that observed voice packets use the assigned class with acceptable loss and delay. A healthy endpoint status alone is insufficient.

Incorrect Answers

B:

At the Ashbourne enterprise network team, a result about egress dscp preservation would not show that the team corrected the failure where a saved QoS policy does not prove that the intended packets actually match its queue.

C:

The known device enters its approved VLAN and an unknown MAC follows the fallback policy. That result would test a control for this other failure: A MAC classification mismatch can override the VLAN intended for a known endpoint. The question instead requires evidence for: A saved QoS policy does not prove that the intended packets actually match its queue. The direct outcome to verify is: Observed voice packets use the assigned class with acceptable loss and delay.

D:

The offered observation is: All approved breakout child interfaces come up at their target speeds. It would support the separate mechanism: Not every physical port supports subdivision into the requested lanes and speeds. In this case the decisive dependency is: A saved QoS policy does not prove that the intended packets actually match its queue. The original keyed verification is: Observed voice packets use the assigned class with acceptable loss and delay.

Question 88

At the Ashbourne enterprise network team, network staff claim their voice priority rule works but cannot show queue traffic or drops during a busy period. Which setting or practice should be reviewed in future?

  1. Trend per-port PoE consumption when phone models are upgraded
  2. Trend priority queue occupancy and packet drops each month
  3. Prevent disabling STP outside reviewed topology designs
  4. Retest patch leads during closet maintenance

Explanation

Correct Answer

B:

This control works beyond the initial remediation because it requires the team to trend priority queue occupancy and packet drops each month.

Incorrect Answers

A:

Trend per-port PoE consumption when phone models are upgraded is not the primary recurring safeguard for this problem. The team should trend priority queue occupancy and packet drops each month. For the Ashbourne enterprise network team, the direct corrective action is to inspect FortiSwitch QoS class counters and egress scheduling under representative load.

C:

The suggested preventive check is: Prevent disabling STP outside reviewed topology designs. Its technical scope concerns: Parallel unmanaged forwarding paths can cause persistent Ethernet loops. This question asks how to sustain control over: A saved QoS policy does not prove that the intended packets actually match its queue. The more targeted safeguard is: Trend priority queue occupancy and packet drops each month.

D:

Retest patch leads during closet maintenance. That safeguard would help prevent recurrence of: Gigabit copper Ethernet needs correctly functioning cable pairs and termination. The risk being reviewed here is instead: A saved QoS policy does not prove that the intended packets actually match its queue. The matching ongoing control is: Trend priority queue occupancy and packet drops each month.

Question 89

At the Quayside network modernization program, a guest uplink creates sustained bursts that crowd out approved office workloads. Which corrective action best meets the requirement?

  1. Rebalance supported scheduling weights and priority allocation to protect necessary traffic classes
  2. Apply the appropriate supported edge-port behavior to true endpoint-only interfaces
  3. Enable supported edge-port protection such as BPDU guard where downstream switches are prohibited
  4. Apply supported ingress rate limiting or policing to the guest traffic class with appropriate thresholds

Explanation

Correct Answer

D:

For the Quayside network modernization program, the appropriate correction is to apply supported ingress rate limiting or policing to the guest traffic class with appropriate thresholds. The decisive reason is that unrestricted low-priority demand can fill shared switch buffers during contention; acceptance evidence is that a controlled burst is limited without disrupting baseline business flows.

Incorrect Answers

A:

The option addresses the separate situation where overly broad strict priority classification can prevent lower queues receiving service. For this case, the more appropriate response is to apply supported ingress rate limiting or policing to the guest traffic class with appropriate thresholds. For the Quayside network modernization program, the direct corrective action is to apply supported ingress rate limiting or policing to the guest traffic class with appropriate thresholds.

B:

The offered action is: Apply the appropriate supported edge-port behavior to true endpoint-only interfaces. It is associated with this separate technical condition: A non-edge STP transition may delay client connectivity even when no downstream bridge exists. The actual incident concerns a different dependency: Unrestricted low-priority demand can fill shared switch buffers during contention. The corresponding change is: Apply supported ingress rate limiting or policing to the guest traffic class with appropriate thresholds.

C:

Enable supported edge-port protection such as BPDU guard where downstream switches are prohibited can be useful for another FortiSwitch 7.6 administration workflow, but it leaves the immediate failure unresolved. Here the priority is to apply supported ingress rate limiting or policing to the guest traffic class with appropriate thresholds. For the Quayside network modernization program, the direct corrective action is to apply supported ingress rate limiting or policing to the guest traffic class with appropriate thresholds.

Question 90

At the Quayside network modernization program, a guest uplink creates sustained bursts that crowd out approved office workloads. Which underlying issue most directly explains this situation?

  1. A saved QoS policy does not prove that the intended packets actually match its queue
  2. Incompatible speed configuration can prevent stable physical link negotiation
  3. Unrestricted low-priority demand can fill shared switch buffers during contention
  4. A speed or duplex mismatch can create retransmissions despite an illuminated link

Explanation

Correct Answer

C:

The strongest explanation is that unrestricted low-priority demand can fill shared switch buffers during contention. This accounts for the outcome and supports the action to apply supported ingress rate limiting or policing to the guest traffic class with appropriate thresholds.

Incorrect Answers

A:

The offered principle is: A saved QoS policy does not prove that the intended packets actually match its queue. In the source material it is associated with: A saved QoS policy does not prove that the intended packets actually match its queue. This case has a different controlling cause: Unrestricted low-priority demand can fill shared switch buffers during contention. Its keyed mechanism is: Unrestricted low-priority demand can fill shared switch buffers during contention.

B:

Incompatible speed configuration can prevent stable physical link negotiation. That is not the mechanism that accounts for the stated failure at the Quayside network modernization program.

D:

Although a speed or duplex mismatch can create retransmissions despite an illuminated link, the presented symptoms do not support that as the primary cause; they indicate that unrestricted low-priority demand can fill shared switch buffers during contention. For the Quayside network modernization program, the direct corrective action is to apply supported ingress rate limiting or policing to the guest traffic class with appropriate thresholds.

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