Question 240
The accepted design for the airport office requires the ability to automatically maintain eligible links between managed FortiSwitch units. Which switch feature is the closest fit?
- Enable flap guard on an unstable interface
- Select appropriate LACP load-balancing criteria
- Set supported speed and duplex consistently
- Split a supported high-speed physical port into subports
- Use an auto-ISL trunk where supported
Explanation
Correct Answer
E:At this network boundary, auto-inter-switch-link mechanisms simplify eligible uplink bundling in supported FortiLink designs. The operator can test this claim by the specific check: inspect discovered ISL membership and active trunk status.
Incorrect Answers
A:Compared with the requested “Use an auto-ISL trunk where supported” at the airport office, this would limit disruption caused by a port repeatedly transitioning up and down instead: flap guard monitors link-state changes and can place an unstable port into a protective state. At the airport office, the operational proof would instead be to inspect discovered ISL membership and active trunk status, whereas “Enable flap guard on an unstable interface” is validated by a different test: inspect flap events and the interface's automatic disable or recovery status.
B:For the airport office, “Select appropriate LACP load-balancing criteria” is a different type of control from “Use an auto-ISL trunk where supported”: trunk hashing chooses a member based on header fields and typically keeps each flow on one link. Unlike the requested feature, that setting addresses the need to spread different traffic flows across the members of an existing trunk, not the objective to automatically maintain eligible links between managed FortiSwitch units.
C:Compared with the requested “Use an auto-ISL trunk where supported” at the airport office, this would restore a physical link with incompatible manual interface negotiation instead: both connected endpoints must agree on operational link characteristics supported by their hardware. At the airport office, the operational proof would instead be to inspect discovered ISL membership and active trunk status, whereas “Set supported speed and duplex consistently” is validated by a different test: check negotiated link speed, duplex and error counters at both ends.
D:Compared with the requested “Use an auto-ISL trunk where supported” at the airport office, this would create several lower-rate interfaces from a supported switch port instead: split-port phy-mode changes how the underlying physical lanes are exposed as separate interfaces. At the airport office, the operational proof would instead be to inspect discovered ISL membership and active trunk status, whereas “Split a supported high-speed physical port into subports” is validated by a different test: check the port's supported phy-mode choices and resulting interface inventory.
Question 241
During validation of a switch linked to a FortiGate running FortiOS 7.6 at the conference venue, the team asks what the change “Use an auto-ISL trunk where supported” actually does. Which outcome is correct?
- Auto-inter-switch-link mechanisms simplify eligible uplink bundling in supported FortiLink designs
- Both connected endpoints must agree on operational link characteristics supported by their hardware
- Split-port phy-mode changes how the underlying physical lanes are exposed as separate interfaces
- Trunk hashing chooses a member based on header fields and typically keeps each flow on one link
Explanation
Correct Answer
A:In this deployment, the configured operation is meant to automatically maintain eligible links between managed FortiSwitch units. The most relevant validation is to inspect discovered ISL membership and active trunk status for the equipment at the conference venue.
Incorrect Answers
B:That behavior applies when engineers “Set supported speed and duplex consistently”; the different operation “Use an auto-ISL trunk where supported” is intended to automatically maintain eligible links between managed FortiSwitch units. That different feature is verified by check negotiated link speed, duplex and error counters at both ends; for “Use an auto-ISL trunk where supported” on a switch linked to a FortiGate running FortiOS 7.6, the relevant evidence is to inspect discovered ISL membership and active trunk status.
C:This outcome would be relevant to “Split a supported high-speed physical port into subports” at the conference venue, not the task “Use an auto-ISL trunk where supported”; the other task is to create several lower-rate interfaces from a supported switch port. The action “Use an auto-ISL trunk where supported” targets a different result: auto-inter-switch-link mechanisms simplify eligible uplink bundling in supported FortiLink designs; the proposed alternative would instead be checked by check the port's supported phy-mode choices and resulting interface inventory.
D:That behavior applies when engineers “Select appropriate LACP load-balancing criteria”; the different operation “Use an auto-ISL trunk where supported” is intended to automatically maintain eligible links between managed FortiSwitch units. That different feature is verified by inspect member utilization with multiple flows and verify the configured hash fields; for “Use an auto-ISL trunk where supported” on a switch linked to a FortiGate running FortiOS 7.6, the relevant evidence is to inspect discovered ISL membership and active trunk status.
Question 242
A FortiSwitch engineer in the campus is documenting successful operation of “Use an auto-ISL trunk where supported.” Which measurement or inspection confirms it?
- Inspect member utilization with multiple flows and verify the configured hash fields
- Check negotiated link speed, duplex and error counters at both ends
- Inspect discovered ISL membership and active trunk status
- Check the port's supported phy-mode choices and resulting interface inventory
Explanation
Correct Answer
C:For the stated requirement, auto-inter-switch-link mechanisms simplify eligible uplink bundling in supported FortiLink designs. Directly measuring that result demonstrates whether the step to automatically maintain eligible links between managed FortiSwitch units succeeded on a switch serving a high-density endpoint area.
Incorrect Answers
A:This check is suited to “Select appropriate LACP load-balancing criteria” when trying to spread different traffic flows across the members of an existing trunk, not to verify “Use an auto-ISL trunk where supported” at the campus. Checking “Use an auto-ISL trunk where supported” at the campus requires evidence of its own mechanism: auto-inter-switch-link mechanisms simplify eligible uplink bundling in supported FortiLink designs; that is not the outcome measured by “Select appropriate LACP load-balancing criteria”.
B:This check is suited to “Set supported speed and duplex consistently” when trying to restore a physical link with incompatible manual interface negotiation, not to verify “Use an auto-ISL trunk where supported” at the campus. Checking “Use an auto-ISL trunk where supported” at the campus requires evidence of its own mechanism: auto-inter-switch-link mechanisms simplify eligible uplink bundling in supported FortiLink designs; that is not the outcome measured by “Set supported speed and duplex consistently”.
D:The proposed check concerns “Split a supported high-speed physical port into subports” rather than “Use an auto-ISL trunk where supported”: split-port phy-mode changes how the underlying physical lanes are exposed as separate interfaces. For “Use an auto-ISL trunk where supported” on a switch serving a high-density endpoint area, a better test would be to inspect discovered ISL membership and active trunk status, which targets automatically maintain eligible links between managed FortiSwitch units rather than the alternative diagnostic “Split a supported high-speed physical port into subports”.
Question 243
An administrator responsible for a managed switch running FortiSwitchOS 7.6 in the remote depot must require sufficient healthy physical links before allowing an aggregate to remain usable. Which configuration best matches that precise goal?
- Select appropriate LACP load-balancing criteria
- Set supported speed and duplex consistently
- Constrain PoE to available power capacity
- Confirm minimum LAG members for service
- Split a supported high-speed physical port into subports
Explanation
Correct Answer
D:The deciding detail is that the aggregate minimum-member condition constrains availability as members fail. This distinction is material to the remote depot, where the stated goal is to require sufficient healthy physical links before allowing an aggregate to remain usable.
Incorrect Answers
A:Compared with the requested “Confirm minimum LAG members for service” at the remote depot, this would spread different traffic flows across the members of an existing trunk instead: trunk hashing chooses a member based on header fields and typically keeps each flow on one link. At the remote depot, the operational proof would instead be to remove members in a test and observe when the logical trunk is considered operational, whereas “Select appropriate LACP load-balancing criteria” is validated by a different test: inspect member utilization with multiple flows and verify the configured hash fields.
B:Compared with the requested “Confirm minimum LAG members for service” at the remote depot, this would restore a physical link with incompatible manual interface negotiation instead: both connected endpoints must agree on operational link characteristics supported by their hardware. At the remote depot, the operational proof would instead be to remove members in a test and observe when the logical trunk is considered operational, whereas “Set supported speed and duplex consistently” is validated by a different test: check negotiated link speed, duplex and error counters at both ends.
C:Compared with the requested “Confirm minimum LAG members for service” at the remote depot, this would prevent a new powered endpoint from exceeding the switch power budget instead: power delivery is constrained by per-port hardware capability and the switch's aggregate PoE budget. At the remote depot, the operational proof would instead be to remove members in a test and observe when the logical trunk is considered operational, whereas “Constrain PoE to available power capacity” is validated by a different test: compare the connected device's requested class with free PoE budget and port allocation.
E:For the remote depot, “Split a supported high-speed physical port into subports” is a different type of control from “Confirm minimum LAG members for service”: split-port phy-mode changes how the underlying physical lanes are exposed as separate interfaces. Unlike the requested feature, that setting addresses the need to create several lower-rate interfaces from a supported switch port, not the objective to require sufficient healthy physical links before allowing an aggregate to remain usable.
Question 244
Before applying the planned operation “Confirm minimum LAG members for service” at the branch office, the administrator must predict its impact. Which prediction is sound?
- Power delivery is constrained by per-port hardware capability and the switch's aggregate PoE budget
- Split-port phy-mode changes how the underlying physical lanes are exposed as separate interfaces
- The aggregate minimum-member condition constrains availability as members fail
- Both connected endpoints must agree on operational link characteristics supported by their hardware
Explanation
Correct Answer
C:The relevant mechanism is: the configured operation is meant to require sufficient healthy physical links before allowing an aggregate to remain usable. The most relevant validation is to remove members in a test and observe when the logical trunk is considered operational for the equipment at the branch office.
Incorrect Answers
A:That behavior applies when engineers “Constrain PoE to available power capacity”; the different operation “Confirm minimum LAG members for service” is intended to require sufficient healthy physical links before allowing an aggregate to remain usable. That different feature is verified by compare the connected device's requested class with free PoE budget and port allocation; for “Confirm minimum LAG members for service” on a remote FortiSwitch installation, the relevant evidence is to remove members in a test and observe when the logical trunk is considered operational.
B:That behavior applies when engineers “Split a supported high-speed physical port into subports”; the different operation “Confirm minimum LAG members for service” is intended to require sufficient healthy physical links before allowing an aggregate to remain usable. That different feature is verified by check the port's supported phy-mode choices and resulting interface inventory; for “Confirm minimum LAG members for service” on a remote FortiSwitch installation, the relevant evidence is to remove members in a test and observe when the logical trunk is considered operational.
D:This outcome would be relevant to “Set supported speed and duplex consistently” at the branch office, not the task “Confirm minimum LAG members for service”; the other task is to restore a physical link with incompatible manual interface negotiation. The action “Confirm minimum LAG members for service” targets a different result: the aggregate minimum-member condition constrains availability as members fail; the proposed alternative would instead be checked by check negotiated link speed, duplex and error counters at both ends.
Question 245
On an endpoint-facing FortiSwitch port at the factory, the team reports that it has configured “Confirm minimum LAG members for service.” Which verification provides the strongest direct evidence that the intended function is working?
- Remove members in a test and observe when the logical trunk is considered operational
- Compare the connected device's requested class with free PoE budget and port allocation
- Check negotiated link speed, duplex and error counters at both ends
- Check the port's supported phy-mode choices and resulting interface inventory
Explanation
Correct Answer
A:This approach fits because the aggregate minimum-member condition constrains availability as members fail. Directly measuring that result demonstrates whether the step to require sufficient healthy physical links before allowing an aggregate to remain usable succeeded on an endpoint-facing FortiSwitch port.
Incorrect Answers
B:This check is suited to “Constrain PoE to available power capacity” when trying to prevent a new powered endpoint from exceeding the switch power budget, not to verify “Confirm minimum LAG members for service” at the factory. Checking “Confirm minimum LAG members for service” at the factory requires evidence of its own mechanism: the aggregate minimum-member condition constrains availability as members fail; that is not the outcome measured by “Constrain PoE to available power capacity”.
C:The proposed check concerns “Set supported speed and duplex consistently” rather than “Confirm minimum LAG members for service”: both connected endpoints must agree on operational link characteristics supported by their hardware. For “Confirm minimum LAG members for service” on an endpoint-facing FortiSwitch port, a better test would be to remove members in a test and observe when the logical trunk is considered operational, which targets require sufficient healthy physical links before allowing an aggregate to remain usable rather than the alternative diagnostic “Set supported speed and duplex consistently”.
D:This check is suited to “Split a supported high-speed physical port into subports” when trying to create several lower-rate interfaces from a supported switch port, not to verify “Confirm minimum LAG members for service” at the factory. Checking “Confirm minimum LAG members for service” at the factory requires evidence of its own mechanism: the aggregate minimum-member condition constrains availability as members fail; that is not the outcome measured by “Split a supported high-speed physical port into subports”.
Question 246
A peer review of the distribution floor asks how the design will manage a switch locally without delegating configuration to a FortiGate. Which FortiSwitch technique is the correct response?
- Use FortiEdge Cloud management for a supported switch
- Authorize a discovered FortiSwitch on FortiGate
- Operate a FortiSwitch in standalone mode
- Enable time synchronization for managed units
Explanation
Correct Answer
C:The critical distinction is that standalone mode exposes local configuration and administration on the switch itself. The operator can test this claim by the specific check: confirm local management access and that the unit is not assigned to a FortiGate controller.
Incorrect Answers
A:For the distribution floor, “Use FortiEdge Cloud management for a supported switch” is a different type of control from “Operate a FortiSwitch in standalone mode”: a cloud management workflow connects the registered switch to the appropriate Fortinet service. Unlike the requested feature, that setting addresses the need to administer an eligible cloud-managed FortiSwitch without relying on FortiLink to a local FortiGate, not the objective to manage a switch locally without delegating configuration to a FortiGate.
B:Compared with the requested “Operate a FortiSwitch in standalone mode” at the distribution floor, this would move an already discovered unit into centrally managed service instead: controller authorization allows the FortiGate to provision and manage that switch via FortiLink. At the distribution floor, the operational proof would instead be to confirm local management access and that the unit is not assigned to a FortiGate controller, whereas “Authorize a discovered FortiSwitch on FortiGate” is validated by a different test: check the managed-switch inventory for an authorized state and configuration synchronization.
D:Compared with the requested “Operate a FortiSwitch in standalone mode” at the distribution floor, this would prevent clock drift from confusing authentication and event correlation instead: a reachable NTP source supplies consistent time to switch and controller management processes. At the distribution floor, the operational proof would instead be to confirm local management access and that the unit is not assigned to a FortiGate controller, whereas “Enable time synchronization for managed units” is validated by a different test: compare FortiGate and FortiSwitch system clocks and NTP association state.
Question 247
During validation of a newly commissioned floor switch at the media studio, the team asks what the change “Operate a FortiSwitch in standalone mode” actually does. Which outcome is correct?
- A unique hardware serial number identifies the FortiSwitch object managed by the controller
- Standalone mode exposes local configuration and administration on the switch itself
- A migration script can translate and reapply supported standalone settings for managed deployment
- Grouping units supports consistent profile or administrative treatment across selected devices
- Controller and Fabric integration correlate switch topology and endpoint observations with FortiGate management
Explanation
Correct Answer
B:That setting is appropriate here because the configured operation is meant to manage a switch locally without delegating configuration to a FortiGate. The most relevant validation is to confirm local management access and that the unit is not assigned to a FortiGate controller for the equipment at the media studio.
Incorrect Answers
A:That behavior applies when engineers “Review FortiSwitch serial number during onboarding”; the different operation “Operate a FortiSwitch in standalone mode” is intended to manage a switch locally without delegating configuration to a FortiGate. That different feature is verified by match the serial in the physical inventory with the FortiGate discovery listing; for “Operate a FortiSwitch in standalone mode” on a newly commissioned floor switch, the relevant evidence is to confirm local management access and that the unit is not assigned to a FortiGate controller.
C:This outcome would be relevant to “Migrate standalone settings with an approved script” at the media studio, not the task “Operate a FortiSwitch in standalone mode”; the other task is to retain required VLAN or port values when converting administration mode. The action “Operate a FortiSwitch in standalone mode” targets a different result: standalone mode exposes local configuration and administration on the switch itself; the proposed alternative would instead be checked by diff the required old settings against the resulting controller-managed configuration.
D:That behavior applies when engineers “Create a FortiSwitch group for common administration”; the different operation “Operate a FortiSwitch in standalone mode” is intended to manage a switch locally without delegating configuration to a FortiGate. That different feature is verified by check each intended serial number's group membership and inherited configuration; for “Operate a FortiSwitch in standalone mode” on a newly commissioned floor switch, the relevant evidence is to confirm local management access and that the unit is not assigned to a FortiGate controller.
E:That behavior applies when engineers “Integrate switch status with the Security Fabric”; the different operation “Operate a FortiSwitch in standalone mode” is intended to manage a switch locally without delegating configuration to a FortiGate. That different feature is verified by look for switch presence and expected topology information in the Fabric view; for “Operate a FortiSwitch in standalone mode” on a newly commissioned floor switch, the relevant evidence is to confirm local management access and that the unit is not assigned to a FortiGate controller.
Question 248
A post-change review at the data hall must validate the implementation of “Operate a FortiSwitch in standalone mode.” What should the reviewer inspect first?
- Inspect the neighbor-detection method and observed adjacency in the active FortiLink connection
- Inspect enabled administrative protocols and test reachability from an approved source
- Confirm local management access and that the unit is not assigned to a FortiGate controller
- Check the backup file timestamp and availability before starting maintenance
Explanation
Correct Answer
C:This is the precise control because standalone mode exposes local configuration and administration on the switch itself. Directly measuring that result demonstrates whether the step to manage a switch locally without delegating configuration to a FortiGate succeeded on a switch linked to a FortiGate running FortiOS 7.6.
Incorrect Answers
A:This check is suited to “Enable neighbor detection appropriate for the FortiLink deployment” when trying to make discovery consistent with the actual supported port and neighbor behavior, not to verify “Operate a FortiSwitch in standalone mode” at the data hall. Checking “Operate a FortiSwitch in standalone mode” at the data hall requires evidence of its own mechanism: standalone mode exposes local configuration and administration on the switch itself; that is not the outcome measured by “Enable neighbor detection appropriate for the FortiLink deployment”.
B:The proposed check concerns “Restrict administrative protocols on switch management interfaces” rather than “Operate a FortiSwitch in standalone mode”: management-access settings decide which administrative services are accepted on an interface. For “Operate a FortiSwitch in standalone mode” on a switch linked to a FortiGate running FortiOS 7.6, a better test would be to confirm local management access and that the unit is not assigned to a FortiGate controller, which targets manage a switch locally without delegating configuration to a FortiGate rather than the alternative diagnostic “Restrict administrative protocols on switch management interfaces”.
D:This check is suited to “Back up FortiSwitch configuration before upgrades” when trying to make recovery possible if a firmware or policy change fails, not to verify “Operate a FortiSwitch in standalone mode” at the data hall. Checking “Operate a FortiSwitch in standalone mode” at the data hall requires evidence of its own mechanism: standalone mode exposes local configuration and administration on the switch itself; that is not the outcome measured by “Back up FortiSwitch configuration before upgrades”.
Question 249
A production incident in the development floor reveals the need to move an already discovered unit into centrally managed service. Which targeted FortiSwitch setting or method should the team use?
- Use the FortiGate switch-controller GUI
- Migrate a standalone FortiSwitch into FortiGate management
- Authorize a discovered FortiSwitch on FortiGate
- Apply an administrative access profile
Explanation
Correct Answer
C:The implementation works because controller authorization allows the FortiGate to provision and manage that switch via FortiLink. This distinction is material to the development floor, where the stated goal is to move an already discovered unit into centrally managed service.
Incorrect Answers
A:Compared with the requested “Authorize a discovered FortiSwitch on FortiGate” at the development floor, this would perform routine managed-switch edits through the centralized user interface instead: the GUI presents managed-switch topology, port settings and status in the controller context. At the development floor, the operational proof would instead be to check the managed-switch inventory for an authorized state and configuration synchronization, whereas “Use the FortiGate switch-controller GUI” is validated by a different test: inspect the switch-controller managed-switch list before editing the target unit.
B:Compared with the requested “Authorize a discovered FortiSwitch on FortiGate” at the development floor, this would replace independent local administration with centralized provisioning instead: the migration sequence transfers supported switch settings into the FortiGate management context. At the development floor, the operational proof would instead be to check the managed-switch inventory for an authorized state and configuration synchronization, whereas “Migrate a standalone FortiSwitch into FortiGate management” is validated by a different test: confirm the switch is authorized and that critical port/VLAN values match the intended migration.
D:For the development floor, “Apply an administrative access profile” is a different type of control from “Authorize a discovered FortiSwitch on FortiGate”: role or access profiles restrict management menus and configuration privileges. Unlike the requested feature, that setting addresses the need to limit which administrators can change switch management and networking features, not the objective to move an already discovered unit into centrally managed service.
Question 250
Before applying the planned operation “Authorize a discovered FortiSwitch on FortiGate” at the conference venue, the administrator must predict its impact. Which prediction is sound?
- SNMP provides structured operational measurements without becoming the forwarding control plane
- Controller authorization allows the FortiGate to provision and manage that switch via FortiLink
- Controller deauthorization changes the authorization relationship and may affect switch reset or password retention
- Firmware maintenance for managed switches should be coordinated through the FortiGate management workflow
Explanation
Correct Answer
B:Given the described goal, the configured operation is meant to move an already discovered unit into centrally managed service. The most relevant validation is to check the managed-switch inventory for an authorized state and configuration synchronization for the equipment at the conference venue.
Incorrect Answers
A:This outcome would be relevant to “Configure remote monitoring through SNMP” at the conference venue, not the task “Authorize a discovered FortiSwitch on FortiGate”; the other task is to expose interface and switch health telemetry to an authorized monitoring collector. The action “Authorize a discovered FortiSwitch on FortiGate” targets a different result: controller authorization allows the FortiGate to provision and manage that switch via FortiLink; the proposed alternative would instead be checked by poll system and interface identifiers from the configured monitoring station.
C:That behavior applies when engineers “Deauthorize a retired managed switch deliberately”; the different operation “Authorize a discovered FortiSwitch on FortiGate” is intended to move an already discovered unit into centrally managed service. That different feature is verified by confirm the intended serial number is no longer authorized and review the deauthorization policy; for “Authorize a discovered FortiSwitch on FortiGate” on a managed switch running FortiSwitchOS 7.6, the relevant evidence is to check the managed-switch inventory for an authorized state and configuration synchronization.
D:That behavior applies when engineers “Perform a centrally coordinated FortiSwitch firmware update”; the different operation “Authorize a discovered FortiSwitch on FortiGate” is intended to move an already discovered unit into centrally managed service. That different feature is verified by verify intended image version, upgrade status and post-reboot switch connectivity; for “Authorize a discovered FortiSwitch on FortiGate” on a managed switch running FortiSwitchOS 7.6, the relevant evidence is to check the managed-switch inventory for an authorized state and configuration synchronization.