Fortinet NSE5_FSW_AD-7.6 (Fortinet NSE 5 - FortiSwitch 7.6 Administrator) Practice Test 23

Question 220

An operations log records this activity at the media studio: keep STP-aware behavior consistent around MCLAG peers. Which result is specifically attributable to that action?

  1. MCLAG/STP integration must be coordinated for access trunks and individual asymmetric links
  2. Bridge path cost contributes to best-root-path selection independently of link aggregation membership
  3. FortiSwitch loop guard monitors the subtending network and works alongside spanning tree
  4. Rapid spanning tree exchanges BPDUs and uses rapid port roles and state transitions where supported

Explanation

Correct Answer

A:

The relevant mechanism is: the configured operation is meant to prevent an aggregated pair from presenting conflicting topology behavior. The most relevant validation is to compare MSTP root information and MCLAG trunk status on each peer for the equipment at the media studio.

Incorrect Answers

B:

This outcome would be relevant to “Adjust STP path cost on a redundant uplink” at the media studio, not the task “Keep STP-aware behavior consistent around MCLAG peers”; the other task is to steer the preferred path toward the existing root over a better link. The action “Keep STP-aware behavior consistent around MCLAG peers” targets a different result: MCLAG/STP integration must be coordinated for access trunks and individual asymmetric links; the proposed alternative would instead be checked by compare accumulated root-path costs and root-port election before and after adjustment.

C:

That behavior applies when engineers “Enable loop guard for downstream loop detection”; the different operation “Keep STP-aware behavior consistent around MCLAG peers” is intended to prevent an aggregated pair from presenting conflicting topology behavior. That different feature is verified by inspect loop-guard counters and the protected port's state after a loop test; for “Keep STP-aware behavior consistent around MCLAG peers” on a carefully segmented Layer 2 network, the relevant evidence is to compare MSTP root information and MCLAG trunk status on each peer.

D:

That behavior applies when engineers “Enable RSTP for rapid converging topology”; the different operation “Keep STP-aware behavior consistent around MCLAG peers” is intended to prevent an aggregated pair from presenting conflicting topology behavior. That different feature is verified by observe root-port and alternate-port role changes during a link-failure test; for “Keep STP-aware behavior consistent around MCLAG peers” on a carefully segmented Layer 2 network, the relevant evidence is to compare MSTP root information and MCLAG trunk status on each peer.

Question 221

On a central switching stack at the retail site, the team reports that it has configured “Keep STP-aware behavior consistent around MCLAG peers.” Which verification provides the strongest direct evidence that the intended function is working?

  1. Compare MSTP root information and MCLAG trunk status on each peer
  2. Inspect edge-port state and whether an unexpected BPDU removes that edge assumption
  3. Compare VLAN-to-instance mappings on switches that belong to the same MST region
  4. Review a BPDU-guard violation and the resulting port status
  5. Inject a test superior BPDU and check that the designated root remains unchanged

Explanation

Correct Answer

A:

This approach fits because MCLAG/STP integration must be coordinated for access trunks and individual asymmetric links. Directly measuring that result demonstrates whether the step to prevent an aggregated pair from presenting conflicting topology behavior succeeded on a central switching stack.

Incorrect Answers

B:

The proposed check concerns “Mark a true endpoint interface as an STP edge port” rather than “Keep STP-aware behavior consistent around MCLAG peers”: edge-port behavior assumes no downstream bridge and should be paired with BPDU protection where appropriate. For “Keep STP-aware behavior consistent around MCLAG peers” on a central switching stack, a better test would be to compare MSTP root information and MCLAG trunk status on each peer, which targets prevent an aggregated pair from presenting conflicting topology behavior rather than the alternative diagnostic “Mark a true endpoint interface as an STP edge port”.

C:

This check is suited to “Use MSTP instances for multiple VLAN groups” when trying to apply distinct spanning-tree forwarding decisions to selected sets of VLANs, not to verify “Keep STP-aware behavior consistent around MCLAG peers” at the retail site. Checking “Keep STP-aware behavior consistent around MCLAG peers” at the retail site requires evidence of its own mechanism: MCLAG/STP integration must be coordinated for access trunks and individual asymmetric links; that is not the outcome measured by “Use MSTP instances for multiple VLAN groups”.

D:

The proposed check concerns “Enable BPDU guard on a genuine edge port” rather than “Keep STP-aware behavior consistent around MCLAG peers”: BPDU guard shuts or blocks the protected edge when it receives spanning-tree control BPDUs. For “Keep STP-aware behavior consistent around MCLAG peers” on a central switching stack, a better test would be to compare MSTP root information and MCLAG trunk status on each peer, which targets prevent an aggregated pair from presenting conflicting topology behavior rather than the alternative diagnostic “Enable BPDU guard on a genuine edge port”.

E:

This check is suited to “Use root guard on a downstream port” when trying to prevent an access-layer device from advertising itself as a superior STP root, not to verify “Keep STP-aware behavior consistent around MCLAG peers” at the retail site. Checking “Keep STP-aware behavior consistent around MCLAG peers” at the retail site requires evidence of its own mechanism: MCLAG/STP integration must be coordinated for access trunks and individual asymmetric links; that is not the outcome measured by “Use root guard on a downstream port”.

Question 222

A network architect documents a single goal for a switch used by multiple office teams: create several lower-rate interfaces from a supported switch port. Which listed procedure provides that capability?

  1. Inspect transceiver DOM and module information
  2. Constrain PoE to available power capacity
  3. Split a supported high-speed physical port into subports
  4. Use an auto-ISL trunk where supported

Explanation

Correct Answer

C:

The critical distinction is that split-port phy-mode changes how the underlying physical lanes are exposed as separate interfaces. The operator can test this claim by the specific check: check the port's supported phy-mode choices and resulting interface inventory.

Incorrect Answers

A:

Compared with the requested “Split a supported high-speed physical port into subports” at the airport office, this would diagnose an optical link that fails intermittently despite correct VLAN settings instead: optic inventory and diagnostics expose module type and supported optical measurements when the transceiver provides them. At the airport office, the operational proof would instead be to check the port's supported phy-mode choices and resulting interface inventory, whereas “Inspect transceiver DOM and module information” is validated by a different test: review recognized module identity, optical power and relevant port error counters.

B:

For the airport office, “Constrain PoE to available power capacity” is a different type of control from “Split a supported high-speed physical port into subports”: power delivery is constrained by per-port hardware capability and the switch's aggregate PoE budget. Unlike the requested feature, that setting addresses the need to prevent a new powered endpoint from exceeding the switch power budget, not the objective to create several lower-rate interfaces from a supported switch port.

D:

Compared with the requested “Split a supported high-speed physical port into subports” at the airport office, this would automatically maintain eligible links between managed FortiSwitch units instead: auto-inter-switch-link mechanisms simplify eligible uplink bundling in supported FortiLink designs. At the airport office, the operational proof would instead be to check the port's supported phy-mode choices and resulting interface inventory, whereas “Use an auto-ISL trunk where supported” is validated by a different test: inspect discovered ISL membership and active trunk status.

Question 223

When engineers split a supported high-speed physical port into subports at the operations center, which forwarding, security, management or diagnostic outcome follows from that action?

  1. Optic inventory and diagnostics expose module type and supported optical measurements when the transceiver provides them
  2. Auto-inter-switch-link mechanisms simplify eligible uplink bundling in supported FortiLink designs
  3. Split-port phy-mode changes how the underlying physical lanes are exposed as separate interfaces
  4. Power delivery is constrained by per-port hardware capability and the switch's aggregate PoE budget

Explanation

Correct Answer

C:

That setting is appropriate here because the configured operation is meant to create several lower-rate interfaces from a supported switch port. The most relevant validation is to check the port's supported phy-mode choices and resulting interface inventory for the equipment at the operations center.

Incorrect Answers

A:

That behavior applies when engineers “Inspect transceiver DOM and module information”; the different operation “Split a supported high-speed physical port into subports” is intended to create several lower-rate interfaces from a supported switch port. That different feature is verified by review recognized module identity, optical power and relevant port error counters; for “Split a supported high-speed physical port into subports” on a production FortiSwitch fabric, the relevant evidence is to check the port's supported phy-mode choices and resulting interface inventory.

B:

This outcome would be relevant to “Use an auto-ISL trunk where supported” at the operations center, not the task “Split a supported high-speed physical port into subports”; the other task is to automatically maintain eligible links between managed FortiSwitch units. The action “Split a supported high-speed physical port into subports” targets a different result: split-port phy-mode changes how the underlying physical lanes are exposed as separate interfaces; the proposed alternative would instead be checked by inspect discovered ISL membership and active trunk status.

D:

That behavior applies when engineers “Constrain PoE to available power capacity”; the different operation “Split a supported high-speed physical port into subports” is intended to create several lower-rate interfaces from a supported switch port. That different feature is verified by compare the connected device's requested class with free PoE budget and port allocation; for “Split a supported high-speed physical port into subports” on a production FortiSwitch fabric, the relevant evidence is to check the port's supported phy-mode choices and resulting interface inventory.

Question 224

A post-change review at the warehouse must validate the implementation of “Split a supported high-speed physical port into subports.” What should the reviewer inspect first?

  1. Compare the connected device's requested class with free PoE budget and port allocation
  2. Check the port's supported phy-mode choices and resulting interface inventory
  3. Inspect discovered ISL membership and active trunk status
  4. Review recognized module identity, optical power and relevant port error counters

Explanation

Correct Answer

B:

This is the precise control because split-port phy-mode changes how the underlying physical lanes are exposed as separate interfaces. Directly measuring that result demonstrates whether the step to create several lower-rate interfaces from a supported switch port succeeded on a newly racked distribution unit.

Incorrect Answers

A:

This check is suited to “Constrain PoE to available power capacity” when trying to prevent a new powered endpoint from exceeding the switch power budget, not to verify “Split a supported high-speed physical port into subports” at the warehouse. Checking “Split a supported high-speed physical port into subports” at the warehouse requires evidence of its own mechanism: split-port phy-mode changes how the underlying physical lanes are exposed as separate interfaces; that is not the outcome measured by “Constrain PoE to available power capacity”.

C:

The proposed check concerns “Use an auto-ISL trunk where supported” rather than “Split a supported high-speed physical port into subports”: auto-inter-switch-link mechanisms simplify eligible uplink bundling in supported FortiLink designs. For “Split a supported high-speed physical port into subports” on a newly racked distribution unit, a better test would be to check the port's supported phy-mode choices and resulting interface inventory, which targets create several lower-rate interfaces from a supported switch port rather than the alternative diagnostic “Use an auto-ISL trunk where supported”.

D:

This check is suited to “Inspect transceiver DOM and module information” when trying to diagnose an optical link that fails intermittently despite correct VLAN settings, not to verify “Split a supported high-speed physical port into subports” at the warehouse. Checking “Split a supported high-speed physical port into subports” at the warehouse requires evidence of its own mechanism: split-port phy-mode changes how the underlying physical lanes are exposed as separate interfaces; that is not the outcome measured by “Inspect transceiver DOM and module information”.

Question 225

The operational requirement for two distribution switches at the headquarters is to diagnose an optical link that fails intermittently despite correct VLAN settings. Which FortiSwitch choice directly targets it?

  1. Split a supported high-speed physical port into subports
  2. Select appropriate LACP load-balancing criteria
  3. Enable flap guard on an unstable interface
  4. Inspect transceiver DOM and module information
  5. Use an auto-ISL trunk where supported

Explanation

Correct Answer

D:

The implementation works because optic inventory and diagnostics expose module type and supported optical measurements when the transceiver provides them. This distinction is material to the headquarters, where the stated goal is to diagnose an optical link that fails intermittently despite correct VLAN settings.

Incorrect Answers

A:

For the headquarters, “Split a supported high-speed physical port into subports” is a different type of control from “Inspect transceiver DOM and module information”: split-port phy-mode changes how the underlying physical lanes are exposed as separate interfaces. Unlike the requested feature, that setting addresses the need to create several lower-rate interfaces from a supported switch port, not the objective to diagnose an optical link that fails intermittently despite correct VLAN settings.

B:

Compared with the requested “Inspect transceiver DOM and module information” at the headquarters, this would spread different traffic flows across the members of an existing trunk instead: trunk hashing chooses a member based on header fields and typically keeps each flow on one link. At the headquarters, the operational proof would instead be to review recognized module identity, optical power and relevant port error counters, whereas “Select appropriate LACP load-balancing criteria” is validated by a different test: inspect member utilization with multiple flows and verify the configured hash fields.

C:

Compared with the requested “Inspect transceiver DOM and module information” at the headquarters, this would limit disruption caused by a port repeatedly transitioning up and down instead: flap guard monitors link-state changes and can place an unstable port into a protective state. At the headquarters, the operational proof would instead be to review recognized module identity, optical power and relevant port error counters, whereas “Enable flap guard on an unstable interface” is validated by a different test: inspect flap events and the interface's automatic disable or recovery status.

E:

Compared with the requested “Inspect transceiver DOM and module information” at the headquarters, this would automatically maintain eligible links between managed FortiSwitch units instead: auto-inter-switch-link mechanisms simplify eligible uplink bundling in supported FortiLink designs. At the headquarters, the operational proof would instead be to review recognized module identity, optical power and relevant port error counters, whereas “Use an auto-ISL trunk where supported” is validated by a different test: inspect discovered ISL membership and active trunk status.

Question 226

A colleague asks about the effect of “Inspect transceiver DOM and module information” on a staging FortiSwitch. Which behavior best characterizes that feature?

  1. Split-port phy-mode changes how the underlying physical lanes are exposed as separate interfaces
  2. Flap guard monitors link-state changes and can place an unstable port into a protective state
  3. Trunk hashing chooses a member based on header fields and typically keeps each flow on one link
  4. Optic inventory and diagnostics expose module type and supported optical measurements when the transceiver provides them

Explanation

Correct Answer

D:

Given the described goal, the configured operation is meant to diagnose an optical link that fails intermittently despite correct VLAN settings. The most relevant validation is to review recognized module identity, optical power and relevant port error counters for the equipment at the hospital wing.

Incorrect Answers

A:

That behavior applies when engineers “Split a supported high-speed physical port into subports”; the different operation “Inspect transceiver DOM and module information” is intended to diagnose an optical link that fails intermittently despite correct VLAN settings. That different feature is verified by check the port's supported phy-mode choices and resulting interface inventory; for “Inspect transceiver DOM and module information” on a staging FortiSwitch, the relevant evidence is to review recognized module identity, optical power and relevant port error counters.

B:

This outcome would be relevant to “Enable flap guard on an unstable interface” at the hospital wing, not the task “Inspect transceiver DOM and module information”; the other task is to limit disruption caused by a port repeatedly transitioning up and down. The action “Inspect transceiver DOM and module information” targets a different result: optic inventory and diagnostics expose module type and supported optical measurements when the transceiver provides them; the proposed alternative would instead be checked by inspect flap events and the interface's automatic disable or recovery status.

C:

That behavior applies when engineers “Select appropriate LACP load-balancing criteria”; the different operation “Inspect transceiver DOM and module information” is intended to diagnose an optical link that fails intermittently despite correct VLAN settings. That different feature is verified by inspect member utilization with multiple flows and verify the configured hash fields; for “Inspect transceiver DOM and module information” on a staging FortiSwitch, the relevant evidence is to review recognized module identity, optical power and relevant port error counters.

Question 227

The work order to diagnose an optical link that fails intermittently despite correct VLAN settings is marked complete on a carefully segmented Layer 2 network. Which observation most directly tests the completed configuration?

  1. Inspect member utilization with multiple flows and verify the configured hash fields
  2. Inspect flap events and the interface's automatic disable or recovery status
  3. Review recognized module identity, optical power and relevant port error counters
  4. Check the port's supported phy-mode choices and resulting interface inventory

Explanation

Correct Answer

C:

The switch behavior that matters is: optic inventory and diagnostics expose module type and supported optical measurements when the transceiver provides them. Directly measuring that result demonstrates whether the step to diagnose an optical link that fails intermittently despite correct VLAN settings succeeded on a carefully segmented Layer 2 network.

Incorrect Answers

A:

This check is suited to “Select appropriate LACP load-balancing criteria” when trying to spread different traffic flows across the members of an existing trunk, not to verify “Inspect transceiver DOM and module information” at the factory. Checking “Inspect transceiver DOM and module information” at the factory requires evidence of its own mechanism: optic inventory and diagnostics expose module type and supported optical measurements when the transceiver provides them; that is not the outcome measured by “Select appropriate LACP load-balancing criteria”.

B:

The proposed check concerns “Enable flap guard on an unstable interface” rather than “Inspect transceiver DOM and module information”: flap guard monitors link-state changes and can place an unstable port into a protective state. For “Inspect transceiver DOM and module information” on a carefully segmented Layer 2 network, a better test would be to review recognized module identity, optical power and relevant port error counters, which targets diagnose an optical link that fails intermittently despite correct VLAN settings rather than the alternative diagnostic “Enable flap guard on an unstable interface”.

D:

This check is suited to “Split a supported high-speed physical port into subports” when trying to create several lower-rate interfaces from a supported switch port, not to verify “Inspect transceiver DOM and module information” at the factory. Checking “Inspect transceiver DOM and module information” at the factory requires evidence of its own mechanism: optic inventory and diagnostics expose module type and supported optical measurements when the transceiver provides them; that is not the outcome measured by “Split a supported high-speed physical port into subports”.

Question 228

During a change window in the distribution floor, engineers are asked to restore a physical link with incompatible manual interface negotiation. What should they configure rather than using a feature for an adjacent purpose?

  1. Set supported speed and duplex consistently
  2. Confirm minimum LAG members for service
  3. Inspect transceiver DOM and module information
  4. Select appropriate LACP load-balancing criteria

Explanation

Correct Answer

A:

At this network boundary, both connected endpoints must agree on operational link characteristics supported by their hardware. The operator can test this claim by the specific check: check negotiated link speed, duplex and error counters at both ends.

Incorrect Answers

B:

Compared with the requested “Set supported speed and duplex consistently” at the distribution floor, this would require sufficient healthy physical links before allowing an aggregate to remain usable instead: the aggregate minimum-member condition constrains availability as members fail. At the distribution floor, the operational proof would instead be to check negotiated link speed, duplex and error counters at both ends, whereas “Confirm minimum LAG members for service” is validated by a different test: remove members in a test and observe when the logical trunk is considered operational.

C:

Compared with the requested “Set supported speed and duplex consistently” at the distribution floor, this would diagnose an optical link that fails intermittently despite correct VLAN settings instead: optic inventory and diagnostics expose module type and supported optical measurements when the transceiver provides them. At the distribution floor, the operational proof would instead be to check negotiated link speed, duplex and error counters at both ends, whereas “Inspect transceiver DOM and module information” is validated by a different test: review recognized module identity, optical power and relevant port error counters.

D:

For the distribution floor, “Select appropriate LACP load-balancing criteria” is a different type of control from “Set supported speed and duplex consistently”: trunk hashing chooses a member based on header fields and typically keeps each flow on one link. Unlike the requested feature, that setting addresses the need to spread different traffic flows across the members of an existing trunk, not the objective to restore a physical link with incompatible manual interface negotiation.

Question 229

When engineers set supported speed and duplex consistently at the media studio, which forwarding, security, management or diagnostic outcome follows from that action?

  1. Optic inventory and diagnostics expose module type and supported optical measurements when the transceiver provides them
  2. Both connected endpoints must agree on operational link characteristics supported by their hardware
  3. Flap guard monitors link-state changes and can place an unstable port into a protective state
  4. The aggregate minimum-member condition constrains availability as members fail
  5. Trunk hashing chooses a member based on header fields and typically keeps each flow on one link

Explanation

Correct Answer

B:

In this deployment, the configured operation is meant to restore a physical link with incompatible manual interface negotiation. The most relevant validation is to check negotiated link speed, duplex and error counters at both ends for the equipment at the media studio.

Incorrect Answers

A:

That behavior applies when engineers “Inspect transceiver DOM and module information”; the different operation “Set supported speed and duplex consistently” is intended to restore a physical link with incompatible manual interface negotiation. That different feature is verified by review recognized module identity, optical power and relevant port error counters; for “Set supported speed and duplex consistently” on a FortiSwitch connected to the security edge, the relevant evidence is to check negotiated link speed, duplex and error counters at both ends.

C:

That behavior applies when engineers “Enable flap guard on an unstable interface”; the different operation “Set supported speed and duplex consistently” is intended to restore a physical link with incompatible manual interface negotiation. That different feature is verified by inspect flap events and the interface's automatic disable or recovery status; for “Set supported speed and duplex consistently” on a FortiSwitch connected to the security edge, the relevant evidence is to check negotiated link speed, duplex and error counters at both ends.

D:

This outcome would be relevant to “Confirm minimum LAG members for service” at the media studio, not the task “Set supported speed and duplex consistently”; the other task is to require sufficient healthy physical links before allowing an aggregate to remain usable. The action “Set supported speed and duplex consistently” targets a different result: both connected endpoints must agree on operational link characteristics supported by their hardware; the proposed alternative would instead be checked by remove members in a test and observe when the logical trunk is considered operational.

E:

That behavior applies when engineers “Select appropriate LACP load-balancing criteria”; the different operation “Set supported speed and duplex consistently” is intended to restore a physical link with incompatible manual interface negotiation. That different feature is verified by inspect member utilization with multiple flows and verify the configured hash fields; for “Set supported speed and duplex consistently” on a FortiSwitch connected to the security edge, the relevant evidence is to check negotiated link speed, duplex and error counters at both ends.

Question 230

An auditor wants operational evidence for the switch action “Set supported speed and duplex consistently” at the retail site. Which check is relevant?

  1. Remove members in a test and observe when the logical trunk is considered operational
  2. Review recognized module identity, optical power and relevant port error counters
  3. Inspect member utilization with multiple flows and verify the configured hash fields
  4. Check negotiated link speed, duplex and error counters at both ends

Explanation

Correct Answer

D:

For the stated requirement, both connected endpoints must agree on operational link characteristics supported by their hardware. Directly measuring that result demonstrates whether the step to restore a physical link with incompatible manual interface negotiation succeeded on an access switch in routine maintenance.

Incorrect Answers

A:

The proposed check concerns “Confirm minimum LAG members for service” rather than “Set supported speed and duplex consistently”: the aggregate minimum-member condition constrains availability as members fail. For “Set supported speed and duplex consistently” on an access switch in routine maintenance, a better test would be to check negotiated link speed, duplex and error counters at both ends, which targets restore a physical link with incompatible manual interface negotiation rather than the alternative diagnostic “Confirm minimum LAG members for service”.

B:

This check is suited to “Inspect transceiver DOM and module information” when trying to diagnose an optical link that fails intermittently despite correct VLAN settings, not to verify “Set supported speed and duplex consistently” at the retail site. Checking “Set supported speed and duplex consistently” at the retail site requires evidence of its own mechanism: both connected endpoints must agree on operational link characteristics supported by their hardware; that is not the outcome measured by “Inspect transceiver DOM and module information”.

C:

This check is suited to “Select appropriate LACP load-balancing criteria” when trying to spread different traffic flows across the members of an existing trunk, not to verify “Set supported speed and duplex consistently” at the retail site. Checking “Set supported speed and duplex consistently” at the retail site requires evidence of its own mechanism: both connected endpoints must agree on operational link characteristics supported by their hardware; that is not the outcome measured by “Select appropriate LACP load-balancing criteria”.

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