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.
Question 101
A feature acceptance test on a managed campus switch concerns “Use a second-tier MCLAG pair.” What should be checked to establish its expected operation?
- Verify both peer states and the dual-homed trunk membership in the MCLAG monitor
- Inspect both tier topologies and the cross-tier trunk state during peer-failure testing
- Examine ISL status and whether the expected descendant switch appears in discovery
- Compare model IDs and installed firmware versions before enabling the peer group
Explanation
Correct Answer
B:This approach fits because a lower tier MCLAG peer group connects with upper-tier switching through approved inter-switch arrangements. Directly measuring that result demonstrates whether the step to preserve redundant distribution to switches deeper in a hierarchical access design succeeded on a managed campus switch.
Incorrect Answers
A:The proposed check concerns “Build a two-peer MCLAG core” rather than “Use a second-tier MCLAG pair”: two peer FortiSwitch units present an aggregated logical attachment to dual-homed devices. For “Use a second-tier MCLAG pair” on a managed campus switch, a better test would be to inspect both tier topologies and the cross-tier trunk state during peer-failure testing, which targets preserve redundant distribution to switches deeper in a hierarchical access design rather than the alternative diagnostic “Build a two-peer MCLAG core”.
C:This check is suited to “Create a switch inter-switch link for FortiLink discovery” when trying to allow managed descendants to be discovered beyond the directly connected switch, not to verify “Use a second-tier MCLAG pair” at the conference venue. Checking “Use a second-tier MCLAG pair” at the conference venue requires evidence of its own mechanism: a lower tier MCLAG peer group connects with upper-tier switching through approved inter-switch arrangements; that is not the outcome measured by “Create a switch inter-switch link for FortiLink discovery”.
D:This check is suited to “Keep MCLAG peer hardware and software aligned” when trying to avoid unsupported mismatches in a redundant switch pair, not to verify “Use a second-tier MCLAG pair” at the conference venue. Checking “Use a second-tier MCLAG pair” at the conference venue requires evidence of its own mechanism: a lower tier MCLAG peer group connects with upper-tier switching through approved inter-switch arrangements; that is not the outcome measured by “Keep MCLAG peer hardware and software aligned”.
Question 102
A peer review of the campus asks how the design will aggregate redundant FortiGate-facing connectivity close to the security edge. Which FortiSwitch technique is the correct response?
- Use a first-tier MCLAG peer group
- Establish redundant interchassis links for MCLAG
- Use a FortiLink LAG with suitable member ports
- Design a three-tier FortiLink stack within supported topologies
Explanation
Correct Answer
A:The critical distinction is that the first pair presents a resilient attachment upstream while serving one or more downstream switches. The operator can test this claim by the specific check: verify both first-tier peers are represented and their shared trunk is synchronized.
Incorrect Answers
B:Compared with the requested “Use a first-tier MCLAG peer group” at the campus, this would avoid losing the peer relationship when one cross-connect fails instead: the interchassis link communicates peer state; at least two links are recommended for ICL resilience. At the campus, the operational proof would instead be to verify both first-tier peers are represented and their shared trunk is synchronized, whereas “Establish redundant interchassis links for MCLAG” is validated by a different test: check the ICL member status on both switches and verify a remaining path after a member fails.
C:Compared with the requested “Use a first-tier MCLAG peer group” at the campus, this would increase resiliency of the FortiGate-to-switch management and data connection instead: a logical aggregate can carry FortiLink when the topology and split-interface settings match its design. At the campus, the operational proof would instead be to verify both first-tier peers are represented and their shared trunk is synchronized, whereas “Use a FortiLink LAG with suitable member ports” is validated by a different test: confirm LACP/member state and whether the FortiLink aggregate remains available after one port fails.
D:For the campus, “Design a three-tier FortiLink stack within supported topologies” is a different type of control from “Use a first-tier MCLAG peer group”: multiple managed tiers require correctly placed ISLs and MCLAGs where redundancy is needed. Unlike the requested feature, that setting addresses the need to provide hierarchical aggregation, distribution and access while retaining centralized discovery, not the objective to aggregate redundant FortiGate-facing connectivity close to the security edge.
Question 103
On a FortiLink-managed access switch, “Use a first-tier MCLAG peer group” is configured for the remote depot. What effect should an administrator expect without assuming unrelated features are enabled?
- An ISL carries the FortiLink control reachability across the switch chain
- Fortinet recommends the same peer model and software version for a supported MCLAG design
- The first pair presents a resilient attachment upstream while serving one or more downstream switches
- Two peer FortiSwitch units present an aggregated logical attachment to dual-homed devices
Explanation
Correct Answer
C:That setting is appropriate here because the configured operation is meant to aggregate redundant FortiGate-facing connectivity close to the security edge. The most relevant validation is to verify both first-tier peers are represented and their shared trunk is synchronized for the equipment at the remote depot.
Incorrect Answers
A:That behavior applies when engineers “Create a switch inter-switch link for FortiLink discovery”; the different operation “Use a first-tier MCLAG peer group” is intended to aggregate redundant FortiGate-facing connectivity close to the security edge. That different feature is verified by examine ISL status and whether the expected descendant switch appears in discovery; for “Use a first-tier MCLAG peer group” on a FortiLink-managed access switch, the relevant evidence is to verify both first-tier peers are represented and their shared trunk is synchronized.
B:That behavior applies when engineers “Keep MCLAG peer hardware and software aligned”; the different operation “Use a first-tier MCLAG peer group” is intended to aggregate redundant FortiGate-facing connectivity close to the security edge. That different feature is verified by compare model IDs and installed firmware versions before enabling the peer group; for “Use a first-tier MCLAG peer group” on a FortiLink-managed access switch, the relevant evidence is to verify both first-tier peers are represented and their shared trunk is synchronized.
D:This outcome would be relevant to “Build a two-peer MCLAG core” at the remote depot, not the task “Use a first-tier MCLAG peer group”; the other task is to maintain data forwarding when one distribution switch stops responding. The action “Use a first-tier MCLAG peer group” targets a different result: the first pair presents a resilient attachment upstream while serving one or more downstream switches; the proposed alternative would instead be checked by verify both peer states and the dual-homed trunk membership in the MCLAG monitor.
Question 104
On a switch linked to a FortiGate running FortiOS 7.6 at the branch office, the team reports that it has configured “Use a first-tier MCLAG peer group.” Which verification provides the strongest direct evidence that the intended function is working?
- Inspect the access switch LACP partner identity and the MCLAG trunk operational state
- Verify both first-tier peers are represented and their shared trunk is synchronized
- Inspect the topology tree and confirm downstream serial numbers appear beneath the uplink switch
- Inspect peer split-brain state and configured priorities on each member
- Inspect both tier topologies and the cross-tier trunk state during peer-failure testing
Explanation
Correct Answer
B:This is the precise control because the first pair presents a resilient attachment upstream while serving one or more downstream switches. Directly measuring that result demonstrates whether the step to aggregate redundant FortiGate-facing connectivity close to the security edge succeeded on a switch linked to a FortiGate running FortiOS 7.6.
Incorrect Answers
A:This check is suited to “Dual-home an access switch with LACP to MCLAG peers” when trying to provide two physical upstream switches without creating separate spanning-tree forwarding paths, not to verify “Use a first-tier MCLAG peer group” at the branch office. Checking “Use a first-tier MCLAG peer group” at the branch office requires evidence of its own mechanism: the first pair presents a resilient attachment upstream while serving one or more downstream switches; that is not the outcome measured by “Dual-home an access switch with LACP to MCLAG peers”.
C:This check is suited to “Form a FortiLink-managed switch cascade” when trying to manage several downstream FortiSwitch units through one upstream connected device, not to verify “Use a first-tier MCLAG peer group” at the branch office. Checking “Use a first-tier MCLAG peer group” at the branch office requires evidence of its own mechanism: the first pair presents a resilient attachment upstream while serving one or more downstream switches; that is not the outcome measured by “Form a FortiLink-managed switch cascade”.
D:The proposed check concerns “Enable MCLAG split-brain detection on both peers” rather than “Use a first-tier MCLAG peer group”: split-brain safeguards determine which peer should enter a dormant state under a detected isolation event. For “Use a first-tier MCLAG peer group” on a switch linked to a FortiGate running FortiOS 7.6, a better test would be to verify both first-tier peers are represented and their shared trunk is synchronized, which targets aggregate redundant FortiGate-facing connectivity close to the security edge rather than the alternative diagnostic “Enable MCLAG split-brain detection on both peers”.
E:The proposed check concerns “Use a second-tier MCLAG pair” rather than “Use a first-tier MCLAG peer group”: a lower tier MCLAG peer group connects with upper-tier switching through approved inter-switch arrangements. For “Use a first-tier MCLAG peer group” on a switch linked to a FortiGate running FortiOS 7.6, a better test would be to verify both first-tier peers are represented and their shared trunk is synchronized, which targets aggregate redundant FortiGate-facing connectivity close to the security edge rather than the alternative diagnostic “Use a second-tier MCLAG pair”.
Question 105
A production incident in the factory reveals the need to allow managed descendants to be discovered beyond the directly connected switch. Which targeted FortiSwitch setting or method should the team use?
- Design a three-tier FortiLink stack within supported topologies
- Use a FortiLink LAG with suitable member ports
- Create a switch inter-switch link for FortiLink discovery
- Establish redundant interchassis links for MCLAG
Explanation
Correct Answer
C:The implementation works because an ISL carries the FortiLink control reachability across the switch chain. This distinction is material to the factory, where the stated goal is to allow managed descendants to be discovered beyond the directly connected switch.
Incorrect Answers
A:For the factory, “Design a three-tier FortiLink stack within supported topologies” is a different type of control from “Create a switch inter-switch link for FortiLink discovery”: multiple managed tiers require correctly placed ISLs and MCLAGs where redundancy is needed. Unlike the requested feature, that setting addresses the need to provide hierarchical aggregation, distribution and access while retaining centralized discovery, not the objective to allow managed descendants to be discovered beyond the directly connected switch.
B:Compared with the requested “Create a switch inter-switch link for FortiLink discovery” at the factory, this would increase resiliency of the FortiGate-to-switch management and data connection instead: a logical aggregate can carry FortiLink when the topology and split-interface settings match its design. At the factory, the operational proof would instead be to examine ISL status and whether the expected descendant switch appears in discovery, whereas “Use a FortiLink LAG with suitable member ports” is validated by a different test: confirm LACP/member state and whether the FortiLink aggregate remains available after one port fails.
D:Compared with the requested “Create a switch inter-switch link for FortiLink discovery” at the factory, this would avoid losing the peer relationship when one cross-connect fails instead: the interchassis link communicates peer state; at least two links are recommended for ICL resilience. At the factory, the operational proof would instead be to examine ISL status and whether the expected descendant switch appears in discovery, whereas “Establish redundant interchassis links for MCLAG” is validated by a different test: check the ICL member status on both switches and verify a remaining path after a member fails.
Question 106
For the distribution floor, an administrator applies the action “Create a switch inter-switch link for FortiLink discovery.” Which effect should appear when it operates as intended?
- An ISL carries the FortiLink control reachability across the switch chain
- Fortinet recommends the same peer model and software version for a supported MCLAG design
- Two peer FortiSwitch units present an aggregated logical attachment to dual-homed devices
- The first pair presents a resilient attachment upstream while serving one or more downstream switches
Explanation
Correct Answer
A:Given the described goal, the configured operation is meant to allow managed descendants to be discovered beyond the directly connected switch. The most relevant validation is to examine ISL status and whether the expected descendant switch appears in discovery for the equipment at the distribution floor.
Incorrect Answers
B:That behavior applies when engineers “Keep MCLAG peer hardware and software aligned”; the different operation “Create a switch inter-switch link for FortiLink discovery” is intended to allow managed descendants to be discovered beyond the directly connected switch. That different feature is verified by compare model IDs and installed firmware versions before enabling the peer group; for “Create a switch inter-switch link for FortiLink discovery” on a FortiSwitch connected to the security edge, the relevant evidence is to examine ISL status and whether the expected descendant switch appears in discovery.
C:This outcome would be relevant to “Build a two-peer MCLAG core” at the distribution floor, not the task “Create a switch inter-switch link for FortiLink discovery”; the other task is to maintain data forwarding when one distribution switch stops responding. The action “Create a switch inter-switch link for FortiLink discovery” targets a different result: an ISL carries the FortiLink control reachability across the switch chain; the proposed alternative would instead be checked by verify both peer states and the dual-homed trunk membership in the MCLAG monitor.
D:That behavior applies when engineers “Use a first-tier MCLAG peer group”; the different operation “Create a switch inter-switch link for FortiLink discovery” is intended to allow managed descendants to be discovered beyond the directly connected switch. That different feature is verified by verify both first-tier peers are represented and their shared trunk is synchronized; for “Create a switch inter-switch link for FortiLink discovery” on a FortiSwitch connected to the security edge, the relevant evidence is to examine ISL status and whether the expected descendant switch appears in discovery.
Question 107
A post-change review at the media studio must validate the implementation of “Create a switch inter-switch link for FortiLink discovery.” What should the reviewer inspect first?
- Inspect the topology tree and confirm downstream serial numbers appear beneath the uplink switch
- Examine ISL status and whether the expected descendant switch appears in discovery
- Inspect peer split-brain state and configured priorities on each member
- Inspect the access switch LACP partner identity and the MCLAG trunk operational state
Explanation
Correct Answer
B:The switch behavior that matters is: an ISL carries the FortiLink control reachability across the switch chain. Directly measuring that result demonstrates whether the step to allow managed descendants to be discovered beyond the directly connected switch succeeded on an access switch in routine maintenance.
Incorrect Answers
A:This check is suited to “Form a FortiLink-managed switch cascade” when trying to manage several downstream FortiSwitch units through one upstream connected device, not to verify “Create a switch inter-switch link for FortiLink discovery” at the media studio. Checking “Create a switch inter-switch link for FortiLink discovery” at the media studio requires evidence of its own mechanism: an ISL carries the FortiLink control reachability across the switch chain; that is not the outcome measured by “Form a FortiLink-managed switch cascade”.
C:The proposed check concerns “Enable MCLAG split-brain detection on both peers” rather than “Create a switch inter-switch link for FortiLink discovery”: split-brain safeguards determine which peer should enter a dormant state under a detected isolation event. For “Create a switch inter-switch link for FortiLink discovery” on an access switch in routine maintenance, a better test would be to examine ISL status and whether the expected descendant switch appears in discovery, which targets allow managed descendants to be discovered beyond the directly connected switch rather than the alternative diagnostic “Enable MCLAG split-brain detection on both peers”.
D:This check is suited to “Dual-home an access switch with LACP to MCLAG peers” when trying to provide two physical upstream switches without creating separate spanning-tree forwarding paths, not to verify “Create a switch inter-switch link for FortiLink discovery” at the media studio. Checking “Create a switch inter-switch link for FortiLink discovery” at the media studio requires evidence of its own mechanism: an ISL carries the FortiLink control reachability across the switch chain; that is not the outcome measured by “Dual-home an access switch with LACP to MCLAG peers”.
Question 108
A switch rollout in the data hall will be approved only if it can increase resiliency of the FortiGate-to-switch management and data connection. Which administrative action meets this acceptance criterion?
- Use a FortiLink LAG with suitable member ports
- Enable MCLAG split-brain detection on both peers
- Use an active LACP trunk for a dual-homed attachment
- Use a first-tier MCLAG peer group
- Dual-home an access switch with LACP to MCLAG peers
Explanation
Correct Answer
A:At this network boundary, a logical aggregate can carry FortiLink when the topology and split-interface settings match its design. The operator can test this claim by the specific check: confirm LACP/member state and whether the FortiLink aggregate remains available after one port fails.
Incorrect Answers
B:Compared with the requested “Use a FortiLink LAG with suitable member ports” at the data hall, 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 data hall, the operational proof would instead be to confirm LACP/member state and whether the FortiLink aggregate remains available after one port fails, 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 FortiLink LAG with suitable member ports” at the data hall, 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 data hall, the operational proof would instead be to confirm LACP/member state and whether the FortiLink aggregate remains available after one port fails, 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.
D:Compared with the requested “Use a FortiLink LAG with suitable member ports” at the data hall, this would aggregate redundant FortiGate-facing connectivity close to the security edge instead: the first pair presents a resilient attachment upstream while serving one or more downstream switches. At the data hall, the operational proof would instead be to confirm LACP/member state and whether the FortiLink aggregate remains available after one port fails, whereas “Use a first-tier MCLAG peer group” is validated by a different test: verify both first-tier peers are represented and their shared trunk is synchronized.
E:For the data hall, “Dual-home an access switch with LACP to MCLAG peers” is a different type of control from “Use a FortiLink LAG with suitable member ports”: 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 increase resiliency of the FortiGate-to-switch management and data connection.
Question 109
On a recently upgraded FortiSwitch, “Use a FortiLink LAG with suitable member ports” is configured for the development floor. What effect should an administrator expect without assuming unrelated features are enabled?
- A logical aggregate can carry FortiLink when the topology and split-interface settings match its design
- A lower tier MCLAG peer group connects with upper-tier switching through approved inter-switch arrangements
- An inter-switch link carries discovery and management traffic onward to additional managed switches
- 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 increase resiliency of the FortiGate-to-switch management and data connection. The most relevant validation is to confirm LACP/member state and whether the FortiLink aggregate remains available after one port fails for the equipment at the development floor.
Incorrect Answers
B:This outcome would be relevant to “Use a second-tier MCLAG pair” at the development floor, not the task “Use a FortiLink LAG with suitable member ports”; the other task is to preserve redundant distribution to switches deeper in a hierarchical access design. The action “Use a FortiLink LAG with suitable member ports” targets a different result: a logical aggregate can carry FortiLink when the topology and split-interface settings match its design; the proposed alternative would instead be checked by inspect both tier topologies and the cross-tier trunk state during peer-failure testing.
C:That behavior applies when engineers “Form a FortiLink-managed switch cascade”; the different operation “Use a FortiLink LAG with suitable member ports” is intended to increase resiliency of the FortiGate-to-switch management and data connection. That different feature is verified by inspect the topology tree and confirm downstream serial numbers appear beneath the uplink switch; for “Use a FortiLink LAG with suitable member ports” on a recently upgraded FortiSwitch, the relevant evidence is to confirm LACP/member state and whether the FortiLink aggregate remains available after one port fails.
D:That behavior applies when engineers “Enable STP-aware MCLAG behavior where required”; the different operation “Use a FortiLink LAG with suitable member ports” is intended to increase resiliency of the FortiGate-to-switch management and data connection. That different feature is verified by inspect MCLAG-STP settings and bridge information on both peers; for “Use a FortiLink LAG with suitable member ports” on a recently upgraded FortiSwitch, the relevant evidence is to confirm LACP/member state and whether the FortiLink aggregate remains available after one port fails.
Question 110
The work order to increase resiliency of the FortiGate-to-switch management and data connection is marked complete on a FortiLink-managed access switch. Which observation most directly tests the completed configuration?
- Examine ISL status and whether the expected descendant switch appears in discovery
- Confirm LACP/member state and whether the FortiLink aggregate remains available after one port fails
- Test an HA failover and monitor FortiSwitch authorization and control-plane reachability
- Inspect the complete three-tier FortiSwitch topology and unauthorized downstream devices
Explanation
Correct Answer
B:For the stated requirement, a logical aggregate can carry FortiLink when the topology and split-interface settings match its design. Directly measuring that result demonstrates whether the step to increase resiliency of the FortiGate-to-switch management and data connection succeeded on a FortiLink-managed access switch.
Incorrect Answers
A:This check is suited to “Create a switch inter-switch link for FortiLink discovery” when trying to allow managed descendants to be discovered beyond the directly connected switch, not to verify “Use a FortiLink LAG with suitable member ports” at the conference venue. Checking “Use a FortiLink LAG with suitable member ports” at the conference venue requires evidence of its own mechanism: a logical aggregate can carry FortiLink when the topology and split-interface settings match its design; that is not the outcome measured by “Create a switch inter-switch link for FortiLink discovery”.
C:This check is suited to “Connect FortiGate HA to a FortiLink stack” when trying to keep switch management connected when the active FortiGate changes, not to verify “Use a FortiLink LAG with suitable member ports” at the conference venue. Checking “Use a FortiLink LAG with suitable member ports” at the conference venue requires evidence of its own mechanism: a logical aggregate can carry FortiLink when the topology and split-interface settings match its design; that is not the outcome measured by “Connect FortiGate HA to a FortiLink stack”.
D:The proposed check concerns “Design a three-tier FortiLink stack within supported topologies” rather than “Use a FortiLink LAG with suitable member ports”: multiple managed tiers require correctly placed ISLs and MCLAGs where redundancy is needed. For “Use a FortiLink LAG with suitable member ports” on a FortiLink-managed access switch, a better test would be to confirm LACP/member state and whether the FortiLink aggregate remains available after one port fails, which targets increase resiliency of the FortiGate-to-switch management and data connection rather than the alternative diagnostic “Design a three-tier FortiLink stack within supported topologies”.