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?
- Choose a lower STP bridge priority for the desired root
- Use root guard on a downstream port
- Use MSTP instances for multiple VLAN groups
- Adjust STP path cost on a redundant uplink
- 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.
Question 211
A change record for an endpoint-facing FortiSwitch port states “Choose a lower STP bridge priority for the desired root.” Which description correctly explains what this will accomplish?
- FortiSwitch loop guard monitors the subtending network and works alongside spanning tree
- The bridge with the lowest complete bridge ID is selected, with MAC breaking priority ties
- BPDU guard shuts or blocks the protected edge when it receives spanning-tree control BPDUs
- Edge-port behavior assumes no downstream bridge and should be paired with BPDU protection where appropriate
Explanation
Correct Answer
B:That setting is appropriate here because the configured operation is meant to make a selected core switch preferable in STP root election. The most relevant validation is to compare effective bridge IDs rather than merely hostnames or interface speeds for the equipment at the staging rack.
Incorrect Answers
A:That behavior applies when engineers “Enable loop guard for downstream loop detection”; the different operation “Choose a lower STP bridge priority for the desired root” is intended to make a selected core switch preferable in STP root election. That different feature is verified by inspect loop-guard counters and the protected port's state after a loop test; for “Choose a lower STP bridge priority for the desired root” on an endpoint-facing FortiSwitch port, the relevant evidence is to compare effective bridge IDs rather than merely hostnames or interface speeds.
C:That behavior applies when engineers “Enable BPDU guard on a genuine edge port”; the different operation “Choose a lower STP bridge priority for the desired root” is intended to make a selected core switch preferable in STP root election. That different feature is verified by review a BPDU-guard violation and the resulting port status; for “Choose a lower STP bridge priority for the desired root” on an endpoint-facing FortiSwitch port, the relevant evidence is to compare effective bridge IDs rather than merely hostnames or interface speeds.
D:This outcome would be relevant to “Mark a true endpoint interface as an STP edge port” at the staging rack, not the task “Choose a lower STP bridge priority for the desired root”; the other task is to allow an end-host port to transition quickly without waiting through normal topology learning. The action “Choose a lower STP bridge priority for the desired root” targets a different result: the bridge with the lowest complete bridge ID is selected, with MAC breaking priority ties; the proposed alternative would instead be checked by inspect edge-port state and whether an unexpected BPDU removes that edge assumption.
Question 212
At the research building, a dashboard shows ordinary link-up state, but the team also needs proof for “Choose a lower STP bridge priority for the desired root.” Which targeted check should be used?
- Observe root-port and alternate-port role changes during a link-failure test
- Inject a test superior BPDU and check that the designated root remains unchanged
- Compare effective bridge IDs rather than merely hostnames or interface speeds
- Compare MSTP root information and MCLAG trunk status on each peer
Explanation
Correct Answer
C:This is the precise control because the bridge with the lowest complete bridge ID is selected, with MAC breaking priority ties. Directly measuring that result demonstrates whether the step to make a selected core switch preferable in STP root election succeeded on a standalone FortiSwitch appliance.
Incorrect Answers
A:The proposed check concerns “Enable RSTP for rapid converging topology” rather than “Choose a lower STP bridge priority for the desired root”: rapid spanning tree exchanges BPDUs and uses rapid port roles and state transitions where supported. For “Choose a lower STP bridge priority for the desired root” on a standalone FortiSwitch appliance, a better test would be to compare effective bridge IDs rather than merely hostnames or interface speeds, which targets make a selected core switch preferable in STP root election rather than the alternative diagnostic “Enable RSTP for rapid converging topology”.
B: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 “Choose a lower STP bridge priority for the desired root” at the research building. Checking “Choose a lower STP bridge priority for the desired root” at the research building requires evidence of its own mechanism: the bridge with the lowest complete bridge ID is selected, with MAC breaking priority ties; that is not the outcome measured by “Use root guard on a downstream port”.
D: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 “Choose a lower STP bridge priority for the desired root” at the research building. Checking “Choose a lower STP bridge priority for the desired root” at the research building requires evidence of its own mechanism: the bridge with the lowest complete bridge ID is selected, with MAC breaking priority ties; that is not the outcome measured by “Keep STP-aware behavior consistent around MCLAG peers”.
Question 213
A switch rollout in the airport office will be approved only if it can allow an end-host port to transition quickly without waiting through normal topology learning. Which administrative action meets this acceptance criterion?
- Choose a lower STP bridge priority for the desired root
- Mark a true endpoint interface as an STP edge port
- Enable BPDU guard on a genuine edge port
- Enable loop guard for downstream loop detection
Explanation
Correct Answer
B:The implementation works because edge-port behavior assumes no downstream bridge and should be paired with BPDU protection where appropriate. This distinction is material to the airport office, where the stated goal is to allow an end-host port to transition quickly without waiting through normal topology learning.
Incorrect Answers
A:Compared with the requested “Mark a true endpoint interface as an STP edge port” at the airport office, 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 airport office, the operational proof would instead be to inspect edge-port state and whether an unexpected BPDU removes that edge assumption, 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.
C:Compared with the requested “Mark a true endpoint interface as an STP edge port” at the airport office, 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 airport office, the operational proof would instead be to inspect edge-port state and whether an unexpected BPDU removes that edge assumption, 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.
D:For the airport office, “Enable loop guard for downstream loop detection” is a different type of control from “Mark a true endpoint interface as an STP edge port”: FortiSwitch loop guard monitors the subtending network and works alongside spanning tree. Unlike the requested feature, that setting addresses the need to detect certain loop conditions beneath a switch port rather than replacing STP, not the objective to allow an end-host port to transition quickly without waiting through normal topology learning.
Question 214
An operations log records this activity at the operations center: mark a true endpoint interface as an STP edge port. Which result is specifically attributable to that action?
- Edge-port behavior assumes no downstream bridge and should be paired with BPDU protection where appropriate
- Rapid spanning tree exchanges BPDUs and uses rapid port roles and state transitions where supported
- Root guard prevents superior BPDUs on that link from changing the intended root path
- MCLAG/STP integration must be coordinated for access trunks and individual asymmetric links
- Bridge path cost contributes to best-root-path selection independently of link aggregation membership
Explanation
Correct Answer
A:Given the described goal, the configured operation is meant to allow an end-host port to transition quickly without waiting through normal topology learning. The most relevant validation is to inspect edge-port state and whether an unexpected BPDU removes that edge assumption for the equipment at the operations center.
Incorrect Answers
B:This outcome would be relevant to “Enable RSTP for rapid converging topology” at the operations center, not the task “Mark a true endpoint interface as an STP edge port”; the other task is to reduce reconvergence delay after a legitimate Layer 2 link state change. The action “Mark a true endpoint interface as an STP edge port” targets a different result: edge-port behavior assumes no downstream bridge and should be paired with BPDU protection where appropriate; the proposed alternative would instead be checked by observe root-port and alternate-port role changes during a link-failure test.
C:That behavior applies when engineers “Use root guard on a downstream port”; the different operation “Mark a true endpoint interface as an STP edge port” is intended to allow an end-host port to transition quickly without waiting through normal topology learning. That different feature is verified by inject a test superior BPDU and check that the designated root remains unchanged; for “Mark a true endpoint interface as an STP edge port” on a local switch administering branch clients, the relevant evidence is to inspect edge-port state and whether an unexpected BPDU removes that edge assumption.
D:That behavior applies when engineers “Keep STP-aware behavior consistent around MCLAG peers”; the different operation “Mark a true endpoint interface as an STP edge port” is intended to allow an end-host port to transition quickly without waiting through normal topology learning. That different feature is verified by compare MSTP root information and MCLAG trunk status on each peer; for “Mark a true endpoint interface as an STP edge port” on a local switch administering branch clients, the relevant evidence is to inspect edge-port state and whether an unexpected BPDU removes that edge assumption.
E:That behavior applies when engineers “Adjust STP path cost on a redundant uplink”; the different operation “Mark a true endpoint interface as an STP edge port” is intended to allow an end-host port to transition quickly without waiting through normal topology learning. That different feature is verified by compare accumulated root-path costs and root-port election before and after adjustment; for “Mark a true endpoint interface as an STP edge port” on a local switch administering branch clients, the relevant evidence is to inspect edge-port state and whether an unexpected BPDU removes that edge assumption.
Question 215
The change-control ticket for a switch used by multiple office teams requires one validation of the goal to allow an end-host port to transition quickly without waiting through normal topology learning. Which evidence should be collected?
- Compare accumulated root-path costs and root-port election before and after adjustment
- Inspect edge-port state and whether an unexpected BPDU removes that edge assumption
- Compare VLAN-to-instance mappings on switches that belong to the same MST region
- Review a BPDU-guard violation and the resulting port status
Explanation
Correct Answer
B:The switch behavior that matters is: edge-port behavior assumes no downstream bridge and should be paired with BPDU protection where appropriate. Directly measuring that result demonstrates whether the step to allow an end-host port to transition quickly without waiting through normal topology learning succeeded on a switch used by multiple office teams.
Incorrect Answers
A:This check is suited to “Adjust STP path cost on a redundant uplink” when trying to steer the preferred path toward the existing root over a better link, not to verify “Mark a true endpoint interface as an STP edge port” at the warehouse. Checking “Mark a true endpoint interface as an STP edge port” at the warehouse requires evidence of its own mechanism: edge-port behavior assumes no downstream bridge and should be paired with BPDU protection where appropriate; that is not the outcome measured by “Adjust STP path cost on a redundant uplink”.
C:The proposed check concerns “Use MSTP instances for multiple VLAN groups” rather than “Mark a true endpoint interface as an STP edge port”: MSTP maps multiple VLANs onto spanning-tree instances within a region. For “Mark a true endpoint interface as an STP edge port” on a switch used by multiple office teams, a better test would be to inspect edge-port state and whether an unexpected BPDU removes that edge assumption, which targets allow an end-host port to transition quickly without waiting through normal topology learning rather than the alternative diagnostic “Use MSTP instances for multiple VLAN groups”.
D:This check is suited to “Enable BPDU guard on a genuine edge port” when trying to stop a newly connected unauthorized switch from altering access-layer topology, not to verify “Mark a true endpoint interface as an STP edge port” at the warehouse. Checking “Mark a true endpoint interface as an STP edge port” at the warehouse requires evidence of its own mechanism: edge-port behavior assumes no downstream bridge and should be paired with BPDU protection where appropriate; that is not the outcome measured by “Enable BPDU guard on a genuine edge port”.
Question 216
An administrator responsible for a production FortiSwitch fabric in the headquarters must steer the preferred path toward the existing root over a better link. Which configuration best matches that precise goal?
- Use root guard on a downstream port
- Adjust STP path cost on a redundant uplink
- Mark a true endpoint interface as an STP edge port
- Enable RSTP for rapid converging topology
Explanation
Correct Answer
B:At this network boundary, bridge path cost contributes to best-root-path selection independently of link aggregation membership. The operator can test this claim by the specific check: compare accumulated root-path costs and root-port election before and after adjustment.
Incorrect Answers
A:Compared with the requested “Adjust STP path cost on a redundant uplink” at the headquarters, 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 headquarters, the operational proof would instead be to compare accumulated root-path costs and root-port election before and after adjustment, 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 headquarters, “Mark a true endpoint interface as an STP edge port” is a different type of control from “Adjust STP path cost on a redundant uplink”: edge-port behavior assumes no downstream bridge and should be paired with BPDU protection where appropriate. Unlike the requested feature, that setting addresses the need to allow an end-host port to transition quickly without waiting through normal topology learning, not the objective to steer the preferred path toward the existing root over a better link.
D:Compared with the requested “Adjust STP path cost on a redundant uplink” at the headquarters, this would reduce reconvergence delay after a legitimate Layer 2 link state change instead: rapid spanning tree exchanges BPDUs and uses rapid port roles and state transitions where supported. At the headquarters, the operational proof would instead be to compare accumulated root-path costs and root-port election before and after adjustment, whereas “Enable RSTP for rapid converging topology” is validated by a different test: observe root-port and alternate-port role changes during a link-failure test.
Question 217
A change record for a newly racked distribution unit states “Adjust STP path cost on a redundant uplink.” Which description correctly explains what this will accomplish?
- Bridge path cost contributes to best-root-path selection independently of link aggregation membership
- BPDU guard shuts or blocks the protected edge when it receives spanning-tree control BPDUs
- MSTP maps multiple VLANs onto spanning-tree instances within a region
- The bridge with the lowest complete bridge ID is selected, with MAC breaking priority ties
Explanation
Correct Answer
A:In this deployment, the configured operation is meant to steer the preferred path toward the existing root over a better link. The most relevant validation is to compare accumulated root-path costs and root-port election before and after adjustment for the equipment at the hospital wing.
Incorrect Answers
B:This outcome would be relevant to “Enable BPDU guard on a genuine edge port” at the hospital wing, not the task “Adjust STP path cost on a redundant uplink”; the other task is to stop a newly connected unauthorized switch from altering access-layer topology. The action “Adjust STP path cost on a redundant uplink” targets a different result: bridge path cost contributes to best-root-path selection independently of link aggregation membership; the proposed alternative would instead be checked by review a BPDU-guard violation and the resulting port status.
C:That behavior applies when engineers “Use MSTP instances for multiple VLAN groups”; the different operation “Adjust STP path cost on a redundant uplink” is intended to steer the preferred path toward the existing root over a better link. That different feature is verified by compare VLAN-to-instance mappings on switches that belong to the same MST region; for “Adjust STP path cost on a redundant uplink” on a newly racked distribution unit, the relevant evidence is to compare accumulated root-path costs and root-port election before and after adjustment.
D:That behavior applies when engineers “Choose a lower STP bridge priority for the desired root”; the different operation “Adjust STP path cost on a redundant uplink” is intended to steer the preferred path toward the existing root over a better link. That different feature is verified by compare effective bridge IDs rather than merely hostnames or interface speeds; for “Adjust STP path cost on a redundant uplink” on a newly racked distribution unit, the relevant evidence is to compare accumulated root-path costs and root-port election before and after adjustment.
Question 218
A FortiSwitch engineer in the training center is documenting successful operation of “Adjust STP path cost on a redundant uplink.” Which measurement or inspection confirms it?
- Observe root-port and alternate-port role changes during a link-failure test
- Inspect loop-guard counters and the protected port's state after a loop test
- Inject a test superior BPDU and check that the designated root remains unchanged
- Compare accumulated root-path costs and root-port election before and after adjustment
- Compare MSTP root information and MCLAG trunk status on each peer
Explanation
Correct Answer
D:For the stated requirement, bridge path cost contributes to best-root-path selection independently of link aggregation membership. Directly measuring that result demonstrates whether the step to steer the preferred path toward the existing root over a better link succeeded on two distribution switches.
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 “Adjust STP path cost on a redundant uplink” at the training center. Checking “Adjust STP path cost on a redundant uplink” at the training center requires evidence of its own mechanism: bridge path cost contributes to best-root-path selection independently of link aggregation membership; that is not the outcome measured by “Enable RSTP for rapid converging topology”.
B:This check is suited to “Enable loop guard for downstream loop detection” when trying to detect certain loop conditions beneath a switch port rather than replacing STP, not to verify “Adjust STP path cost on a redundant uplink” at the training center. Checking “Adjust STP path cost on a redundant uplink” at the training center requires evidence of its own mechanism: bridge path cost contributes to best-root-path selection independently of link aggregation membership; that is not the outcome measured by “Enable loop guard for downstream loop detection”.
C:The proposed check concerns “Use root guard on a downstream port” rather than “Adjust STP path cost on a redundant uplink”: root guard prevents superior BPDUs on that link from changing the intended root path. For “Adjust STP path cost on a redundant uplink” on two distribution switches, a better test would be to compare accumulated root-path costs and root-port election before and after adjustment, which targets steer the preferred path toward the existing root over a better link rather than the alternative diagnostic “Use root guard on a downstream port”.
E:The proposed check concerns “Keep STP-aware behavior consistent around MCLAG peers” rather than “Adjust STP path cost on a redundant uplink”: MCLAG/STP integration must be coordinated for access trunks and individual asymmetric links. For “Adjust STP path cost on a redundant uplink” on two distribution switches, a better test would be to compare accumulated root-path costs and root-port election before and after adjustment, which targets steer the preferred path toward the existing root over a better link rather than the alternative diagnostic “Keep STP-aware behavior consistent around MCLAG peers”.
Question 219
For the lab, the network team needs to prevent an aggregated pair from presenting conflicting topology behavior. Which change is the most direct way to implement that requirement on a staging FortiSwitch?
- Enable BPDU guard on a genuine edge port
- Use MSTP instances for multiple VLAN groups
- Keep STP-aware behavior consistent around MCLAG peers
- Choose a lower STP bridge priority for the desired root
Explanation
Correct Answer
C:The deciding detail is that MCLAG/STP integration must be coordinated for access trunks and individual asymmetric links. This distinction is material to the lab, where the stated goal is to prevent an aggregated pair from presenting conflicting topology behavior.
Incorrect Answers
A:Compared with the requested “Keep STP-aware behavior consistent around MCLAG peers” 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 MSTP root information and MCLAG trunk status on each peer, 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.
B:Compared with the requested “Keep STP-aware behavior consistent around MCLAG peers” 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 compare MSTP root information and MCLAG trunk status on each peer, 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.
D:For the lab, “Choose a lower STP bridge priority for the desired root” is a different type of control from “Keep STP-aware behavior consistent around MCLAG peers”: the bridge with the lowest complete bridge ID is selected, with MAC breaking priority ties. Unlike the requested feature, that setting addresses the need to make a selected core switch preferable in STP root election, not the objective to prevent an aggregated pair from presenting conflicting topology behavior.
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?
- MCLAG/STP integration must be coordinated for access trunks and individual asymmetric links
- Bridge path cost contributes to best-root-path selection independently of link aggregation membership
- FortiSwitch loop guard monitors the subtending network and works alongside spanning tree
- 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.