Question 190
Four FortiSwitch units in the headquarters share an MSTP instance. Their bridge IDs use these priority/MAC combinations: FSW-A: 20480, 02:00:0a:01:0c:2d; FSW-B: 20480, 02:00:0a:00:0a:20; FSW-C: 24576, 02:00:0a:02:0e:3a; FSW-D: 28672, 02:00:0a:03:10:47. Assuming all advertise and see each other, which switch becomes the root?
- FSW-D
- FSW-A
- FSW-C
- FSW-B
Explanation
Correct Answer
D:For the headquarters, the winning bridge ID compares priority 20480 first, using MAC 02:00:0a:00:0a:20 to break any priority tie. FSW-B has the lowest complete bridge ID and therefore becomes root.
Incorrect Answers
A:FSW-D advertises priority 28672 and MAC 02:00:0a:03:10:47, whereas FSW-B advertises the superior bridge ID with priority 20480 and MAC 02:00:0a:00:0a:20. The priority-then-MAC comparison therefore rejects this specific candidate.
B:FSW-A advertises priority 20480 and MAC 02:00:0a:01:0c:2d, whereas FSW-B advertises the superior bridge ID with priority 20480 and MAC 02:00:0a:00:0a:20. The priority-then-MAC comparison therefore rejects this specific candidate.
C:FSW-C advertises priority 24576 and MAC 02:00:0a:02:0e:3a, whereas FSW-B advertises the superior bridge ID with priority 20480 and MAC 02:00:0a:00:0a:20. The priority-then-MAC comparison therefore rejects this specific candidate.
Question 191
Four FortiSwitch units in the hospital wing share an MSTP instance. Their bridge IDs use these priority/MAC combinations: FSW-A: 12288, 02:00:0b:02:0f:3b; FSW-B: 16384, 02:00:0b:01:0d:2e; FSW-C: 12288, 02:00:0b:00:0b:21; FSW-D: 20480, 02:00:0b:03:11:48. Assuming all advertise and see each other, which switch becomes the root?
- FSW-D
- FSW-A
- FSW-B
- FSW-C
Explanation
Correct Answer
D:For the hospital wing, the winning bridge ID compares priority 12288 first, using MAC 02:00:0b:00:0b:21 to break any priority tie. FSW-C has the lowest complete bridge ID and therefore becomes root.
Incorrect Answers
A:FSW-D advertises priority 20480 and MAC 02:00:0b:03:11:48, whereas FSW-C advertises the superior bridge ID with priority 12288 and MAC 02:00:0b:00:0b:21. The priority-then-MAC comparison therefore rejects this specific candidate.
B:FSW-A advertises priority 12288 and MAC 02:00:0b:02:0f:3b, whereas FSW-C advertises the superior bridge ID with priority 12288 and MAC 02:00:0b:00:0b:21. The priority-then-MAC comparison therefore rejects this specific candidate.
C:FSW-B advertises priority 16384 and MAC 02:00:0b:01:0d:2e, whereas FSW-C advertises the superior bridge ID with priority 12288 and MAC 02:00:0b:00:0b:21. The priority-then-MAC comparison therefore rejects this specific candidate.
Question 192
Four FortiSwitch units in the training center share an MSTP instance. Their bridge IDs use these priority/MAC combinations: FSW-A: 4096, 02:00:0c:00:0c:22; FSW-B: 8192, 02:00:0c:01:0e:2f; FSW-C: 12288, 02:00:0c:02:10:3c; FSW-D: 16384, 02:00:0c:03:12:49. Assuming all advertise and see each other, which switch becomes the root?
- FSW-C
- FSW-A
- FSW-D
- FSW-B
Explanation
Correct Answer
B:For the training center, the winning bridge ID compares priority 4096 first, using MAC 02:00:0c:00:0c:22 to break any priority tie. FSW-A has the lowest complete bridge ID and therefore becomes root.
Incorrect Answers
A:FSW-C advertises priority 12288 and MAC 02:00:0c:02:10:3c, whereas FSW-A advertises the superior bridge ID with priority 4096 and MAC 02:00:0c:00:0c:22. The priority-then-MAC comparison therefore rejects this specific candidate.
C:FSW-D advertises priority 16384 and MAC 02:00:0c:03:12:49, whereas FSW-A advertises the superior bridge ID with priority 4096 and MAC 02:00:0c:00:0c:22. The priority-then-MAC comparison therefore rejects this specific candidate.
D:FSW-B advertises priority 8192 and MAC 02:00:0c:01:0e:2f, whereas FSW-A advertises the superior bridge ID with priority 4096 and MAC 02:00:0c:00:0c:22. The priority-then-MAC comparison therefore rejects this specific candidate.
Question 193
Four FortiSwitch units in the lab share an MSTP instance. Their bridge IDs use these priority/MAC combinations: FSW-A: 12288, 02:00:0d:01:0f:30; FSW-B: 12288, 02:00:0d:00:0d:23; FSW-C: 16384, 02:00:0d:02:11:3d; FSW-D: 20480, 02:00:0d:03:13:4a. Assuming all advertise and see each other, which switch becomes the root?
- FSW-A
- FSW-B
- FSW-D
- FSW-C
Explanation
Correct Answer
B:For the lab, the winning bridge ID compares priority 12288 first, using MAC 02:00:0d:00:0d:23 to break any priority tie. FSW-B has the lowest complete bridge ID and therefore becomes root.
Incorrect Answers
A:FSW-A advertises priority 12288 and MAC 02:00:0d:01:0f:30, whereas FSW-B advertises the superior bridge ID with priority 12288 and MAC 02:00:0d:00:0d:23. The priority-then-MAC comparison therefore rejects this specific candidate.
C:FSW-D advertises priority 20480 and MAC 02:00:0d:03:13:4a, whereas FSW-B advertises the superior bridge ID with priority 12288 and MAC 02:00:0d:00:0d:23. The priority-then-MAC comparison therefore rejects this specific candidate.
D:FSW-C advertises priority 16384 and MAC 02:00:0d:02:11:3d, whereas FSW-B advertises the superior bridge ID with priority 12288 and MAC 02:00:0d:00:0d:23. The priority-then-MAC comparison therefore rejects this specific candidate.
Question 194
Four FortiSwitch units in the media studio share an MSTP instance. Their bridge IDs use these priority/MAC combinations: FSW-A: 24576, 02:00:0e:02:12:3e; FSW-B: 28672, 02:00:0e:01:10:31; FSW-C: 24576, 02:00:0e:00:0e:24; FSW-D: 32768, 02:00:0e:03:14:4b. Assuming all advertise and see each other, which switch becomes the root?
- FSW-B
- FSW-C
- FSW-A
- FSW-D
Explanation
Correct Answer
B:For the media studio, the winning bridge ID compares priority 24576 first, using MAC 02:00:0e:00:0e:24 to break any priority tie. FSW-C has the lowest complete bridge ID and therefore becomes root.
Incorrect Answers
A:FSW-B advertises priority 28672 and MAC 02:00:0e:01:10:31, whereas FSW-C advertises the superior bridge ID with priority 24576 and MAC 02:00:0e:00:0e:24. The priority-then-MAC comparison therefore rejects this specific candidate.
C:FSW-A advertises priority 24576 and MAC 02:00:0e:02:12:3e, whereas FSW-C advertises the superior bridge ID with priority 24576 and MAC 02:00:0e:00:0e:24. The priority-then-MAC comparison therefore rejects this specific candidate.
D:FSW-D advertises priority 32768 and MAC 02:00:0e:03:14:4b, whereas FSW-C advertises the superior bridge ID with priority 24576 and MAC 02:00:0e:00:0e:24. The priority-then-MAC comparison therefore rejects this specific candidate.
Question 195
On a managed switch running FortiSwitchOS 7.6 in the clinic, the next task is to stop a newly connected unauthorized switch from altering access-layer topology. What is the appropriate configuration decision?
- Use root guard on a downstream port
- Enable BPDU guard on a genuine edge port
- Adjust STP path cost on a redundant uplink
- Enable RSTP for rapid converging topology
Explanation
Correct Answer
B:The deciding detail is that BPDU guard shuts or blocks the protected edge when it receives spanning-tree control BPDUs. This distinction is material to the clinic, where the stated goal is to stop a newly connected unauthorized switch from altering access-layer topology.
Incorrect Answers
A:For the clinic, “Use root guard on a downstream port” is a different type of control from “Enable BPDU guard on a genuine edge port”: 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 stop a newly connected unauthorized switch from altering access-layer topology.
C:Compared with the requested “Enable BPDU guard on a genuine edge port” at the clinic, 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 clinic, the operational proof would instead be to review a BPDU-guard violation and the resulting port status, 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.
D:Compared with the requested “Enable BPDU guard on a genuine edge port” at the clinic, 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 clinic, the operational proof would instead be to review a BPDU-guard violation and the resulting port status, 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 196
On an access switch in routine maintenance, “Enable BPDU guard on a genuine edge port” is configured for the data hall. What effect should an administrator expect without assuming unrelated features are enabled?
- Edge-port behavior assumes no downstream bridge and should be paired with BPDU protection where appropriate
- 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
- MSTP maps multiple VLANs onto spanning-tree instances within a region
- MCLAG/STP integration must be coordinated for access trunks and individual asymmetric links
Explanation
Correct Answer
C:The relevant mechanism is: the configured operation is meant to stop a newly connected unauthorized switch from altering access-layer topology. The most relevant validation is to review a BPDU-guard violation and the resulting port status for the equipment at the data hall.
Incorrect Answers
A:That behavior applies when engineers “Mark a true endpoint interface as an STP edge port”; the different operation “Enable BPDU guard on a genuine edge port” is intended to stop a newly connected unauthorized switch from altering access-layer topology. That different feature is verified by inspect edge-port state and whether an unexpected BPDU removes that edge assumption; for “Enable BPDU guard on a genuine edge port” on an access switch in routine maintenance, the relevant evidence is to review a BPDU-guard violation and the resulting port status.
B:That behavior applies when engineers “Choose a lower STP bridge priority for the desired root”; the different operation “Enable BPDU guard on a genuine edge port” is intended to stop a newly connected unauthorized switch from altering access-layer topology. That different feature is verified by compare effective bridge IDs rather than merely hostnames or interface speeds; for “Enable BPDU guard on a genuine edge port” on an access switch in routine maintenance, the relevant evidence is to review a BPDU-guard violation and the resulting port status.
D:This outcome would be relevant to “Use MSTP instances for multiple VLAN groups” at the data hall, not the task “Enable BPDU guard on a genuine edge port”; the other task is to apply distinct spanning-tree forwarding decisions to selected sets of VLANs. The action “Enable BPDU guard on a genuine edge port” targets a different result: BPDU guard shuts or blocks the protected edge when it receives spanning-tree control BPDUs; the proposed alternative would instead be checked by compare VLAN-to-instance mappings on switches that belong to the same MST region.
E:That behavior applies when engineers “Keep STP-aware behavior consistent around MCLAG peers”; the different operation “Enable BPDU guard on a genuine edge port” is intended to stop a newly connected unauthorized switch from altering access-layer topology. That different feature is verified by compare MSTP root information and MCLAG trunk status on each peer; for “Enable BPDU guard on a genuine edge port” on an access switch in routine maintenance, the relevant evidence is to review a BPDU-guard violation and the resulting port status.
Question 197
A feature acceptance test on a managed campus switch concerns “Enable BPDU guard on a genuine edge port.” What should be checked to establish its expected operation?
- Compare effective bridge IDs rather than merely hostnames or interface speeds
- Inspect loop-guard counters and the protected port's state after a loop test
- Review a BPDU-guard violation and the resulting port status
- Compare accumulated root-path costs and root-port election before and after adjustment
Explanation
Correct Answer
C:This approach fits because BPDU guard shuts or blocks the protected edge when it receives spanning-tree control BPDUs. Directly measuring that result demonstrates whether the step to stop a newly connected unauthorized switch from altering access-layer topology succeeded on a managed campus switch.
Incorrect Answers
A:This check is suited to “Choose a lower STP bridge priority for the desired root” when trying to make a selected core switch preferable in STP root election, not to verify “Enable BPDU guard on a genuine edge port” at the development floor. Checking “Enable BPDU guard on a genuine edge port” at the development floor requires evidence of its own mechanism: BPDU guard shuts or blocks the protected edge when it receives spanning-tree control BPDUs; that is not the outcome measured by “Choose a lower STP bridge priority for the desired root”.
B:The proposed check concerns “Enable loop guard for downstream loop detection” rather than “Enable BPDU guard on a genuine edge port”: FortiSwitch loop guard monitors the subtending network and works alongside spanning tree. For “Enable BPDU guard on a genuine edge port” on a managed campus switch, a better test would be to review a BPDU-guard violation and the resulting port status, which targets stop a newly connected unauthorized switch from altering access-layer topology rather than the alternative diagnostic “Enable loop guard for downstream loop detection”.
D: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 “Enable BPDU guard on a genuine edge port” at the development floor. Checking “Enable BPDU guard on a genuine edge port” at the development floor requires evidence of its own mechanism: BPDU guard shuts or blocks the protected edge when it receives spanning-tree control BPDUs; that is not the outcome measured by “Adjust STP path cost on a redundant uplink”.
Question 198
At the conference venue, a technician is choosing between several switching features to prevent an access-layer device from advertising itself as a superior STP root. Which one belongs in the implementation plan?
- Use MSTP instances for multiple VLAN groups
- Use root guard on a downstream port
- Keep STP-aware behavior consistent around MCLAG peers
- Mark a true endpoint interface as an STP edge port
Explanation
Correct Answer
B:The critical distinction is that root guard prevents superior BPDUs on that link from changing the intended root path. The operator can test this claim by the specific check: inject a test superior BPDU and check that the designated root remains unchanged.
Incorrect Answers
A:Compared with the requested “Use root guard on a downstream port” at the conference venue, 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 conference venue, the operational proof would instead be to inject a test superior BPDU and check that the designated root remains unchanged, 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 conference venue, “Keep STP-aware behavior consistent around MCLAG peers” is a different type of control from “Use root guard on a downstream port”: 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 prevent an access-layer device from advertising itself as a superior STP root.
D:Compared with the requested “Use root guard on a downstream port” at the conference venue, 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 conference venue, the operational proof would instead be to inject a test superior BPDU and check that the designated root remains unchanged, 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 199
For the hospital wing, an administrator applies the action “Use root guard on a downstream port.” Which effect should appear when it operates as intended?
- FortiSwitch loop guard monitors the subtending network and works alongside spanning tree
- Bridge path cost contributes to best-root-path selection independently of link aggregation membership
- The bridge with the lowest complete bridge ID is selected, with MAC breaking priority ties
- 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
Explanation
Correct Answer
E:That setting is appropriate here because the configured operation is meant to prevent an access-layer device from advertising itself as a superior STP root. The most relevant validation is to inject a test superior BPDU and check that the designated root remains unchanged for the equipment at the hospital wing.
Incorrect Answers
A:This outcome would be relevant to “Enable loop guard for downstream loop detection” at the hospital wing, not the task “Use root guard on a downstream port”; the other task is to detect certain loop conditions beneath a switch port rather than replacing STP. The action “Use root guard on a downstream port” targets a different result: root guard prevents superior BPDUs on that link from changing the intended root path; the proposed alternative would instead be checked by inspect loop-guard counters and the protected port's state after a loop test.
B:That behavior applies when engineers “Adjust STP path cost on a redundant uplink”; the different operation “Use root guard on a downstream port” is intended to prevent an access-layer device from advertising itself as a superior STP root. That different feature is verified by compare accumulated root-path costs and root-port election before and after adjustment; for “Use root guard on a downstream port” on a FortiLink-managed access switch, the relevant evidence is to 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 root guard on a downstream port” is intended to prevent an access-layer device from advertising itself as a superior STP root. That different feature is verified by compare effective bridge IDs rather than merely hostnames or interface speeds; for “Use root guard on a downstream port” on a FortiLink-managed access switch, the relevant evidence is to inject a test superior BPDU and check that the designated root remains unchanged.
D:That behavior applies when engineers “Enable RSTP for rapid converging topology”; the different operation “Use root guard on a downstream port” is intended to prevent an access-layer device from advertising itself as a superior STP root. That different feature is verified by observe root-port and alternate-port role changes during a link-failure test; for “Use root guard on a downstream port” on a FortiLink-managed access switch, the relevant evidence is to inject a test superior BPDU and check that the designated root remains unchanged.
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?
- Inspect edge-port state and whether an unexpected BPDU removes that edge assumption
- Review a BPDU-guard violation and the resulting port status
- Inject a test superior BPDU and check that the designated root remains unchanged
- 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”.