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

Question 370

A network architect documents a single goal for a FortiLink-managed access switch: centrally manage switches separated from FortiGate by an IP-routed network. Which listed procedure provides that capability?

  1. Disable split-interface for a same-switch LAG when required
  2. Use an HA FortiGate pair to manage an access switch
  3. Use a fully meshed connection between adjacent MCLAG tiers
  4. Use routed Layer 3 FortiLink for a remote island

Explanation

Correct Answer

D:

Given the described goal, l3 FortiLink requires reachable management addressing instead of a continuous Layer 2 switch-controller path. The operator can test this claim by the specific check: test IP routing and controller communication between the remote switch and FortiGate.

Incorrect Answers

A:

For the retail site, “Disable split-interface for a same-switch LAG when required” is a different type of control from “Use routed Layer 3 FortiLink for a remote island”: the supported aggregate topology can require split-interface disabled so member links form the intended logical trunk. Unlike the requested feature, that setting addresses the need to operate a FortiLink aggregate whose physical members all terminate on one FortiSwitch, not the objective to centrally manage switches separated from FortiGate by an IP-routed network.

B:

Compared with the requested “Use routed Layer 3 FortiLink for a remote island” at the retail site, this would retain controller availability across a firewall failover instead: the FortiGate HA cluster presents the management service while the switch wiring follows a supported HA topology. At the retail site, the operational proof would instead be to test IP routing and controller communication between the remote switch and FortiGate, whereas “Use an HA FortiGate pair to manage an access switch” is validated by a different test: perform a controlled HA role change and verify the switch remains centrally managed.

C:

Compared with the requested “Use routed Layer 3 FortiLink for a remote island” at the retail site, this would maintain upstream connectivity when one higher-tier switch or link fails instead: cross-tier links reach both peers in the upper tier rather than funneling all traffic through one unit. At the retail site, the operational proof would instead be to test IP routing and controller communication between the remote switch and FortiGate, whereas “Use a fully meshed connection between adjacent MCLAG tiers” is validated by a different test: trace every lower-tier peer's uplinks to both upper-tier devices.

Question 371

For the airport office, an administrator applies the action “Use routed Layer 3 FortiLink for a remote island.” Which effect should appear when it operates as intended?

  1. In-band L3 management uses the FortiSwitch internal management interface for the controller path
  2. L3 FortiLink requires reachable management addressing instead of a continuous Layer 2 switch-controller path
  3. A static ISL defines the inter-switch path and can carry manually controlled VLAN settings
  4. Separate FortiLink interfaces manage separate VLAN and switch groups for LAN and WAN roles

Explanation

Correct Answer

B:

The switch behavior that matters is: the configured operation is meant to centrally manage switches separated from FortiGate by an IP-routed network. The most relevant validation is to test IP routing and controller communication between the remote switch and FortiGate for the equipment at the airport office.

Incorrect Answers

A:

This outcome would be relevant to “Select in-band management for a routed FortiSwitch island” at the airport office, not the task “Use routed Layer 3 FortiLink for a remote island”; the other task is to use a switch's internal interface to carry routed FortiLink control traffic. The action “Use routed Layer 3 FortiLink for a remote island” targets a different result: l3 FortiLink requires reachable management addressing instead of a continuous Layer 2 switch-controller path; the proposed alternative would instead be checked by verify the internal interface IP and routed connectivity to the controller.

C:

That behavior applies when engineers “Use a supported static ISL for a specialized topology”; the different operation “Use routed Layer 3 FortiLink for a remote island” is intended to centrally manage switches separated from FortiGate by an IP-routed network. That different feature is verified by inspect static-ISL status and the intended allowed VLAN configuration; for “Use routed Layer 3 FortiLink for a remote island” on a switch linked to a FortiGate running FortiOS 7.6, the relevant evidence is to test IP routing and controller communication between the remote switch and FortiGate.

D:

That behavior applies when engineers “Keep independent LAN and WAN FortiLink stacks”; the different operation “Use routed Layer 3 FortiLink for a remote island” is intended to centrally manage switches separated from FortiGate by an IP-routed network. That different feature is verified by confirm each stack's FortiLink interface and that units do not cross the wrong stack; for “Use routed Layer 3 FortiLink for a remote island” on a switch linked to a FortiGate running FortiOS 7.6, the relevant evidence is to test IP routing and controller communication between the remote switch and FortiGate.

Question 372

On a switch serving a high-density endpoint area at the operations center, the team reports that it has configured “Use routed Layer 3 FortiLink for a remote island.” Which verification provides the strongest direct evidence that the intended function is working?

  1. Test IP routing and controller communication between the remote switch and FortiGate
  2. Perform a parent-switch outage test and observe remaining access-layer connectivity
  3. Compare end-to-end source and destination addressing and remove an intervening NAT rule
  4. Check peer and ICL health and validate data forwarding when one peer is isolated
  5. Compare the effective ISL VLAN list with the downstream topology requirements

Explanation

Correct Answer

A:

At this network boundary, l3 FortiLink requires reachable management addressing instead of a continuous Layer 2 switch-controller path. Directly measuring that result demonstrates whether the step to centrally manage switches separated from FortiGate by an IP-routed network succeeded on a switch serving a high-density endpoint area.

Incorrect Answers

B:

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 “Use routed Layer 3 FortiLink for a remote island” at the operations center. Checking “Use routed Layer 3 FortiLink for a remote island” at the operations center requires evidence of its own mechanism: l3 FortiLink requires reachable management addressing instead of a continuous Layer 2 switch-controller path; that is not the outcome measured by “Use redundant uplinks rather than a single-chain design for critical endpoints”.

C:

This check is suited to “Avoid NAT between routed FortiLink island and FortiGate” when trying to preserve a supported L3 FortiLink controller communication path, not to verify “Use routed Layer 3 FortiLink for a remote island” at the operations center. Checking “Use routed Layer 3 FortiLink for a remote island” at the operations center requires evidence of its own mechanism: l3 FortiLink requires reachable management addressing instead of a continuous Layer 2 switch-controller path; that is not the outcome measured by “Avoid NAT between routed FortiLink island and FortiGate”.

D:

The proposed check concerns “Deploy an MCLAG distribution peer pair” rather than “Use routed Layer 3 FortiLink for a remote island”: peer switches cooperate as one logical aggregation endpoint for dual-homed downstream trunks. For “Use routed Layer 3 FortiLink for a remote island” on a switch serving a high-density endpoint area, a better test would be to test IP routing and controller communication between the remote switch and FortiGate, which targets centrally manage switches separated from FortiGate by an IP-routed network rather than the alternative diagnostic “Deploy an MCLAG distribution peer pair”.

E:

The proposed check concerns “Use FortiLink VLAN optimization where appropriate” rather than “Use routed Layer 3 FortiLink for a remote island”: optimization restricts or adjusts VLAN distribution to reduce superfluous trunk state. For “Use routed Layer 3 FortiLink for a remote island” on a switch serving a high-density endpoint area, a better test would be to test IP routing and controller communication between the remote switch and FortiGate, which targets centrally manage switches separated from FortiGate by an IP-routed network rather than the alternative diagnostic “Use FortiLink VLAN optimization where appropriate”.

Question 373

At the warehouse, a technician is choosing between several switching features to use a switch's internal interface to carry routed FortiLink control traffic. Which one belongs in the implementation plan?

  1. Disable split-interface for a same-switch LAG when required
  2. Avoid stretching production VLANs across Layer 3 FortiLink
  3. Select in-band management for a routed FortiSwitch island
  4. Prefer a dual-homed server MCLAG attachment

Explanation

Correct Answer

C:

In this deployment, in-band L3 management uses the FortiSwitch internal management interface for the controller path. This distinction is material to the warehouse, where the stated goal is to use a switch's internal interface to carry routed FortiLink control traffic.

Incorrect Answers

A:

Compared with the requested “Select in-band management for a routed FortiSwitch island” at the warehouse, this would operate a FortiLink aggregate whose physical members all terminate on one FortiSwitch instead: the supported aggregate topology can require split-interface disabled so member links form the intended logical trunk. At the warehouse, the operational proof would instead be to verify the internal interface IP and routed connectivity to the controller, whereas “Disable split-interface for a same-switch LAG when required” is validated by a different test: check both physical member terminations and the FortiGate aggregate configuration.

B:

Compared with the requested “Select in-band management for a routed FortiSwitch island” at the warehouse, 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 warehouse, the operational proof would instead be to verify the internal interface IP and routed connectivity to the controller, whereas “Avoid stretching production VLANs across Layer 3 FortiLink” is validated by a different test: trace the VLAN boundary and verify routing rather than a nonexistent L2 stretch.

D:

For the warehouse, “Prefer a dual-homed server MCLAG attachment” is a different type of control from “Select in-band management for a routed FortiSwitch island”: a server LACP trunk can span the two MCLAG peers while presenting one logical aggregate. Unlike the requested feature, that setting addresses the need to maintain server connectivity when one FortiSwitch peer fails, not the objective to use a switch's internal interface to carry routed FortiLink control traffic.

Question 374

On a remote FortiSwitch installation, “Select in-band management for a routed FortiSwitch island” is configured for the remote depot. What effect should an administrator expect without assuming unrelated features are enabled?

  1. A static ISL defines the inter-switch path and can carry manually controlled VLAN settings
  2. The FortiGate HA cluster presents the management service while the switch wiring follows a supported HA topology
  3. In-band L3 management uses the FortiSwitch internal management interface for the controller path
  4. First-tier peers act as a redundant upstream anchor for downstream distribution or access switches

Explanation

Correct Answer

C:

For the stated requirement, the configured operation is meant to use a switch's internal interface to carry routed FortiLink control traffic. The most relevant validation is to verify the internal interface IP and routed connectivity to the controller for the equipment at the remote depot.

Incorrect Answers

A:

That behavior applies when engineers “Use a supported static ISL for a specialized topology”; the different operation “Select in-band management for a routed FortiSwitch island” is intended to use a switch's internal interface to carry routed FortiLink control traffic. That different feature is verified by inspect static-ISL status and the intended allowed VLAN configuration; for “Select in-band management for a routed FortiSwitch island” on a remote FortiSwitch installation, the relevant evidence is to verify the internal interface IP and routed connectivity to the controller.

B:

That behavior applies when engineers “Use an HA FortiGate pair to manage an access switch”; the different operation “Select in-band management for a routed FortiSwitch island” is intended to use a switch's internal interface to carry routed FortiLink control traffic. That different feature is verified by perform a controlled HA role change and verify the switch remains centrally managed; for “Select in-band management for a routed FortiSwitch island” on a remote FortiSwitch installation, the relevant evidence is to verify the internal interface IP and routed connectivity to the controller.

D:

This outcome would be relevant to “Provide first-tier MCLAG before downstream redundancy” at the remote depot, not the task “Select in-band management for a routed FortiSwitch island”; the other task is to protect the switch pair closest to the FortiGate from a single chassis outage. The action “Select in-band management for a routed FortiSwitch island” targets a different result: in-band L3 management uses the FortiSwitch internal management interface for the controller path; the proposed alternative would instead be checked by monitor first-tier peer synchronization and FortiLink reachability after failover.

Question 375

A design review at the branch office discusses “Select in-band management for a routed FortiSwitch island.” Select the TWO characteristics that belong to this feature. (Choose TWO.)

  1. Redundant topology design removes a single parent chassis from the data-plane dependency chain
  2. Verify the internal interface IP and routed connectivity to the controller
  3. Separate FortiLink interfaces manage separate VLAN and switch groups for LAN and WAN roles
  4. Peer switches cooperate as one logical aggregation endpoint for dual-homed downstream trunks
  5. In-band L3 management uses the FortiSwitch internal management interface for the controller path

Explanation

Correct Answers

B:

The stated check directly tests whether the intended function is active at the branch office. It provides evidence about “Select in-band management for a routed FortiSwitch island” beyond ordinary link-up state on an endpoint-facing FortiSwitch port.

E:

The deciding detail is that the described mechanism corresponds to the operation that administrators use to use a switch's internal interface to carry routed FortiLink control traffic. The result should be observable on an endpoint-facing FortiSwitch port.

Incorrect Answers

A:

That characteristic reflects “Use redundant uplinks rather than a single-chain design for critical endpoints” rather than “Select in-band management for a routed FortiSwitch island” at the branch office. Its actual role is to prevent an upstream switch failure disconnecting every switch below it, a different configuration need.

C:

That characteristic reflects “Keep independent LAN and WAN FortiLink stacks” rather than “Select in-band management for a routed FortiSwitch island” at the branch office. Its actual role is to use separate switching infrastructure for different security-edge functions, a different configuration need.

D:

That characteristic reflects “Deploy an MCLAG distribution peer pair” rather than “Select in-band management for a routed FortiSwitch island” at the branch office. Its actual role is to avoid a single distribution-chassis failure stopping attached access switches, a different configuration need.

Question 376

The accepted design for the factory requires the ability to separate switch control traffic onto the management port where supported. Which switch feature is the closest fit?

  1. Select in-band management for a routed FortiSwitch island
  2. Select out-of-band management for a routed island
  3. Deploy a full-mesh HA FortiLink architecture
  4. Attach an access switch to both MCLAG peers

Explanation

Correct Answer

B:

The relevant mechanism is: out-of-band L3 FortiLink uses a dedicated management interface rather than the ordinary data plane. The operator can test this claim by the specific check: test management-port IP connectivity and confirm the correct FortiLink source path.

Incorrect Answers

A:

For the factory, “Select in-band management for a routed FortiSwitch island” is a different type of control from “Select out-of-band management for a routed island”: in-band L3 management uses the FortiSwitch internal management interface for the controller path. Unlike the requested feature, that setting addresses the need to use a switch's internal interface to carry routed FortiLink control traffic, not the objective to separate switch control traffic onto the management port where supported.

C:

Compared with the requested “Select out-of-band management for a routed island” at the factory, 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 factory, the operational proof would instead be to test management-port IP connectivity and confirm the correct FortiLink source path, 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.

D:

Compared with the requested “Select out-of-band management for a routed island” at the factory, 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 factory, the operational proof would instead be to test management-port IP connectivity and confirm the correct FortiLink source path, 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.

Question 377

A change record for a newly commissioned floor switch states “Select out-of-band management for a routed island.” Which description correctly explains what this will accomplish?

  1. The supported aggregate topology can require split-interface disabled so member links form the intended logical trunk
  2. Out-of-band L3 FortiLink uses a dedicated management interface rather than the ordinary data plane
  3. FortiLink-over-L3 provides a management path, not a continuous VLAN data-plane extension
  4. A server LACP trunk can span the two MCLAG peers while presenting one logical aggregate

Explanation

Correct Answer

B:

This approach fits because the configured operation is meant to separate switch control traffic onto the management port where supported. The most relevant validation is to test management-port IP connectivity and confirm the correct FortiLink source path for the equipment at the distribution floor.

Incorrect Answers

A:

That behavior applies when engineers “Disable split-interface for a same-switch LAG when required”; the different operation “Select out-of-band management for a routed island” is intended to separate switch control traffic onto the management port where supported. That different feature is verified by check both physical member terminations and the FortiGate aggregate configuration; for “Select out-of-band management for a routed island” on a newly commissioned floor switch, the relevant evidence is to test management-port IP connectivity and confirm the correct FortiLink source path.

C:

This outcome would be relevant to “Avoid stretching production VLANs across Layer 3 FortiLink” at the distribution floor, not the task “Select out-of-band management for a routed island”; the other task is to keep remote switch islands from assuming a shared Layer 2 segment across an IP network. The action “Select out-of-band management for a routed island” targets a different result: out-of-band L3 FortiLink uses a dedicated management interface rather than the ordinary data plane; 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 “Prefer a dual-homed server MCLAG attachment”; the different operation “Select out-of-band management for a routed island” is intended to separate switch control traffic onto the management port where supported. That different feature is verified by inspect server bond partner details and both peer switch trunk memberships; for “Select out-of-band management for a routed island” on a newly commissioned floor switch, the relevant evidence is to test management-port IP connectivity and confirm the correct FortiLink source path.

Question 378

An auditor wants operational evidence for the switch action “Select out-of-band management for a routed island” at the media studio. Which check is relevant?

  1. Perform a controlled HA role change and verify the switch remains centrally managed
  2. Inspect static-ISL status and the intended allowed VLAN configuration
  3. Test management-port IP connectivity and confirm the correct FortiLink source path
  4. Monitor first-tier peer synchronization and FortiLink reachability after failover

Explanation

Correct Answer

C:

The critical distinction is that out-of-band L3 FortiLink uses a dedicated management interface rather than the ordinary data plane. Directly measuring that result demonstrates whether the step to separate switch control traffic onto the management port where supported succeeded on a switch linked to a FortiGate running FortiOS 7.6.

Incorrect Answers

A:

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 “Select out-of-band management for a routed island” at the media studio. Checking “Select out-of-band management for a routed island” at the media studio requires evidence of its own mechanism: out-of-band L3 FortiLink uses a dedicated management interface rather than the ordinary data plane; that is not the outcome measured by “Use an HA FortiGate pair to manage an access switch”.

B:

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 “Select out-of-band management for a routed island” at the media studio. Checking “Select out-of-band management for a routed island” at the media studio requires evidence of its own mechanism: out-of-band L3 FortiLink uses a dedicated management interface rather than the ordinary data plane; that is not the outcome measured by “Use a supported static ISL for a specialized topology”.

D:

The proposed check concerns “Provide first-tier MCLAG before downstream redundancy” rather than “Select out-of-band management for a routed island”: first-tier peers act as a redundant upstream anchor for downstream distribution or access switches. For “Select out-of-band management for a routed island” on a switch linked to a FortiGate running FortiOS 7.6, a better test would be to test management-port IP connectivity and confirm the correct FortiLink source path, which targets separate switch control traffic onto the management port where supported rather than the alternative diagnostic “Provide first-tier MCLAG before downstream redundancy”.

Question 379

A deployment review at the retail site identifies this objective: preserve a supported L3 FortiLink controller communication path. Which FortiSwitch operation should be selected?

  1. Avoid NAT between routed FortiLink island and FortiGate
  2. Prefer a dual-homed server MCLAG attachment
  3. Disable split-interface for a same-switch LAG when required
  4. Use direct one-to-one FortiGate-to-FortiSwitch wiring
  5. Avoid stretching production VLANs across Layer 3 FortiLink

Explanation

Correct Answer

A:

That setting is appropriate here because Fortinet's L3 FortiLink limitations disallow address translation between the switch and its FortiGate. This distinction is material to the retail site, where the stated goal is to preserve a supported L3 FortiLink controller communication path.

Incorrect Answers

B:

For the retail site, “Prefer a dual-homed server MCLAG attachment” is a different type of control from “Avoid NAT between routed FortiLink island and FortiGate”: a server LACP trunk can span the two MCLAG peers while presenting one logical aggregate. Unlike the requested feature, that setting addresses the need to maintain server connectivity when one FortiSwitch peer fails, not the objective to preserve a supported L3 FortiLink controller communication path.

C:

Compared with the requested “Avoid NAT between routed FortiLink island and FortiGate” at the retail site, this would operate a FortiLink aggregate whose physical members all terminate on one FortiSwitch instead: the supported aggregate topology can require split-interface disabled so member links form the intended logical trunk. At the retail site, the operational proof would instead be to compare end-to-end source and destination addressing and remove an intervening NAT rule, whereas “Disable split-interface for a same-switch LAG when required” is validated by a different test: check both physical member terminations and the FortiGate aggregate configuration.

D:

Compared with the requested “Avoid NAT between routed FortiLink island and FortiGate” at the retail site, this would deploy a small branch with one managed switch and minimal switching complexity instead: a single FortiLink connection allows the FortiGate to manage the directly attached switch. At the retail site, the operational proof would instead be to compare end-to-end source and destination addressing and remove an intervening NAT rule, whereas “Use direct one-to-one FortiGate-to-FortiSwitch wiring” is validated by a different test: inspect FortiLink status and the one-switch topology after startup.

E:

Compared with the requested “Avoid NAT between routed FortiLink island and FortiGate” at the retail site, 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 retail site, the operational proof would instead be to compare end-to-end source and destination addressing and remove an intervening NAT rule, 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.

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.

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