Question 320
The work order to give authorized operators controlled switch access without depending on an empty local password is marked complete on a managed campus switch. Which observation most directly tests the completed configuration?
- Compare controller-configured port values with device status and sync indicators
- Inspect the restored local settings and confirm there is no controller configuration conflict
- Compare the controller's managed-port settings with the provisioned running state
- Check the collector for test link or authentication events with correct timestamps
- Verify the applied profile and successful login using the assigned administrator credentials
- Observe whether a newly discovered serial number becomes authorized without manual action
Explanation
Correct Answer
E:This is the precise control because FortiGate switch profiles can set managed switch administrative credentials centrally. Directly measuring that result demonstrates whether the step to give authorized operators controlled switch access without depending on an empty local password succeeded on a managed campus switch.
Incorrect Answers
A:The proposed check concerns “Check managed-switch configuration synchronization” rather than “Select a FortiSwitch profile with a managed admin password”: synchronization status identifies divergence between controller intent and provisioned switch state. For “Select a FortiSwitch profile with a managed admin password” on a managed campus switch, a better test would be to verify the applied profile and successful login using the assigned administrator credentials, which targets give authorized operators controlled switch access without depending on an empty local password rather than the alternative diagnostic “Check managed-switch configuration synchronization”.
B:This check is suited to “Restore the saved standalone configuration locally” when trying to recover a locally administered switch after a failed change, not to verify “Select a FortiSwitch profile with a managed admin password” at the conference venue. Checking “Select a FortiSwitch profile with a managed admin password” at the conference venue requires evidence of its own mechanism: FortiGate switch profiles can set managed switch administrative credentials centrally; that is not the outcome measured by “Restore the saved standalone configuration locally”.
C:The proposed check concerns “Apply FortiSwitch port configuration from FortiGate” rather than “Select a FortiSwitch profile with a managed admin password”: FortiGate pushes intended FortiSwitch configuration rather than relying on untracked local edits. For “Select a FortiSwitch profile with a managed admin password” on a managed campus switch, a better test would be to verify the applied profile and successful login using the assigned administrator credentials, which targets give authorized operators controlled switch access without depending on an empty local password rather than the alternative diagnostic “Apply FortiSwitch port configuration from FortiGate”.
D:This check is suited to “Send operational messages to an external syslog collector” when trying to retain switch events outside the device for investigation and retention, not to verify “Select a FortiSwitch profile with a managed admin password” at the conference venue. Checking “Select a FortiSwitch profile with a managed admin password” at the conference venue requires evidence of its own mechanism: FortiGate switch profiles can set managed switch administrative credentials centrally; that is not the outcome measured by “Send operational messages to an external syslog collector”.
F:This check is suited to “Enable automatic FortiSwitch authorization where appropriate” when trying to reduce manual approvals for trusted units on a controlled provisioning network, not to verify “Select a FortiSwitch profile with a managed admin password” at the conference venue. Checking “Select a FortiSwitch profile with a managed admin password” at the conference venue requires evidence of its own mechanism: FortiGate switch profiles can set managed switch administrative credentials centrally; that is not the outcome measured by “Enable automatic FortiSwitch authorization where appropriate”.
Question 321
An administrator responsible for a recently upgraded FortiSwitch in the campus must make discovery consistent with the actual supported port and neighbor behavior. Which configuration best matches that precise goal?
- Enable automatic FortiSwitch authorization where appropriate
- Enable neighbor detection appropriate for the FortiLink deployment
- Select a FortiSwitch profile with a managed admin password
- Apply FortiSwitch port configuration from FortiGate
Explanation
Correct Answer
B:The implementation works because FortiLink discovery uses configured neighbor detection; FortiOS 7.6.1 uses LLDP as its default method. This distinction is material to the campus, where the stated goal is to make discovery consistent with the actual supported port and neighbor behavior.
Incorrect Answers
A:Compared with the requested “Enable neighbor detection appropriate for the FortiLink deployment” at the campus, this would reduce manual approvals for trusted units on a controlled provisioning network instead: the FortiLink controller can authorize discovered devices automatically when that setting is enabled. At the campus, the operational proof would instead be to inspect the neighbor-detection method and observed adjacency in the active FortiLink connection, whereas “Enable automatic FortiSwitch authorization where appropriate” is validated by a different test: observe whether a newly discovered serial number becomes authorized without manual action.
C:Compared with the requested “Enable neighbor detection appropriate for the FortiLink deployment” at the campus, this would give authorized operators controlled switch access without depending on an empty local password instead: FortiGate switch profiles can set managed switch administrative credentials centrally. At the campus, the operational proof would instead be to inspect the neighbor-detection method and observed adjacency in the active FortiLink connection, whereas “Select a FortiSwitch profile with a managed admin password” is validated by a different test: verify the applied profile and successful login using the assigned administrator credentials.
D:For the campus, “Apply FortiSwitch port configuration from FortiGate” is a different type of control from “Enable neighbor detection appropriate for the FortiLink deployment”: FortiGate pushes intended FortiSwitch configuration rather than relying on untracked local edits. Unlike the requested feature, that setting addresses the need to keep managed port and VLAN settings under centralized change control, not the objective to make discovery consistent with the actual supported port and neighbor behavior.
Question 322
When engineers enable neighbor detection appropriate for the FortiLink deployment at the remote depot, which forwarding, security, management or diagnostic outcome follows from that action?
- The migration sequence transfers supported switch settings into the FortiGate management context
- The GUI presents managed-switch topology, port settings and status in the controller context
- Discovery-capable ports advertise and detect controller connectivity without preprogramming the full local switch
- FortiLink discovery uses configured neighbor detection; FortiOS 7.6.1 uses LLDP as its default method
Explanation
Correct Answer
D:Given the described goal, the configured operation is meant to make discovery consistent with the actual supported port and neighbor behavior. The most relevant validation is to inspect the neighbor-detection method and observed adjacency in the active FortiLink connection for the equipment at the remote depot.
Incorrect Answers
A:That behavior applies when engineers “Migrate a standalone FortiSwitch into FortiGate management”; the different operation “Enable neighbor detection appropriate for the FortiLink deployment” is intended to make discovery consistent with the actual supported port and neighbor behavior. That different feature is verified by confirm the switch is authorized and that critical port/VLAN values match the intended migration; for “Enable neighbor detection appropriate for the FortiLink deployment” on a FortiLink-managed access switch, the relevant evidence is to inspect the neighbor-detection method and observed adjacency in the active FortiLink connection.
B:This outcome would be relevant to “Use the FortiGate switch-controller GUI” at the remote depot, not the task “Enable neighbor detection appropriate for the FortiLink deployment”; the other task is to perform routine managed-switch edits through the centralized user interface. The action “Enable neighbor detection appropriate for the FortiLink deployment” targets a different result: FortiLink discovery uses configured neighbor detection; FortiOS 7.6.1 uses LLDP as its default method; the proposed alternative would instead be checked by inspect the switch-controller managed-switch list before editing the target unit.
C:That behavior applies when engineers “Use a supported auto-discovery FortiSwitch port”; the different operation “Enable neighbor detection appropriate for the FortiLink deployment” is intended to make discovery consistent with the actual supported port and neighbor behavior. That different feature is verified by check the port's model-dependent auto-discovery support and switch discovery event; for “Enable neighbor detection appropriate for the FortiLink deployment” on a FortiLink-managed access switch, the relevant evidence is to inspect the neighbor-detection method and observed adjacency in the active FortiLink connection.
Question 323
An auditor wants operational evidence for the switch action “Enable neighbor detection appropriate for the FortiLink deployment” at the branch office. Which check is relevant?
- Inspect the neighbor-detection method and observed adjacency in the active FortiLink connection
- Verify intended image version, upgrade status and post-reboot switch connectivity
- Poll system and interface identifiers from the configured monitoring station
- Confirm device registration, service connectivity and cloud-visible online state
Explanation
Correct Answer
A:The switch behavior that matters is: FortiLink discovery uses configured neighbor detection; FortiOS 7.6.1 uses LLDP as its default method. Directly measuring that result demonstrates whether the step to make discovery consistent with the actual supported port and neighbor behavior succeeded on a switch linked to a FortiGate running FortiOS 7.6.
Incorrect Answers
B:The proposed check concerns “Perform a centrally coordinated FortiSwitch firmware update” rather than “Enable neighbor detection appropriate for the FortiLink deployment”: firmware maintenance for managed switches should be coordinated through the FortiGate management workflow. For “Enable neighbor detection appropriate for the FortiLink deployment” on a switch linked to a FortiGate running FortiOS 7.6, a better test would be to inspect the neighbor-detection method and observed adjacency in the active FortiLink connection, which targets make discovery consistent with the actual supported port and neighbor behavior rather than the alternative diagnostic “Perform a centrally coordinated FortiSwitch firmware update”.
C:This check is suited to “Configure remote monitoring through SNMP” when trying to expose interface and switch health telemetry to an authorized monitoring collector, not to verify “Enable neighbor detection appropriate for the FortiLink deployment” at the branch office. Checking “Enable neighbor detection appropriate for the FortiLink deployment” at the branch office requires evidence of its own mechanism: FortiLink discovery uses configured neighbor detection; FortiOS 7.6.1 uses LLDP as its default method; that is not the outcome measured by “Configure remote monitoring through SNMP”.
D:This check is suited to “Use FortiEdge Cloud management for a supported switch” when trying to administer an eligible cloud-managed FortiSwitch without relying on FortiLink to a local FortiGate, not to verify “Enable neighbor detection appropriate for the FortiLink deployment” at the branch office. Checking “Enable neighbor detection appropriate for the FortiLink deployment” at the branch office requires evidence of its own mechanism: FortiLink discovery uses configured neighbor detection; FortiOS 7.6.1 uses LLDP as its default method; that is not the outcome measured by “Use FortiEdge Cloud management for a supported switch”.
Question 324
A peer review of the factory asks how the design will remove an old device from centralized switch management without accidentally changing a replacement unit. Which FortiSwitch technique is the correct response?
- Create a FortiSwitch group for common administration
- Deauthorize a retired managed switch deliberately
- Integrate switch status with the Security Fabric
- Review FortiSwitch serial number during onboarding
- Migrate standalone settings with an approved script
Explanation
Correct Answer
B:At this network boundary, controller deauthorization changes the authorization relationship and may affect switch reset or password retention. The operator can test this claim by the specific check: confirm the intended serial number is no longer authorized and review the deauthorization policy.
Incorrect Answers
A:Compared with the requested “Deauthorize a retired managed switch deliberately” at the factory, this would apply shared settings to several managed switches with related roles instead: grouping units supports consistent profile or administrative treatment across selected devices. At the factory, the operational proof would instead be to confirm the intended serial number is no longer authorized and review the deauthorization policy, whereas “Create a FortiSwitch group for common administration” is validated by a different test: check each intended serial number's group membership and inherited configuration.
C:Compared with the requested “Deauthorize a retired managed switch deliberately” at the factory, this would provide visibility of managed access infrastructure in the Fortinet environment instead: controller and Fabric integration correlate switch topology and endpoint observations with FortiGate management. At the factory, the operational proof would instead be to confirm the intended serial number is no longer authorized and review the deauthorization policy, whereas “Integrate switch status with the Security Fabric” is validated by a different test: look for switch presence and expected topology information in the Fabric view.
D:For the factory, “Review FortiSwitch serial number during onboarding” is a different type of control from “Deauthorize a retired managed switch deliberately”: a unique hardware serial number identifies the FortiSwitch object managed by the controller. Unlike the requested feature, that setting addresses the need to avoid configuring a similarly named but different discovered unit, not the objective to remove an old device from centralized switch management without accidentally changing a replacement unit.
E:Compared with the requested “Deauthorize a retired managed switch deliberately” at the factory, this would retain required VLAN or port values when converting administration mode instead: a migration script can translate and reapply supported standalone settings for managed deployment. At the factory, the operational proof would instead be to confirm the intended serial number is no longer authorized and review the deauthorization policy, whereas “Migrate standalone settings with an approved script” is validated by a different test: diff the required old settings against the resulting controller-managed configuration.
Question 325
Before applying the planned operation “Deauthorize a retired managed switch deliberately” at the research building, the administrator must predict its impact. Which prediction is sound?
- Controller deauthorization changes the authorization relationship and may affect switch reset or password retention
- Management-access settings decide which administrative services are accepted on an interface
- FortiLink discovery uses configured neighbor detection; FortiOS 7.6.1 uses LLDP as its default method
- A configuration export preserves management settings independently of the device's current runtime state
Explanation
Correct Answer
A:In this deployment, the configured operation is meant to remove an old device from centralized switch management without accidentally changing a replacement unit. The most relevant validation is to confirm the intended serial number is no longer authorized and review the deauthorization policy for the equipment at the research building.
Incorrect Answers
B:This outcome would be relevant to “Restrict administrative protocols on switch management interfaces” at the research building, not the task “Deauthorize a retired managed switch deliberately”; the other task is to reduce exposure of the switch control plane to unauthorized clients. The action “Deauthorize a retired managed switch deliberately” targets a different result: controller deauthorization changes the authorization relationship and may affect switch reset or password retention; the proposed alternative would instead be checked by inspect enabled administrative protocols and test reachability from an approved source.
C:That behavior applies when engineers “Enable neighbor detection appropriate for the FortiLink deployment”; the different operation “Deauthorize a retired managed switch deliberately” is intended to remove an old device from centralized switch management without accidentally changing a replacement unit. That different feature is verified by inspect the neighbor-detection method and observed adjacency in the active FortiLink connection; for “Deauthorize a retired managed switch deliberately” on a managed switch running FortiSwitchOS 7.6, the relevant evidence is to confirm the intended serial number is no longer authorized and review the deauthorization policy.
D:That behavior applies when engineers “Back up FortiSwitch configuration before upgrades”; the different operation “Deauthorize a retired managed switch deliberately” is intended to remove an old device from centralized switch management without accidentally changing a replacement unit. That different feature is verified by check the backup file timestamp and availability before starting maintenance; for “Deauthorize a retired managed switch deliberately” on a managed switch running FortiSwitchOS 7.6, the relevant evidence is to confirm the intended serial number is no longer authorized and review the deauthorization policy.
Question 326
The operational requirement for an access switch in routine maintenance at the clinic is to avoid issuing settings to an unsupported FortiSwitch platform. Which FortiSwitch choice directly targets it?
- Enable automatic FortiSwitch authorization where appropriate
- Check supported model and feature availability before provisioning
- Apply an administrative access profile
- Select a FortiSwitch profile with a managed admin password
Explanation
Correct Answer
B:For the stated requirement, supported capabilities vary by model and hardware; validating the feature matrix prevents invalid configuration assumptions. The operator can test this claim by the specific check: compare the exact SKU and FortiSwitchOS release against the target feature documentation.
Incorrect Answers
A:For the clinic, “Enable automatic FortiSwitch authorization where appropriate” is a different type of control from “Check supported model and feature availability before provisioning”: the FortiLink controller can authorize discovered devices automatically when that setting is enabled. Unlike the requested feature, that setting addresses the need to reduce manual approvals for trusted units on a controlled provisioning network, not the objective to avoid issuing settings to an unsupported FortiSwitch platform.
C:Compared with the requested “Check supported model and feature availability before provisioning” at the clinic, this would limit which administrators can change switch management and networking features instead: role or access profiles restrict management menus and configuration privileges. At the clinic, the operational proof would instead be to compare the exact SKU and FortiSwitchOS release against the target feature documentation, whereas “Apply an administrative access profile” is validated by a different test: test which GUI menus and CLI commands are available to the assigned administrator.
D:Compared with the requested “Check supported model and feature availability before provisioning” at the clinic, this would give authorized operators controlled switch access without depending on an empty local password instead: FortiGate switch profiles can set managed switch administrative credentials centrally. At the clinic, the operational proof would instead be to compare the exact SKU and FortiSwitchOS release against the target feature documentation, whereas “Select a FortiSwitch profile with a managed admin password” is validated by a different test: verify the applied profile and successful login using the assigned administrator credentials.
Question 327
Before applying the planned operation “Check supported model and feature availability before provisioning” at the data hall, the administrator must predict its impact. Which prediction is sound?
- Discovery-capable ports advertise and detect controller connectivity without preprogramming the full local switch
- Supported capabilities vary by model and hardware; validating the feature matrix prevents invalid configuration assumptions
- The GUI presents managed-switch topology, port settings and status in the controller context
- Controller deauthorization changes the authorization relationship and may affect switch reset or password retention
Explanation
Correct Answer
B:The deciding detail is that the configured operation is meant to avoid issuing settings to an unsupported FortiSwitch platform. The most relevant validation is to compare the exact SKU and FortiSwitchOS release against the target feature documentation for the equipment at the data hall.
Incorrect Answers
A:This outcome would be relevant to “Use a supported auto-discovery FortiSwitch port” at the data hall, not the task “Check supported model and feature availability before provisioning”; the other task is to allow an unconfigured switch to find its FortiLink controller during installation. The action “Check supported model and feature availability before provisioning” targets a different result: supported capabilities vary by model and hardware; validating the feature matrix prevents invalid configuration assumptions; the proposed alternative would instead be checked by check the port's model-dependent auto-discovery support and switch discovery event.
C:That behavior applies when engineers “Use the FortiGate switch-controller GUI”; the different operation “Check supported model and feature availability before provisioning” is intended to avoid issuing settings to an unsupported FortiSwitch platform. That different feature is verified by inspect the switch-controller managed-switch list before editing the target unit; for “Check supported model and feature availability before provisioning” on a managed campus switch, the relevant evidence is to compare the exact SKU and FortiSwitchOS release against the target feature documentation.
D:That behavior applies when engineers “Deauthorize a retired managed switch deliberately”; the different operation “Check supported model and feature availability before provisioning” is intended to avoid issuing settings to an unsupported FortiSwitch platform. That different feature is verified by confirm the intended serial number is no longer authorized and review the deauthorization policy; for “Check supported model and feature availability before provisioning” on a managed campus switch, the relevant evidence is to compare the exact SKU and FortiSwitchOS release against the target feature documentation.
Question 328
For the development floor, the network team needs to deploy a small branch with one managed switch and minimal switching complexity. Which change is the most direct way to implement that requirement on a recently upgraded FortiSwitch?
- Deploy an MCLAG distribution peer pair
- Keep independent LAN and WAN FortiLink stacks
- Use direct one-to-one FortiGate-to-FortiSwitch wiring
- Provide second-tier MCLAG for resilient access aggregation
- Use VLAN pruning on ISL trunks
Explanation
Correct Answer
C:The relevant mechanism is: a single FortiLink connection allows the FortiGate to manage the directly attached switch. The operator can test this claim by the specific check: inspect FortiLink status and the one-switch topology after startup.
Incorrect Answers
A:For the development floor, “Deploy an MCLAG distribution peer pair” is a different type of control from “Use direct one-to-one FortiGate-to-FortiSwitch wiring”: 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 deploy a small branch with one managed switch and minimal switching complexity.
B:Compared with the requested “Use direct one-to-one FortiGate-to-FortiSwitch wiring” at the development floor, this would use separate switching infrastructure for different security-edge functions instead: separate FortiLink interfaces manage separate VLAN and switch groups for LAN and WAN roles. At the development floor, the operational proof would instead be to inspect FortiLink status and the one-switch topology after startup, whereas “Keep independent LAN and WAN FortiLink stacks” is validated by a different test: confirm each stack's FortiLink interface and that units do not cross the wrong stack.
D:Compared with the requested “Use direct one-to-one FortiGate-to-FortiSwitch wiring” at the development floor, this would protect the next aggregation layer beneath an already redundant core instead: a lower peer group supplies redundant endpoints for access switches deeper in the design. At the development floor, the operational proof would instead be to inspect FortiLink status and the one-switch topology after startup, whereas “Provide second-tier MCLAG for resilient access aggregation” is validated by a different test: check second-tier ICL and access trunks rather than only first-tier connectivity.
E:Compared with the requested “Use direct one-to-one FortiGate-to-FortiSwitch wiring” at the development floor, this would avoid transporting VLAN traffic across parts of the stack with no members instead: VLAN pruning limits inter-switch VLAN carriage to those actually required along each path. At the development floor, the operational proof would instead be to inspect FortiLink status and the one-switch topology after startup, whereas “Use VLAN pruning on ISL trunks” is validated by a different test: inspect which VLAN IDs remain active on each intermediate ISL trunk.
Question 329
Before applying the planned operation “Use direct one-to-one FortiGate-to-FortiSwitch wiring” at the conference venue, the administrator must predict its impact. Which prediction is sound?
- Downstream FortiSwitch units join through supported inter-switch links to the first unit
- An interchassis link with multiple members avoids making one cable the sole MCLAG coordination path
- A single FortiLink connection allows the FortiGate to manage the directly attached switch
- Split-interface behavior is topology-dependent and distinct from a conventional active aggregate
Explanation
Correct Answer
C:This approach fits because the configured operation is meant to deploy a small branch with one managed switch and minimal switching complexity. The most relevant validation is to inspect FortiLink status and the one-switch topology after startup for the equipment at the conference venue.
Incorrect Answers
A:That behavior applies when engineers “Cascade access switches through an upstream managed switch”; the different operation “Use direct one-to-one FortiGate-to-FortiSwitch wiring” is intended to deploy a small branch with one managed switch and minimal switching complexity. That different feature is verified by inspect child-switch discovery and the parent ISL forwarding state; for “Use direct one-to-one FortiGate-to-FortiSwitch wiring” on a FortiLink-managed access switch, the relevant evidence is to inspect FortiLink status and the one-switch topology after startup.
B:This outcome would be relevant to “Build a redundant ICL between peers” at the conference venue, not the task “Use direct one-to-one FortiGate-to-FortiSwitch wiring”; the other task is to retain peer-state exchange if one physical interchassis cable fails. The action “Use direct one-to-one FortiGate-to-FortiSwitch wiring” targets a different result: a single FortiLink connection allows the FortiGate to manage the directly attached switch; 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 “Configure a FortiLink split interface where the topology requires it”; the different operation “Use direct one-to-one FortiGate-to-FortiSwitch wiring” is intended to deploy a small branch with one managed switch and minimal switching complexity. That different feature is verified by verify split-interface state against which FortiSwitch devices each member connects to; for “Use direct one-to-one FortiGate-to-FortiSwitch wiring” on a FortiLink-managed access switch, the relevant evidence is to inspect FortiLink status and the one-switch topology after startup.
Question 330
The work order to deploy a small branch with one managed switch and minimal switching complexity is marked complete on a switch linked to a FortiGate running FortiOS 7.6. Which observation most directly tests the completed configuration?
- Audit per-tier peer groups and the full three-layer physical uplink map
- Capture FortiLink control traffic at both ends of the Layer 2 segment
- Trace the VLAN boundary and verify routing rather than a nonexistent L2 stretch
- Inspect FortiLink status and the one-switch topology after startup
Explanation
Correct Answer
D:The critical distinction is that a single FortiLink connection allows the FortiGate to manage the directly attached switch. Directly measuring that result demonstrates whether the step to deploy a small branch with one managed switch and minimal switching complexity succeeded on a switch linked to a FortiGate running FortiOS 7.6.
Incorrect Answers
A:This check is suited to “Design a three-tier MCLAG hierarchy” when trying to extend resilient aggregation through core, distribution and access levels, not to verify “Use direct one-to-one FortiGate-to-FortiSwitch wiring” at the campus. Checking “Use direct one-to-one FortiGate-to-FortiSwitch wiring” at the campus requires evidence of its own mechanism: a single FortiLink connection allows the FortiGate to manage the directly attached switch; that is not the outcome measured by “Design a three-tier MCLAG hierarchy”.
B:The proposed check concerns “Use FortiLink over a point-to-point Layer 2 transit” rather than “Use direct one-to-one FortiGate-to-FortiSwitch wiring”: point-to-point L2 transit preserves required FortiLink discovery and management frames across the middle network. For “Use direct one-to-one FortiGate-to-FortiSwitch wiring” on a switch linked to a FortiGate running FortiOS 7.6, a better test would be to inspect FortiLink status and the one-switch topology after startup, which targets deploy a small branch with one managed switch and minimal switching complexity rather than the alternative diagnostic “Use FortiLink over a point-to-point Layer 2 transit”.
C:This check is suited to “Avoid stretching production VLANs across Layer 3 FortiLink” when trying to keep remote switch islands from assuming a shared Layer 2 segment across an IP network, not to verify “Use direct one-to-one FortiGate-to-FortiSwitch wiring” at the campus. Checking “Use direct one-to-one FortiGate-to-FortiSwitch wiring” at the campus requires evidence of its own mechanism: a single FortiLink connection allows the FortiGate to manage the directly attached switch; that is not the outcome measured by “Avoid stretching production VLANs across Layer 3 FortiLink”.