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

Question 380

An operations log records this activity at the airport office: avoid NAT between routed FortiLink island and FortiGate. Which result is specifically attributable to that action?

  1. First-tier peers act as a redundant upstream anchor for downstream distribution or access switches
  2. Fortinet's L3 FortiLink limitations disallow address translation between the switch and its FortiGate
  3. The FortiGate HA cluster presents the management service while the switch wiring follows a supported HA topology
  4. A static ISL defines the inter-switch path and can carry manually controlled VLAN settings

Explanation

Correct Answer

B:

This is the precise control because the configured operation is meant to preserve a supported L3 FortiLink controller communication path. The most relevant validation is to compare end-to-end source and destination addressing and remove an intervening NAT rule for the equipment at the airport office.

Incorrect Answers

A:

This outcome would be relevant to “Provide first-tier MCLAG before downstream redundancy” at the airport office, not the task “Avoid NAT between routed FortiLink island and FortiGate”; the other task is to protect the switch pair closest to the FortiGate from a single chassis outage. The action “Avoid NAT between routed FortiLink island and FortiGate” targets a different result: Fortinet's L3 FortiLink limitations disallow address translation between the switch and its FortiGate; the proposed alternative would instead be checked by monitor first-tier peer synchronization and FortiLink reachability after failover.

C:

That behavior applies when engineers “Use an HA FortiGate pair to manage an access switch”; the different operation “Avoid NAT between routed FortiLink island and FortiGate” is intended to preserve a supported L3 FortiLink controller communication path. That different feature is verified by perform a controlled HA role change and verify the switch remains centrally managed; for “Avoid NAT between routed FortiLink island and FortiGate” on a managed switch running FortiSwitchOS 7.6, the relevant evidence is to compare end-to-end source and destination addressing and remove an intervening NAT rule.

D:

That behavior applies when engineers “Use a supported static ISL for a specialized topology”; the different operation “Avoid NAT between routed FortiLink island and FortiGate” is intended to preserve a supported L3 FortiLink controller communication path. That different feature is verified by inspect static-ISL status and the intended allowed VLAN configuration; for “Avoid NAT between routed FortiLink island and FortiGate” on a managed switch running FortiSwitchOS 7.6, the relevant evidence is to compare end-to-end source and destination addressing and remove an intervening NAT rule.

Question 381

A technician says “Avoid NAT between routed FortiLink island and FortiGate” has solved the issue at the conference venue. Which diagnostic step would substantiate that claim?

  1. Confirm each stack's FortiLink interface and that units do not cross the wrong stack
  2. Compare end-to-end source and destination addressing and remove an intervening NAT rule
  3. Perform a parent-switch outage test and observe remaining access-layer connectivity
  4. Check peer and ICL health and validate data forwarding when one peer is isolated

Explanation

Correct Answer

B:

The implementation works because Fortinet's L3 FortiLink limitations disallow address translation between the switch and its FortiGate. Directly measuring that result demonstrates whether the step to preserve a supported L3 FortiLink controller communication path succeeded on a remote FortiSwitch installation.

Incorrect Answers

A:

This check is suited to “Keep independent LAN and WAN FortiLink stacks” when trying to use separate switching infrastructure for different security-edge functions, not to verify “Avoid NAT between routed FortiLink island and FortiGate” at the conference venue. Checking “Avoid NAT between routed FortiLink island and FortiGate” at the conference venue requires evidence of its own mechanism: Fortinet's L3 FortiLink limitations disallow address translation between the switch and its FortiGate; that is not the outcome measured by “Keep independent LAN and WAN FortiLink stacks”.

C:

This check is suited to “Use redundant uplinks rather than a single-chain design for critical endpoints” when trying to prevent an upstream switch failure disconnecting every switch below it, not to verify “Avoid NAT between routed FortiLink island and FortiGate” at the conference venue. Checking “Avoid NAT between routed FortiLink island and FortiGate” at the conference venue requires evidence of its own mechanism: Fortinet's L3 FortiLink limitations disallow address translation between the switch and its FortiGate; that is not the outcome measured by “Use redundant uplinks rather than a single-chain design for critical endpoints”.

D:

The proposed check concerns “Deploy an MCLAG distribution peer pair” rather than “Avoid NAT between routed FortiLink island and FortiGate”: peer switches cooperate as one logical aggregation endpoint for dual-homed downstream trunks. For “Avoid NAT between routed FortiLink island and FortiGate” on a remote FortiSwitch installation, a better test would be to compare end-to-end source and destination addressing and remove an intervening NAT rule, which targets preserve a supported L3 FortiLink controller communication path rather than the alternative diagnostic “Deploy an MCLAG distribution peer pair”.

Question 382

On an endpoint-facing FortiSwitch port in the campus, the next task is to keep remote switch islands from assuming a shared Layer 2 segment across an IP network. What is the appropriate configuration decision?

  1. Use FortiLink VLAN optimization where appropriate
  2. Select out-of-band management for a routed island
  3. Use redundant uplinks rather than a single-chain design for critical endpoints
  4. Avoid stretching production VLANs across Layer 3 FortiLink

Explanation

Correct Answer

D:

Given the described goal, FortiLink-over-L3 provides a management path, not a continuous VLAN data-plane extension. The operator can test this claim by the specific check: trace the VLAN boundary and verify routing rather than a nonexistent L2 stretch.

Incorrect Answers

A:

Compared with the requested “Avoid stretching production VLANs across Layer 3 FortiLink” at the campus, 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 campus, the operational proof would instead be to trace the VLAN boundary and verify routing rather than a nonexistent L2 stretch, 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:

Compared with the requested “Avoid stretching production VLANs across Layer 3 FortiLink” at the campus, 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 campus, the operational proof would instead be to trace the VLAN boundary and verify routing rather than a nonexistent L2 stretch, 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.

C:

For the campus, “Use redundant uplinks rather than a single-chain design for critical endpoints” is a different type of control from “Avoid stretching production VLANs across Layer 3 FortiLink”: redundant topology design removes a single parent chassis from the data-plane dependency chain. Unlike the requested feature, that setting addresses the need to prevent an upstream switch failure disconnecting every switch below it, not the objective to keep remote switch islands from assuming a shared Layer 2 segment across an IP network.

Question 383

A change record for a standalone FortiSwitch appliance states “Avoid stretching production VLANs across Layer 3 FortiLink.” Which description correctly explains what this will accomplish?

  1. FortiLink-over-L3 provides a management path, not a continuous VLAN data-plane extension
  2. The ring variant requires supported peer and inter-switch arrangements rather than uncontrolled Ethernet loops
  3. Split-interface behavior is topology-dependent and distinct from a conventional active aggregate
  4. Downstream FortiSwitch units join through supported inter-switch links to the first unit
  5. An interchassis link with multiple members avoids making one cable the sole MCLAG coordination path

Explanation

Correct Answer

A:

The switch behavior that matters is: the configured operation is meant to keep remote switch islands from assuming a shared Layer 2 segment across an IP network. The most relevant validation is to trace the VLAN boundary and verify routing rather than a nonexistent L2 stretch for the equipment at the remote depot.

Incorrect Answers

B:

That behavior applies when engineers “Use an MCLAG+ ring only where supported”; the different operation “Avoid stretching production VLANs across Layer 3 FortiLink” is intended to keep remote switch islands from assuming a shared Layer 2 segment across an IP network. That different feature is verified by verify documented peer links and spanning-tree/MCLAG status for the complete ring; for “Avoid stretching production VLANs across Layer 3 FortiLink” on a standalone FortiSwitch appliance, the relevant evidence is to trace the VLAN boundary and verify routing rather than a nonexistent L2 stretch.

C:

That behavior applies when engineers “Configure a FortiLink split interface where the topology requires it”; the different operation “Avoid stretching production VLANs across Layer 3 FortiLink” is intended to keep remote switch islands from assuming a shared Layer 2 segment across an IP network. That different feature is verified by verify split-interface state against which FortiSwitch devices each member connects to; for “Avoid stretching production VLANs across Layer 3 FortiLink” on a standalone FortiSwitch appliance, the relevant evidence is to trace the VLAN boundary and verify routing rather than a nonexistent L2 stretch.

D:

This outcome would be relevant to “Cascade access switches through an upstream managed switch” at the remote depot, not the task “Avoid stretching production VLANs across Layer 3 FortiLink”; the other task is to extend a FortiLink-managed network beyond the number of direct controller ports. The action “Avoid stretching production VLANs across Layer 3 FortiLink” targets a different result: FortiLink-over-L3 provides a management path, not a continuous VLAN data-plane extension; the proposed alternative would instead be checked by inspect child-switch discovery and the parent ISL forwarding state.

E:

That behavior applies when engineers “Build a redundant ICL between peers”; the different operation “Avoid stretching production VLANs across Layer 3 FortiLink” is intended to keep remote switch islands from assuming a shared Layer 2 segment across an IP network. That different feature is verified by inspect all ICL member interfaces and test a single-cable failure; for “Avoid stretching production VLANs across Layer 3 FortiLink” on a standalone FortiSwitch appliance, the relevant evidence is to trace the VLAN boundary and verify routing rather than a nonexistent L2 stretch.

Question 384

After implementing “Avoid stretching production VLANs across Layer 3 FortiLink,” the site engineer needs to assess its actual effect on a newly commissioned floor switch. Which test is the best match?

  1. Trace the VLAN boundary and verify routing rather than a nonexistent L2 stretch
  2. Verify which tier holds the FortiGate uplink and which links serve access switches
  3. Audit per-tier peer groups and the full three-layer physical uplink map
  4. Capture FortiLink control traffic at both ends of the Layer 2 segment

Explanation

Correct Answer

A:

At this network boundary, FortiLink-over-L3 provides a management path, not a continuous VLAN data-plane extension. Directly measuring that result demonstrates whether the step to keep remote switch islands from assuming a shared Layer 2 segment across an IP network succeeded on a newly commissioned floor switch.

Incorrect Answers

B:

This check is suited to “Deploy a two-tier FortiSwitch hierarchy” when trying to separate distribution and access functions while keeping central FortiLink management, not to verify “Avoid stretching production VLANs across Layer 3 FortiLink” at the branch office. Checking “Avoid stretching production VLANs across Layer 3 FortiLink” at the branch office requires evidence of its own mechanism: FortiLink-over-L3 provides a management path, not a continuous VLAN data-plane extension; that is not the outcome measured by “Deploy a two-tier FortiSwitch hierarchy”.

C:

The proposed check concerns “Design a three-tier MCLAG hierarchy” rather than “Avoid stretching production VLANs across Layer 3 FortiLink”: supported tiered MCLAG topologies permit multi-layer redundancy with active member links. For “Avoid stretching production VLANs across Layer 3 FortiLink” on a newly commissioned floor switch, a better test would be to trace the VLAN boundary and verify routing rather than a nonexistent L2 stretch, which targets keep remote switch islands from assuming a shared Layer 2 segment across an IP network rather than the alternative diagnostic “Design a three-tier MCLAG hierarchy”.

D:

This check is suited to “Use FortiLink over a point-to-point Layer 2 transit” when trying to reach a remote switch through a transparent dedicated bridging path, not to verify “Avoid stretching production VLANs across Layer 3 FortiLink” at the branch office. Checking “Avoid stretching production VLANs across Layer 3 FortiLink” at the branch office requires evidence of its own mechanism: FortiLink-over-L3 provides a management path, not a continuous VLAN data-plane extension; that is not the outcome measured by “Use FortiLink over a point-to-point Layer 2 transit”.

Question 385

A production incident in the factory reveals the need to respect FortiLink-over-L3 island controller design limits. Which targeted FortiSwitch setting or method should the team use?

  1. Use FortiLink over a point-to-point Layer 2 transit
  2. Design a three-tier MCLAG hierarchy
  3. Avoid stretching production VLANs across Layer 3 FortiLink
  4. Keep a routed island on one controlling FortiGate

Explanation

Correct Answer

D:

In this deployment, all switches in a single routed FortiSwitch island must be managed by the same FortiGate. This distinction is material to the factory, where the stated goal is to respect FortiLink-over-L3 island controller design limits.

Incorrect Answers

A:

Compared with the requested “Keep a routed island on one controlling FortiGate” at the factory, this would reach a remote switch through a transparent dedicated bridging path instead: point-to-point L2 transit preserves required FortiLink discovery and management frames across the middle network. At the factory, the operational proof would instead be to check controller association of each switch serial in the island, whereas “Use FortiLink over a point-to-point Layer 2 transit” is validated by a different test: capture FortiLink control traffic at both ends of the Layer 2 segment.

B:

Compared with the requested “Keep a routed island on one controlling FortiGate” at the factory, this would extend resilient aggregation through core, distribution and access levels instead: supported tiered MCLAG topologies permit multi-layer redundancy with active member links. At the factory, the operational proof would instead be to check controller association of each switch serial in the island, whereas “Design a three-tier MCLAG hierarchy” is validated by a different test: audit per-tier peer groups and the full three-layer physical uplink map.

C:

For the factory, “Avoid stretching production VLANs across Layer 3 FortiLink” is a different type of control from “Keep a routed island on one controlling FortiGate”: FortiLink-over-L3 provides a management path, not a continuous VLAN data-plane extension. Unlike the requested feature, that setting addresses the need to keep remote switch islands from assuming a shared Layer 2 segment across an IP network, not the objective to respect FortiLink-over-L3 island controller design limits.

Question 386

An operations log records this activity at the distribution floor: keep a routed island on one controlling FortiGate. Which result is specifically attributable to that action?

  1. A lower peer group supplies redundant endpoints for access switches deeper in the design
  2. All switches in a single routed FortiSwitch island must be managed by the same FortiGate
  3. VLAN pruning limits inter-switch VLAN carriage to those actually required along each path
  4. In-band L3 management uses the FortiSwitch internal management interface for the controller path
  5. One switch tier aggregates downstream access units via ISLs or supported trunks

Explanation

Correct Answer

B:

For the stated requirement, the configured operation is meant to respect FortiLink-over-L3 island controller design limits. The most relevant validation is to check controller association of each switch serial in the island for the equipment at the distribution floor.

Incorrect Answers

A:

That behavior applies when engineers “Provide second-tier MCLAG for resilient access aggregation”; the different operation “Keep a routed island on one controlling FortiGate” is intended to respect FortiLink-over-L3 island controller design limits. That different feature is verified by check second-tier ICL and access trunks rather than only first-tier connectivity; for “Keep a routed island on one controlling FortiGate” on a switch used by multiple office teams, the relevant evidence is to check controller association of each switch serial in the island.

C:

This outcome would be relevant to “Use VLAN pruning on ISL trunks” at the distribution floor, not the task “Keep a routed island on one controlling FortiGate”; the other task is to avoid transporting VLAN traffic across parts of the stack with no members. The action “Keep a routed island on one controlling FortiGate” targets a different result: all switches in a single routed FortiSwitch island must be managed by the same FortiGate; the proposed alternative would instead be checked by inspect which VLAN IDs remain active on each intermediate ISL trunk.

D:

That behavior applies when engineers “Select in-band management for a routed FortiSwitch island”; the different operation “Keep a routed island on one controlling FortiGate” is intended to respect FortiLink-over-L3 island controller design limits. That different feature is verified by verify the internal interface IP and routed connectivity to the controller; for “Keep a routed island on one controlling FortiGate” on a switch used by multiple office teams, the relevant evidence is to check controller association of each switch serial in the island.

E:

That behavior applies when engineers “Deploy a two-tier FortiSwitch hierarchy”; the different operation “Keep a routed island on one controlling FortiGate” is intended to respect FortiLink-over-L3 island controller design limits. That different feature is verified by verify which tier holds the FortiGate uplink and which links serve access switches; for “Keep a routed island on one controlling FortiGate” on a switch used by multiple office teams, the relevant evidence is to check controller association of each switch serial in the island.

Question 387

The change-control ticket for a production FortiSwitch fabric requires one validation of the goal to respect FortiLink-over-L3 island controller design limits. Which evidence should be collected?

  1. Inspect server bond partner details and both peer switch trunk memberships
  2. Inspect both active LACP members and observe service through a peer maintenance window
  3. Inspect FortiLink status and the one-switch topology after startup
  4. Check controller association of each switch serial in the island

Explanation

Correct Answer

D:

The deciding detail is that all switches in a single routed FortiSwitch island must be managed by the same FortiGate. Directly measuring that result demonstrates whether the step to respect FortiLink-over-L3 island controller design limits succeeded on a production FortiSwitch fabric.

Incorrect Answers

A:

This check is suited to “Prefer a dual-homed server MCLAG attachment” when trying to maintain server connectivity when one FortiSwitch peer fails, not to verify “Keep a routed island on one controlling FortiGate” at the media studio. Checking “Keep a routed island on one controlling FortiGate” at the media studio requires evidence of its own mechanism: all switches in a single routed FortiSwitch island must be managed by the same FortiGate; that is not the outcome measured by “Prefer a dual-homed server MCLAG attachment”.

B:

This check is suited to “Attach an access switch to both MCLAG peers” when trying to give the access layer two independent upstream hardware paths, not to verify “Keep a routed island on one controlling FortiGate” at the media studio. Checking “Keep a routed island on one controlling FortiGate” at the media studio requires evidence of its own mechanism: all switches in a single routed FortiSwitch island must be managed by the same FortiGate; that is not the outcome measured by “Attach an access switch to both MCLAG peers”.

C:

The proposed check concerns “Use direct one-to-one FortiGate-to-FortiSwitch wiring” rather than “Keep a routed island on one controlling FortiGate”: a single FortiLink connection allows the FortiGate to manage the directly attached switch. For “Keep a routed island on one controlling FortiGate” on a production FortiSwitch fabric, a better test would be to check controller association of each switch serial in the island, which targets respect FortiLink-over-L3 island controller design limits rather than the alternative diagnostic “Use direct one-to-one FortiGate-to-FortiSwitch wiring”.

Question 388

A switch rollout in the data hall will be approved only if it can control uplink behavior where automatic ISL discovery is not the intended configuration. Which administrative action meets this acceptance criterion?

  1. Use FortiLink over a point-to-point Layer 2 transit
  2. Avoid stretching production VLANs across Layer 3 FortiLink
  3. Use an MCLAG+ ring only where supported
  4. Use a supported static ISL for a specialized topology

Explanation

Correct Answer

D:

The relevant mechanism is: a static ISL defines the inter-switch path and can carry manually controlled VLAN settings. The operator can test this claim by the specific check: inspect static-ISL status and the intended allowed VLAN configuration.

Incorrect Answers

A:

Compared with the requested “Use a supported static ISL for a specialized topology” at the data hall, this would reach a remote switch through a transparent dedicated bridging path instead: point-to-point L2 transit preserves required FortiLink discovery and management frames across the middle network. At the data hall, the operational proof would instead be to inspect static-ISL status and the intended allowed VLAN configuration, whereas “Use FortiLink over a point-to-point Layer 2 transit” is validated by a different test: capture FortiLink control traffic at both ends of the Layer 2 segment.

B:

Compared with the requested “Use a supported static ISL for a specialized topology” at the data hall, this would keep remote switch islands from assuming a shared Layer 2 segment across an IP network instead: FortiLink-over-L3 provides a management path, not a continuous VLAN data-plane extension. At the data hall, the operational proof would instead be to inspect static-ISL status and the intended allowed VLAN configuration, whereas “Avoid stretching production VLANs across Layer 3 FortiLink” is validated by a different test: trace the VLAN boundary and verify routing rather than a nonexistent L2 stretch.

C:

For the data hall, “Use an MCLAG+ ring only where supported” is a different type of control from “Use a supported static ISL for a specialized topology”: the ring variant requires supported peer and inter-switch arrangements rather than uncontrolled Ethernet loops. Unlike the requested feature, that setting addresses the need to provide an appropriate redundant path in a ring-like MCLAG topology, not the objective to control uplink behavior where automatic ISL discovery is not the intended configuration.

Question 389

A change record for two distribution switches states “Use a supported static ISL for a specialized topology.” Which description correctly explains what this will accomplish?

  1. VLAN pruning limits inter-switch VLAN carriage to those actually required along each path
  2. A static ISL defines the inter-switch path and can carry manually controlled VLAN settings
  3. One switch tier aggregates downstream access units via ISLs or supported trunks
  4. A lower peer group supplies redundant endpoints for access switches deeper in the design

Explanation

Correct Answer

B:

This approach fits because the configured operation is meant to control uplink behavior where automatic ISL discovery is not the intended configuration. The most relevant validation is to inspect static-ISL status and the intended allowed VLAN configuration for the equipment at the development floor.

Incorrect Answers

A:

That behavior applies when engineers “Use VLAN pruning on ISL trunks”; the different operation “Use a supported static ISL for a specialized topology” is intended to control uplink behavior where automatic ISL discovery is not the intended configuration. That different feature is verified by inspect which VLAN IDs remain active on each intermediate ISL trunk; for “Use a supported static ISL for a specialized topology” on two distribution switches, the relevant evidence is to inspect static-ISL status and the intended allowed VLAN configuration.

C:

That behavior applies when engineers “Deploy a two-tier FortiSwitch hierarchy”; the different operation “Use a supported static ISL for a specialized topology” is intended to control uplink behavior where automatic ISL discovery is not the intended configuration. That different feature is verified by verify which tier holds the FortiGate uplink and which links serve access switches; for “Use a supported static ISL for a specialized topology” on two distribution switches, the relevant evidence is to inspect static-ISL status and the intended allowed VLAN configuration.

D:

This outcome would be relevant to “Provide second-tier MCLAG for resilient access aggregation” at the development floor, not the task “Use a supported static ISL for a specialized topology”; the other task is to protect the next aggregation layer beneath an already redundant core. The action “Use a supported static ISL for a specialized topology” targets a different result: a static ISL defines the inter-switch path and can carry manually controlled VLAN settings; the proposed alternative would instead be checked by check second-tier ICL and access trunks rather than only first-tier connectivity.

Question 390

A FortiSwitch engineer in the conference venue is documenting successful operation of “Use a supported static ISL for a specialized topology.” Which measurement or inspection confirms it?

  1. Verify the internal interface IP and routed connectivity to the controller
  2. Inspect static-ISL status and the intended allowed VLAN configuration
  3. Inspect both active LACP members and observe service through a peer maintenance window
  4. Follow physical uplink inventory and test each HA member's controller reachability
  5. Inspect FortiLink status and the one-switch topology after startup

Explanation

Correct Answer

B:

The critical distinction is that a static ISL defines the inter-switch path and can carry manually controlled VLAN settings. Directly measuring that result demonstrates whether the step to control uplink behavior where automatic ISL discovery is not the intended configuration succeeded on a staging FortiSwitch.

Incorrect Answers

A:

The proposed check concerns “Select in-band management for a routed FortiSwitch island” rather than “Use a supported static ISL for a specialized topology”: in-band L3 management uses the FortiSwitch internal management interface for the controller path. For “Use a supported static ISL for a specialized topology” on a staging FortiSwitch, a better test would be to inspect static-ISL status and the intended allowed VLAN configuration, which targets control uplink behavior where automatic ISL discovery is not the intended configuration rather than the alternative diagnostic “Select in-band management for a routed FortiSwitch island”.

C:

The proposed check concerns “Attach an access switch to both MCLAG peers” rather than “Use a supported static ISL for a specialized topology”: dual-homed LACP membership uses links toward each peer instead of relying on one parent chassis. For “Use a supported static ISL for a specialized topology” on a staging FortiSwitch, a better test would be to inspect static-ISL status and the intended allowed VLAN configuration, which targets control uplink behavior where automatic ISL discovery is not the intended configuration rather than the alternative diagnostic “Attach an access switch to both MCLAG peers”.

D:

This check is suited to “Deploy a full-mesh HA FortiLink architecture” when trying to avoid loss of one FortiGate connection causing loss of switch access, not to verify “Use a supported static ISL for a specialized topology” at the conference venue. Checking “Use a supported static ISL for a specialized topology” at the conference venue requires evidence of its own mechanism: a static ISL defines the inter-switch path and can carry manually controlled VLAN settings; that is not the outcome measured by “Deploy a full-mesh HA FortiLink architecture”.

E:

This check is suited to “Use direct one-to-one FortiGate-to-FortiSwitch wiring” when trying to deploy a small branch with one managed switch and minimal switching complexity, not to verify “Use a supported static ISL for a specialized topology” at the conference venue. Checking “Use a supported static ISL for a specialized topology” at the conference venue requires evidence of its own mechanism: a static ISL defines the inter-switch path and can carry manually controlled VLAN settings; that is not the outcome measured by “Use direct one-to-one FortiGate-to-FortiSwitch wiring”.

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