Fortinet NSE5_FSW_AD-7.6 (Fortinet NSE 5 - FortiSwitch 7.6 Administrator) Practice Test 36

Question 350

A switch change for the lab consists of this step: use a fully meshed connection between adjacent MCLAG tiers. Which behavior reflects the purpose of that change?

  1. Cross-tier links reach both peers in the upper tier rather than funneling all traffic through one unit
  2. A server LACP trunk can span the two MCLAG peers while presenting one logical aggregate
  3. FortiLink-over-L3 provides a management path, not a continuous VLAN data-plane extension
  4. Point-to-point L2 transit preserves required FortiLink discovery and management frames across the middle network
  5. A single FortiLink connection allows the FortiGate to manage the directly attached switch

Explanation

Correct Answer

A:

For the stated requirement, the configured operation is meant to maintain upstream connectivity when one higher-tier switch or link fails. The most relevant validation is to trace every lower-tier peer's uplinks to both upper-tier devices for the equipment at the lab.

Incorrect Answers

B:

That behavior applies when engineers “Prefer a dual-homed server MCLAG attachment”; the different operation “Use a fully meshed connection between adjacent MCLAG tiers” is intended to maintain upstream connectivity when one higher-tier switch or link fails. That different feature is verified by inspect server bond partner details and both peer switch trunk memberships; for “Use a fully meshed connection between adjacent MCLAG tiers” on a carefully segmented Layer 2 network, the relevant evidence is to trace every lower-tier peer's uplinks to both upper-tier devices.

C:

This outcome would be relevant to “Avoid stretching production VLANs across Layer 3 FortiLink” at the lab, not the task “Use a fully meshed connection between adjacent MCLAG tiers”; the other task is to keep remote switch islands from assuming a shared Layer 2 segment across an IP network. The action “Use a fully meshed connection between adjacent MCLAG tiers” targets a different result: cross-tier links reach both peers in the upper tier rather than funneling all traffic through one unit; the proposed alternative would instead be checked by trace the VLAN boundary and verify routing rather than a nonexistent L2 stretch.

D:

That behavior applies when engineers “Use FortiLink over a point-to-point Layer 2 transit”; the different operation “Use a fully meshed connection between adjacent MCLAG tiers” is intended to maintain upstream connectivity when one higher-tier switch or link fails. That different feature is verified by capture FortiLink control traffic at both ends of the Layer 2 segment; for “Use a fully meshed connection between adjacent MCLAG tiers” on a carefully segmented Layer 2 network, the relevant evidence is to trace every lower-tier peer's uplinks to both upper-tier devices.

E:

That behavior applies when engineers “Use direct one-to-one FortiGate-to-FortiSwitch wiring”; the different operation “Use a fully meshed connection between adjacent MCLAG tiers” is intended to maintain upstream connectivity when one higher-tier switch or link fails. That different feature is verified by inspect FortiLink status and the one-switch topology after startup; for “Use a fully meshed connection between adjacent MCLAG tiers” on a carefully segmented Layer 2 network, the relevant evidence is to trace every lower-tier peer's uplinks to both upper-tier devices.

Question 351

A post-change review at the staging rack must validate the implementation of “Use a fully meshed connection between adjacent MCLAG tiers.” What should the reviewer inspect first?

  1. Monitor first-tier peer synchronization and FortiLink reachability after failover
  2. Trace every lower-tier peer's uplinks to both upper-tier devices
  3. Inspect static-ISL status and the intended allowed VLAN configuration
  4. Perform a controlled HA role change and verify the switch remains centrally managed

Explanation

Correct Answer

B:

The deciding detail is that cross-tier links reach both peers in the upper tier rather than funneling all traffic through one unit. Directly measuring that result demonstrates whether the step to maintain upstream connectivity when one higher-tier switch or link fails succeeded on a central switching stack.

Incorrect Answers

A:

The proposed check concerns “Provide first-tier MCLAG before downstream redundancy” rather than “Use a fully meshed connection between adjacent MCLAG tiers”: first-tier peers act as a redundant upstream anchor for downstream distribution or access switches. For “Use a fully meshed connection between adjacent MCLAG tiers” on a central switching stack, a better test would be to trace every lower-tier peer's uplinks to both upper-tier devices, which targets maintain upstream connectivity when one higher-tier switch or link fails rather than the alternative diagnostic “Provide first-tier MCLAG before downstream redundancy”.

C:

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 “Use a fully meshed connection between adjacent MCLAG tiers” at the staging rack. Checking “Use a fully meshed connection between adjacent MCLAG tiers” at the staging rack requires evidence of its own mechanism: cross-tier links reach both peers in the upper tier rather than funneling all traffic through one unit; that is not the outcome measured by “Use a supported static ISL for a specialized topology”.

D:

This check is suited to “Use an HA FortiGate pair to manage an access switch” when trying to retain controller availability across a firewall failover, not to verify “Use a fully meshed connection between adjacent MCLAG tiers” at the staging rack. Checking “Use a fully meshed connection between adjacent MCLAG tiers” at the staging rack requires evidence of its own mechanism: cross-tier links reach both peers in the upper tier rather than funneling all traffic through one unit; that is not the outcome measured by “Use an HA FortiGate pair to manage an access switch”.

Question 352

An administrator responsible for a switch used by multiple office teams in the research building must extend resilient aggregation through core, distribution and access levels. Which configuration best matches that precise goal?

  1. Design a three-tier MCLAG hierarchy
  2. Use VLAN pruning on ISL trunks
  3. Select out-of-band management for a routed island
  4. Configure a FortiLink split interface where the topology requires it

Explanation

Correct Answer

A:

The relevant mechanism is: supported tiered MCLAG topologies permit multi-layer redundancy with active member links. The operator can test this claim by the specific check: audit per-tier peer groups and the full three-layer physical uplink map.

Incorrect Answers

B:

For the research building, “Use VLAN pruning on ISL trunks” is a different type of control from “Design a three-tier MCLAG hierarchy”: 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 extend resilient aggregation through core, distribution and access levels.

C:

Compared with the requested “Design a three-tier MCLAG hierarchy” at the research building, 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 research building, the operational proof would instead be to audit per-tier peer groups and the full three-layer physical uplink map, 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.

D:

Compared with the requested “Design a three-tier MCLAG hierarchy” at the research building, 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 research building, the operational proof would instead be to audit per-tier peer groups and the full three-layer physical uplink map, 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 353

The operator has decided to design a three-tier MCLAG hierarchy on a production FortiSwitch fabric at the airport office. Which operational behavior is the most reasonable expectation of that specific feature?

  1. Supported tiered MCLAG topologies permit multi-layer redundancy with active member links
  2. Dual-homed LACP membership uses links toward each peer instead of relying on one parent chassis
  3. A server LACP trunk can span the two MCLAG peers while presenting one logical aggregate
  4. A single FortiLink connection allows the FortiGate to manage the directly attached switch
  5. FortiLink-over-L3 provides a management path, not a continuous VLAN data-plane extension

Explanation

Correct Answer

A:

This approach fits because the configured operation is meant to extend resilient aggregation through core, distribution and access levels. The most relevant validation is to audit per-tier peer groups and the full three-layer physical uplink map for the equipment at the airport office.

Incorrect Answers

B:

That behavior applies when engineers “Attach an access switch to both MCLAG peers”; the different operation “Design a three-tier MCLAG hierarchy” is intended to extend resilient aggregation through core, distribution and access levels. That different feature is verified by inspect both active LACP members and observe service through a peer maintenance window; for “Design a three-tier MCLAG hierarchy” on a production FortiSwitch fabric, the relevant evidence is to audit per-tier peer groups and the full three-layer physical uplink map.

C:

This outcome would be relevant to “Prefer a dual-homed server MCLAG attachment” at the airport office, not the task “Design a three-tier MCLAG hierarchy”; the other task is to maintain server connectivity when one FortiSwitch peer fails. The action “Design a three-tier MCLAG hierarchy” targets a different result: supported tiered MCLAG topologies permit multi-layer redundancy with active member links; the proposed alternative would instead be checked by inspect server bond partner details and both peer switch trunk memberships.

D:

That behavior applies when engineers “Use direct one-to-one FortiGate-to-FortiSwitch wiring”; the different operation “Design a three-tier MCLAG hierarchy” is intended to extend resilient aggregation through core, distribution and access levels. That different feature is verified by inspect FortiLink status and the one-switch topology after startup; for “Design a three-tier MCLAG hierarchy” on a production FortiSwitch fabric, the relevant evidence is to audit per-tier peer groups and the full three-layer physical uplink map.

E:

That behavior applies when engineers “Avoid stretching production VLANs across Layer 3 FortiLink”; the different operation “Design a three-tier MCLAG hierarchy” is intended to extend resilient aggregation through core, distribution and access levels. That different feature is verified by trace the VLAN boundary and verify routing rather than a nonexistent L2 stretch; for “Design a three-tier MCLAG hierarchy” on a production FortiSwitch fabric, the relevant evidence is to audit per-tier peer groups and the full three-layer physical uplink map.

Question 354

An auditor wants operational evidence for the switch action “Design a three-tier MCLAG hierarchy” at the operations center. Which check is relevant?

  1. Perform a controlled HA role change and verify the switch remains centrally managed
  2. Monitor first-tier peer synchronization and FortiLink reachability after failover
  3. Trace every lower-tier peer's uplinks to both upper-tier devices
  4. Audit per-tier peer groups and the full three-layer physical uplink map

Explanation

Correct Answer

D:

The critical distinction is that supported tiered MCLAG topologies permit multi-layer redundancy with active member links. Directly measuring that result demonstrates whether the step to extend resilient aggregation through core, distribution and access levels succeeded on a newly racked distribution unit.

Incorrect Answers

A:

The proposed check concerns “Use an HA FortiGate pair to manage an access switch” rather than “Design a three-tier MCLAG hierarchy”: the FortiGate HA cluster presents the management service while the switch wiring follows a supported HA topology. For “Design a three-tier MCLAG hierarchy” on a newly racked distribution unit, a better test would be to audit per-tier peer groups and the full three-layer physical uplink map, which targets extend resilient aggregation through core, distribution and access levels rather than the alternative diagnostic “Use an HA FortiGate pair to manage an access switch”.

B:

This check is suited to “Provide first-tier MCLAG before downstream redundancy” when trying to protect the switch pair closest to the FortiGate from a single chassis outage, not to verify “Design a three-tier MCLAG hierarchy” at the operations center. Checking “Design a three-tier MCLAG hierarchy” at the operations center requires evidence of its own mechanism: supported tiered MCLAG topologies permit multi-layer redundancy with active member links; that is not the outcome measured by “Provide first-tier MCLAG before downstream redundancy”.

C:

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 “Design a three-tier MCLAG hierarchy” at the operations center. Checking “Design a three-tier MCLAG hierarchy” at the operations center requires evidence of its own mechanism: supported tiered MCLAG topologies permit multi-layer redundancy with active member links; that is not the outcome measured by “Use a fully meshed connection between adjacent MCLAG tiers”.

Question 355

A peer review of the warehouse asks how the design will use separate switching infrastructure for different security-edge functions. Which FortiSwitch technique is the correct response?

  1. Use FortiLink VLAN optimization where appropriate
  2. Deploy an MCLAG distribution peer pair
  3. Keep independent LAN and WAN FortiLink stacks
  4. Use redundant uplinks rather than a single-chain design for critical endpoints

Explanation

Correct Answer

C:

That setting is appropriate here because separate FortiLink interfaces manage separate VLAN and switch groups for LAN and WAN roles. This distinction is material to the warehouse, where the stated goal is to use separate switching infrastructure for different security-edge functions.

Incorrect Answers

A:

Compared with the requested “Keep independent LAN and WAN FortiLink stacks” at the warehouse, this would reduce unnecessary VLAN configuration work on managed inter-switch connections instead: optimization restricts or adjusts VLAN distribution to reduce superfluous trunk state. At the warehouse, the operational proof would instead be to confirm each stack's FortiLink interface and that units do not cross the wrong stack, whereas “Use FortiLink VLAN optimization where appropriate” is validated by a different test: compare the effective ISL VLAN list with the downstream topology requirements.

B:

For the warehouse, “Deploy an MCLAG distribution peer pair” is a different type of control from “Keep independent LAN and WAN FortiLink stacks”: 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 use separate switching infrastructure for different security-edge functions.

D:

Compared with the requested “Keep independent LAN and WAN FortiLink stacks” 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 confirm each stack's FortiLink interface and that units do not cross the wrong stack, 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 356

A switch change for the headquarters consists of this step: keep independent LAN and WAN FortiLink stacks. Which behavior reflects the purpose of that change?

  1. The supported aggregate topology can require split-interface disabled so member links form the intended logical trunk
  2. An interchassis link with multiple members avoids making one cable the sole MCLAG coordination path
  3. Separate FortiLink interfaces manage separate VLAN and switch groups for LAN and WAN roles
  4. Downstream FortiSwitch units join through supported inter-switch links to the first unit

Explanation

Correct Answer

C:

This is the precise control because the configured operation is meant to use separate switching infrastructure for different security-edge functions. The most relevant validation is to confirm each stack's FortiLink interface and that units do not cross the wrong stack for the equipment at the headquarters.

Incorrect Answers

A:

That behavior applies when engineers “Disable split-interface for a same-switch LAG when required”; the different operation “Keep independent LAN and WAN FortiLink stacks” is intended to use separate switching infrastructure for different security-edge functions. That different feature is verified by check both physical member terminations and the FortiGate aggregate configuration; for “Keep independent LAN and WAN FortiLink stacks” on a staging FortiSwitch, the relevant evidence is to confirm each stack's FortiLink interface and that units do not cross the wrong stack.

B:

This outcome would be relevant to “Build a redundant ICL between peers” at the headquarters, not the task “Keep independent LAN and WAN FortiLink stacks”; the other task is to retain peer-state exchange if one physical interchassis cable fails. The action “Keep independent LAN and WAN FortiLink stacks” targets a different result: separate FortiLink interfaces manage separate VLAN and switch groups for LAN and WAN roles; the proposed alternative would instead be checked by inspect all ICL member interfaces and test a single-cable failure.

D:

That behavior applies when engineers “Cascade access switches through an upstream managed switch”; the different operation “Keep independent LAN and WAN FortiLink stacks” is intended to use separate switching infrastructure for different security-edge functions. That different feature is verified by inspect child-switch discovery and the parent ISL forwarding state; for “Keep independent LAN and WAN FortiLink stacks” on a staging FortiSwitch, the relevant evidence is to confirm each stack's FortiLink interface and that units do not cross the wrong stack.

Question 357

A technician says “Keep independent LAN and WAN FortiLink stacks” has solved the issue at the hospital wing. Which diagnostic step would substantiate that claim?

  1. Test IP routing and controller communication between the remote switch and FortiGate
  2. Confirm each stack's FortiLink interface and that units do not cross the wrong stack
  3. Audit per-tier peer groups and the full three-layer physical uplink map
  4. Verify documented peer links and spanning-tree/MCLAG status for the complete ring
  5. Check controller association of each switch serial in the island

Explanation

Correct Answer

B:

The implementation works because separate FortiLink interfaces manage separate VLAN and switch groups for LAN and WAN roles. Directly measuring that result demonstrates whether the step to use separate switching infrastructure for different security-edge functions succeeded on a carefully segmented Layer 2 network.

Incorrect Answers

A:

The proposed check concerns “Use routed Layer 3 FortiLink for a remote island” rather than “Keep independent LAN and WAN FortiLink stacks”: l3 FortiLink requires reachable management addressing instead of a continuous Layer 2 switch-controller path. For “Keep independent LAN and WAN FortiLink stacks” on a carefully segmented Layer 2 network, a better test would be to confirm each stack's FortiLink interface and that units do not cross the wrong stack, which targets use separate switching infrastructure for different security-edge functions rather than the alternative diagnostic “Use routed Layer 3 FortiLink for a remote island”.

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 “Keep independent LAN and WAN FortiLink stacks” at the hospital wing. Checking “Keep independent LAN and WAN FortiLink stacks” at the hospital wing requires evidence of its own mechanism: separate FortiLink interfaces manage separate VLAN and switch groups for LAN and WAN roles; that is not the outcome measured by “Design a three-tier MCLAG hierarchy”.

D:

The proposed check concerns “Use an MCLAG+ ring only where supported” rather than “Keep independent LAN and WAN FortiLink stacks”: the ring variant requires supported peer and inter-switch arrangements rather than uncontrolled Ethernet loops. For “Keep independent LAN and WAN FortiLink stacks” on a carefully segmented Layer 2 network, a better test would be to confirm each stack's FortiLink interface and that units do not cross the wrong stack, which targets use separate switching infrastructure for different security-edge functions rather than the alternative diagnostic “Use an MCLAG+ ring only where supported”.

E:

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 “Keep independent LAN and WAN FortiLink stacks” at the hospital wing. Checking “Keep independent LAN and WAN FortiLink stacks” at the hospital wing requires evidence of its own mechanism: separate FortiLink interfaces manage separate VLAN and switch groups for LAN and WAN roles; that is not the outcome measured by “Keep a routed island on one controlling FortiGate”.

Question 358

A production incident in the training center reveals the need to avoid loss of one FortiGate connection causing loss of switch access. Which targeted FortiSwitch setting or method should the team use?

  1. Use FortiLink VLAN optimization where appropriate
  2. Deploy a full-mesh HA FortiLink architecture
  3. Deploy an MCLAG distribution peer pair
  4. Use redundant uplinks rather than a single-chain design for critical endpoints

Explanation

Correct Answer

B:

Given the described goal, supported fully meshed wiring attaches the FortiGate cluster redundantly to the appropriate switch layer. The operator can test this claim by the specific check: follow physical uplink inventory and test each HA member's controller reachability.

Incorrect Answers

A:

Compared with the requested “Deploy a full-mesh HA FortiLink architecture” at the training center, this would reduce unnecessary VLAN configuration work on managed inter-switch connections instead: optimization restricts or adjusts VLAN distribution to reduce superfluous trunk state. At the training center, the operational proof would instead be to follow physical uplink inventory and test each HA member's controller reachability, whereas “Use FortiLink VLAN optimization where appropriate” is validated by a different test: compare the effective ISL VLAN list with the downstream topology requirements.

C:

For the training center, “Deploy an MCLAG distribution peer pair” is a different type of control from “Deploy a full-mesh HA FortiLink architecture”: 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 avoid loss of one FortiGate connection causing loss of switch access.

D:

Compared with the requested “Deploy a full-mesh HA FortiLink architecture” at the training center, 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 training center, the operational proof would instead be to follow physical uplink inventory and test each HA member's controller reachability, 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 359

For the lab, an administrator applies the action “Deploy a full-mesh HA FortiLink architecture.” Which effect should appear when it operates as intended?

  1. An interchassis link with multiple members avoids making one cable the sole MCLAG coordination path
  2. Downstream FortiSwitch units join through supported inter-switch links to the first unit
  3. The supported aggregate topology can require split-interface disabled so member links form the intended logical trunk
  4. Supported fully meshed wiring attaches the FortiGate cluster redundantly to the appropriate switch layer

Explanation

Correct Answer

D:

The switch behavior that matters is: the configured operation is meant to avoid loss of one FortiGate connection causing loss of switch access. The most relevant validation is to follow physical uplink inventory and test each HA member's controller reachability for the equipment at the lab.

Incorrect Answers

A:

This outcome would be relevant to “Build a redundant ICL between peers” at the lab, not the task “Deploy a full-mesh HA FortiLink architecture”; the other task is to retain peer-state exchange if one physical interchassis cable fails. The action “Deploy a full-mesh HA FortiLink architecture” targets a different result: supported fully meshed wiring attaches the FortiGate cluster redundantly to the appropriate switch layer; the proposed alternative would instead be checked by inspect all ICL member interfaces and test a single-cable failure.

B:

That behavior applies when engineers “Cascade access switches through an upstream managed switch”; the different operation “Deploy a full-mesh HA FortiLink architecture” is intended to avoid loss of one FortiGate connection causing loss of switch access. That different feature is verified by inspect child-switch discovery and the parent ISL forwarding state; for “Deploy a full-mesh HA FortiLink architecture” on a FortiSwitch connected to the security edge, the relevant evidence is to follow physical uplink inventory and test each HA member's controller reachability.

C:

That behavior applies when engineers “Disable split-interface for a same-switch LAG when required”; the different operation “Deploy a full-mesh HA FortiLink architecture” is intended to avoid loss of one FortiGate connection causing loss of switch access. That different feature is verified by check both physical member terminations and the FortiGate aggregate configuration; for “Deploy a full-mesh HA FortiLink architecture” on a FortiSwitch connected to the security edge, the relevant evidence is to follow physical uplink inventory and test each HA member's controller reachability.

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?

  1. Test IP routing and controller communication between the remote switch and FortiGate
  2. Audit per-tier peer groups and the full three-layer physical uplink map
  3. Check controller association of each switch serial in the island
  4. 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”.

Fortinet NSE 5 - FortiSwitch 7.6 Administrator (NSE5_FSW_AD-7.6) Practice Tests