Question 390
A FortiSwitch engineer in the conference venue is documenting successful operation of “Use a supported static ISL for a specialized topology.” Which measurement or inspection confirms it?
- Verify the internal interface IP and routed connectivity to the controller
- Inspect static-ISL status and the intended allowed VLAN configuration
- Inspect both active LACP members and observe service through a peer maintenance window
- Follow physical uplink inventory and test each HA member's controller reachability
- Inspect FortiLink status and the one-switch topology after startup
Explanation
Correct Answer
B:The critical distinction is that a static ISL defines the inter-switch path and can carry manually controlled VLAN settings. Directly measuring that result demonstrates whether the step to control uplink behavior where automatic ISL discovery is not the intended configuration succeeded on a staging FortiSwitch.
Incorrect Answers
A:The proposed check concerns “Select in-band management for a routed FortiSwitch island” rather than “Use a supported static ISL for a specialized topology”: in-band L3 management uses the FortiSwitch internal management interface for the controller path. For “Use a supported static ISL for a specialized topology” on a staging FortiSwitch, a better test would be to inspect static-ISL status and the intended allowed VLAN configuration, which targets control uplink behavior where automatic ISL discovery is not the intended configuration rather than the alternative diagnostic “Select in-band management for a routed FortiSwitch island”.
C:The proposed check concerns “Attach an access switch to both MCLAG peers” rather than “Use a supported static ISL for a specialized topology”: dual-homed LACP membership uses links toward each peer instead of relying on one parent chassis. For “Use a supported static ISL for a specialized topology” on a staging FortiSwitch, a better test would be to inspect static-ISL status and the intended allowed VLAN configuration, which targets control uplink behavior where automatic ISL discovery is not the intended configuration rather than the alternative diagnostic “Attach an access switch to both MCLAG peers”.
D:This check is suited to “Deploy a full-mesh HA FortiLink architecture” when trying to avoid loss of one FortiGate connection causing loss of switch access, not to verify “Use a supported static ISL for a specialized topology” at the conference venue. Checking “Use a supported static ISL for a specialized topology” at the conference venue requires evidence of its own mechanism: a static ISL defines the inter-switch path and can carry manually controlled VLAN settings; that is not the outcome measured by “Deploy a full-mesh HA FortiLink architecture”.
E: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 a supported static ISL for a specialized topology” at the conference venue. Checking “Use a supported static ISL for a specialized topology” at the conference venue requires evidence of its own mechanism: a static ISL defines the inter-switch path and can carry manually controlled VLAN settings; that is not the outcome measured by “Use direct one-to-one FortiGate-to-FortiSwitch wiring”.
Question 391
An administrator responsible for a newly commissioned floor switch in the campus must avoid transporting VLAN traffic across parts of the stack with no members. Which configuration best matches that precise goal?
- Cascade access switches through an upstream managed switch
- Use VLAN pruning on ISL trunks
- Avoid stretching production VLANs across Layer 3 FortiLink
- Use an MCLAG+ ring only where supported
Explanation
Correct Answer
B:That setting is appropriate here because VLAN pruning limits inter-switch VLAN carriage to those actually required along each path. This distinction is material to the campus, where the stated goal is to avoid transporting VLAN traffic across parts of the stack with no members.
Incorrect Answers
A:For the campus, “Cascade access switches through an upstream managed switch” is a different type of control from “Use VLAN pruning on ISL trunks”: 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 avoid transporting VLAN traffic across parts of the stack with no members.
C:Compared with the requested “Use VLAN pruning on ISL trunks” at the campus, 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 campus, the operational proof would instead be to inspect which VLAN IDs remain active on each intermediate ISL trunk, 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 VLAN pruning on ISL trunks” at the campus, 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 campus, the operational proof would instead be to inspect which VLAN IDs remain active on each intermediate ISL trunk, 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.
Question 392
A colleague asks about the effect of “Use VLAN pruning on ISL trunks” on a local switch administering branch clients. Which behavior best characterizes that feature?
- One switch tier aggregates downstream access units via ISLs or supported trunks
- VLAN pruning limits inter-switch VLAN carriage to those actually required along each path
- Supported tiered MCLAG topologies permit multi-layer redundancy with active member links
- A lower peer group supplies redundant endpoints for access switches deeper in the design
Explanation
Correct Answer
B:This is the precise control because the configured operation is meant to avoid transporting VLAN traffic across parts of the stack with no members. The most relevant validation is to inspect which VLAN IDs remain active on each intermediate ISL trunk for the equipment at the remote depot.
Incorrect Answers
A:This outcome would be relevant to “Deploy a two-tier FortiSwitch hierarchy” at the remote depot, not the task “Use VLAN pruning on ISL trunks”; the other task is to separate distribution and access functions while keeping central FortiLink management. The action “Use VLAN pruning on ISL trunks” targets a different result: VLAN pruning limits inter-switch VLAN carriage to those actually required along each path; the proposed alternative would instead be checked by verify which tier holds the FortiGate uplink and which links serve access switches.
C:That behavior applies when engineers “Design a three-tier MCLAG hierarchy”; the different operation “Use VLAN pruning on ISL trunks” is intended to avoid transporting VLAN traffic across parts of the stack with no members. That different feature is verified by audit per-tier peer groups and the full three-layer physical uplink map; for “Use VLAN pruning on ISL trunks” on a local switch administering branch clients, the relevant evidence is to inspect which VLAN IDs remain active on each intermediate ISL trunk.
D:That behavior applies when engineers “Provide second-tier MCLAG for resilient access aggregation”; the different operation “Use VLAN pruning on ISL trunks” is intended to avoid transporting VLAN traffic across parts of the stack with no members. That different feature is verified by check second-tier ICL and access trunks rather than only first-tier connectivity; for “Use VLAN pruning on ISL trunks” on a local switch administering branch clients, the relevant evidence is to inspect which VLAN IDs remain active on each intermediate ISL trunk.
Question 393
A feature acceptance test on a switch used by multiple office teams concerns “Use VLAN pruning on ISL trunks.” What should be checked to establish its expected operation?
- Inspect both active LACP members and observe service through a peer maintenance window
- Verify the internal interface IP and routed connectivity to the controller
- Inspect which VLAN IDs remain active on each intermediate ISL trunk
- Follow physical uplink inventory and test each HA member's controller reachability
Explanation
Correct Answer
C:The implementation works because VLAN pruning limits inter-switch VLAN carriage to those actually required along each path. Directly measuring that result demonstrates whether the step to avoid transporting VLAN traffic across parts of the stack with no members succeeded on a switch used by multiple office teams.
Incorrect Answers
A: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 “Use VLAN pruning on ISL trunks” at the branch office. Checking “Use VLAN pruning on ISL trunks” at the branch office requires evidence of its own mechanism: VLAN pruning limits inter-switch VLAN carriage to those actually required along each path; that is not the outcome measured by “Attach an access switch to both MCLAG peers”.
B: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 “Use VLAN pruning on ISL trunks” at the branch office. Checking “Use VLAN pruning on ISL trunks” at the branch office requires evidence of its own mechanism: VLAN pruning limits inter-switch VLAN carriage to those actually required along each path; that is not the outcome measured by “Select in-band management for a routed FortiSwitch island”.
D:The proposed check concerns “Deploy a full-mesh HA FortiLink architecture” rather than “Use VLAN pruning on ISL trunks”: supported fully meshed wiring attaches the FortiGate cluster redundantly to the appropriate switch layer. For “Use VLAN pruning on ISL trunks” on a switch used by multiple office teams, a better test would be to inspect which VLAN IDs remain active on each intermediate ISL trunk, which targets avoid transporting VLAN traffic across parts of the stack with no members rather than the alternative diagnostic “Deploy a full-mesh HA FortiLink architecture”.
Question 394
A peer review of the factory asks how the design will reduce unnecessary VLAN configuration work on managed inter-switch connections. Which FortiSwitch technique is the correct response?
- Configure a FortiLink split interface where the topology requires it
- Use redundant uplinks rather than a single-chain design for critical endpoints
- Use VLAN pruning on ISL trunks
- Select out-of-band management for a routed island
- Use FortiLink VLAN optimization where appropriate
Explanation
Correct Answer
E:Given the described goal, optimization restricts or adjusts VLAN distribution to reduce superfluous trunk state. The operator can test this claim by the specific check: compare the effective ISL VLAN list with the downstream topology requirements.
Incorrect Answers
A:Compared with the requested “Use FortiLink VLAN optimization where appropriate” at the factory, this would handle alternate FortiLink connectivity without incorrectly combining members into one LACP bundle instead: split-interface behavior is topology-dependent and distinct from a conventional active aggregate. At the factory, the operational proof would instead be to compare the effective ISL VLAN list with the downstream topology requirements, whereas “Configure a FortiLink split interface where the topology requires it” is validated by a different test: verify split-interface state against which FortiSwitch devices each member connects to.
B:Compared with the requested “Use FortiLink VLAN optimization where appropriate” at the factory, this would prevent an upstream switch failure disconnecting every switch below it instead: redundant topology design removes a single parent chassis from the data-plane dependency chain. At the factory, the operational proof would instead be to compare the effective ISL VLAN list with the downstream topology requirements, whereas “Use redundant uplinks rather than a single-chain design for critical endpoints” is validated by a different test: perform a parent-switch outage test and observe remaining access-layer connectivity.
C:For the factory, “Use VLAN pruning on ISL trunks” is a different type of control from “Use FortiLink VLAN optimization where appropriate”: VLAN pruning limits inter-switch VLAN carriage to those actually required along each path. Unlike the requested feature, that setting addresses the need to avoid transporting VLAN traffic across parts of the stack with no members, not the objective to reduce unnecessary VLAN configuration work on managed inter-switch connections.
D:Compared with the requested “Use FortiLink VLAN optimization where appropriate” at the factory, this would separate switch control traffic onto the management port where supported instead: out-of-band L3 FortiLink uses a dedicated management interface rather than the ordinary data plane. At the factory, the operational proof would instead be to compare the effective ISL VLAN list with the downstream topology requirements, whereas “Select out-of-band management for a routed island” is validated by a different test: test management-port IP connectivity and confirm the correct FortiLink source path.
Question 395
When engineers use FortiLink VLAN optimization where appropriate at the research building, which forwarding, security, management or diagnostic outcome follows from that action?
- The ring variant requires supported peer and inter-switch arrangements rather than uncontrolled Ethernet loops
- FortiLink-over-L3 provides a management path, not a continuous VLAN data-plane extension
- Optimization restricts or adjusts VLAN distribution to reduce superfluous trunk state
- Downstream FortiSwitch units join through supported inter-switch links to the first unit
Explanation
Correct Answer
C:The switch behavior that matters is: the configured operation is meant to reduce unnecessary VLAN configuration work on managed inter-switch connections. The most relevant validation is to compare the effective ISL VLAN list with the downstream topology requirements for the equipment at the research building.
Incorrect Answers
A:This outcome would be relevant to “Use an MCLAG+ ring only where supported” at the research building, not the task “Use FortiLink VLAN optimization where appropriate”; the other task is to provide an appropriate redundant path in a ring-like MCLAG topology. The action “Use FortiLink VLAN optimization where appropriate” targets a different result: optimization restricts or adjusts VLAN distribution to reduce superfluous trunk state; the proposed alternative would instead be checked by verify documented peer links and spanning-tree/MCLAG status for the complete ring.
B:That behavior applies when engineers “Avoid stretching production VLANs across Layer 3 FortiLink”; the different operation “Use FortiLink VLAN optimization where appropriate” is intended to reduce unnecessary VLAN configuration work on managed inter-switch connections. That different feature is verified by trace the VLAN boundary and verify routing rather than a nonexistent L2 stretch; for “Use FortiLink VLAN optimization where appropriate” on a newly racked distribution unit, the relevant evidence is to compare the effective ISL VLAN list with the downstream topology requirements.
D:That behavior applies when engineers “Cascade access switches through an upstream managed switch”; the different operation “Use FortiLink VLAN optimization where appropriate” is intended to reduce unnecessary VLAN configuration work on managed inter-switch connections. That different feature is verified by inspect child-switch discovery and the parent ISL forwarding state; for “Use FortiLink VLAN optimization where appropriate” on a newly racked distribution unit, the relevant evidence is to compare the effective ISL VLAN list with the downstream topology requirements.
Question 396
On two distribution switches at the clinic, the team reports that it has configured “Use FortiLink VLAN optimization where appropriate.” Which verification provides the strongest direct evidence that the intended function is working?
- Check second-tier ICL and access trunks rather than only first-tier connectivity
- Audit per-tier peer groups and the full three-layer physical uplink map
- Verify which tier holds the FortiGate uplink and which links serve access switches
- Compare the effective ISL VLAN list with the downstream topology requirements
Explanation
Correct Answer
D:At this network boundary, optimization restricts or adjusts VLAN distribution to reduce superfluous trunk state. Directly measuring that result demonstrates whether the step to reduce unnecessary VLAN configuration work on managed inter-switch connections succeeded on two distribution switches.
Incorrect Answers
A:This check is suited to “Provide second-tier MCLAG for resilient access aggregation” when trying to protect the next aggregation layer beneath an already redundant core, not to verify “Use FortiLink VLAN optimization where appropriate” at the clinic. Checking “Use FortiLink VLAN optimization where appropriate” at the clinic requires evidence of its own mechanism: optimization restricts or adjusts VLAN distribution to reduce superfluous trunk state; that is not the outcome measured by “Provide second-tier MCLAG for resilient access aggregation”.
B:This check is suited to “Design a three-tier MCLAG hierarchy” when trying to extend resilient aggregation through core, distribution and access levels, not to verify “Use FortiLink VLAN optimization where appropriate” at the clinic. Checking “Use FortiLink VLAN optimization where appropriate” at the clinic requires evidence of its own mechanism: optimization restricts or adjusts VLAN distribution to reduce superfluous trunk state; that is not the outcome measured by “Design a three-tier MCLAG hierarchy”.
C:The proposed check concerns “Deploy a two-tier FortiSwitch hierarchy” rather than “Use FortiLink VLAN optimization where appropriate”: one switch tier aggregates downstream access units via ISLs or supported trunks. For “Use FortiLink VLAN optimization where appropriate” on two distribution switches, a better test would be to compare the effective ISL VLAN list with the downstream topology requirements, which targets reduce unnecessary VLAN configuration work on managed inter-switch connections rather than the alternative diagnostic “Deploy a two-tier FortiSwitch hierarchy”.
Question 397
A network architect documents a single goal for a staging FortiSwitch: maintain server connectivity when one FortiSwitch peer fails. Which listed procedure provides that capability?
- Prefer a dual-homed server MCLAG attachment
- Select out-of-band management for a routed island
- Build a redundant ICL between peers
- Configure a FortiLink split interface where the topology requires it
- Use VLAN pruning on ISL trunks
Explanation
Correct Answer
A:In this deployment, a server LACP trunk can span the two MCLAG peers while presenting one logical aggregate. This distinction is material to the data hall, where the stated goal is to maintain server connectivity when one FortiSwitch peer fails.
Incorrect Answers
B:For the data hall, “Select out-of-band management for a routed island” is a different type of control from “Prefer a dual-homed server MCLAG attachment”: out-of-band L3 FortiLink uses a dedicated management interface rather than the ordinary data plane. Unlike the requested feature, that setting addresses the need to separate switch control traffic onto the management port where supported, not the objective to maintain server connectivity when one FortiSwitch peer fails.
C:Compared with the requested “Prefer a dual-homed server MCLAG attachment” at the data hall, this would retain peer-state exchange if one physical interchassis cable fails instead: an interchassis link with multiple members avoids making one cable the sole MCLAG coordination path. At the data hall, the operational proof would instead be to inspect server bond partner details and both peer switch trunk memberships, whereas “Build a redundant ICL between peers” is validated by a different test: inspect all ICL member interfaces and test a single-cable failure.
D:Compared with the requested “Prefer a dual-homed server MCLAG attachment” at the data hall, this would handle alternate FortiLink connectivity without incorrectly combining members into one LACP bundle instead: split-interface behavior is topology-dependent and distinct from a conventional active aggregate. At the data hall, the operational proof would instead be to inspect server bond partner details and both peer switch trunk memberships, whereas “Configure a FortiLink split interface where the topology requires it” is validated by a different test: verify split-interface state against which FortiSwitch devices each member connects to.
E:Compared with the requested “Prefer a dual-homed server MCLAG attachment” at the data hall, this would avoid transporting VLAN traffic across parts of the stack with no members instead: VLAN pruning limits inter-switch VLAN carriage to those actually required along each path. At the data hall, the operational proof would instead be to inspect server bond partner details and both peer switch trunk memberships, whereas “Use VLAN pruning on ISL trunks” is validated by a different test: inspect which VLAN IDs remain active on each intermediate ISL trunk.
Question 398
A colleague asks about the effect of “Prefer a dual-homed server MCLAG attachment” on a carefully segmented Layer 2 network. Which behavior best characterizes that feature?
- A server LACP trunk can span the two MCLAG peers while presenting one logical aggregate
- The ring variant requires supported peer and inter-switch arrangements rather than uncontrolled Ethernet loops
- Point-to-point L2 transit preserves required FortiLink discovery and management frames across the middle network
- FortiLink-over-L3 provides a management path, not a continuous VLAN data-plane extension
Explanation
Correct Answer
A:For the stated requirement, the configured operation is meant to maintain server connectivity when one FortiSwitch peer fails. The most relevant validation is to inspect server bond partner details and both peer switch trunk memberships for the equipment at the development floor.
Incorrect Answers
B:That behavior applies when engineers “Use an MCLAG+ ring only where supported”; the different operation “Prefer a dual-homed server MCLAG attachment” is intended to maintain server connectivity when one FortiSwitch peer fails. That different feature is verified by verify documented peer links and spanning-tree/MCLAG status for the complete ring; for “Prefer a dual-homed server MCLAG attachment” on a carefully segmented Layer 2 network, the relevant evidence is to inspect server bond partner details and both peer switch trunk memberships.
C:That behavior applies when engineers “Use FortiLink over a point-to-point Layer 2 transit”; the different operation “Prefer a dual-homed server MCLAG attachment” is intended to maintain server connectivity when one FortiSwitch peer fails. That different feature is verified by capture FortiLink control traffic at both ends of the Layer 2 segment; for “Prefer a dual-homed server MCLAG attachment” on a carefully segmented Layer 2 network, the relevant evidence is to inspect server bond partner details and both peer switch trunk memberships.
D:This outcome would be relevant to “Avoid stretching production VLANs across Layer 3 FortiLink” at the development floor, not the task “Prefer a dual-homed server MCLAG attachment”; the other task is to keep remote switch islands from assuming a shared Layer 2 segment across an IP network. The action “Prefer a dual-homed server MCLAG attachment” targets a different result: a server LACP trunk can span the two MCLAG peers while presenting one logical aggregate; the proposed alternative would instead be checked by trace the VLAN boundary and verify routing rather than a nonexistent L2 stretch.
Question 399
The work order to maintain server connectivity when one FortiSwitch peer fails is marked complete on a central switching stack. Which observation most directly tests the completed configuration?
- Check second-tier ICL and access trunks rather than only first-tier connectivity
- Verify which tier holds the FortiGate uplink and which links serve access switches
- Inspect server bond partner details and both peer switch trunk memberships
- Inspect static-ISL status and the intended allowed VLAN configuration
Explanation
Correct Answer
C:The deciding detail is that a server LACP trunk can span the two MCLAG peers while presenting one logical aggregate. Directly measuring that result demonstrates whether the step to maintain server connectivity when one FortiSwitch peer fails succeeded on a central switching stack.
Incorrect Answers
A:The proposed check concerns “Provide second-tier MCLAG for resilient access aggregation” rather than “Prefer a dual-homed server MCLAG attachment”: a lower peer group supplies redundant endpoints for access switches deeper in the design. For “Prefer a dual-homed server MCLAG attachment” on a central switching stack, a better test would be to inspect server bond partner details and both peer switch trunk memberships, which targets maintain server connectivity when one FortiSwitch peer fails rather than the alternative diagnostic “Provide second-tier MCLAG for resilient access aggregation”.
B:This check is suited to “Deploy a two-tier FortiSwitch hierarchy” when trying to separate distribution and access functions while keeping central FortiLink management, not to verify “Prefer a dual-homed server MCLAG attachment” at the conference venue. Checking “Prefer a dual-homed server MCLAG attachment” at the conference venue requires evidence of its own mechanism: a server LACP trunk can span the two MCLAG peers while presenting one logical aggregate; that is not the outcome measured by “Deploy a two-tier FortiSwitch hierarchy”.
D:This check is suited to “Use a supported static ISL for a specialized topology” when trying to control uplink behavior where automatic ISL discovery is not the intended configuration, not to verify “Prefer a dual-homed server MCLAG attachment” at the conference venue. Checking “Prefer a dual-homed server MCLAG attachment” at the conference venue requires evidence of its own mechanism: a server LACP trunk can span the two MCLAG peers while presenting one logical aggregate; that is not the outcome measured by “Use a supported static ISL for a specialized topology”.
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.