Question 280
For the lab, an administrator applies the action “Use FortiEdge Cloud management for a supported switch.” Which effect should appear when it operates as intended?
- Management-access settings decide which administrative services are accepted on an interface
- Discovery-capable ports advertise and detect controller connectivity without preprogramming the full local switch
- The GUI presents managed-switch topology, port settings and status in the controller context
- A configuration export preserves management settings independently of the device's current runtime state
- A cloud management workflow connects the registered switch to the appropriate Fortinet service
Explanation
Correct Answer
E:The relevant mechanism is: the configured operation is meant to administer an eligible cloud-managed FortiSwitch without relying on FortiLink to a local FortiGate. The most relevant validation is to confirm device registration, service connectivity and cloud-visible online state for the equipment at the lab.
Incorrect Answers
A:That behavior applies when engineers “Restrict administrative protocols on switch management interfaces”; the different operation “Use FortiEdge Cloud management for a supported switch” is intended to administer an eligible cloud-managed FortiSwitch without relying on FortiLink to a local FortiGate. That different feature is verified by inspect enabled administrative protocols and test reachability from an approved source; for “Use FortiEdge Cloud management for a supported switch” on a recently upgraded FortiSwitch, the relevant evidence is to confirm device registration, service connectivity and cloud-visible online state.
B:That behavior applies when engineers “Use a supported auto-discovery FortiSwitch port”; the different operation “Use FortiEdge Cloud management for a supported switch” is intended to administer an eligible cloud-managed FortiSwitch without relying on FortiLink to a local FortiGate. That different feature is verified by check the port's model-dependent auto-discovery support and switch discovery event; for “Use FortiEdge Cloud management for a supported switch” on a recently upgraded FortiSwitch, the relevant evidence is to confirm device registration, service connectivity and cloud-visible online state.
C:This outcome would be relevant to “Use the FortiGate switch-controller GUI” at the lab, not the task “Use FortiEdge Cloud management for a supported switch”; the other task is to perform routine managed-switch edits through the centralized user interface. The action “Use FortiEdge Cloud management for a supported switch” targets a different result: a cloud management workflow connects the registered switch to the appropriate Fortinet service; the proposed alternative would instead be checked by inspect the switch-controller managed-switch list before editing the target unit.
D:That behavior applies when engineers “Back up FortiSwitch configuration before upgrades”; the different operation “Use FortiEdge Cloud management for a supported switch” is intended to administer an eligible cloud-managed FortiSwitch without relying on FortiLink to a local FortiGate. That different feature is verified by check the backup file timestamp and availability before starting maintenance; for “Use FortiEdge Cloud management for a supported switch” on a recently upgraded FortiSwitch, the relevant evidence is to confirm device registration, service connectivity and cloud-visible online state.
Question 281
After implementing “Use FortiEdge Cloud management for a supported switch,” the site engineer needs to assess its actual effect on a FortiLink-managed access switch. Which test is the best match?
- Inspect the restored local settings and confirm there is no controller configuration conflict
- Confirm device registration, service connectivity and cloud-visible online state
- Check the collector for test link or authentication events with correct timestamps
- Compare controller-configured port values with device status and sync indicators
Explanation
Correct Answer
B:This approach fits because a cloud management workflow connects the registered switch to the appropriate Fortinet service. Directly measuring that result demonstrates whether the step to administer an eligible cloud-managed FortiSwitch without relying on FortiLink to a local FortiGate succeeded on a FortiLink-managed access switch.
Incorrect Answers
A: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 “Use FortiEdge Cloud management for a supported switch” at the staging rack. Checking “Use FortiEdge Cloud management for a supported switch” at the staging rack requires evidence of its own mechanism: a cloud management workflow connects the registered switch to the appropriate Fortinet service; that is not the outcome measured by “Restore the saved standalone configuration locally”.
C: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 “Use FortiEdge Cloud management for a supported switch” at the staging rack. Checking “Use FortiEdge Cloud management for a supported switch” at the staging rack requires evidence of its own mechanism: a cloud management workflow connects the registered switch to the appropriate Fortinet service; that is not the outcome measured by “Send operational messages to an external syslog collector”.
D:The proposed check concerns “Check managed-switch configuration synchronization” rather than “Use FortiEdge Cloud management for a supported switch”: synchronization status identifies divergence between controller intent and provisioned switch state. For “Use FortiEdge Cloud management for a supported switch” on a FortiLink-managed access switch, a better test would be to confirm device registration, service connectivity and cloud-visible online state, which targets administer an eligible cloud-managed FortiSwitch without relying on FortiLink to a local FortiGate rather than the alternative diagnostic “Check managed-switch configuration synchronization”.
Question 282
An administrator responsible for a switch linked to a FortiGate running FortiOS 7.6 in the research building must recover a locally administered switch after a failed change. Which configuration best matches that precise goal?
- Operate a FortiSwitch in standalone mode
- Assign a reachable FortiLink interface IP subnet
- Integrate switch status with the Security Fabric
- Restore the saved standalone configuration locally
Explanation
Correct Answer
D:The critical distinction is that standalone backup/restore reloads a saved device configuration rather than rebuilding a FortiGate-managed object. The operator can test this claim by the specific check: inspect the restored local settings and confirm there is no controller configuration conflict.
Incorrect Answers
A:Compared with the requested “Restore the saved standalone configuration locally” at the research building, this would manage a switch locally without delegating configuration to a FortiGate instead: standalone mode exposes local configuration and administration on the switch itself. At the research building, the operational proof would instead be to inspect the restored local settings and confirm there is no controller configuration conflict, whereas “Operate a FortiSwitch in standalone mode” is validated by a different test: confirm local management access and that the unit is not assigned to a FortiGate controller.
B:For the research building, “Assign a reachable FortiLink interface IP subnet” is a different type of control from “Restore the saved standalone configuration locally”: the controller interface provides management addressing and reachability for connected managed units. Unlike the requested feature, that setting addresses the need to support switch-controller management communication over the FortiLink connection, not the objective to recover a locally administered switch after a failed change.
C:Compared with the requested “Restore the saved standalone configuration locally” at the research building, 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 research building, the operational proof would instead be to inspect the restored local settings and confirm there is no controller configuration conflict, 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.
Question 283
On a switch serving a high-density endpoint area, “Restore the saved standalone configuration locally” is configured for the airport office. What effect should an administrator expect without assuming unrelated features are enabled?
- A migration script can translate and reapply supported standalone settings for managed deployment
- Standalone backup/restore reloads a saved device configuration rather than rebuilding a FortiGate-managed object
- FortiGate pushes intended FortiSwitch configuration rather than relying on untracked local edits
- The FortiLink controller can authorize discovered devices automatically when that setting is enabled
Explanation
Correct Answer
B:That setting is appropriate here because the configured operation is meant to recover a locally administered switch after a failed change. The most relevant validation is to inspect the restored local settings and confirm there is no controller configuration conflict for the equipment at the airport office.
Incorrect Answers
A:That behavior applies when engineers “Migrate standalone settings with an approved script”; the different operation “Restore the saved standalone configuration locally” is intended to recover a locally administered switch after a failed change. That different feature is verified by diff the required old settings against the resulting controller-managed configuration; for “Restore the saved standalone configuration locally” on a switch serving a high-density endpoint area, the relevant evidence is to inspect the restored local settings and confirm there is no controller configuration conflict.
C:This outcome would be relevant to “Apply FortiSwitch port configuration from FortiGate” at the airport office, not the task “Restore the saved standalone configuration locally”; the other task is to keep managed port and VLAN settings under centralized change control. The action “Restore the saved standalone configuration locally” targets a different result: standalone backup/restore reloads a saved device configuration rather than rebuilding a FortiGate-managed object; the proposed alternative would instead be checked by compare the controller's managed-port settings with the provisioned running state.
D:That behavior applies when engineers “Enable automatic FortiSwitch authorization where appropriate”; the different operation “Restore the saved standalone configuration locally” is intended to recover a locally administered switch after a failed change. That different feature is verified by observe whether a newly discovered serial number becomes authorized without manual action; for “Restore the saved standalone configuration locally” on a switch serving a high-density endpoint area, the relevant evidence is to inspect the restored local settings and confirm there is no controller configuration conflict.
Question 284
At the operations center, a dashboard shows ordinary link-up state, but the team also needs proof for “Restore the saved standalone configuration locally.” Which targeted check should be used?
- Check the backup file timestamp and availability before starting maintenance
- Inspect the neighbor-detection method and observed adjacency in the active FortiLink connection
- Inspect enabled administrative protocols and test reachability from an approved source
- Inspect the restored local settings and confirm there is no controller configuration conflict
- Inspect the switch-controller managed-switch list before editing the target unit
Explanation
Correct Answer
D:This is the precise control because standalone backup/restore reloads a saved device configuration rather than rebuilding a FortiGate-managed object. Directly measuring that result demonstrates whether the step to recover a locally administered switch after a failed change succeeded on a managed switch running FortiSwitchOS 7.6.
Incorrect Answers
A:The proposed check concerns “Back up FortiSwitch configuration before upgrades” rather than “Restore the saved standalone configuration locally”: a configuration export preserves management settings independently of the device's current runtime state. For “Restore the saved standalone configuration locally” on a managed switch running FortiSwitchOS 7.6, a better test would be to inspect the restored local settings and confirm there is no controller configuration conflict, which targets recover a locally administered switch after a failed change rather than the alternative diagnostic “Back up FortiSwitch configuration before upgrades”.
B:The proposed check concerns “Enable neighbor detection appropriate for the FortiLink deployment” rather than “Restore the saved standalone configuration locally”: FortiLink discovery uses configured neighbor detection; FortiOS 7.6.1 uses LLDP as its default method. For “Restore the saved standalone configuration locally” on a managed switch running FortiSwitchOS 7.6, a better test would be to inspect the restored local settings and confirm there is no controller configuration conflict, which targets recover a locally administered switch after a failed change rather than the alternative diagnostic “Enable neighbor detection appropriate for the FortiLink deployment”.
C:This check is suited to “Restrict administrative protocols on switch management interfaces” when trying to reduce exposure of the switch control plane to unauthorized clients, not to verify “Restore the saved standalone configuration locally” at the operations center. Checking “Restore the saved standalone configuration locally” at the operations center requires evidence of its own mechanism: standalone backup/restore reloads a saved device configuration rather than rebuilding a FortiGate-managed object; that is not the outcome measured by “Restrict administrative protocols on switch management interfaces”.
E:This check is suited to “Use the FortiGate switch-controller GUI” when trying to perform routine managed-switch edits through the centralized user interface, not to verify “Restore the saved standalone configuration locally” at the operations center. Checking “Restore the saved standalone configuration locally” at the operations center requires evidence of its own mechanism: standalone backup/restore reloads a saved device configuration rather than rebuilding a FortiGate-managed object; that is not the outcome measured by “Use the FortiGate switch-controller GUI”.
Question 285
A peer review of the warehouse asks how the design will retain required VLAN or port values when converting administration mode. Which FortiSwitch technique is the correct response?
- Apply FortiSwitch port configuration from FortiGate
- Enable neighbor detection appropriate for the FortiLink deployment
- Migrate standalone settings with an approved script
- Enable automatic FortiSwitch authorization where appropriate
Explanation
Correct Answer
C:The implementation works because a migration script can translate and reapply supported standalone settings for managed deployment. This distinction is material to the warehouse, where the stated goal is to retain required VLAN or port values when converting administration mode.
Incorrect Answers
A:For the warehouse, “Apply FortiSwitch port configuration from FortiGate” is a different type of control from “Migrate standalone settings with an approved script”: 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 retain required VLAN or port values when converting administration mode.
B:Compared with the requested “Migrate standalone settings with an approved script” at the warehouse, this would make discovery consistent with the actual supported port and neighbor behavior instead: FortiLink discovery uses configured neighbor detection; FortiOS 7.6.1 uses LLDP as its default method. At the warehouse, the operational proof would instead be to diff the required old settings against the resulting controller-managed configuration, whereas “Enable neighbor detection appropriate for the FortiLink deployment” is validated by a different test: inspect the neighbor-detection method and observed adjacency in the active FortiLink connection.
D:Compared with the requested “Migrate standalone settings with an approved script” at the warehouse, 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 warehouse, the operational proof would instead be to diff the required old settings against the resulting controller-managed configuration, 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.
Question 286
For the headquarters, an administrator applies the action “Migrate standalone settings with an approved script.” Which effect should appear when it operates as intended?
- Discovery-capable ports advertise and detect controller connectivity without preprogramming the full local switch
- A configuration export preserves management settings independently of the device's current runtime state
- The GUI presents managed-switch topology, port settings and status in the controller context
- A migration script can translate and reapply supported standalone settings for managed deployment
Explanation
Correct Answer
D:Given the described goal, the configured operation is meant to retain required VLAN or port values when converting administration mode. The most relevant validation is to diff the required old settings against the resulting controller-managed configuration for the equipment at the headquarters.
Incorrect Answers
A:That behavior applies when engineers “Use a supported auto-discovery FortiSwitch port”; the different operation “Migrate standalone settings with an approved script” is intended to retain required VLAN or port values when converting administration mode. That different feature is verified by check the port's model-dependent auto-discovery support and switch discovery event; for “Migrate standalone settings with an approved script” on an endpoint-facing FortiSwitch port, the relevant evidence is to diff the required old settings against the resulting controller-managed configuration.
B:That behavior applies when engineers “Back up FortiSwitch configuration before upgrades”; the different operation “Migrate standalone settings with an approved script” is intended to retain required VLAN or port values when converting administration mode. That different feature is verified by check the backup file timestamp and availability before starting maintenance; for “Migrate standalone settings with an approved script” on an endpoint-facing FortiSwitch port, the relevant evidence is to diff the required old settings against the resulting controller-managed configuration.
C:This outcome would be relevant to “Use the FortiGate switch-controller GUI” at the headquarters, not the task “Migrate standalone settings with an approved script”; the other task is to perform routine managed-switch edits through the centralized user interface. The action “Migrate standalone settings with an approved script” targets a different result: a migration script can translate and reapply supported standalone settings for managed deployment; the proposed alternative would instead be checked by inspect the switch-controller managed-switch list before editing the target unit.
Question 287
A FortiSwitch engineer in the hospital wing is documenting successful operation of “Migrate standalone settings with an approved script.” Which measurement or inspection confirms it?
- Compare controller-configured port values with device status and sync indicators
- Check the collector for test link or authentication events with correct timestamps
- Diff the required old settings against the resulting controller-managed configuration
- Confirm device registration, service connectivity and cloud-visible online state
- Compare the exact SKU and FortiSwitchOS release against the target feature documentation
Explanation
Correct Answer
C:The switch behavior that matters is: a migration script can translate and reapply supported standalone settings for managed deployment. Directly measuring that result demonstrates whether the step to retain required VLAN or port values when converting administration mode succeeded on a recently upgraded FortiSwitch.
Incorrect Answers
A:The proposed check concerns “Check managed-switch configuration synchronization” rather than “Migrate standalone settings with an approved script”: synchronization status identifies divergence between controller intent and provisioned switch state. For “Migrate standalone settings with an approved script” on a recently upgraded FortiSwitch, a better test would be to diff the required old settings against the resulting controller-managed configuration, which targets retain required VLAN or port values when converting administration mode rather than the alternative diagnostic “Check managed-switch configuration synchronization”.
B: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 “Migrate standalone settings with an approved script” at the hospital wing. Checking “Migrate standalone settings with an approved script” at the hospital wing requires evidence of its own mechanism: a migration script can translate and reapply supported standalone settings for managed deployment; that is not the outcome measured by “Send operational messages to an external syslog collector”.
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 “Migrate standalone settings with an approved script” at the hospital wing. Checking “Migrate standalone settings with an approved script” at the hospital wing requires evidence of its own mechanism: a migration script can translate and reapply supported standalone settings for managed deployment; that is not the outcome measured by “Use FortiEdge Cloud management for a supported switch”.
E:The proposed check concerns “Check supported model and feature availability before provisioning” rather than “Migrate standalone settings with an approved script”: supported capabilities vary by model and hardware; validating the feature matrix prevents invalid configuration assumptions. For “Migrate standalone settings with an approved script” on a recently upgraded FortiSwitch, a better test would be to diff the required old settings against the resulting controller-managed configuration, which targets retain required VLAN or port values when converting administration mode rather than the alternative diagnostic “Check supported model and feature availability before provisioning”.
Question 288
A production incident in the training center reveals the need to replace independent local administration with centralized provisioning. Which targeted FortiSwitch setting or method should the team use?
- Migrate a standalone FortiSwitch into FortiGate management
- Assign a reachable FortiLink interface IP subnet
- Use FortiGate switch-controller CLI
- Perform a centrally coordinated FortiSwitch firmware update
Explanation
Correct Answer
A:At this network boundary, the migration sequence transfers supported switch settings into the FortiGate management context. The operator can test this claim by the specific check: confirm the switch is authorized and that critical port/VLAN values match the intended migration.
Incorrect Answers
B:Compared with the requested “Migrate a standalone FortiSwitch into FortiGate management” at the training center, this would support switch-controller management communication over the FortiLink connection instead: the controller interface provides management addressing and reachability for connected managed units. At the training center, the operational proof would instead be to confirm the switch is authorized and that critical port/VLAN values match the intended migration, whereas “Assign a reachable FortiLink interface IP subnet” is validated by a different test: examine controller interface IP settings and switch management address assignment.
C:Compared with the requested “Migrate a standalone FortiSwitch into FortiGate management” at the training center, this would carry out a repeatable centrally managed configuration using commands instead: the controller CLI provides managed-switch objects and port settings that can be provisioned to switches. At the training center, the operational proof would instead be to confirm the switch is authorized and that critical port/VLAN values match the intended migration, whereas “Use FortiGate switch-controller CLI” is validated by a different test: review the controller's managed-switch configuration and ensuing synchronization status.
D:For the training center, “Perform a centrally coordinated FortiSwitch firmware update” is a different type of control from “Migrate a standalone FortiSwitch into FortiGate management”: firmware maintenance for managed switches should be coordinated through the FortiGate management workflow. Unlike the requested feature, that setting addresses the need to keep controller-managed units on a planned supported release, not the objective to replace independent local administration with centralized provisioning.
Question 289
On a switch linked to a FortiGate running FortiOS 7.6, “Migrate a standalone FortiSwitch into FortiGate management” is configured for the lab. What effect should an administrator expect without assuming unrelated features are enabled?
- Standalone backup/restore reloads a saved device configuration rather than rebuilding a FortiGate-managed object
- Controller and Fabric integration correlate switch topology and endpoint observations with FortiGate management
- A unique hardware serial number identifies the FortiSwitch object managed by the controller
- The migration sequence transfers supported switch settings into the FortiGate management context
Explanation
Correct Answer
D:In this deployment, the configured operation is meant to replace independent local administration with centralized provisioning. The most relevant validation is to confirm the switch is authorized and that critical port/VLAN values match the intended migration for the equipment at the lab.
Incorrect Answers
A:That behavior applies when engineers “Restore the saved standalone configuration locally”; the different operation “Migrate a standalone FortiSwitch into FortiGate management” is intended to replace independent local administration with centralized provisioning. That different feature is verified by inspect the restored local settings and confirm there is no controller configuration conflict; for “Migrate a standalone FortiSwitch into FortiGate management” on a switch linked to a FortiGate running FortiOS 7.6, the relevant evidence is to confirm the switch is authorized and that critical port/VLAN values match the intended migration.
B:That behavior applies when engineers “Integrate switch status with the Security Fabric”; the different operation “Migrate a standalone FortiSwitch into FortiGate management” is intended to replace independent local administration with centralized provisioning. That different feature is verified by look for switch presence and expected topology information in the Fabric view; for “Migrate a standalone FortiSwitch into FortiGate management” on a switch linked to a FortiGate running FortiOS 7.6, the relevant evidence is to confirm the switch is authorized and that critical port/VLAN values match the intended migration.
C:This outcome would be relevant to “Review FortiSwitch serial number during onboarding” at the lab, not the task “Migrate a standalone FortiSwitch into FortiGate management”; the other task is to avoid configuring a similarly named but different discovered unit. The action “Migrate a standalone FortiSwitch into FortiGate management” targets a different result: the migration sequence transfers supported switch settings into the FortiGate management context; the proposed alternative would instead be checked by match the serial in the physical inventory with the FortiGate discovery listing.
Question 290
After the team configures “Migrate a standalone FortiSwitch into FortiGate management” on a switch serving a high-density endpoint area, which TWO claims about the configuration are valid? (Choose TWO.)
- FortiLink discovery uses configured neighbor detection; FortiOS 7.6.1 uses LLDP as its default method
- The migration sequence transfers supported switch settings into the FortiGate management context
- The FortiLink controller can authorize discovered devices automatically when that setting is enabled
- Confirm the switch is authorized and that critical port/VLAN values match the intended migration
- Management-access settings decide which administrative services are accepted on an interface
Explanation
Correct Answers
B:For the stated requirement, the described mechanism corresponds to the operation that administrators use to replace independent local administration with centralized provisioning. The result should be observable on a switch serving a high-density endpoint area.
D:The stated check directly tests whether the intended function is active at the media studio. It provides evidence about “Migrate a standalone FortiSwitch into FortiGate management” beyond ordinary link-up state on a switch serving a high-density endpoint area.
Incorrect Answers
A:That characteristic reflects “Enable neighbor detection appropriate for the FortiLink deployment” rather than “Migrate a standalone FortiSwitch into FortiGate management” at the media studio. Its actual role is to make discovery consistent with the actual supported port and neighbor behavior, a different configuration need.
C:That characteristic reflects “Enable automatic FortiSwitch authorization where appropriate” rather than “Migrate a standalone FortiSwitch into FortiGate management” at the media studio. Its actual role is to reduce manual approvals for trusted units on a controlled provisioning network, a different configuration need.
E:That characteristic reflects “Restrict administrative protocols on switch management interfaces” rather than “Migrate a standalone FortiSwitch into FortiGate management” at the media studio. Its actual role is to reduce exposure of the switch control plane to unauthorized clients, a different configuration need.