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

Question 200

A post-change review at the training center must validate the implementation of “Use root guard on a downstream port.” What should the reviewer inspect first?

  1. Inspect edge-port state and whether an unexpected BPDU removes that edge assumption
  2. Review a BPDU-guard violation and the resulting port status
  3. Inject a test superior BPDU and check that the designated root remains unchanged
  4. Observe root-port and alternate-port role changes during a link-failure test

Explanation

Correct Answer

C:

This is the precise control because root guard prevents superior BPDUs on that link from changing the intended root path. Directly measuring that result demonstrates whether the step to prevent an access-layer device from advertising itself as a superior STP root succeeded on a switch linked to a FortiGate running FortiOS 7.6.

Incorrect Answers

A:

This check is suited to “Mark a true endpoint interface as an STP edge port” when trying to allow an end-host port to transition quickly without waiting through normal topology learning, not to verify “Use root guard on a downstream port” at the training center. Checking “Use root guard on a downstream port” at the training center requires evidence of its own mechanism: root guard prevents superior BPDUs on that link from changing the intended root path; that is not the outcome measured by “Mark a true endpoint interface as an STP edge port”.

B:

The proposed check concerns “Enable BPDU guard on a genuine edge port” rather than “Use root guard on a downstream port”: BPDU guard shuts or blocks the protected edge when it receives spanning-tree control BPDUs. For “Use root guard on a downstream port” on a switch linked to a FortiGate running FortiOS 7.6, a better test would be to inject a test superior BPDU and check that the designated root remains unchanged, which targets prevent an access-layer device from advertising itself as a superior STP root rather than the alternative diagnostic “Enable BPDU guard on a genuine edge port”.

D:

This check is suited to “Enable RSTP for rapid converging topology” when trying to reduce reconvergence delay after a legitimate Layer 2 link state change, not to verify “Use root guard on a downstream port” at the training center. Checking “Use root guard on a downstream port” at the training center requires evidence of its own mechanism: root guard prevents superior BPDUs on that link from changing the intended root path; that is not the outcome measured by “Enable RSTP for rapid converging topology”.

Question 201

The accepted design for the lab requires the ability to detect certain loop conditions beneath a switch port rather than replacing STP. Which switch feature is the closest fit?

  1. Use MSTP instances for multiple VLAN groups
  2. Enable loop guard for downstream loop detection
  3. Keep STP-aware behavior consistent around MCLAG peers
  4. Mark a true endpoint interface as an STP edge port

Explanation

Correct Answer

B:

The implementation works because FortiSwitch loop guard monitors the subtending network and works alongside spanning tree. This distinction is material to the lab, where the stated goal is to detect certain loop conditions beneath a switch port rather than replacing STP.

Incorrect Answers

A:

Compared with the requested “Enable loop guard for downstream loop detection” at the lab, this would apply distinct spanning-tree forwarding decisions to selected sets of VLANs instead: MSTP maps multiple VLANs onto spanning-tree instances within a region. At the lab, the operational proof would instead be to inspect loop-guard counters and the protected port's state after a loop test, whereas “Use MSTP instances for multiple VLAN groups” is validated by a different test: compare VLAN-to-instance mappings on switches that belong to the same MST region.

C:

For the lab, “Keep STP-aware behavior consistent around MCLAG peers” is a different type of control from “Enable loop guard for downstream loop detection”: MCLAG/STP integration must be coordinated for access trunks and individual asymmetric links. Unlike the requested feature, that setting addresses the need to prevent an aggregated pair from presenting conflicting topology behavior, not the objective to detect certain loop conditions beneath a switch port rather than replacing STP.

D:

Compared with the requested “Enable loop guard for downstream loop detection” at the lab, this would allow an end-host port to transition quickly without waiting through normal topology learning instead: edge-port behavior assumes no downstream bridge and should be paired with BPDU protection where appropriate. At the lab, the operational proof would instead be to inspect loop-guard counters and the protected port's state after a loop test, whereas “Mark a true endpoint interface as an STP edge port” is validated by a different test: inspect edge-port state and whether an unexpected BPDU removes that edge assumption.

Question 202

On a managed switch running FortiSwitchOS 7.6, “Enable loop guard for downstream loop detection” is configured for the staging rack. What effect should an administrator expect without assuming unrelated features are enabled?

  1. Bridge path cost contributes to best-root-path selection independently of link aggregation membership
  2. FortiSwitch loop guard monitors the subtending network and works alongside spanning tree
  3. The bridge with the lowest complete bridge ID is selected, with MAC breaking priority ties
  4. Root guard prevents superior BPDUs on that link from changing the intended root path

Explanation

Correct Answer

B:

Given the described goal, the configured operation is meant to detect certain loop conditions beneath a switch port rather than replacing STP. The most relevant validation is to inspect loop-guard counters and the protected port's state after a loop test for the equipment at the staging rack.

Incorrect Answers

A:

That behavior applies when engineers “Adjust STP path cost on a redundant uplink”; the different operation “Enable loop guard for downstream loop detection” is intended to detect certain loop conditions beneath a switch port rather than replacing STP. That different feature is verified by compare accumulated root-path costs and root-port election before and after adjustment; for “Enable loop guard for downstream loop detection” on a managed switch running FortiSwitchOS 7.6, the relevant evidence is to inspect loop-guard counters and the protected port's state after a loop test.

C:

That behavior applies when engineers “Choose a lower STP bridge priority for the desired root”; the different operation “Enable loop guard for downstream loop detection” is intended to detect certain loop conditions beneath a switch port rather than replacing STP. That different feature is verified by compare effective bridge IDs rather than merely hostnames or interface speeds; for “Enable loop guard for downstream loop detection” on a managed switch running FortiSwitchOS 7.6, the relevant evidence is to inspect loop-guard counters and the protected port's state after a loop test.

D:

This outcome would be relevant to “Use root guard on a downstream port” at the staging rack, not the task “Enable loop guard for downstream loop detection”; the other task is to prevent an access-layer device from advertising itself as a superior STP root. The action “Enable loop guard for downstream loop detection” targets a different result: FortiSwitch loop guard monitors the subtending network and works alongside spanning tree; the proposed alternative would instead be checked by inject a test superior BPDU and check that the designated root remains unchanged.

Question 203

The work order to detect certain loop conditions beneath a switch port rather than replacing STP is marked complete on a remote FortiSwitch installation. Which observation most directly tests the completed configuration?

  1. Observe root-port and alternate-port role changes during a link-failure test
  2. Inspect loop-guard counters and the protected port's state after a loop test
  3. Review a BPDU-guard violation and the resulting port status
  4. Inspect edge-port state and whether an unexpected BPDU removes that edge assumption
  5. Compare VLAN-to-instance mappings on switches that belong to the same MST region

Explanation

Correct Answer

B:

The switch behavior that matters is: FortiSwitch loop guard monitors the subtending network and works alongside spanning tree. Directly measuring that result demonstrates whether the step to detect certain loop conditions beneath a switch port rather than replacing STP succeeded on a remote FortiSwitch installation.

Incorrect Answers

A:

This check is suited to “Enable RSTP for rapid converging topology” when trying to reduce reconvergence delay after a legitimate Layer 2 link state change, not to verify “Enable loop guard for downstream loop detection” at the research building. Checking “Enable loop guard for downstream loop detection” at the research building requires evidence of its own mechanism: FortiSwitch loop guard monitors the subtending network and works alongside spanning tree; that is not the outcome measured by “Enable RSTP for rapid converging topology”.

C:

The proposed check concerns “Enable BPDU guard on a genuine edge port” rather than “Enable loop guard for downstream loop detection”: BPDU guard shuts or blocks the protected edge when it receives spanning-tree control BPDUs. For “Enable loop guard for downstream loop detection” on a remote FortiSwitch installation, a better test would be to inspect loop-guard counters and the protected port's state after a loop test, which targets detect certain loop conditions beneath a switch port rather than replacing STP rather than the alternative diagnostic “Enable BPDU guard on a genuine edge port”.

D:

This check is suited to “Mark a true endpoint interface as an STP edge port” when trying to allow an end-host port to transition quickly without waiting through normal topology learning, not to verify “Enable loop guard for downstream loop detection” at the research building. Checking “Enable loop guard for downstream loop detection” at the research building requires evidence of its own mechanism: FortiSwitch loop guard monitors the subtending network and works alongside spanning tree; that is not the outcome measured by “Mark a true endpoint interface as an STP edge port”.

E:

The proposed check concerns “Use MSTP instances for multiple VLAN groups” rather than “Enable loop guard for downstream loop detection”: MSTP maps multiple VLANs onto spanning-tree instances within a region. For “Enable loop guard for downstream loop detection” on a remote FortiSwitch installation, a better test would be to inspect loop-guard counters and the protected port's state after a loop test, which targets detect certain loop conditions beneath a switch port rather than replacing STP rather than the alternative diagnostic “Use MSTP instances for multiple VLAN groups”.

Question 204

A deployment review at the clinic identifies this objective: apply distinct spanning-tree forwarding decisions to selected sets of VLANs. Which FortiSwitch operation should be selected?

  1. Enable loop guard for downstream loop detection
  2. Mark a true endpoint interface as an STP edge port
  3. Keep STP-aware behavior consistent around MCLAG peers
  4. Use MSTP instances for multiple VLAN groups

Explanation

Correct Answer

D:

At this network boundary, MSTP maps multiple VLANs onto spanning-tree instances within a region. The operator can test this claim by the specific check: compare VLAN-to-instance mappings on switches that belong to the same MST region.

Incorrect Answers

A:

Compared with the requested “Use MSTP instances for multiple VLAN groups” at the clinic, this would detect certain loop conditions beneath a switch port rather than replacing STP instead: FortiSwitch loop guard monitors the subtending network and works alongside spanning tree. At the clinic, the operational proof would instead be to compare VLAN-to-instance mappings on switches that belong to the same MST region, whereas “Enable loop guard for downstream loop detection” is validated by a different test: inspect loop-guard counters and the protected port's state after a loop test.

B:

Compared with the requested “Use MSTP instances for multiple VLAN groups” at the clinic, this would allow an end-host port to transition quickly without waiting through normal topology learning instead: edge-port behavior assumes no downstream bridge and should be paired with BPDU protection where appropriate. At the clinic, the operational proof would instead be to compare VLAN-to-instance mappings on switches that belong to the same MST region, whereas “Mark a true endpoint interface as an STP edge port” is validated by a different test: inspect edge-port state and whether an unexpected BPDU removes that edge assumption.

C:

For the clinic, “Keep STP-aware behavior consistent around MCLAG peers” is a different type of control from “Use MSTP instances for multiple VLAN groups”: MCLAG/STP integration must be coordinated for access trunks and individual asymmetric links. Unlike the requested feature, that setting addresses the need to prevent an aggregated pair from presenting conflicting topology behavior, not the objective to apply distinct spanning-tree forwarding decisions to selected sets of VLANs.

Question 205

A change record for a standalone FortiSwitch appliance states “Use MSTP instances for multiple VLAN groups.” Which description correctly explains what this will accomplish?

  1. MSTP maps multiple VLANs onto spanning-tree instances within a region
  2. Root guard prevents superior BPDUs on that link from changing the intended root path
  3. The bridge with the lowest complete bridge ID is selected, with MAC breaking priority ties
  4. Bridge path cost contributes to best-root-path selection independently of link aggregation membership

Explanation

Correct Answer

A:

In this deployment, the configured operation is meant to apply distinct spanning-tree forwarding decisions to selected sets of VLANs. The most relevant validation is to compare VLAN-to-instance mappings on switches that belong to the same MST region for the equipment at the data hall.

Incorrect Answers

B:

This outcome would be relevant to “Use root guard on a downstream port” at the data hall, not the task “Use MSTP instances for multiple VLAN groups”; the other task is to prevent an access-layer device from advertising itself as a superior STP root. The action “Use MSTP instances for multiple VLAN groups” targets a different result: MSTP maps multiple VLANs onto spanning-tree instances within a region; the proposed alternative would instead be checked by inject a test superior BPDU and check that the designated root remains unchanged.

C:

That behavior applies when engineers “Choose a lower STP bridge priority for the desired root”; the different operation “Use MSTP instances for multiple VLAN groups” is intended to apply distinct spanning-tree forwarding decisions to selected sets of VLANs. That different feature is verified by compare effective bridge IDs rather than merely hostnames or interface speeds; for “Use MSTP instances for multiple VLAN groups” on a standalone FortiSwitch appliance, the relevant evidence is to compare VLAN-to-instance mappings on switches that belong to the same MST region.

D:

That behavior applies when engineers “Adjust STP path cost on a redundant uplink”; the different operation “Use MSTP instances for multiple VLAN groups” is intended to apply distinct spanning-tree forwarding decisions to selected sets of VLANs. That different feature is verified by compare accumulated root-path costs and root-port election before and after adjustment; for “Use MSTP instances for multiple VLAN groups” on a standalone FortiSwitch appliance, the relevant evidence is to compare VLAN-to-instance mappings on switches that belong to the same MST region.

Question 206

An auditor wants operational evidence for the switch action “Use MSTP instances for multiple VLAN groups” at the warehouse. Which check is relevant?

  1. Compare VLAN-to-instance mappings on switches that belong to the same MST region
  2. Observe root-port and alternate-port role changes during a link-failure test
  3. Review a BPDU-guard violation and the resulting port status
  4. Inspect edge-port state and whether an unexpected BPDU removes that edge assumption

Explanation

Correct Answer

A:

For the stated requirement, MSTP maps multiple VLANs onto spanning-tree instances within a region. Directly measuring that result demonstrates whether the step to apply distinct spanning-tree forwarding decisions to selected sets of VLANs succeeded on a newly commissioned floor switch.

Incorrect Answers

B:

This check is suited to “Enable RSTP for rapid converging topology” when trying to reduce reconvergence delay after a legitimate Layer 2 link state change, not to verify “Use MSTP instances for multiple VLAN groups” at the warehouse. Checking “Use MSTP instances for multiple VLAN groups” at the warehouse requires evidence of its own mechanism: MSTP maps multiple VLANs onto spanning-tree instances within a region; that is not the outcome measured by “Enable RSTP for rapid converging topology”.

C:

The proposed check concerns “Enable BPDU guard on a genuine edge port” rather than “Use MSTP instances for multiple VLAN groups”: BPDU guard shuts or blocks the protected edge when it receives spanning-tree control BPDUs. For “Use MSTP instances for multiple VLAN groups” on a newly commissioned floor switch, a better test would be to compare VLAN-to-instance mappings on switches that belong to the same MST region, which targets apply distinct spanning-tree forwarding decisions to selected sets of VLANs rather than the alternative diagnostic “Enable BPDU guard on a genuine edge port”.

D:

This check is suited to “Mark a true endpoint interface as an STP edge port” when trying to allow an end-host port to transition quickly without waiting through normal topology learning, not to verify “Use MSTP instances for multiple VLAN groups” at the warehouse. Checking “Use MSTP instances for multiple VLAN groups” at the warehouse requires evidence of its own mechanism: MSTP maps multiple VLANs onto spanning-tree instances within a region; that is not the outcome measured by “Mark a true endpoint interface as an STP edge port”.

Question 207

A peer review of the headquarters asks how the design will reduce reconvergence delay after a legitimate Layer 2 link state change. Which FortiSwitch technique is the correct response?

  1. Choose a lower STP bridge priority for the desired root
  2. Use root guard on a downstream port
  3. Keep STP-aware behavior consistent around MCLAG peers
  4. Adjust STP path cost on a redundant uplink
  5. Enable RSTP for rapid converging topology

Explanation

Correct Answer

E:

The deciding detail is that rapid spanning tree exchanges BPDUs and uses rapid port roles and state transitions where supported. This distinction is material to the headquarters, where the stated goal is to reduce reconvergence delay after a legitimate Layer 2 link state change.

Incorrect Answers

A:

Compared with the requested “Enable RSTP for rapid converging topology” at the headquarters, this would make a selected core switch preferable in STP root election instead: the bridge with the lowest complete bridge ID is selected, with MAC breaking priority ties. At the headquarters, the operational proof would instead be to observe root-port and alternate-port role changes during a link-failure test, whereas “Choose a lower STP bridge priority for the desired root” is validated by a different test: compare effective bridge IDs rather than merely hostnames or interface speeds.

B:

For the headquarters, “Use root guard on a downstream port” is a different type of control from “Enable RSTP for rapid converging topology”: root guard prevents superior BPDUs on that link from changing the intended root path. Unlike the requested feature, that setting addresses the need to prevent an access-layer device from advertising itself as a superior STP root, not the objective to reduce reconvergence delay after a legitimate Layer 2 link state change.

C:

Compared with the requested “Enable RSTP for rapid converging topology” at the headquarters, this would prevent an aggregated pair from presenting conflicting topology behavior instead: MCLAG/STP integration must be coordinated for access trunks and individual asymmetric links. At the headquarters, the operational proof would instead be to observe root-port and alternate-port role changes during a link-failure test, whereas “Keep STP-aware behavior consistent around MCLAG peers” is validated by a different test: compare MSTP root information and MCLAG trunk status on each peer.

D:

Compared with the requested “Enable RSTP for rapid converging topology” at the headquarters, this would steer the preferred path toward the existing root over a better link instead: bridge path cost contributes to best-root-path selection independently of link aggregation membership. At the headquarters, the operational proof would instead be to observe root-port and alternate-port role changes during a link-failure test, whereas “Adjust STP path cost on a redundant uplink” is validated by a different test: compare accumulated root-path costs and root-port election before and after adjustment.

Question 208

An operations log records this activity at the hospital wing: enable RSTP for rapid converging topology. Which result is specifically attributable to that action?

  1. BPDU guard shuts or blocks the protected edge when it receives spanning-tree control BPDUs
  2. Bridge path cost contributes to best-root-path selection independently of link aggregation membership
  3. MSTP maps multiple VLANs onto spanning-tree instances within a region
  4. Rapid spanning tree exchanges BPDUs and uses rapid port roles and state transitions where supported

Explanation

Correct Answer

D:

The relevant mechanism is: the configured operation is meant to reduce reconvergence delay after a legitimate Layer 2 link state change. The most relevant validation is to observe root-port and alternate-port role changes during a link-failure test for the equipment at the hospital wing.

Incorrect Answers

A:

That behavior applies when engineers “Enable BPDU guard on a genuine edge port”; the different operation “Enable RSTP for rapid converging topology” is intended to reduce reconvergence delay after a legitimate Layer 2 link state change. That different feature is verified by review a BPDU-guard violation and the resulting port status; for “Enable RSTP for rapid converging topology” on a switch used by multiple office teams, the relevant evidence is to observe root-port and alternate-port role changes during a link-failure test.

B:

That behavior applies when engineers “Adjust STP path cost on a redundant uplink”; the different operation “Enable RSTP for rapid converging topology” is intended to reduce reconvergence delay after a legitimate Layer 2 link state change. That different feature is verified by compare accumulated root-path costs and root-port election before and after adjustment; for “Enable RSTP for rapid converging topology” on a switch used by multiple office teams, the relevant evidence is to observe root-port and alternate-port role changes during a link-failure test.

C:

This outcome would be relevant to “Use MSTP instances for multiple VLAN groups” at the hospital wing, not the task “Enable RSTP for rapid converging topology”; the other task is to apply distinct spanning-tree forwarding decisions to selected sets of VLANs. The action “Enable RSTP for rapid converging topology” targets a different result: rapid spanning tree exchanges BPDUs and uses rapid port roles and state transitions where supported; the proposed alternative would instead be checked by compare VLAN-to-instance mappings on switches that belong to the same MST region.

Question 209

A technician says “Enable RSTP for rapid converging topology” has solved the issue at the training center. Which diagnostic step would substantiate that claim?

  1. Observe root-port and alternate-port role changes during a link-failure test
  2. Inspect edge-port state and whether an unexpected BPDU removes that edge assumption
  3. Compare MSTP root information and MCLAG trunk status on each peer
  4. Inspect loop-guard counters and the protected port's state after a loop test

Explanation

Correct Answer

A:

This approach fits because rapid spanning tree exchanges BPDUs and uses rapid port roles and state transitions where supported. Directly measuring that result demonstrates whether the step to reduce reconvergence delay after a legitimate Layer 2 link state change succeeded on a managed switch running FortiSwitchOS 7.6.

Incorrect Answers

B:

This check is suited to “Mark a true endpoint interface as an STP edge port” when trying to allow an end-host port to transition quickly without waiting through normal topology learning, not to verify “Enable RSTP for rapid converging topology” at the training center. Checking “Enable RSTP for rapid converging topology” at the training center requires evidence of its own mechanism: rapid spanning tree exchanges BPDUs and uses rapid port roles and state transitions where supported; that is not the outcome measured by “Mark a true endpoint interface as an STP edge port”.

C:

This check is suited to “Keep STP-aware behavior consistent around MCLAG peers” when trying to prevent an aggregated pair from presenting conflicting topology behavior, not to verify “Enable RSTP for rapid converging topology” at the training center. Checking “Enable RSTP for rapid converging topology” at the training center requires evidence of its own mechanism: rapid spanning tree exchanges BPDUs and uses rapid port roles and state transitions where supported; that is not the outcome measured by “Keep STP-aware behavior consistent around MCLAG peers”.

D:

The proposed check concerns “Enable loop guard for downstream loop detection” rather than “Enable RSTP for rapid converging topology”: FortiSwitch loop guard monitors the subtending network and works alongside spanning tree. For “Enable RSTP for rapid converging topology” on a managed switch running FortiSwitchOS 7.6, a better test would be to observe root-port and alternate-port role changes during a link-failure test, which targets reduce reconvergence delay after a legitimate Layer 2 link state change rather than the alternative diagnostic “Enable loop guard for downstream loop detection”.

Question 210

A production incident in the lab reveals the need to make a selected core switch preferable in STP root election. Which targeted FortiSwitch setting or method should the team use?

  1. Choose a lower STP bridge priority for the desired root
  2. Use root guard on a downstream port
  3. Use MSTP instances for multiple VLAN groups
  4. Adjust STP path cost on a redundant uplink
  5. Enable BPDU guard on a genuine edge port

Explanation

Correct Answer

A:

The critical distinction is that the bridge with the lowest complete bridge ID is selected, with MAC breaking priority ties. The operator can test this claim by the specific check: compare effective bridge IDs rather than merely hostnames or interface speeds.

Incorrect Answers

B:

Compared with the requested “Choose a lower STP bridge priority for the desired root” at the lab, this would prevent an access-layer device from advertising itself as a superior STP root instead: root guard prevents superior BPDUs on that link from changing the intended root path. At the lab, the operational proof would instead be to compare effective bridge IDs rather than merely hostnames or interface speeds, whereas “Use root guard on a downstream port” is validated by a different test: inject a test superior BPDU and check that the designated root remains unchanged.

C:

For the lab, “Use MSTP instances for multiple VLAN groups” is a different type of control from “Choose a lower STP bridge priority for the desired root”: MSTP maps multiple VLANs onto spanning-tree instances within a region. Unlike the requested feature, that setting addresses the need to apply distinct spanning-tree forwarding decisions to selected sets of VLANs, not the objective to make a selected core switch preferable in STP root election.

D:

Compared with the requested “Choose a lower STP bridge priority for the desired root” at the lab, this would steer the preferred path toward the existing root over a better link instead: bridge path cost contributes to best-root-path selection independently of link aggregation membership. At the lab, the operational proof would instead be to compare effective bridge IDs rather than merely hostnames or interface speeds, whereas “Adjust STP path cost on a redundant uplink” is validated by a different test: compare accumulated root-path costs and root-port election before and after adjustment.

E:

Compared with the requested “Choose a lower STP bridge priority for the desired root” at the lab, this would stop a newly connected unauthorized switch from altering access-layer topology instead: BPDU guard shuts or blocks the protected edge when it receives spanning-tree control BPDUs. At the lab, the operational proof would instead be to compare effective bridge IDs rather than merely hostnames or interface speeds, whereas “Enable BPDU guard on a genuine edge port” is validated by a different test: review a BPDU-guard violation and the resulting port status.

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