Question 400
The operational requirement for a FortiSwitch connected to the security edge at the campus is to provide an appropriate redundant path in a ring-like MCLAG topology. Which FortiSwitch choice directly targets it?
- Use FortiLink over a point-to-point Layer 2 transit
- Deploy a two-tier FortiSwitch hierarchy
- Design a three-tier MCLAG hierarchy
- Use an MCLAG+ ring only where supported
Explanation
Correct Answer
D:The relevant mechanism is: the ring variant requires supported peer and inter-switch arrangements rather than uncontrolled Ethernet loops. The operator can test this claim by the specific check: verify documented peer links and spanning-tree/MCLAG status for the complete ring.
Incorrect Answers
A:For the campus, “Use FortiLink over a point-to-point Layer 2 transit” is a different type of control from “Use an MCLAG+ ring only where supported”: point-to-point L2 transit preserves required FortiLink discovery and management frames across the middle network. Unlike the requested feature, that setting addresses the need to reach a remote switch through a transparent dedicated bridging path, not the objective to provide an appropriate redundant path in a ring-like MCLAG topology.
B:Compared with the requested “Use an MCLAG+ ring only where supported” at the campus, this would separate distribution and access functions while keeping central FortiLink management instead: one switch tier aggregates downstream access units via ISLs or supported trunks. At the campus, the operational proof would instead be to verify documented peer links and spanning-tree/MCLAG status for the complete ring, whereas “Deploy a two-tier FortiSwitch hierarchy” is validated by a different test: verify which tier holds the FortiGate uplink and which links serve access switches.
C:Compared with the requested “Use an MCLAG+ ring only where supported” at the campus, this would extend resilient aggregation through core, distribution and access levels instead: supported tiered MCLAG topologies permit multi-layer redundancy with active member links. At the campus, the operational proof would instead be to verify documented peer links and spanning-tree/MCLAG status for the complete ring, whereas “Design a three-tier MCLAG hierarchy” is validated by a different test: audit per-tier peer groups and the full three-layer physical uplink map.
Question 401
When engineers use an MCLAG+ ring only where supported at the remote depot, which forwarding, security, management or diagnostic outcome follows from that action?
- A lower peer group supplies redundant endpoints for access switches deeper in the design
- In-band L3 management uses the FortiSwitch internal management interface for the controller path
- The ring variant requires supported peer and inter-switch arrangements rather than uncontrolled Ethernet loops
- A static ISL defines the inter-switch path and can carry manually controlled VLAN settings
- Supported fully meshed wiring attaches the FortiGate cluster redundantly to the appropriate switch layer
Explanation
Correct Answer
C:This approach fits because the configured operation is meant to provide an appropriate redundant path in a ring-like MCLAG topology. The most relevant validation is to verify documented peer links and spanning-tree/MCLAG status for the complete ring for the equipment at the remote depot.
Incorrect Answers
A:That behavior applies when engineers “Provide second-tier MCLAG for resilient access aggregation”; the different operation “Use an MCLAG+ ring only where supported” is intended to provide an appropriate redundant path in a ring-like MCLAG topology. That different feature is verified by check second-tier ICL and access trunks rather than only first-tier connectivity; for “Use an MCLAG+ ring only where supported” on an access switch in routine maintenance, the relevant evidence is to verify documented peer links and spanning-tree/MCLAG status for the complete ring.
B:This outcome would be relevant to “Select in-band management for a routed FortiSwitch island” at the remote depot, not the task “Use an MCLAG+ ring only where supported”; the other task is to use a switch's internal interface to carry routed FortiLink control traffic. The action “Use an MCLAG+ ring only where supported” targets a different result: the ring variant requires supported peer and inter-switch arrangements rather than uncontrolled Ethernet loops; the proposed alternative would instead be checked by verify the internal interface IP and routed connectivity to the controller.
D:That behavior applies when engineers “Use a supported static ISL for a specialized topology”; the different operation “Use an MCLAG+ ring only where supported” is intended to provide an appropriate redundant path in a ring-like MCLAG topology. That different feature is verified by inspect static-ISL status and the intended allowed VLAN configuration; for “Use an MCLAG+ ring only where supported” on an access switch in routine maintenance, the relevant evidence is to verify documented peer links and spanning-tree/MCLAG status for the complete ring.
E:That behavior applies when engineers “Deploy a full-mesh HA FortiLink architecture”; the different operation “Use an MCLAG+ ring only where supported” is intended to provide an appropriate redundant path in a ring-like MCLAG topology. That different feature is verified by follow physical uplink inventory and test each HA member's controller reachability; for “Use an MCLAG+ ring only where supported” on an access switch in routine maintenance, the relevant evidence is to verify documented peer links and spanning-tree/MCLAG status for the complete ring.
Question 402
An auditor wants operational evidence for the switch action “Use an MCLAG+ ring only where supported” at the lab. Which check is relevant?
- Inspect FortiLink status and the one-switch topology after startup
- Verify documented peer links and spanning-tree/MCLAG status for the complete ring
- Compare the effective ISL VLAN list with the downstream topology requirements
- Compare end-to-end source and destination addressing and remove an intervening NAT rule
Explanation
Correct Answer
B:The critical distinction is that the ring variant requires supported peer and inter-switch arrangements rather than uncontrolled Ethernet loops. Directly measuring that result demonstrates whether the step to provide an appropriate redundant path in a ring-like MCLAG topology succeeded on a managed campus switch.
Incorrect Answers
A:This check is suited to “Use direct one-to-one FortiGate-to-FortiSwitch wiring” when trying to deploy a small branch with one managed switch and minimal switching complexity, not to verify “Use an MCLAG+ ring only where supported” at the lab. Checking “Use an MCLAG+ ring only where supported” at the lab requires evidence of its own mechanism: the ring variant requires supported peer and inter-switch arrangements rather than uncontrolled Ethernet loops; that is not the outcome measured by “Use direct one-to-one FortiGate-to-FortiSwitch wiring”.
C:The proposed check concerns “Use FortiLink VLAN optimization where appropriate” rather than “Use an MCLAG+ ring only where supported”: optimization restricts or adjusts VLAN distribution to reduce superfluous trunk state. For “Use an MCLAG+ ring only where supported” on a managed campus switch, a better test would be to verify documented peer links and spanning-tree/MCLAG status for the complete ring, which targets provide an appropriate redundant path in a ring-like MCLAG topology rather than the alternative diagnostic “Use FortiLink VLAN optimization where appropriate”.
D:This check is suited to “Avoid NAT between routed FortiLink island and FortiGate” when trying to preserve a supported L3 FortiLink controller communication path, not to verify “Use an MCLAG+ ring only where supported” at the lab. Checking “Use an MCLAG+ ring only where supported” at the lab requires evidence of its own mechanism: the ring variant requires supported peer and inter-switch arrangements rather than uncontrolled Ethernet loops; that is not the outcome measured by “Avoid NAT between routed FortiLink island and FortiGate”.
Question 403
During a change window in the staging rack, engineers are asked to protect the switch pair closest to the FortiGate from a single chassis outage. What should they configure rather than using a feature for an adjacent purpose?
- Cascade access switches through an upstream managed switch
- Provide first-tier MCLAG before downstream redundancy
- Avoid stretching production VLANs across Layer 3 FortiLink
- Prefer a dual-homed server MCLAG attachment
Explanation
Correct Answer
B:That setting is appropriate here because first-tier peers act as a redundant upstream anchor for downstream distribution or access switches. This distinction is material to the staging rack, where the stated goal is to protect the switch pair closest to the FortiGate from a single chassis outage.
Incorrect Answers
A:For the staging rack, “Cascade access switches through an upstream managed switch” is a different type of control from “Provide first-tier MCLAG before downstream redundancy”: downstream FortiSwitch units join through supported inter-switch links to the first unit. Unlike the requested feature, that setting addresses the need to extend a FortiLink-managed network beyond the number of direct controller ports, not the objective to protect the switch pair closest to the FortiGate from a single chassis outage.
C:Compared with the requested “Provide first-tier MCLAG before downstream redundancy” at the staging rack, this would keep remote switch islands from assuming a shared Layer 2 segment across an IP network instead: FortiLink-over-L3 provides a management path, not a continuous VLAN data-plane extension. At the staging rack, the operational proof would instead be to monitor first-tier peer synchronization and FortiLink reachability after failover, whereas “Avoid stretching production VLANs across Layer 3 FortiLink” is validated by a different test: trace the VLAN boundary and verify routing rather than a nonexistent L2 stretch.
D:Compared with the requested “Provide first-tier MCLAG before downstream redundancy” at the staging rack, this would maintain server connectivity when one FortiSwitch peer fails instead: a server LACP trunk can span the two MCLAG peers while presenting one logical aggregate. At the staging rack, the operational proof would instead be to monitor first-tier peer synchronization and FortiLink reachability after failover, whereas “Prefer a dual-homed server MCLAG attachment” is validated by a different test: inspect server bond partner details and both peer switch trunk memberships.
Question 404
A colleague asks about the effect of “Provide first-tier MCLAG before downstream redundancy” on a staging FortiSwitch. Which behavior best characterizes that feature?
- A lower peer group supplies redundant endpoints for access switches deeper in the design
- First-tier peers act as a redundant upstream anchor for downstream distribution or access switches
- Supported tiered MCLAG topologies permit multi-layer redundancy with active member links
- One switch tier aggregates downstream access units via ISLs or supported trunks
Explanation
Correct Answer
B:This is the precise control because the configured operation is meant to protect the switch pair closest to the FortiGate from a single chassis outage. The most relevant validation is to monitor first-tier peer synchronization and FortiLink reachability after failover for the equipment at the research building.
Incorrect Answers
A:That behavior applies when engineers “Provide second-tier MCLAG for resilient access aggregation”; the different operation “Provide first-tier MCLAG before downstream redundancy” is intended to protect the switch pair closest to the FortiGate from a single chassis outage. That different feature is verified by check second-tier ICL and access trunks rather than only first-tier connectivity; for “Provide first-tier MCLAG before downstream redundancy” on a staging FortiSwitch, the relevant evidence is to monitor first-tier peer synchronization and FortiLink reachability after failover.
C:That behavior applies when engineers “Design a three-tier MCLAG hierarchy”; the different operation “Provide first-tier MCLAG before downstream redundancy” is intended to protect the switch pair closest to the FortiGate from a single chassis outage. That different feature is verified by audit per-tier peer groups and the full three-layer physical uplink map; for “Provide first-tier MCLAG before downstream redundancy” on a staging FortiSwitch, the relevant evidence is to monitor first-tier peer synchronization and FortiLink reachability after failover.
D:This outcome would be relevant to “Deploy a two-tier FortiSwitch hierarchy” at the research building, not the task “Provide first-tier MCLAG before downstream redundancy”; the other task is to separate distribution and access functions while keeping central FortiLink management. The action “Provide first-tier MCLAG before downstream redundancy” targets a different result: first-tier peers act as a redundant upstream anchor for downstream distribution or access switches; the proposed alternative would instead be checked by verify which tier holds the FortiGate uplink and which links serve access switches.
Question 405
A technician says “Provide first-tier MCLAG before downstream redundancy” has solved the issue at the clinic. Which diagnostic step would substantiate that claim?
- Follow physical uplink inventory and test each HA member's controller reachability
- Inspect static-ISL status and the intended allowed VLAN configuration
- Inspect both active LACP members and observe service through a peer maintenance window
- Verify the internal interface IP and routed connectivity to the controller
- Monitor first-tier peer synchronization and FortiLink reachability after failover
Explanation
Correct Answer
E:The implementation works because first-tier peers act as a redundant upstream anchor for downstream distribution or access switches. Directly measuring that result demonstrates whether the step to protect the switch pair closest to the FortiGate from a single chassis outage succeeded on a carefully segmented Layer 2 network.
Incorrect Answers
A:The proposed check concerns “Deploy a full-mesh HA FortiLink architecture” rather than “Provide first-tier MCLAG before downstream redundancy”: supported fully meshed wiring attaches the FortiGate cluster redundantly to the appropriate switch layer. For “Provide first-tier MCLAG before downstream redundancy” on a carefully segmented Layer 2 network, a better test would be to monitor first-tier peer synchronization and FortiLink reachability after failover, which targets protect the switch pair closest to the FortiGate from a single chassis outage rather than the alternative diagnostic “Deploy a full-mesh HA FortiLink architecture”.
B:The proposed check concerns “Use a supported static ISL for a specialized topology” rather than “Provide first-tier MCLAG before downstream redundancy”: a static ISL defines the inter-switch path and can carry manually controlled VLAN settings. For “Provide first-tier MCLAG before downstream redundancy” on a carefully segmented Layer 2 network, a better test would be to monitor first-tier peer synchronization and FortiLink reachability after failover, which targets protect the switch pair closest to the FortiGate from a single chassis outage rather than the alternative diagnostic “Use a supported static ISL for a specialized topology”.
C:This check is suited to “Attach an access switch to both MCLAG peers” when trying to give the access layer two independent upstream hardware paths, not to verify “Provide first-tier MCLAG before downstream redundancy” at the clinic. Checking “Provide first-tier MCLAG before downstream redundancy” at the clinic requires evidence of its own mechanism: first-tier peers act as a redundant upstream anchor for downstream distribution or access switches; that is not the outcome measured by “Attach an access switch to both MCLAG peers”.
D:This check is suited to “Select in-band management for a routed FortiSwitch island” when trying to use a switch's internal interface to carry routed FortiLink control traffic, not to verify “Provide first-tier MCLAG before downstream redundancy” at the clinic. Checking “Provide first-tier MCLAG before downstream redundancy” at the clinic requires evidence of its own mechanism: first-tier peers act as a redundant upstream anchor for downstream distribution or access switches; that is not the outcome measured by “Select in-band management for a routed FortiSwitch island”.
Question 406
For the data hall, the network team needs to protect the next aggregation layer beneath an already redundant core. Which change is the most direct way to implement that requirement on a central switching stack?
- Use an MCLAG+ ring only where supported
- Use an HA FortiGate pair to manage an access switch
- Provide second-tier MCLAG for resilient access aggregation
- Use a fully meshed connection between adjacent MCLAG tiers
Explanation
Correct Answer
C:Given the described goal, a lower peer group supplies redundant endpoints for access switches deeper in the design. The operator can test this claim by the specific check: check second-tier ICL and access trunks rather than only first-tier connectivity.
Incorrect Answers
A:Compared with the requested “Provide second-tier MCLAG for resilient access aggregation” at the data hall, this would provide an appropriate redundant path in a ring-like MCLAG topology instead: the ring variant requires supported peer and inter-switch arrangements rather than uncontrolled Ethernet loops. At the data hall, the operational proof would instead be to check second-tier ICL and access trunks rather than only first-tier connectivity, whereas “Use an MCLAG+ ring only where supported” is validated by a different test: verify documented peer links and spanning-tree/MCLAG status for the complete ring.
B:Compared with the requested “Provide second-tier MCLAG for resilient access aggregation” at the data hall, this would retain controller availability across a firewall failover instead: the FortiGate HA cluster presents the management service while the switch wiring follows a supported HA topology. At the data hall, the operational proof would instead be to check second-tier ICL and access trunks rather than only first-tier connectivity, whereas “Use an HA FortiGate pair to manage an access switch” is validated by a different test: perform a controlled HA role change and verify the switch remains centrally managed.
D:For the data hall, “Use a fully meshed connection between adjacent MCLAG tiers” is a different type of control from “Provide second-tier MCLAG for resilient access aggregation”: cross-tier links reach both peers in the upper tier rather than funneling all traffic through one unit. Unlike the requested feature, that setting addresses the need to maintain upstream connectivity when one higher-tier switch or link fails, not the objective to protect the next aggregation layer beneath an already redundant core.
Question 407
When engineers provide second-tier MCLAG for resilient access aggregation at the development floor, which forwarding, security, management or diagnostic outcome follows from that action?
- L3 FortiLink requires reachable management addressing instead of a continuous Layer 2 switch-controller path
- A lower peer group supplies redundant endpoints for access switches deeper in the design
- Separate FortiLink interfaces manage separate VLAN and switch groups for LAN and WAN roles
- Peer switches cooperate as one logical aggregation endpoint for dual-homed downstream trunks
Explanation
Correct Answer
B:The switch behavior that matters is: the configured operation is meant to protect the next aggregation layer beneath an already redundant core. The most relevant validation is to check second-tier ICL and access trunks rather than only first-tier connectivity for the equipment at the development floor.
Incorrect Answers
A:That behavior applies when engineers “Use routed Layer 3 FortiLink for a remote island”; the different operation “Provide second-tier MCLAG for resilient access aggregation” is intended to protect the next aggregation layer beneath an already redundant core. That different feature is verified by test IP routing and controller communication between the remote switch and FortiGate; for “Provide second-tier MCLAG for resilient access aggregation” on a FortiSwitch connected to the security edge, the relevant evidence is to check second-tier ICL and access trunks rather than only first-tier connectivity.
C:This outcome would be relevant to “Keep independent LAN and WAN FortiLink stacks” at the development floor, not the task “Provide second-tier MCLAG for resilient access aggregation”; the other task is to use separate switching infrastructure for different security-edge functions. The action “Provide second-tier MCLAG for resilient access aggregation” targets a different result: a lower peer group supplies redundant endpoints for access switches deeper in the design; the proposed alternative would instead be checked by confirm each stack's FortiLink interface and that units do not cross the wrong stack.
D:That behavior applies when engineers “Deploy an MCLAG distribution peer pair”; the different operation “Provide second-tier MCLAG for resilient access aggregation” is intended to protect the next aggregation layer beneath an already redundant core. That different feature is verified by check peer and ICL health and validate data forwarding when one peer is isolated; for “Provide second-tier MCLAG for resilient access aggregation” on a FortiSwitch connected to the security edge, the relevant evidence is to check second-tier ICL and access trunks rather than only first-tier connectivity.
Question 408
At the conference venue, a dashboard shows ordinary link-up state, but the team also needs proof for “Provide second-tier MCLAG for resilient access aggregation.” Which targeted check should be used?
- Verify split-interface state against which FortiSwitch devices each member connects to
- Check second-tier ICL and access trunks rather than only first-tier connectivity
- Test management-port IP connectivity and confirm the correct FortiLink source path
- Perform a parent-switch outage test and observe remaining access-layer connectivity
- Inspect which VLAN IDs remain active on each intermediate ISL trunk
Explanation
Correct Answer
B:At this network boundary, a lower peer group supplies redundant endpoints for access switches deeper in the design. Directly measuring that result demonstrates whether the step to protect the next aggregation layer beneath an already redundant core succeeded on an access switch in routine maintenance.
Incorrect Answers
A:This check is suited to “Configure a FortiLink split interface where the topology requires it” when trying to handle alternate FortiLink connectivity without incorrectly combining members into one LACP bundle, not to verify “Provide second-tier MCLAG for resilient access aggregation” at the conference venue. Checking “Provide second-tier MCLAG for resilient access aggregation” at the conference venue requires evidence of its own mechanism: a lower peer group supplies redundant endpoints for access switches deeper in the design; that is not the outcome measured by “Configure a FortiLink split interface where the topology requires it”.
C:The proposed check concerns “Select out-of-band management for a routed island” rather than “Provide second-tier MCLAG for resilient access aggregation”: out-of-band L3 FortiLink uses a dedicated management interface rather than the ordinary data plane. For “Provide second-tier MCLAG for resilient access aggregation” on an access switch in routine maintenance, a better test would be to check second-tier ICL and access trunks rather than only first-tier connectivity, which targets protect the next aggregation layer beneath an already redundant core rather than the alternative diagnostic “Select out-of-band management for a routed island”.
D:The proposed check concerns “Use redundant uplinks rather than a single-chain design for critical endpoints” rather than “Provide second-tier MCLAG for resilient access aggregation”: redundant topology design removes a single parent chassis from the data-plane dependency chain. For “Provide second-tier MCLAG for resilient access aggregation” on an access switch in routine maintenance, a better test would be to check second-tier ICL and access trunks rather than only first-tier connectivity, which targets protect the next aggregation layer beneath an already redundant core rather than the alternative diagnostic “Use redundant uplinks rather than a single-chain design for critical endpoints”.
E:This check is suited to “Use VLAN pruning on ISL trunks” when trying to avoid transporting VLAN traffic across parts of the stack with no members, not to verify “Provide second-tier MCLAG for resilient access aggregation” at the conference venue. Checking “Provide second-tier MCLAG for resilient access aggregation” at the conference venue requires evidence of its own mechanism: a lower peer group supplies redundant endpoints for access switches deeper in the design; that is not the outcome measured by “Use VLAN pruning on ISL trunks”.
Question 409
On a managed campus switch in the hospital wing, the next task is to prevent an upstream switch failure disconnecting every switch below it. What is the appropriate configuration decision?
- Cascade access switches through an upstream managed switch
- Avoid stretching production VLANs across Layer 3 FortiLink
- Use redundant uplinks rather than a single-chain design for critical endpoints
- Prefer a dual-homed server MCLAG attachment
Explanation
Correct Answer
C:In this deployment, redundant topology design removes a single parent chassis from the data-plane dependency chain. This distinction is material to the hospital wing, where the stated goal is to prevent an upstream switch failure disconnecting every switch below it.
Incorrect Answers
A:For the hospital wing, “Cascade access switches through an upstream managed switch” is a different type of control from “Use redundant uplinks rather than a single-chain design for critical endpoints”: downstream FortiSwitch units join through supported inter-switch links to the first unit. Unlike the requested feature, that setting addresses the need to extend a FortiLink-managed network beyond the number of direct controller ports, not the objective to prevent an upstream switch failure disconnecting every switch below it.
B:Compared with the requested “Use redundant uplinks rather than a single-chain design for critical endpoints” at the hospital wing, this would keep remote switch islands from assuming a shared Layer 2 segment across an IP network instead: FortiLink-over-L3 provides a management path, not a continuous VLAN data-plane extension. At the hospital wing, the operational proof would instead be to perform a parent-switch outage test and observe remaining access-layer connectivity, whereas “Avoid stretching production VLANs across Layer 3 FortiLink” is validated by a different test: trace the VLAN boundary and verify routing rather than a nonexistent L2 stretch.
D:Compared with the requested “Use redundant uplinks rather than a single-chain design for critical endpoints” at the hospital wing, this would maintain server connectivity when one FortiSwitch peer fails instead: a server LACP trunk can span the two MCLAG peers while presenting one logical aggregate. At the hospital wing, the operational proof would instead be to perform a parent-switch outage test and observe remaining access-layer connectivity, whereas “Prefer a dual-homed server MCLAG attachment” is validated by a different test: inspect server bond partner details and both peer switch trunk memberships.
Question 410
Before applying the planned operation “Use redundant uplinks rather than a single-chain design for critical endpoints” at the training center, the administrator must predict its impact. Which prediction is sound?
- One switch tier aggregates downstream access units via ISLs or supported trunks
- First-tier peers act as a redundant upstream anchor for downstream distribution or access switches
- Redundant topology design removes a single parent chassis from the data-plane dependency chain
- Supported tiered MCLAG topologies permit multi-layer redundancy with active member links
Explanation
Correct Answer
C:For the stated requirement, the configured operation is meant to prevent an upstream switch failure disconnecting every switch below it. The most relevant validation is to perform a parent-switch outage test and observe remaining access-layer connectivity for the equipment at the training center.
Incorrect Answers
A:This outcome would be relevant to “Deploy a two-tier FortiSwitch hierarchy” at the training center, not the task “Use redundant uplinks rather than a single-chain design for critical endpoints”; the other task is to separate distribution and access functions while keeping central FortiLink management. The action “Use redundant uplinks rather than a single-chain design for critical endpoints” targets a different result: redundant topology design removes a single parent chassis from the data-plane dependency chain; the proposed alternative would instead be checked by verify which tier holds the FortiGate uplink and which links serve access switches.
B:That behavior applies when engineers “Provide first-tier MCLAG before downstream redundancy”; the different operation “Use redundant uplinks rather than a single-chain design for critical endpoints” is intended to prevent an upstream switch failure disconnecting every switch below it. That different feature is verified by monitor first-tier peer synchronization and FortiLink reachability after failover; for “Use redundant uplinks rather than a single-chain design for critical endpoints” on a recently upgraded FortiSwitch, the relevant evidence is to perform a parent-switch outage test and observe remaining access-layer connectivity.
D:That behavior applies when engineers “Design a three-tier MCLAG hierarchy”; the different operation “Use redundant uplinks rather than a single-chain design for critical endpoints” is intended to prevent an upstream switch failure disconnecting every switch below it. That different feature is verified by audit per-tier peer groups and the full three-layer physical uplink map; for “Use redundant uplinks rather than a single-chain design for critical endpoints” on a recently upgraded FortiSwitch, the relevant evidence is to perform a parent-switch outage test and observe remaining access-layer connectivity.