Question 90
On a carefully segmented Layer 2 network in the retail site, the next task is to avoid losing the peer relationship when one cross-connect fails. What is the appropriate configuration decision?
- Establish redundant interchassis links for MCLAG
- Build a two-peer MCLAG core
- Keep MCLAG peer hardware and software aligned
- Create a switch inter-switch link for FortiLink discovery
Explanation
Correct Answer
A:The critical distinction is that the interchassis link communicates peer state; at least two links are recommended for ICL resilience. The operator can test this claim by the specific check: check the ICL member status on both switches and verify a remaining path after a member fails.
Incorrect Answers
B:Compared with the requested “Establish redundant interchassis links for MCLAG” at the retail site, this would maintain data forwarding when one distribution switch stops responding instead: two peer FortiSwitch units present an aggregated logical attachment to dual-homed devices. At the retail site, the operational proof would instead be to check the ICL member status on both switches and verify a remaining path after a member fails, whereas “Build a two-peer MCLAG core” is validated by a different test: verify both peer states and the dual-homed trunk membership in the MCLAG monitor.
C:Compared with the requested “Establish redundant interchassis links for MCLAG” at the retail site, this would avoid unsupported mismatches in a redundant switch pair instead: Fortinet recommends the same peer model and software version for a supported MCLAG design. At the retail site, the operational proof would instead be to check the ICL member status on both switches and verify a remaining path after a member fails, whereas “Keep MCLAG peer hardware and software aligned” is validated by a different test: compare model IDs and installed firmware versions before enabling the peer group.
D:For the retail site, “Create a switch inter-switch link for FortiLink discovery” is a different type of control from “Establish redundant interchassis links for MCLAG”: an ISL carries the FortiLink control reachability across the switch chain. Unlike the requested feature, that setting addresses the need to allow managed descendants to be discovered beyond the directly connected switch, not the objective to avoid losing the peer relationship when one cross-connect fails.
Question 91
A switch change for the airport office consists of this step: establish redundant interchassis links for MCLAG. Which behavior reflects the purpose of that change?
- An inter-switch link carries discovery and management traffic onward to additional managed switches
- Split-brain safeguards determine which peer should enter a dormant state under a detected isolation event
- The interchassis link communicates peer state; at least two links are recommended for ICL resilience
- A supported HA/FortiLink wiring design provides connectivity to the FortiGate cluster rather than a single appliance
Explanation
Correct Answer
C:That setting is appropriate here because the configured operation is meant to avoid losing the peer relationship when one cross-connect fails. The most relevant validation is to check the ICL member status on both switches and verify a remaining path after a member fails for the equipment at the airport office.
Incorrect Answers
A:That behavior applies when engineers “Form a FortiLink-managed switch cascade”; the different operation “Establish redundant interchassis links for MCLAG” is intended to avoid losing the peer relationship when one cross-connect fails. That different feature is verified by inspect the topology tree and confirm downstream serial numbers appear beneath the uplink switch; for “Establish redundant interchassis links for MCLAG” on a central switching stack, the relevant evidence is to check the ICL member status on both switches and verify a remaining path after a member fails.
B:This outcome would be relevant to “Enable MCLAG split-brain detection on both peers” at the airport office, not the task “Establish redundant interchassis links for MCLAG”; the other task is to avoid both surviving switches independently claiming active service when the ICL is severed. The action “Establish redundant interchassis links for MCLAG” targets a different result: the interchassis link communicates peer state; at least two links are recommended for ICL resilience; the proposed alternative would instead be checked by inspect peer split-brain state and configured priorities on each member.
D:That behavior applies when engineers “Connect FortiGate HA to a FortiLink stack”; the different operation “Establish redundant interchassis links for MCLAG” is intended to avoid losing the peer relationship when one cross-connect fails. That different feature is verified by test an HA failover and monitor FortiSwitch authorization and control-plane reachability; for “Establish redundant interchassis links for MCLAG” on a central switching stack, the relevant evidence is to check the ICL member status on both switches and verify a remaining path after a member fails.
Question 92
After implementing “Establish redundant interchassis links for MCLAG,” the site engineer needs to assess its actual effect on a switch used by multiple office teams. Which test is the best match?
- Confirm LACP/member state and whether the FortiLink aggregate remains available after one port fails
- Check the ICL member status on both switches and verify a remaining path after a member fails
- Inspect the access switch LACP partner identity and the MCLAG trunk operational state
- Inspect MCLAG-STP settings and bridge information on both peers
Explanation
Correct Answer
B:This is the precise control because the interchassis link communicates peer state; at least two links are recommended for ICL resilience. Directly measuring that result demonstrates whether the step to avoid losing the peer relationship when one cross-connect fails succeeded on a switch used by multiple office teams.
Incorrect Answers
A:This check is suited to “Use a FortiLink LAG with suitable member ports” when trying to increase resiliency of the FortiGate-to-switch management and data connection, not to verify “Establish redundant interchassis links for MCLAG” at the operations center. Checking “Establish redundant interchassis links for MCLAG” at the operations center requires evidence of its own mechanism: the interchassis link communicates peer state; at least two links are recommended for ICL resilience; that is not the outcome measured by “Use a FortiLink LAG with suitable member ports”.
C:The proposed check concerns “Dual-home an access switch with LACP to MCLAG peers” rather than “Establish redundant interchassis links for MCLAG”: an MCLAG presents the pair as a logical LACP partner for the access switch. For “Establish redundant interchassis links for MCLAG” on a switch used by multiple office teams, a better test would be to check the ICL member status on both switches and verify a remaining path after a member fails, which targets avoid losing the peer relationship when one cross-connect fails rather than the alternative diagnostic “Dual-home an access switch with LACP to MCLAG peers”.
D:This check is suited to “Enable STP-aware MCLAG behavior where required” when trying to keep bridge-loop protection consistent when LAGs span peer switches, not to verify “Establish redundant interchassis links for MCLAG” at the operations center. Checking “Establish redundant interchassis links for MCLAG” at the operations center requires evidence of its own mechanism: the interchassis link communicates peer state; at least two links are recommended for ICL resilience; that is not the outcome measured by “Enable STP-aware MCLAG behavior where required”.
Question 93
At the warehouse, a technician is choosing between several switching features to provide two physical upstream switches without creating separate spanning-tree forwarding paths. Which one belongs in the implementation plan?
- Use an active LACP trunk for a dual-homed attachment
- Connect FortiGate HA to a FortiLink stack
- Create a switch inter-switch link for FortiLink discovery
- Build a two-peer MCLAG core
- Dual-home an access switch with LACP to MCLAG peers
Explanation
Correct Answer
E:The implementation works because an MCLAG presents the pair as a logical LACP partner for the access switch. This distinction is material to the warehouse, where the stated goal is to provide two physical upstream switches without creating separate spanning-tree forwarding paths.
Incorrect Answers
A:For the warehouse, “Use an active LACP trunk for a dual-homed attachment” is a different type of control from “Dual-home an access switch with LACP to MCLAG peers”: LACP identifies and maintains logical members; independent ports are not a substitute for a bundled attachment. Unlike the requested feature, that setting addresses the need to negotiate port bundling with an access device attached to MCLAG peers, not the objective to provide two physical upstream switches without creating separate spanning-tree forwarding paths.
B:Compared with the requested “Dual-home an access switch with LACP to MCLAG peers” at the warehouse, this would keep switch management connected when the active FortiGate changes instead: a supported HA/FortiLink wiring design provides connectivity to the FortiGate cluster rather than a single appliance. At the warehouse, the operational proof would instead be to inspect the access switch LACP partner identity and the MCLAG trunk operational state, whereas “Connect FortiGate HA to a FortiLink stack” is validated by a different test: test an HA failover and monitor FortiSwitch authorization and control-plane reachability.
C:Compared with the requested “Dual-home an access switch with LACP to MCLAG peers” at the warehouse, this would allow managed descendants to be discovered beyond the directly connected switch instead: an ISL carries the FortiLink control reachability across the switch chain. At the warehouse, the operational proof would instead be to inspect the access switch LACP partner identity and the MCLAG trunk operational state, whereas “Create a switch inter-switch link for FortiLink discovery” is validated by a different test: examine ISL status and whether the expected descendant switch appears in discovery.
D:Compared with the requested “Dual-home an access switch with LACP to MCLAG peers” at the warehouse, this would maintain data forwarding when one distribution switch stops responding instead: two peer FortiSwitch units present an aggregated logical attachment to dual-homed devices. At the warehouse, the operational proof would instead be to inspect the access switch LACP partner identity and the MCLAG trunk operational state, whereas “Build a two-peer MCLAG core” is validated by a different test: verify both peer states and the dual-homed trunk membership in the MCLAG monitor.
Question 94
The operator has decided to dual-home an access switch with LACP to MCLAG peers on a newly racked distribution unit at the remote depot. Which operational behavior is the most reasonable expectation of that specific feature?
- An inter-switch link carries discovery and management traffic onward to additional managed switches
- An MCLAG presents the pair as a logical LACP partner for the access switch
- The first pair presents a resilient attachment upstream while serving one or more downstream switches
- Split-brain safeguards determine which peer should enter a dormant state under a detected isolation event
Explanation
Correct Answer
B:Given the described goal, the configured operation is meant to provide two physical upstream switches without creating separate spanning-tree forwarding paths. The most relevant validation is to inspect the access switch LACP partner identity and the MCLAG trunk operational state for the equipment at the remote depot.
Incorrect Answers
A:This outcome would be relevant to “Form a FortiLink-managed switch cascade” at the remote depot, not the task “Dual-home an access switch with LACP to MCLAG peers”; the other task is to manage several downstream FortiSwitch units through one upstream connected device. The action “Dual-home an access switch with LACP to MCLAG peers” targets a different result: an MCLAG presents the pair as a logical LACP partner for the access switch; the proposed alternative would instead be checked by inspect the topology tree and confirm downstream serial numbers appear beneath the uplink switch.
C:That behavior applies when engineers “Use a first-tier MCLAG peer group”; the different operation “Dual-home an access switch with LACP to MCLAG peers” is intended to provide two physical upstream switches without creating separate spanning-tree forwarding paths. That different feature is verified by verify both first-tier peers are represented and their shared trunk is synchronized; for “Dual-home an access switch with LACP to MCLAG peers” on a newly racked distribution unit, the relevant evidence is to inspect the access switch LACP partner identity and the MCLAG trunk operational state.
D:That behavior applies when engineers “Enable MCLAG split-brain detection on both peers”; the different operation “Dual-home an access switch with LACP to MCLAG peers” is intended to provide two physical upstream switches without creating separate spanning-tree forwarding paths. That different feature is verified by inspect peer split-brain state and configured priorities on each member; for “Dual-home an access switch with LACP to MCLAG peers” on a newly racked distribution unit, the relevant evidence is to inspect the access switch LACP partner identity and the MCLAG trunk operational state.
Question 95
At the branch office, a dashboard shows ordinary link-up state, but the team also needs proof for “Dual-home an access switch with LACP to MCLAG peers.” Which targeted check should be used?
- Check the ICL member status on both switches and verify a remaining path after a member fails
- Inspect the access switch LACP partner identity and the MCLAG trunk operational state
- Inspect the complete three-tier FortiSwitch topology and unauthorized downstream devices
- Confirm LACP/member state and whether the FortiLink aggregate remains available after one port fails
Explanation
Correct Answer
B:The switch behavior that matters is: an MCLAG presents the pair as a logical LACP partner for the access switch. Directly measuring that result demonstrates whether the step to provide two physical upstream switches without creating separate spanning-tree forwarding paths succeeded on two distribution switches.
Incorrect Answers
A:This check is suited to “Establish redundant interchassis links for MCLAG” when trying to avoid losing the peer relationship when one cross-connect fails, not to verify “Dual-home an access switch with LACP to MCLAG peers” at the branch office. Checking “Dual-home an access switch with LACP to MCLAG peers” at the branch office requires evidence of its own mechanism: an MCLAG presents the pair as a logical LACP partner for the access switch; that is not the outcome measured by “Establish redundant interchassis links for MCLAG”.
C:This check is suited to “Design a three-tier FortiLink stack within supported topologies” when trying to provide hierarchical aggregation, distribution and access while retaining centralized discovery, not to verify “Dual-home an access switch with LACP to MCLAG peers” at the branch office. Checking “Dual-home an access switch with LACP to MCLAG peers” at the branch office requires evidence of its own mechanism: an MCLAG presents the pair as a logical LACP partner for the access switch; that is not the outcome measured by “Design a three-tier FortiLink stack within supported topologies”.
D:The proposed check concerns “Use a FortiLink LAG with suitable member ports” rather than “Dual-home an access switch with LACP to MCLAG peers”: a logical aggregate can carry FortiLink when the topology and split-interface settings match its design. For “Dual-home an access switch with LACP to MCLAG peers” on two distribution switches, a better test would be to inspect the access switch LACP partner identity and the MCLAG trunk operational state, which targets provide two physical upstream switches without creating separate spanning-tree forwarding paths rather than the alternative diagnostic “Use a FortiLink LAG with suitable member ports”.
Question 96
The accepted design for the factory requires the ability to keep switch management connected when the active FortiGate changes. Which switch feature is the closest fit?
- Dual-home an access switch with LACP to MCLAG peers
- Connect FortiGate HA to a FortiLink stack
- Create a switch inter-switch link for FortiLink discovery
- Use an active LACP trunk for a dual-homed attachment
Explanation
Correct Answer
B:At this network boundary, a supported HA/FortiLink wiring design provides connectivity to the FortiGate cluster rather than a single appliance. The operator can test this claim by the specific check: test an HA failover and monitor FortiSwitch authorization and control-plane reachability.
Incorrect Answers
A:For the factory, “Dual-home an access switch with LACP to MCLAG peers” is a different type of control from “Connect FortiGate HA to a FortiLink stack”: an MCLAG presents the pair as a logical LACP partner for the access switch. Unlike the requested feature, that setting addresses the need to provide two physical upstream switches without creating separate spanning-tree forwarding paths, not the objective to keep switch management connected when the active FortiGate changes.
C:Compared with the requested “Connect FortiGate HA to a FortiLink stack” at the factory, this would allow managed descendants to be discovered beyond the directly connected switch instead: an ISL carries the FortiLink control reachability across the switch chain. At the factory, the operational proof would instead be to test an HA failover and monitor FortiSwitch authorization and control-plane reachability, whereas “Create a switch inter-switch link for FortiLink discovery” is validated by a different test: examine ISL status and whether the expected descendant switch appears in discovery.
D:Compared with the requested “Connect FortiGate HA to a FortiLink stack” at the factory, this would negotiate port bundling with an access device attached to MCLAG peers instead: LACP identifies and maintains logical members; independent ports are not a substitute for a bundled attachment. At the factory, the operational proof would instead be to test an HA failover and monitor FortiSwitch authorization and control-plane reachability, whereas “Use an active LACP trunk for a dual-homed attachment” is validated by a different test: check LACP actor/partner state on every participating interface.
Question 97
A switch change for the distribution floor consists of this step: connect FortiGate HA to a FortiLink stack. Which behavior reflects the purpose of that change?
- A supported HA/FortiLink wiring design provides connectivity to the FortiGate cluster rather than a single appliance
- The first pair presents a resilient attachment upstream while serving one or more downstream switches
- An inter-switch link carries discovery and management traffic onward to additional managed switches
- The interchassis link communicates peer state; at least two links are recommended for ICL resilience
- MCLAG STP awareness coordinates the spanning-tree view of the aggregated downstream attachment
Explanation
Correct Answer
A:In this deployment, the configured operation is meant to keep switch management connected when the active FortiGate changes. The most relevant validation is to test an HA failover and monitor FortiSwitch authorization and control-plane reachability for the equipment at the distribution floor.
Incorrect Answers
B:This outcome would be relevant to “Use a first-tier MCLAG peer group” at the distribution floor, not the task “Connect FortiGate HA to a FortiLink stack”; the other task is to aggregate redundant FortiGate-facing connectivity close to the security edge. The action “Connect FortiGate HA to a FortiLink stack” targets a different result: a supported HA/FortiLink wiring design provides connectivity to the FortiGate cluster rather than a single appliance; the proposed alternative would instead be checked by verify both first-tier peers are represented and their shared trunk is synchronized.
C:That behavior applies when engineers “Form a FortiLink-managed switch cascade”; the different operation “Connect FortiGate HA to a FortiLink stack” is intended to keep switch management connected when the active FortiGate changes. That different feature is verified by inspect the topology tree and confirm downstream serial numbers appear beneath the uplink switch; for “Connect FortiGate HA to a FortiLink stack” on a carefully segmented Layer 2 network, the relevant evidence is to test an HA failover and monitor FortiSwitch authorization and control-plane reachability.
D:That behavior applies when engineers “Establish redundant interchassis links for MCLAG”; the different operation “Connect FortiGate HA to a FortiLink stack” is intended to keep switch management connected when the active FortiGate changes. That different feature is verified by check the ICL member status on both switches and verify a remaining path after a member fails; for “Connect FortiGate HA to a FortiLink stack” on a carefully segmented Layer 2 network, the relevant evidence is to test an HA failover and monitor FortiSwitch authorization and control-plane reachability.
E:That behavior applies when engineers “Enable STP-aware MCLAG behavior where required”; the different operation “Connect FortiGate HA to a FortiLink stack” is intended to keep switch management connected when the active FortiGate changes. That different feature is verified by inspect MCLAG-STP settings and bridge information on both peers; for “Connect FortiGate HA to a FortiLink stack” on a carefully segmented Layer 2 network, the relevant evidence is to test an HA failover and monitor FortiSwitch authorization and control-plane reachability.
Question 98
The change-control ticket for a central switching stack requires one validation of the goal to keep switch management connected when the active FortiGate changes. Which evidence should be collected?
- Confirm LACP/member state and whether the FortiLink aggregate remains available after one port fails
- Inspect the complete three-tier FortiSwitch topology and unauthorized downstream devices
- Inspect both tier topologies and the cross-tier trunk state during peer-failure testing
- Test an HA failover and monitor FortiSwitch authorization and control-plane reachability
Explanation
Correct Answer
D:For the stated requirement, a supported HA/FortiLink wiring design provides connectivity to the FortiGate cluster rather than a single appliance. Directly measuring that result demonstrates whether the step to keep switch management connected when the active FortiGate changes succeeded on a central switching stack.
Incorrect Answers
A:This check is suited to “Use a FortiLink LAG with suitable member ports” when trying to increase resiliency of the FortiGate-to-switch management and data connection, not to verify “Connect FortiGate HA to a FortiLink stack” at the media studio. Checking “Connect FortiGate HA to a FortiLink stack” at the media studio requires evidence of its own mechanism: a supported HA/FortiLink wiring design provides connectivity to the FortiGate cluster rather than a single appliance; that is not the outcome measured by “Use a FortiLink LAG with suitable member ports”.
B:The proposed check concerns “Design a three-tier FortiLink stack within supported topologies” rather than “Connect FortiGate HA to a FortiLink stack”: multiple managed tiers require correctly placed ISLs and MCLAGs where redundancy is needed. For “Connect FortiGate HA to a FortiLink stack” on a central switching stack, a better test would be to test an HA failover and monitor FortiSwitch authorization and control-plane reachability, which targets keep switch management connected when the active FortiGate changes rather than the alternative diagnostic “Design a three-tier FortiLink stack within supported topologies”.
C:This check is suited to “Use a second-tier MCLAG pair” when trying to preserve redundant distribution to switches deeper in a hierarchical access design, not to verify “Connect FortiGate HA to a FortiLink stack” at the media studio. Checking “Connect FortiGate HA to a FortiLink stack” at the media studio requires evidence of its own mechanism: a supported HA/FortiLink wiring design provides connectivity to the FortiGate cluster rather than a single appliance; that is not the outcome measured by “Use a second-tier MCLAG pair”.
Question 99
An administrator responsible for a FortiSwitch connected to the security edge in the retail site must preserve redundant distribution to switches deeper in a hierarchical access design. Which configuration best matches that precise goal?
- Use a first-tier MCLAG peer group
- Enable MCLAG split-brain detection on both peers
- Form a FortiLink-managed switch cascade
- Use a second-tier MCLAG pair
Explanation
Correct Answer
D:The deciding detail is that a lower tier MCLAG peer group connects with upper-tier switching through approved inter-switch arrangements. This distinction is material to the retail site, where the stated goal is to preserve redundant distribution to switches deeper in a hierarchical access design.
Incorrect Answers
A:For the retail site, “Use a first-tier MCLAG peer group” is a different type of control from “Use a second-tier MCLAG pair”: the first pair presents a resilient attachment upstream while serving one or more downstream switches. Unlike the requested feature, that setting addresses the need to aggregate redundant FortiGate-facing connectivity close to the security edge, not the objective to preserve redundant distribution to switches deeper in a hierarchical access design.
B:Compared with the requested “Use a second-tier MCLAG pair” at the retail site, this would avoid both surviving switches independently claiming active service when the ICL is severed instead: split-brain safeguards determine which peer should enter a dormant state under a detected isolation event. At the retail site, the operational proof would instead be to inspect both tier topologies and the cross-tier trunk state during peer-failure testing, whereas “Enable MCLAG split-brain detection on both peers” is validated by a different test: inspect peer split-brain state and configured priorities on each member.
C:Compared with the requested “Use a second-tier MCLAG pair” at the retail site, this would manage several downstream FortiSwitch units through one upstream connected device instead: an inter-switch link carries discovery and management traffic onward to additional managed switches. At the retail site, the operational proof would instead be to inspect both tier topologies and the cross-tier trunk state during peer-failure testing, whereas “Form a FortiLink-managed switch cascade” is validated by a different test: inspect the topology tree and confirm downstream serial numbers appear beneath the uplink switch.
Question 100
The operator has decided to use a second-tier MCLAG pair on an access switch in routine maintenance at the airport office. Which operational behavior is the most reasonable expectation of that specific feature?
- The interchassis link communicates peer state; at least two links are recommended for ICL resilience
- A supported HA/FortiLink wiring design provides connectivity to the FortiGate cluster rather than a single appliance
- A lower tier MCLAG peer group connects with upper-tier switching through approved inter-switch arrangements
- Multiple managed tiers require correctly placed ISLs and MCLAGs where redundancy is needed
- A logical aggregate can carry FortiLink when the topology and split-interface settings match its design
Explanation
Correct Answer
C:The relevant mechanism is: the configured operation is meant to preserve redundant distribution to switches deeper in a hierarchical access design. The most relevant validation is to inspect both tier topologies and the cross-tier trunk state during peer-failure testing for the equipment at the airport office.
Incorrect Answers
A:That behavior applies when engineers “Establish redundant interchassis links for MCLAG”; the different operation “Use a second-tier MCLAG pair” is intended to preserve redundant distribution to switches deeper in a hierarchical access design. That different feature is verified by check the ICL member status on both switches and verify a remaining path after a member fails; for “Use a second-tier MCLAG pair” on an access switch in routine maintenance, the relevant evidence is to inspect both tier topologies and the cross-tier trunk state during peer-failure testing.
B:That behavior applies when engineers “Connect FortiGate HA to a FortiLink stack”; the different operation “Use a second-tier MCLAG pair” is intended to preserve redundant distribution to switches deeper in a hierarchical access design. That different feature is verified by test an HA failover and monitor FortiSwitch authorization and control-plane reachability; for “Use a second-tier MCLAG pair” on an access switch in routine maintenance, the relevant evidence is to inspect both tier topologies and the cross-tier trunk state during peer-failure testing.
D:That behavior applies when engineers “Design a three-tier FortiLink stack within supported topologies”; the different operation “Use a second-tier MCLAG pair” is intended to preserve redundant distribution to switches deeper in a hierarchical access design. That different feature is verified by inspect the complete three-tier FortiSwitch topology and unauthorized downstream devices; for “Use a second-tier MCLAG pair” on an access switch in routine maintenance, the relevant evidence is to inspect both tier topologies and the cross-tier trunk state during peer-failure testing.
E:This outcome would be relevant to “Use a FortiLink LAG with suitable member ports” at the airport office, not the task “Use a second-tier MCLAG pair”; the other task is to increase resiliency of the FortiGate-to-switch management and data connection. The action “Use a second-tier MCLAG pair” targets a different result: a lower tier MCLAG peer group connects with upper-tier switching through approved inter-switch arrangements; the proposed alternative would instead be checked by confirm LACP/member state and whether the FortiLink aggregate remains available after one port fails.