Question 330
The work order to deploy a small branch with one managed switch and minimal switching complexity is marked complete on a switch linked to a FortiGate running FortiOS 7.6. Which observation most directly tests the completed configuration?
- Audit per-tier peer groups and the full three-layer physical uplink map
- Capture FortiLink control traffic at both ends of the Layer 2 segment
- Trace the VLAN boundary and verify routing rather than a nonexistent L2 stretch
- Inspect FortiLink status and the one-switch topology after startup
Explanation
Correct Answer
D:The critical distinction is that a single FortiLink connection allows the FortiGate to manage the directly attached switch. Directly measuring that result demonstrates whether the step to deploy a small branch with one managed switch and minimal switching complexity succeeded on a switch linked to a FortiGate running FortiOS 7.6.
Incorrect Answers
A: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 direct one-to-one FortiGate-to-FortiSwitch wiring” at the campus. Checking “Use direct one-to-one FortiGate-to-FortiSwitch wiring” at the campus requires evidence of its own mechanism: a single FortiLink connection allows the FortiGate to manage the directly attached switch; that is not the outcome measured by “Design a three-tier MCLAG hierarchy”.
B:The proposed check concerns “Use FortiLink over a point-to-point Layer 2 transit” rather than “Use direct one-to-one FortiGate-to-FortiSwitch wiring”: point-to-point L2 transit preserves required FortiLink discovery and management frames across the middle network. For “Use direct one-to-one FortiGate-to-FortiSwitch wiring” on a switch linked to a FortiGate running FortiOS 7.6, a better test would be to inspect FortiLink status and the one-switch topology after startup, which targets deploy a small branch with one managed switch and minimal switching complexity rather than the alternative diagnostic “Use FortiLink over a point-to-point Layer 2 transit”.
C:This check is suited to “Avoid stretching production VLANs across Layer 3 FortiLink” when trying to keep remote switch islands from assuming a shared Layer 2 segment across an IP network, not to verify “Use direct one-to-one FortiGate-to-FortiSwitch wiring” at the campus. Checking “Use direct one-to-one FortiGate-to-FortiSwitch wiring” at the campus requires evidence of its own mechanism: a single FortiLink connection allows the FortiGate to manage the directly attached switch; that is not the outcome measured by “Avoid stretching production VLANs across Layer 3 FortiLink”.
Question 331
A network architect documents a single goal for a switch serving a high-density endpoint area: extend a FortiLink-managed network beyond the number of direct controller ports. Which listed procedure provides that capability?
- Deploy a full-mesh HA FortiLink architecture
- Select in-band management for a routed FortiSwitch island
- Attach an access switch to both MCLAG peers
- Use redundant uplinks rather than a single-chain design for critical endpoints
- Cascade access switches through an upstream managed switch
Explanation
Correct Answer
E:That setting is appropriate here because downstream FortiSwitch units join through supported inter-switch links to the first unit. This distinction is material to the remote depot, where the stated goal is to extend a FortiLink-managed network beyond the number of direct controller ports.
Incorrect Answers
A:For the remote depot, “Deploy a full-mesh HA FortiLink architecture” is a different type of control from “Cascade access switches through an upstream managed switch”: supported fully meshed wiring attaches the FortiGate cluster redundantly to the appropriate switch layer. Unlike the requested feature, that setting addresses the need to avoid loss of one FortiGate connection causing loss of switch access, not the objective to extend a FortiLink-managed network beyond the number of direct controller ports.
B:Compared with the requested “Cascade access switches through an upstream managed switch” at the remote depot, this would use a switch's internal interface to carry routed FortiLink control traffic instead: in-band L3 management uses the FortiSwitch internal management interface for the controller path. At the remote depot, the operational proof would instead be to inspect child-switch discovery and the parent ISL forwarding state, whereas “Select in-band management for a routed FortiSwitch island” is validated by a different test: verify the internal interface IP and routed connectivity to the controller.
C:Compared with the requested “Cascade access switches through an upstream managed switch” at the remote depot, this would give the access layer two independent upstream hardware paths instead: dual-homed LACP membership uses links toward each peer instead of relying on one parent chassis. At the remote depot, the operational proof would instead be to inspect child-switch discovery and the parent ISL forwarding state, whereas “Attach an access switch to both MCLAG peers” is validated by a different test: inspect both active LACP members and observe service through a peer maintenance window.
D:Compared with the requested “Cascade access switches through an upstream managed switch” at the remote depot, 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 remote depot, the operational proof would instead be to inspect child-switch discovery and the parent ISL forwarding state, 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.
Question 332
During validation of a managed switch running FortiSwitchOS 7.6 at the lab, the team asks what the change “Cascade access switches through an upstream managed switch” actually does. Which outcome is correct?
- Cross-tier links reach both peers in the upper tier rather than funneling all traffic through one unit
- Fortinet's L3 FortiLink limitations disallow address translation between the switch and its FortiGate
- Downstream FortiSwitch units join through supported inter-switch links to the first unit
- The supported aggregate topology can require split-interface disabled so member links form the intended logical trunk
Explanation
Correct Answer
C:This is the precise control because the configured operation is meant to extend a FortiLink-managed network beyond the number of direct controller ports. The most relevant validation is to inspect child-switch discovery and the parent ISL forwarding state for the equipment at the lab.
Incorrect Answers
A:That behavior applies when engineers “Use a fully meshed connection between adjacent MCLAG tiers”; the different operation “Cascade access switches through an upstream managed switch” is intended to extend a FortiLink-managed network beyond the number of direct controller ports. That different feature is verified by trace every lower-tier peer's uplinks to both upper-tier devices; for “Cascade access switches through an upstream managed switch” on a managed switch running FortiSwitchOS 7.6, the relevant evidence is to inspect child-switch discovery and the parent ISL forwarding state.
B:That behavior applies when engineers “Avoid NAT between routed FortiLink island and FortiGate”; the different operation “Cascade access switches through an upstream managed switch” is intended to extend a FortiLink-managed network beyond the number of direct controller ports. That different feature is verified by compare end-to-end source and destination addressing and remove an intervening NAT rule; for “Cascade access switches through an upstream managed switch” on a managed switch running FortiSwitchOS 7.6, the relevant evidence is to inspect child-switch discovery and the parent ISL forwarding state.
D:This outcome would be relevant to “Disable split-interface for a same-switch LAG when required” at the lab, not the task “Cascade access switches through an upstream managed switch”; the other task is to operate a FortiLink aggregate whose physical members all terminate on one FortiSwitch. The action “Cascade access switches through an upstream managed switch” targets a different result: downstream FortiSwitch units join through supported inter-switch links to the first unit; the proposed alternative would instead be checked by check both physical member terminations and the FortiGate aggregate configuration.
Question 333
A technician says “Cascade access switches through an upstream managed switch” has solved the issue at the staging rack. Which diagnostic step would substantiate that claim?
- Verify documented peer links and spanning-tree/MCLAG status for the complete ring
- Inspect child-switch discovery and the parent ISL forwarding state
- Test IP routing and controller communication between the remote switch and FortiGate
- Check controller association of each switch serial in the island
Explanation
Correct Answer
B:The implementation works because downstream FortiSwitch units join through supported inter-switch links to the first unit. Directly measuring that result demonstrates whether the step to extend a FortiLink-managed network beyond the number of direct controller ports succeeded on a remote FortiSwitch installation.
Incorrect Answers
A:This check is suited to “Use an MCLAG+ ring only where supported” when trying to provide an appropriate redundant path in a ring-like MCLAG topology, not to verify “Cascade access switches through an upstream managed switch” at the staging rack. Checking “Cascade access switches through an upstream managed switch” at the staging rack requires evidence of its own mechanism: downstream FortiSwitch units join through supported inter-switch links to the first unit; that is not the outcome measured by “Use an MCLAG+ ring only where supported”.
C:This check is suited to “Use routed Layer 3 FortiLink for a remote island” when trying to centrally manage switches separated from FortiGate by an IP-routed network, not to verify “Cascade access switches through an upstream managed switch” at the staging rack. Checking “Cascade access switches through an upstream managed switch” at the staging rack requires evidence of its own mechanism: downstream FortiSwitch units join through supported inter-switch links to the first unit; that is not the outcome measured by “Use routed Layer 3 FortiLink for a remote island”.
D:The proposed check concerns “Keep a routed island on one controlling FortiGate” rather than “Cascade access switches through an upstream managed switch”: all switches in a single routed FortiSwitch island must be managed by the same FortiGate. For “Cascade access switches through an upstream managed switch” on a remote FortiSwitch installation, a better test would be to inspect child-switch discovery and the parent ISL forwarding state, which targets extend a FortiLink-managed network beyond the number of direct controller ports rather than the alternative diagnostic “Keep a routed island on one controlling FortiGate”.
Question 334
The operational requirement for an endpoint-facing FortiSwitch port at the research building is to retain controller availability across a firewall failover. Which FortiSwitch choice directly targets it?
- Use VLAN pruning on ISL trunks
- Use an HA FortiGate pair to manage an access switch
- Provide second-tier MCLAG for resilient access aggregation
- Deploy an MCLAG distribution peer pair
Explanation
Correct Answer
B:Given the described goal, the FortiGate HA cluster presents the management service while the switch wiring follows a supported HA topology. The operator can test this claim by the specific check: perform a controlled HA role change and verify the switch remains centrally managed.
Incorrect Answers
A:Compared with the requested “Use an HA FortiGate pair to manage an access switch” at the research building, 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 research building, the operational proof would instead be to perform a controlled HA role change and verify the switch remains centrally managed, whereas “Use VLAN pruning on ISL trunks” is validated by a different test: inspect which VLAN IDs remain active on each intermediate ISL trunk.
C:Compared with the requested “Use an HA FortiGate pair to manage an access switch” at the research building, this would protect the next aggregation layer beneath an already redundant core instead: a lower peer group supplies redundant endpoints for access switches deeper in the design. At the research building, the operational proof would instead be to perform a controlled HA role change and verify the switch remains centrally managed, whereas “Provide second-tier MCLAG for resilient access aggregation” is validated by a different test: check second-tier ICL and access trunks rather than only first-tier connectivity.
D:For the research building, “Deploy an MCLAG distribution peer pair” is a different type of control from “Use an HA FortiGate pair to manage an access switch”: peer switches cooperate as one logical aggregation endpoint for dual-homed downstream trunks. Unlike the requested feature, that setting addresses the need to avoid a single distribution-chassis failure stopping attached access switches, not the objective to retain controller availability across a firewall failover.
Question 335
Before applying the planned operation “Use an HA FortiGate pair to manage an access switch” at the clinic, the administrator must predict its impact. Which prediction is sound?
- Split-interface behavior is topology-dependent and distinct from a conventional active aggregate
- The FortiGate HA cluster presents the management service while the switch wiring follows a supported HA topology
- A single FortiLink connection allows the FortiGate to manage the directly attached switch
- An interchassis link with multiple members avoids making one cable the sole MCLAG coordination path
- Out-of-band L3 FortiLink uses a dedicated management interface rather than the ordinary data plane
Explanation
Correct Answer
B:The switch behavior that matters is: the configured operation is meant to retain controller availability across a firewall failover. The most relevant validation is to perform a controlled HA role change and verify the switch remains centrally managed for the equipment at the clinic.
Incorrect Answers
A:That behavior applies when engineers “Configure a FortiLink split interface where the topology requires it”; the different operation “Use an HA FortiGate pair to manage an access switch” is intended to retain controller availability across a firewall failover. That different feature is verified by verify split-interface state against which FortiSwitch devices each member connects to; for “Use an HA FortiGate pair to manage an access switch” on a standalone FortiSwitch appliance, the relevant evidence is to perform a controlled HA role change and verify the switch remains centrally managed.
C:That behavior applies when engineers “Use direct one-to-one FortiGate-to-FortiSwitch wiring”; the different operation “Use an HA FortiGate pair to manage an access switch” is intended to retain controller availability across a firewall failover. That different feature is verified by inspect FortiLink status and the one-switch topology after startup; for “Use an HA FortiGate pair to manage an access switch” on a standalone FortiSwitch appliance, the relevant evidence is to perform a controlled HA role change and verify the switch remains centrally managed.
D:This outcome would be relevant to “Build a redundant ICL between peers” at the clinic, not the task “Use an HA FortiGate pair to manage an access switch”; the other task is to retain peer-state exchange if one physical interchassis cable fails. The action “Use an HA FortiGate pair to manage an access switch” targets a different result: the FortiGate HA cluster presents the management service while the switch wiring follows a supported HA topology; the proposed alternative would instead be checked by inspect all ICL member interfaces and test a single-cable failure.
E:That behavior applies when engineers “Select out-of-band management for a routed island”; the different operation “Use an HA FortiGate pair to manage an access switch” is intended to retain controller availability across a firewall failover. That different feature is verified by test management-port IP connectivity and confirm the correct FortiLink source path; for “Use an HA FortiGate pair to manage an access switch” on a standalone FortiSwitch appliance, the relevant evidence is to perform a controlled HA role change and verify the switch remains centrally managed.
Question 336
After implementing “Use an HA FortiGate pair to manage an access switch,” the site engineer needs to assess its actual effect on a newly commissioned floor switch. Which test is the best match?
- Capture FortiLink control traffic at both ends of the Layer 2 segment
- Trace the VLAN boundary and verify routing rather than a nonexistent L2 stretch
- Perform a controlled HA role change and verify the switch remains centrally managed
- Audit per-tier peer groups and the full three-layer physical uplink map
Explanation
Correct Answer
C:At this network boundary, the FortiGate HA cluster presents the management service while the switch wiring follows a supported HA topology. Directly measuring that result demonstrates whether the step to retain controller availability across a firewall failover succeeded on a newly commissioned floor switch.
Incorrect Answers
A:The proposed check concerns “Use FortiLink over a point-to-point Layer 2 transit” rather than “Use an HA FortiGate pair to manage an access switch”: point-to-point L2 transit preserves required FortiLink discovery and management frames across the middle network. For “Use an HA FortiGate pair to manage an access switch” on a newly commissioned floor switch, a better test would be to perform a controlled HA role change and verify the switch remains centrally managed, which targets retain controller availability across a firewall failover rather than the alternative diagnostic “Use FortiLink over a point-to-point Layer 2 transit”.
B:This check is suited to “Avoid stretching production VLANs across Layer 3 FortiLink” when trying to keep remote switch islands from assuming a shared Layer 2 segment across an IP network, not to verify “Use an HA FortiGate pair to manage an access switch” at the data hall. Checking “Use an HA FortiGate pair to manage an access switch” at the data hall requires evidence of its own mechanism: the FortiGate HA cluster presents the management service while the switch wiring follows a supported HA topology; that is not the outcome measured by “Avoid stretching production VLANs across Layer 3 FortiLink”.
D: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 an HA FortiGate pair to manage an access switch” at the data hall. Checking “Use an HA FortiGate pair to manage an access switch” at the data hall requires evidence of its own mechanism: the FortiGate HA cluster presents the management service while the switch wiring follows a supported HA topology; that is not the outcome measured by “Design a three-tier MCLAG hierarchy”.
Question 337
The accepted design for the development floor requires the ability to separate distribution and access functions while keeping central FortiLink management. Which switch feature is the closest fit?
- Deploy a two-tier FortiSwitch hierarchy
- Select in-band management for a routed FortiSwitch island
- Use a supported static ISL for a specialized topology
- Deploy a full-mesh HA FortiLink architecture
Explanation
Correct Answer
A:In this deployment, one switch tier aggregates downstream access units via ISLs or supported trunks. This distinction is material to the development floor, where the stated goal is to separate distribution and access functions while keeping central FortiLink management.
Incorrect Answers
B:Compared with the requested “Deploy a two-tier FortiSwitch hierarchy” at the development floor, this would use a switch's internal interface to carry routed FortiLink control traffic instead: in-band L3 management uses the FortiSwitch internal management interface for the controller path. At the development floor, the operational proof would instead be to verify which tier holds the FortiGate uplink and which links serve access switches, whereas “Select in-band management for a routed FortiSwitch island” is validated by a different test: verify the internal interface IP and routed connectivity to the controller.
C:For the development floor, “Use a supported static ISL for a specialized topology” is a different type of control from “Deploy a two-tier FortiSwitch hierarchy”: a static ISL defines the inter-switch path and can carry manually controlled VLAN settings. Unlike the requested feature, that setting addresses the need to control uplink behavior where automatic ISL discovery is not the intended configuration, not the objective to separate distribution and access functions while keeping central FortiLink management.
D:Compared with the requested “Deploy a two-tier FortiSwitch hierarchy” at the development floor, this would avoid loss of one FortiGate connection causing loss of switch access instead: supported fully meshed wiring attaches the FortiGate cluster redundantly to the appropriate switch layer. At the development floor, the operational proof would instead be to verify which tier holds the FortiGate uplink and which links serve access switches, whereas “Deploy a full-mesh HA FortiLink architecture” is validated by a different test: follow physical uplink inventory and test each HA member's controller reachability.
Question 338
During validation of a switch used by multiple office teams at the conference venue, the team asks what the change “Deploy a two-tier FortiSwitch hierarchy” actually does. Which outcome is correct?
- Redundant topology design removes a single parent chassis from the data-plane dependency chain
- Optimization restricts or adjusts VLAN distribution to reduce superfluous trunk state
- One switch tier aggregates downstream access units via ISLs or supported trunks
- Fortinet's L3 FortiLink limitations disallow address translation between the switch and its FortiGate
Explanation
Correct Answer
C:For the stated requirement, the configured operation is meant to separate distribution and access functions while keeping central FortiLink management. The most relevant validation is to verify which tier holds the FortiGate uplink and which links serve access switches for the equipment at the conference venue.
Incorrect Answers
A:That behavior applies when engineers “Use redundant uplinks rather than a single-chain design for critical endpoints”; the different operation “Deploy a two-tier FortiSwitch hierarchy” is intended to separate distribution and access functions while keeping central FortiLink management. That different feature is verified by perform a parent-switch outage test and observe remaining access-layer connectivity; for “Deploy a two-tier FortiSwitch hierarchy” on a switch used by multiple office teams, the relevant evidence is to verify which tier holds the FortiGate uplink and which links serve access switches.
B:This outcome would be relevant to “Use FortiLink VLAN optimization where appropriate” at the conference venue, not the task “Deploy a two-tier FortiSwitch hierarchy”; the other task is to reduce unnecessary VLAN configuration work on managed inter-switch connections. The action “Deploy a two-tier FortiSwitch hierarchy” targets a different result: one switch tier aggregates downstream access units via ISLs or supported trunks; the proposed alternative would instead be checked by compare the effective ISL VLAN list with the downstream topology requirements.
D:That behavior applies when engineers “Avoid NAT between routed FortiLink island and FortiGate”; the different operation “Deploy a two-tier FortiSwitch hierarchy” is intended to separate distribution and access functions while keeping central FortiLink management. That different feature is verified by compare end-to-end source and destination addressing and remove an intervening NAT rule; for “Deploy a two-tier FortiSwitch hierarchy” on a switch used by multiple office teams, the relevant evidence is to verify which tier holds the FortiGate uplink and which links serve access switches.
Question 339
At the hospital wing, a dashboard shows ordinary link-up state, but the team also needs proof for “Deploy a two-tier FortiSwitch hierarchy.” Which targeted check should be used?
- Trace every lower-tier peer's uplinks to both upper-tier devices
- Check both physical member terminations and the FortiGate aggregate configuration
- Verify which tier holds the FortiGate uplink and which links serve access switches
- Verify documented peer links and spanning-tree/MCLAG status for the complete ring
- Inspect child-switch discovery and the parent ISL forwarding state
Explanation
Correct Answer
C:The deciding detail is that one switch tier aggregates downstream access units via ISLs or supported trunks. Directly measuring that result demonstrates whether the step to separate distribution and access functions while keeping central FortiLink management succeeded on a managed switch running FortiSwitchOS 7.6.
Incorrect Answers
A:This check is suited to “Use a fully meshed connection between adjacent MCLAG tiers” when trying to maintain upstream connectivity when one higher-tier switch or link fails, not to verify “Deploy a two-tier FortiSwitch hierarchy” at the hospital wing. Checking “Deploy a two-tier FortiSwitch hierarchy” at the hospital wing requires evidence of its own mechanism: one switch tier aggregates downstream access units via ISLs or supported trunks; that is not the outcome measured by “Use a fully meshed connection between adjacent MCLAG tiers”.
B:The proposed check concerns “Disable split-interface for a same-switch LAG when required” rather than “Deploy a two-tier FortiSwitch hierarchy”: the supported aggregate topology can require split-interface disabled so member links form the intended logical trunk. For “Deploy a two-tier FortiSwitch hierarchy” on a managed switch running FortiSwitchOS 7.6, a better test would be to verify which tier holds the FortiGate uplink and which links serve access switches, which targets separate distribution and access functions while keeping central FortiLink management rather than the alternative diagnostic “Disable split-interface for a same-switch LAG when required”.
D:This check is suited to “Use an MCLAG+ ring only where supported” when trying to provide an appropriate redundant path in a ring-like MCLAG topology, not to verify “Deploy a two-tier FortiSwitch hierarchy” at the hospital wing. Checking “Deploy a two-tier FortiSwitch hierarchy” at the hospital wing requires evidence of its own mechanism: one switch tier aggregates downstream access units via ISLs or supported trunks; that is not the outcome measured by “Use an MCLAG+ ring only where supported”.
E:The proposed check concerns “Cascade access switches through an upstream managed switch” rather than “Deploy a two-tier FortiSwitch hierarchy”: downstream FortiSwitch units join through supported inter-switch links to the first unit. For “Deploy a two-tier FortiSwitch hierarchy” on a managed switch running FortiSwitchOS 7.6, a better test would be to verify which tier holds the FortiGate uplink and which links serve access switches, which targets separate distribution and access functions while keeping central FortiLink management rather than the alternative diagnostic “Cascade access switches through an upstream managed switch”.
Question 340
A deployment review at the training center identifies this objective: avoid a single distribution-chassis failure stopping attached access switches. Which FortiSwitch operation should be selected?
- Deploy an MCLAG distribution peer pair
- Deploy a full-mesh HA FortiLink architecture
- Use a supported static ISL for a specialized topology
- Select in-band management for a routed FortiSwitch island
Explanation
Correct Answer
A:The relevant mechanism is: peer switches cooperate as one logical aggregation endpoint for dual-homed downstream trunks. The operator can test this claim by the specific check: check peer and ICL health and validate data forwarding when one peer is isolated.
Incorrect Answers
B:Compared with the requested “Deploy an MCLAG distribution peer pair” at the training center, this would avoid loss of one FortiGate connection causing loss of switch access instead: supported fully meshed wiring attaches the FortiGate cluster redundantly to the appropriate switch layer. At the training center, the operational proof would instead be to check peer and ICL health and validate data forwarding when one peer is isolated, whereas “Deploy a full-mesh HA FortiLink architecture” is validated by a different test: follow physical uplink inventory and test each HA member's controller reachability.
C:For the training center, “Use a supported static ISL for a specialized topology” is a different type of control from “Deploy an MCLAG distribution peer pair”: a static ISL defines the inter-switch path and can carry manually controlled VLAN settings. Unlike the requested feature, that setting addresses the need to control uplink behavior where automatic ISL discovery is not the intended configuration, not the objective to avoid a single distribution-chassis failure stopping attached access switches.
D:Compared with the requested “Deploy an MCLAG distribution peer pair” at the training center, this would use a switch's internal interface to carry routed FortiLink control traffic instead: in-band L3 management uses the FortiSwitch internal management interface for the controller path. At the training center, the operational proof would instead be to check peer and ICL health and validate data forwarding when one peer is isolated, whereas “Select in-band management for a routed FortiSwitch island” is validated by a different test: verify the internal interface IP and routed connectivity to the controller.