Question 360
After implementing “Deploy a full-mesh HA FortiLink architecture,” the site engineer needs to assess its actual effect on an access switch in routine maintenance. Which test is the best match?
- Test IP routing and controller communication between the remote switch and FortiGate
- Audit per-tier peer groups and the full three-layer physical uplink map
- Check controller association of each switch serial in the island
- Follow physical uplink inventory and test each HA member's controller reachability
Explanation
Correct Answer
D:At this network boundary, supported fully meshed wiring attaches the FortiGate cluster redundantly to the appropriate switch layer. Directly measuring that result demonstrates whether the step to avoid loss of one FortiGate connection causing loss of switch access succeeded on an access switch in routine maintenance.
Incorrect Answers
A:The proposed check concerns “Use routed Layer 3 FortiLink for a remote island” rather than “Deploy a full-mesh HA FortiLink architecture”: l3 FortiLink requires reachable management addressing instead of a continuous Layer 2 switch-controller path. For “Deploy a full-mesh HA FortiLink architecture” on an access switch in routine maintenance, a better test would be to follow physical uplink inventory and test each HA member's controller reachability, which targets avoid loss of one FortiGate connection causing loss of switch access rather than the alternative diagnostic “Use routed Layer 3 FortiLink for a remote island”.
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 “Deploy a full-mesh HA FortiLink architecture” at the media studio. Checking “Deploy a full-mesh HA FortiLink architecture” at the media studio requires evidence of its own mechanism: supported fully meshed wiring attaches the FortiGate cluster redundantly to the appropriate switch layer; that is not the outcome measured by “Design a three-tier MCLAG hierarchy”.
C:This check is suited to “Keep a routed island on one controlling FortiGate” when trying to respect FortiLink-over-L3 island controller design limits, not to verify “Deploy a full-mesh HA FortiLink architecture” at the media studio. Checking “Deploy a full-mesh HA FortiLink architecture” at the media studio requires evidence of its own mechanism: supported fully meshed wiring attaches the FortiGate cluster redundantly to the appropriate switch layer; that is not the outcome measured by “Keep a routed island on one controlling FortiGate”.
Question 361
The operational requirement for a managed campus switch at the retail site is to handle alternate FortiLink connectivity without incorrectly combining members into one LACP bundle. Which FortiSwitch choice directly targets it?
- Configure a FortiLink split interface where the topology requires it
- Use a fully meshed connection between adjacent MCLAG tiers
- Use an HA FortiGate pair to manage an access switch
- Use a supported static ISL for a specialized topology
- Provide first-tier MCLAG before downstream redundancy
Explanation
Correct Answer
A:In this deployment, split-interface behavior is topology-dependent and distinct from a conventional active aggregate. This distinction is material to the retail site, where the stated goal is to handle alternate FortiLink connectivity without incorrectly combining members into one LACP bundle.
Incorrect Answers
B:Compared with the requested “Configure a FortiLink split interface where the topology requires it” at the retail site, this would maintain upstream connectivity when one higher-tier switch or link fails instead: cross-tier links reach both peers in the upper tier rather than funneling all traffic through one unit. At the retail site, the operational proof would instead be to verify split-interface state against which FortiSwitch devices each member connects to, whereas “Use a fully meshed connection between adjacent MCLAG tiers” is validated by a different test: trace every lower-tier peer's uplinks to both upper-tier devices.
C:For the retail site, “Use an HA FortiGate pair to manage an access switch” is a different type of control from “Configure a FortiLink split interface where the topology requires it”: the FortiGate HA cluster presents the management service while the switch wiring follows a supported HA topology. Unlike the requested feature, that setting addresses the need to retain controller availability across a firewall failover, not the objective to handle alternate FortiLink connectivity without incorrectly combining members into one LACP bundle.
D:Compared with the requested “Configure a FortiLink split interface where the topology requires it” at the retail site, this would control uplink behavior where automatic ISL discovery is not the intended configuration instead: a static ISL defines the inter-switch path and can carry manually controlled VLAN settings. At the retail site, the operational proof would instead be to verify split-interface state against which FortiSwitch devices each member connects to, whereas “Use a supported static ISL for a specialized topology” is validated by a different test: inspect static-ISL status and the intended allowed VLAN configuration.
E:Compared with the requested “Configure a FortiLink split interface where the topology requires it” at the retail site, this would protect the switch pair closest to the FortiGate from a single chassis outage instead: first-tier peers act as a redundant upstream anchor for downstream distribution or access switches. At the retail site, the operational proof would instead be to verify split-interface state against which FortiSwitch devices each member connects to, whereas “Provide first-tier MCLAG before downstream redundancy” is validated by a different test: monitor first-tier peer synchronization and FortiLink reachability after failover.
Question 362
On a recently upgraded FortiSwitch, “Configure a FortiLink split interface where the topology requires it” is configured for the airport office. What effect should an administrator expect without assuming unrelated features are enabled?
- 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
- Split-interface behavior is topology-dependent and distinct from a conventional active aggregate
- Redundant topology design removes a single parent chassis from the data-plane dependency chain
Explanation
Correct Answer
C:For the stated requirement, the configured operation is meant to handle alternate FortiLink connectivity without incorrectly combining members into one LACP bundle. The most relevant validation is to verify split-interface state against which FortiSwitch devices each member connects to for the equipment at the airport office.
Incorrect Answers
A:That behavior applies when engineers “Keep independent LAN and WAN FortiLink stacks”; the different operation “Configure a FortiLink split interface where the topology requires it” is intended to handle alternate FortiLink connectivity without incorrectly combining members into one LACP bundle. That different feature is verified by confirm each stack's FortiLink interface and that units do not cross the wrong stack; for “Configure a FortiLink split interface where the topology requires it” on a recently upgraded FortiSwitch, the relevant evidence is to verify split-interface state against which FortiSwitch devices each member connects to.
B:This outcome would be relevant to “Deploy an MCLAG distribution peer pair” at the airport office, not the task “Configure a FortiLink split interface where the topology requires it”; the other task is to avoid a single distribution-chassis failure stopping attached access switches. The action “Configure a FortiLink split interface where the topology requires it” targets a different result: split-interface behavior is topology-dependent and distinct from a conventional active aggregate; the proposed alternative would instead be checked by check peer and ICL health and validate data forwarding when one peer is isolated.
D:That behavior applies when engineers “Use redundant uplinks rather than a single-chain design for critical endpoints”; the different operation “Configure a FortiLink split interface where the topology requires it” is intended to handle alternate FortiLink connectivity without incorrectly combining members into one LACP bundle. That different feature is verified by perform a parent-switch outage test and observe remaining access-layer connectivity; for “Configure a FortiLink split interface where the topology requires it” on a recently upgraded FortiSwitch, the relevant evidence is to verify split-interface state against which FortiSwitch devices each member connects to.
Question 363
At the operations center, a dashboard shows ordinary link-up state, but the team also needs proof for “Configure a FortiLink split interface where the topology requires it.” Which targeted check should be used?
- Compare end-to-end source and destination addressing and remove an intervening NAT rule
- Check both physical member terminations and the FortiGate aggregate configuration
- Inspect all ICL member interfaces and test a single-cable failure
- Verify split-interface state against which FortiSwitch devices each member connects to
Explanation
Correct Answer
D:The deciding detail is that split-interface behavior is topology-dependent and distinct from a conventional active aggregate. Directly measuring that result demonstrates whether the step to handle alternate FortiLink connectivity without incorrectly combining members into one LACP bundle succeeded on a FortiLink-managed access switch.
Incorrect Answers
A: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 “Configure a FortiLink split interface where the topology requires it” at the operations center. Checking “Configure a FortiLink split interface where the topology requires it” at the operations center requires evidence of its own mechanism: split-interface behavior is topology-dependent and distinct from a conventional active aggregate; that is not the outcome measured by “Avoid NAT between routed FortiLink island and FortiGate”.
B:The proposed check concerns “Disable split-interface for a same-switch LAG when required” rather than “Configure a FortiLink split interface where the topology requires it”: the supported aggregate topology can require split-interface disabled so member links form the intended logical trunk. For “Configure a FortiLink split interface where the topology requires it” on a FortiLink-managed access switch, a better test would be to verify split-interface state against which FortiSwitch devices each member connects to, which targets handle alternate FortiLink connectivity without incorrectly combining members into one LACP bundle rather than the alternative diagnostic “Disable split-interface for a same-switch LAG when required”.
C:This check is suited to “Build a redundant ICL between peers” when trying to retain peer-state exchange if one physical interchassis cable fails, not to verify “Configure a FortiLink split interface where the topology requires it” at the operations center. Checking “Configure a FortiLink split interface where the topology requires it” at the operations center requires evidence of its own mechanism: split-interface behavior is topology-dependent and distinct from a conventional active aggregate; that is not the outcome measured by “Build a redundant ICL between peers”.
Question 364
During a change window in the warehouse, engineers are asked to operate a FortiLink aggregate whose physical members all terminate on one FortiSwitch. What should they configure rather than using a feature for an adjacent purpose?
- Avoid NAT between routed FortiLink island and FortiGate
- Disable split-interface for a same-switch LAG when required
- Use redundant uplinks rather than a single-chain design for critical endpoints
- Use FortiLink VLAN optimization where appropriate
- Configure a FortiLink split interface where the topology requires it
Explanation
Correct Answer
B:The relevant mechanism is: the supported aggregate topology can require split-interface disabled so member links form the intended logical trunk. The operator can test this claim by the specific check: check both physical member terminations and the FortiGate aggregate configuration.
Incorrect Answers
A:Compared with the requested “Disable split-interface for a same-switch LAG when required” at the warehouse, this would preserve a supported L3 FortiLink controller communication path instead: Fortinet's L3 FortiLink limitations disallow address translation between the switch and its FortiGate. At the warehouse, the operational proof would instead be to check both physical member terminations and the FortiGate aggregate configuration, whereas “Avoid NAT between routed FortiLink island and FortiGate” is validated by a different test: compare end-to-end source and destination addressing and remove an intervening NAT rule.
C:Compared with the requested “Disable split-interface for a same-switch LAG when required” at the warehouse, 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 warehouse, the operational proof would instead be to check both physical member terminations and the FortiGate aggregate configuration, 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.
D:For the warehouse, “Use FortiLink VLAN optimization where appropriate” is a different type of control from “Disable split-interface for a same-switch LAG when required”: optimization restricts or adjusts VLAN distribution to reduce superfluous trunk state. Unlike the requested feature, that setting addresses the need to reduce unnecessary VLAN configuration work on managed inter-switch connections, not the objective to operate a FortiLink aggregate whose physical members all terminate on one FortiSwitch.
E:Compared with the requested “Disable split-interface for a same-switch LAG when required” at the warehouse, 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 warehouse, the operational proof would instead be to check both physical member terminations and the FortiGate aggregate configuration, 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.
Question 365
For the headquarters, an administrator applies the action “Disable split-interface for a same-switch LAG when required.” Which effect should appear when it operates as intended?
- The supported aggregate topology can require split-interface disabled so member links form the intended logical trunk
- Downstream FortiSwitch units join through supported inter-switch links to the first unit
- All switches in a single routed FortiSwitch island must be managed by the same FortiGate
- The ring variant requires supported peer and inter-switch arrangements rather than uncontrolled Ethernet loops
Explanation
Correct Answer
A:This approach fits because the configured operation is meant to operate a FortiLink aggregate whose physical members all terminate on one FortiSwitch. The most relevant validation is to check both physical member terminations and the FortiGate aggregate configuration for the equipment at the headquarters.
Incorrect Answers
B:That behavior applies when engineers “Cascade access switches through an upstream managed switch”; the different operation “Disable split-interface for a same-switch LAG when required” is intended to operate a FortiLink aggregate whose physical members all terminate on one FortiSwitch. That different feature is verified by inspect child-switch discovery and the parent ISL forwarding state; for “Disable split-interface for a same-switch LAG when required” on a central switching stack, the relevant evidence is to check both physical member terminations and the FortiGate aggregate configuration.
C:That behavior applies when engineers “Keep a routed island on one controlling FortiGate”; the different operation “Disable split-interface for a same-switch LAG when required” is intended to operate a FortiLink aggregate whose physical members all terminate on one FortiSwitch. That different feature is verified by check controller association of each switch serial in the island; for “Disable split-interface for a same-switch LAG when required” on a central switching stack, the relevant evidence is to check both physical member terminations and the FortiGate aggregate configuration.
D:This outcome would be relevant to “Use an MCLAG+ ring only where supported” at the headquarters, not the task “Disable split-interface for a same-switch LAG when required”; the other task is to provide an appropriate redundant path in a ring-like MCLAG topology. The action “Disable split-interface for a same-switch LAG when required” targets a different result: the supported aggregate topology can require split-interface disabled so member links form the intended logical trunk; the proposed alternative would instead be checked by verify documented peer links and spanning-tree/MCLAG status for the complete ring.
Question 366
A FortiSwitch engineer in the hospital wing is documenting successful operation of “Disable split-interface for a same-switch LAG when required.” Which measurement or inspection confirms it?
- Check both physical member terminations and the FortiGate aggregate configuration
- 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
Explanation
Correct Answer
A:The critical distinction is that the supported aggregate topology can require split-interface disabled so member links form the intended logical trunk. Directly measuring that result demonstrates whether the step to operate a FortiLink aggregate whose physical members all terminate on one FortiSwitch succeeded on a FortiSwitch connected to the security edge.
Incorrect Answers
B: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 “Disable split-interface for a same-switch LAG when required” at the hospital wing. Checking “Disable split-interface for a same-switch LAG when required” at the hospital wing requires evidence of its own mechanism: the supported aggregate topology can require split-interface disabled so member links form the intended logical trunk; that is not the outcome measured by “Provide second-tier MCLAG for resilient access aggregation”.
C: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 “Disable split-interface for a same-switch LAG when required” at the hospital wing. Checking “Disable split-interface for a same-switch LAG when required” at the hospital wing requires evidence of its own mechanism: the supported aggregate topology can require split-interface disabled so member links form the intended logical trunk; that is not the outcome measured by “Design a three-tier MCLAG hierarchy”.
D:The proposed check concerns “Deploy a two-tier FortiSwitch hierarchy” rather than “Disable split-interface for a same-switch LAG when required”: one switch tier aggregates downstream access units via ISLs or supported trunks. For “Disable split-interface for a same-switch LAG when required” on a FortiSwitch connected to the security edge, a better test would be to check both physical member terminations and the FortiGate aggregate configuration, which targets operate a FortiLink aggregate whose physical members all terminate on one FortiSwitch rather than the alternative diagnostic “Deploy a two-tier FortiSwitch hierarchy”.
Question 367
For the factory, the network team needs to reach a remote switch through a transparent dedicated bridging path. Which change is the most direct way to implement that requirement on an access switch in routine maintenance?
- Select in-band management for a routed FortiSwitch island
- Deploy an MCLAG distribution peer pair
- Keep independent LAN and WAN FortiLink stacks
- Use FortiLink over a point-to-point Layer 2 transit
Explanation
Correct Answer
D:That setting is appropriate here because point-to-point L2 transit preserves required FortiLink discovery and management frames across the middle network. This distinction is material to the factory, where the stated goal is to reach a remote switch through a transparent dedicated bridging path.
Incorrect Answers
A:For the factory, “Select in-band management for a routed FortiSwitch island” is a different type of control from “Use FortiLink over a point-to-point Layer 2 transit”: in-band L3 management uses the FortiSwitch internal management interface for the controller path. Unlike the requested feature, that setting addresses the need to use a switch's internal interface to carry routed FortiLink control traffic, not the objective to reach a remote switch through a transparent dedicated bridging path.
B:Compared with the requested “Use FortiLink over a point-to-point Layer 2 transit” at the factory, this would avoid a single distribution-chassis failure stopping attached access switches instead: peer switches cooperate as one logical aggregation endpoint for dual-homed downstream trunks. At the factory, the operational proof would instead be to capture FortiLink control traffic at both ends of the Layer 2 segment, whereas “Deploy an MCLAG distribution peer pair” is validated by a different test: check peer and ICL health and validate data forwarding when one peer is isolated.
C:Compared with the requested “Use FortiLink over a point-to-point Layer 2 transit” at the factory, this would use separate switching infrastructure for different security-edge functions instead: separate FortiLink interfaces manage separate VLAN and switch groups for LAN and WAN roles. At the factory, the operational proof would instead be to capture FortiLink control traffic at both ends of the Layer 2 segment, whereas “Keep independent LAN and WAN FortiLink stacks” is validated by a different test: confirm each stack's FortiLink interface and that units do not cross the wrong stack.
Question 368
On a managed campus switch, “Use FortiLink over a point-to-point Layer 2 transit” is configured for the distribution floor. What effect should an administrator expect without assuming unrelated features are enabled?
- Optimization restricts or adjusts VLAN distribution to reduce superfluous trunk state
- Redundant topology design removes a single parent chassis from the data-plane dependency chain
- Point-to-point L2 transit preserves required FortiLink discovery and management frames across the middle network
- Split-interface behavior is topology-dependent and distinct from a conventional active aggregate
- Fortinet's L3 FortiLink limitations disallow address translation between the switch and its FortiGate
Explanation
Correct Answer
C:This is the precise control because the configured operation is meant to reach a remote switch through a transparent dedicated bridging path. The most relevant validation is to capture FortiLink control traffic at both ends of the Layer 2 segment for the equipment at the distribution floor.
Incorrect Answers
A:That behavior applies when engineers “Use FortiLink VLAN optimization where appropriate”; the different operation “Use FortiLink over a point-to-point Layer 2 transit” is intended to reach a remote switch through a transparent dedicated bridging path. That different feature is verified by compare the effective ISL VLAN list with the downstream topology requirements; for “Use FortiLink over a point-to-point Layer 2 transit” on a managed campus switch, the relevant evidence is to capture FortiLink control traffic at both ends of the Layer 2 segment.
B:That behavior applies when engineers “Use redundant uplinks rather than a single-chain design for critical endpoints”; the different operation “Use FortiLink over a point-to-point Layer 2 transit” is intended to reach a remote switch through a transparent dedicated bridging path. That different feature is verified by perform a parent-switch outage test and observe remaining access-layer connectivity; for “Use FortiLink over a point-to-point Layer 2 transit” on a managed campus switch, the relevant evidence is to capture FortiLink control traffic at both ends of the Layer 2 segment.
D:That behavior applies when engineers “Configure a FortiLink split interface where the topology requires it”; the different operation “Use FortiLink over a point-to-point Layer 2 transit” is intended to reach a remote switch through a transparent dedicated bridging path. That different feature is verified by verify split-interface state against which FortiSwitch devices each member connects to; for “Use FortiLink over a point-to-point Layer 2 transit” on a managed campus switch, the relevant evidence is to capture FortiLink control traffic at both ends of the Layer 2 segment.
E:This outcome would be relevant to “Avoid NAT between routed FortiLink island and FortiGate” at the distribution floor, not the task “Use FortiLink over a point-to-point Layer 2 transit”; the other task is to preserve a supported L3 FortiLink controller communication path. The action “Use FortiLink over a point-to-point Layer 2 transit” targets a different result: point-to-point L2 transit preserves required FortiLink discovery and management frames across the middle network; the proposed alternative would instead be checked by compare end-to-end source and destination addressing and remove an intervening NAT rule.
Question 369
A feature acceptance test on a recently upgraded FortiSwitch concerns “Use FortiLink over a point-to-point Layer 2 transit.” What should be checked to establish its expected operation?
- Verify documented peer links and spanning-tree/MCLAG status for the complete ring
- Check controller association of each switch serial in the island
- Inspect child-switch discovery and the parent ISL forwarding state
- Capture FortiLink control traffic at both ends of the Layer 2 segment
Explanation
Correct Answer
D:The implementation works because point-to-point L2 transit preserves required FortiLink discovery and management frames across the middle network. Directly measuring that result demonstrates whether the step to reach a remote switch through a transparent dedicated bridging path succeeded on a recently upgraded FortiSwitch.
Incorrect Answers
A:The proposed check concerns “Use an MCLAG+ ring only where supported” rather than “Use FortiLink over a point-to-point Layer 2 transit”: the ring variant requires supported peer and inter-switch arrangements rather than uncontrolled Ethernet loops. For “Use FortiLink over a point-to-point Layer 2 transit” on a recently upgraded FortiSwitch, a better test would be to capture FortiLink control traffic at both ends of the Layer 2 segment, which targets reach a remote switch through a transparent dedicated bridging path rather than the alternative diagnostic “Use an MCLAG+ ring only where supported”.
B:This check is suited to “Keep a routed island on one controlling FortiGate” when trying to respect FortiLink-over-L3 island controller design limits, not to verify “Use FortiLink over a point-to-point Layer 2 transit” at the media studio. Checking “Use FortiLink over a point-to-point Layer 2 transit” at the media studio requires evidence of its own mechanism: point-to-point L2 transit preserves required FortiLink discovery and management frames across the middle network; that is not the outcome measured by “Keep a routed island on one controlling FortiGate”.
C:This check is suited to “Cascade access switches through an upstream managed switch” when trying to extend a FortiLink-managed network beyond the number of direct controller ports, not to verify “Use FortiLink over a point-to-point Layer 2 transit” at the media studio. Checking “Use FortiLink over a point-to-point Layer 2 transit” at the media studio requires evidence of its own mechanism: point-to-point L2 transit preserves required FortiLink discovery and management frames across the middle network; that is not the outcome measured by “Cascade access switches through an upstream managed switch”.
Question 370
A network architect documents a single goal for a FortiLink-managed access switch: centrally manage switches separated from FortiGate by an IP-routed network. Which listed procedure provides that capability?
- Disable split-interface for a same-switch LAG when required
- Use an HA FortiGate pair to manage an access switch
- Use a fully meshed connection between adjacent MCLAG tiers
- Use routed Layer 3 FortiLink for a remote island
Explanation
Correct Answer
D:Given the described goal, l3 FortiLink requires reachable management addressing instead of a continuous Layer 2 switch-controller path. The operator can test this claim by the specific check: test IP routing and controller communication between the remote switch and FortiGate.
Incorrect Answers
A:For the retail site, “Disable split-interface for a same-switch LAG when required” is a different type of control from “Use routed Layer 3 FortiLink for a remote island”: the supported aggregate topology can require split-interface disabled so member links form the intended logical trunk. Unlike the requested feature, that setting addresses the need to operate a FortiLink aggregate whose physical members all terminate on one FortiSwitch, not the objective to centrally manage switches separated from FortiGate by an IP-routed network.
B:Compared with the requested “Use routed Layer 3 FortiLink for a remote island” at the retail site, 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 retail site, the operational proof would instead be to test IP routing and controller communication between the remote switch and FortiGate, 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.
C:Compared with the requested “Use routed Layer 3 FortiLink for a remote island” at the retail site, this would maintain upstream connectivity when one higher-tier switch or link fails instead: cross-tier links reach both peers in the upper tier rather than funneling all traffic through one unit. At the retail site, the operational proof would instead be to test IP routing and controller communication between the remote switch and FortiGate, whereas “Use a fully meshed connection between adjacent MCLAG tiers” is validated by a different test: trace every lower-tier peer's uplinks to both upper-tier devices.