Question 270
A deployment review at the training center identifies this objective: apply shared settings to several managed switches with related roles. Which FortiSwitch operation should be selected?
- Deauthorize a retired managed switch deliberately
- Configure remote monitoring through SNMP
- Mark a FortiGate interface as dedicated to FortiSwitch
- Create a FortiSwitch group for common administration
Explanation
Correct Answer
D:The critical distinction is that grouping units supports consistent profile or administrative treatment across selected devices. The operator can test this claim by the specific check: check each intended serial number's group membership and inherited configuration.
Incorrect Answers
A:Compared with the requested “Create a FortiSwitch group for common administration” at the training center, this would remove an old device from centralized switch management without accidentally changing a replacement unit instead: controller deauthorization changes the authorization relationship and may affect switch reset or password retention. At the training center, the operational proof would instead be to check each intended serial number's group membership and inherited configuration, whereas “Deauthorize a retired managed switch deliberately” is validated by a different test: confirm the intended serial number is no longer authorized and review the deauthorization policy.
B:Compared with the requested “Create a FortiSwitch group for common administration” at the training center, this would expose interface and switch health telemetry to an authorized monitoring collector instead: SNMP provides structured operational measurements without becoming the forwarding control plane. At the training center, the operational proof would instead be to check each intended serial number's group membership and inherited configuration, whereas “Configure remote monitoring through SNMP” is validated by a different test: poll system and interface identifiers from the configured monitoring station.
C:For the training center, “Mark a FortiGate interface as dedicated to FortiSwitch” is a different type of control from “Create a FortiSwitch group for common administration”: FortiLink enablement distinguishes the switch-controller link from an ordinary production interface. Unlike the requested feature, that setting addresses the need to make a chosen Ethernet interface function as a FortiLink management attachment, not the objective to apply shared settings to several managed switches with related roles.
Question 271
A switch change for the lab consists of this step: create a FortiSwitch group for common administration. Which behavior reflects the purpose of that change?
- Grouping units supports consistent profile or administrative treatment across selected devices
- A cloud management workflow connects the registered switch to the appropriate Fortinet service
- The controller interface provides management addressing and reachability for connected managed units
- Standalone mode exposes local configuration and administration on the switch itself
Explanation
Correct Answer
A:That setting is appropriate here because the configured operation is meant to apply shared settings to several managed switches with related roles. The most relevant validation is to check each intended serial number's group membership and inherited configuration for the equipment at the lab.
Incorrect Answers
B:That behavior applies when engineers “Use FortiEdge Cloud management for a supported switch”; the different operation “Create a FortiSwitch group for common administration” is intended to apply shared settings to several managed switches with related roles. That different feature is verified by confirm device registration, service connectivity and cloud-visible online state; for “Create a FortiSwitch group for common administration” on an access switch in routine maintenance, the relevant evidence is to check each intended serial number's group membership and inherited configuration.
C:This outcome would be relevant to “Assign a reachable FortiLink interface IP subnet” at the lab, not the task “Create a FortiSwitch group for common administration”; the other task is to support switch-controller management communication over the FortiLink connection. The action “Create a FortiSwitch group for common administration” targets a different result: grouping units supports consistent profile or administrative treatment across selected devices; the proposed alternative would instead be checked by examine controller interface IP settings and switch management address assignment.
D:That behavior applies when engineers “Operate a FortiSwitch in standalone mode”; the different operation “Create a FortiSwitch group for common administration” is intended to apply shared settings to several managed switches with related roles. That different feature is verified by confirm local management access and that the unit is not assigned to a FortiGate controller; for “Create a FortiSwitch group for common administration” on an access switch in routine maintenance, the relevant evidence is to check each intended serial number's group membership and inherited configuration.
Question 272
A post-change review at the staging rack must validate the implementation of “Create a FortiSwitch group for common administration.” What should the reviewer inspect first?
- Diff the required old settings against the resulting controller-managed configuration
- Check each intended serial number's group membership and inherited configuration
- Compare the controller's managed-port settings with the provisioned running state
- Match the serial in the physical inventory with the FortiGate discovery listing
Explanation
Correct Answer
B:This is the precise control because grouping units supports consistent profile or administrative treatment across selected devices. Directly measuring that result demonstrates whether the step to apply shared settings to several managed switches with related roles succeeded on a managed campus switch.
Incorrect Answers
A:The proposed check concerns “Migrate standalone settings with an approved script” rather than “Create a FortiSwitch group for common administration”: a migration script can translate and reapply supported standalone settings for managed deployment. For “Create a FortiSwitch group for common administration” on a managed campus switch, a better test would be to check each intended serial number's group membership and inherited configuration, which targets apply shared settings to several managed switches with related roles rather than the alternative diagnostic “Migrate standalone settings with an approved script”.
C:This check is suited to “Apply FortiSwitch port configuration from FortiGate” when trying to keep managed port and VLAN settings under centralized change control, not to verify “Create a FortiSwitch group for common administration” at the staging rack. Checking “Create a FortiSwitch group for common administration” at the staging rack requires evidence of its own mechanism: grouping units supports consistent profile or administrative treatment across selected devices; that is not the outcome measured by “Apply FortiSwitch port configuration from FortiGate”.
D:This check is suited to “Review FortiSwitch serial number during onboarding” when trying to avoid configuring a similarly named but different discovered unit, not to verify “Create a FortiSwitch group for common administration” at the staging rack. Checking “Create a FortiSwitch group for common administration” at the staging rack requires evidence of its own mechanism: grouping units supports consistent profile or administrative treatment across selected devices; that is not the outcome measured by “Review FortiSwitch serial number during onboarding”.
Question 273
On a recently upgraded FortiSwitch in the research building, the next task is to perform routine managed-switch edits through the centralized user interface. What is the appropriate configuration decision?
- Select a FortiSwitch profile with a managed admin password
- Migrate a standalone FortiSwitch into FortiGate management
- Use the FortiGate switch-controller GUI
- Create a FortiSwitch group for common administration
- Apply an administrative access profile
Explanation
Correct Answer
C:The implementation works because the GUI presents managed-switch topology, port settings and status in the controller context. This distinction is material to the research building, where the stated goal is to perform routine managed-switch edits through the centralized user interface.
Incorrect Answers
A:Compared with the requested “Use the FortiGate switch-controller GUI” at the research building, 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 research building, the operational proof would instead be to inspect the switch-controller managed-switch list before editing the target unit, 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.
B:Compared with the requested “Use the FortiGate switch-controller GUI” at the research building, this would replace independent local administration with centralized provisioning instead: the migration sequence transfers supported switch settings into the FortiGate management context. At the research building, the operational proof would instead be to inspect the switch-controller managed-switch list before editing the target unit, 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:Compared with the requested “Use the FortiGate switch-controller GUI” at the research building, 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 research building, the operational proof would instead be to inspect the switch-controller managed-switch list before editing the target unit, 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.
E:For the research building, “Apply an administrative access profile” is a different type of control from “Use the FortiGate switch-controller GUI”: 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 perform routine managed-switch edits through the centralized user interface.
Question 274
For the clinic, an administrator applies the action “Use the FortiGate switch-controller GUI.” Which effect should appear when it operates as intended?
- Controller deauthorization changes the authorization relationship and may affect switch reset or password retention
- The GUI presents managed-switch topology, port settings and status in the controller context
- SNMP provides structured operational measurements without becoming the forwarding control plane
- 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 perform routine managed-switch edits through the centralized user interface. The most relevant validation is to inspect the switch-controller managed-switch list before editing the target unit for the equipment at the clinic.
Incorrect Answers
A:That behavior applies when engineers “Deauthorize a retired managed switch deliberately”; the different operation “Use the FortiGate switch-controller GUI” is intended to perform routine managed-switch edits through the centralized user interface. That different feature is verified by confirm the intended serial number is no longer authorized and review the deauthorization policy; for “Use the FortiGate switch-controller GUI” on a staging FortiSwitch, the relevant evidence is to inspect the switch-controller managed-switch list before editing the target unit.
C:This outcome would be relevant to “Configure remote monitoring through SNMP” at the clinic, not the task “Use the FortiGate switch-controller GUI”; the other task is to expose interface and switch health telemetry to an authorized monitoring collector. The action “Use the FortiGate switch-controller GUI” targets a different result: the GUI presents managed-switch topology, port settings and status in the controller context; the proposed alternative would instead be checked by poll system and interface identifiers from the configured monitoring station.
D:That behavior applies when engineers “Perform a centrally coordinated FortiSwitch firmware update”; the different operation “Use the FortiGate switch-controller GUI” is intended to perform routine managed-switch edits through the centralized user interface. That different feature is verified by verify intended image version, upgrade status and post-reboot switch connectivity; for “Use the FortiGate switch-controller GUI” on a staging FortiSwitch, the relevant evidence is to inspect the switch-controller managed-switch list before editing the target unit.
Question 275
The work order to perform routine managed-switch edits through the centralized user interface is marked complete on a carefully segmented Layer 2 network. Which observation most directly tests the completed configuration?
- Look for switch presence and expected topology information in the Fabric view
- Examine controller interface IP settings and switch management address assignment
- Inspect the switch-controller managed-switch list before editing the target unit
- Confirm local management access and that the unit is not assigned to a FortiGate controller
Explanation
Correct Answer
C:The switch behavior that matters is: the GUI presents managed-switch topology, port settings and status in the controller context. Directly measuring that result demonstrates whether the step to perform routine managed-switch edits through the centralized user interface succeeded on a carefully segmented Layer 2 network.
Incorrect Answers
A:This check is suited to “Integrate switch status with the Security Fabric” when trying to provide visibility of managed access infrastructure in the Fortinet environment, not to verify “Use the FortiGate switch-controller GUI” at the data hall. Checking “Use the FortiGate switch-controller GUI” at the data hall requires evidence of its own mechanism: the GUI presents managed-switch topology, port settings and status in the controller context; that is not the outcome measured by “Integrate switch status with the Security Fabric”.
B:This check is suited to “Assign a reachable FortiLink interface IP subnet” when trying to support switch-controller management communication over the FortiLink connection, not to verify “Use the FortiGate switch-controller GUI” at the data hall. Checking “Use the FortiGate switch-controller GUI” at the data hall requires evidence of its own mechanism: the GUI presents managed-switch topology, port settings and status in the controller context; that is not the outcome measured by “Assign a reachable FortiLink interface IP subnet”.
D:The proposed check concerns “Operate a FortiSwitch in standalone mode” rather than “Use the FortiGate switch-controller GUI”: standalone mode exposes local configuration and administration on the switch itself. For “Use the FortiGate switch-controller GUI” on a carefully segmented Layer 2 network, a better test would be to inspect the switch-controller managed-switch list before editing the target unit, which targets perform routine managed-switch edits through the centralized user interface rather than the alternative diagnostic “Operate a FortiSwitch in standalone mode”.
Question 276
At the warehouse, a technician is choosing between several switching features to carry out a repeatable centrally managed configuration using commands. Which one belongs in the implementation plan?
- Perform a centrally coordinated FortiSwitch firmware update
- Configure remote monitoring through SNMP
- Assign a reachable FortiLink interface IP subnet
- Use FortiEdge Cloud management for a supported switch
- Use FortiGate switch-controller CLI
Explanation
Correct Answer
E:At this network boundary, the controller CLI provides managed-switch objects and port settings that can be provisioned to switches. The operator can test this claim by the specific check: review the controller's managed-switch configuration and ensuing synchronization status.
Incorrect Answers
A:For the warehouse, “Perform a centrally coordinated FortiSwitch firmware update” is a different type of control from “Use FortiGate switch-controller CLI”: 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 carry out a repeatable centrally managed configuration using commands.
B:Compared with the requested “Use FortiGate switch-controller CLI” at the warehouse, this would expose interface and switch health telemetry to an authorized monitoring collector instead: SNMP provides structured operational measurements without becoming the forwarding control plane. At the warehouse, the operational proof would instead be to review the controller's managed-switch configuration and ensuing synchronization status, whereas “Configure remote monitoring through SNMP” is validated by a different test: poll system and interface identifiers from the configured monitoring station.
C:Compared with the requested “Use FortiGate switch-controller CLI” at the warehouse, 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 warehouse, the operational proof would instead be to review the controller's managed-switch configuration and ensuing synchronization status, whereas “Assign a reachable FortiLink interface IP subnet” is validated by a different test: examine controller interface IP settings and switch management address assignment.
D:Compared with the requested “Use FortiGate switch-controller CLI” at the warehouse, this would administer an eligible cloud-managed FortiSwitch without relying on FortiLink to a local FortiGate instead: a cloud management workflow connects the registered switch to the appropriate Fortinet service. At the warehouse, the operational proof would instead be to review the controller's managed-switch configuration and ensuing synchronization status, whereas “Use FortiEdge Cloud management for a supported switch” is validated by a different test: confirm device registration, service connectivity and cloud-visible online state.
Question 277
On a FortiSwitch connected to the security edge, “Use FortiGate switch-controller CLI” is configured for the headquarters. 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
- The controller CLI provides managed-switch objects and port settings that can be provisioned to switches
- A unique hardware serial number identifies the FortiSwitch object managed by the controller
- Controller and Fabric integration correlate switch topology and endpoint observations with FortiGate management
Explanation
Correct Answer
B:In this deployment, the configured operation is meant to carry out a repeatable centrally managed configuration using commands. The most relevant validation is to review the controller's managed-switch configuration and ensuing synchronization status for the equipment at the headquarters.
Incorrect Answers
A:That behavior applies when engineers “Migrate standalone settings with an approved script”; the different operation “Use FortiGate switch-controller CLI” is intended to carry out a repeatable centrally managed configuration using commands. That different feature is verified by diff the required old settings against the resulting controller-managed configuration; for “Use FortiGate switch-controller CLI” on a FortiSwitch connected to the security edge, the relevant evidence is to review the controller's managed-switch configuration and ensuing synchronization status.
C:This outcome would be relevant to “Review FortiSwitch serial number during onboarding” at the headquarters, not the task “Use FortiGate switch-controller CLI”; the other task is to avoid configuring a similarly named but different discovered unit. The action “Use FortiGate switch-controller CLI” targets a different result: the controller CLI provides managed-switch objects and port settings that can be provisioned to switches; the proposed alternative would instead be checked by match the serial in the physical inventory with the FortiGate discovery listing.
D:That behavior applies when engineers “Integrate switch status with the Security Fabric”; the different operation “Use FortiGate switch-controller CLI” is intended to carry out a repeatable centrally managed configuration using commands. That different feature is verified by look for switch presence and expected topology information in the Fabric view; for “Use FortiGate switch-controller CLI” on a FortiSwitch connected to the security edge, the relevant evidence is to review the controller's managed-switch configuration and ensuing synchronization status.
Question 278
A technician says “Use FortiGate switch-controller CLI” has solved the issue at the hospital wing. Which diagnostic step would substantiate that claim?
- Observe whether a newly discovered serial number becomes authorized without manual action
- Review the controller's managed-switch configuration and ensuing synchronization status
- Inspect the neighbor-detection method and observed adjacency in the active FortiLink connection
- Inspect enabled administrative protocols and test reachability from an approved source
Explanation
Correct Answer
B:For the stated requirement, the controller CLI provides managed-switch objects and port settings that can be provisioned to switches. Directly measuring that result demonstrates whether the step to carry out a repeatable centrally managed configuration using commands succeeded on an access switch in routine maintenance.
Incorrect Answers
A: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 “Use FortiGate switch-controller CLI” at the hospital wing. Checking “Use FortiGate switch-controller CLI” at the hospital wing requires evidence of its own mechanism: the controller CLI provides managed-switch objects and port settings that can be provisioned to switches; that is not the outcome measured by “Enable automatic FortiSwitch authorization where appropriate”.
C:The proposed check concerns “Enable neighbor detection appropriate for the FortiLink deployment” rather than “Use FortiGate switch-controller CLI”: FortiLink discovery uses configured neighbor detection; FortiOS 7.6.1 uses LLDP as its default method. For “Use FortiGate switch-controller CLI” on an access switch in routine maintenance, a better test would be to review the controller's managed-switch configuration and ensuing synchronization status, which targets carry out a repeatable centrally managed configuration using commands rather than the alternative diagnostic “Enable neighbor detection appropriate for the FortiLink deployment”.
D: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 “Use FortiGate switch-controller CLI” at the hospital wing. Checking “Use FortiGate switch-controller CLI” at the hospital wing requires evidence of its own mechanism: the controller CLI provides managed-switch objects and port settings that can be provisioned to switches; that is not the outcome measured by “Restrict administrative protocols on switch management interfaces”.
Question 279
A switch rollout in the training center will be approved only if it can administer an eligible cloud-managed FortiSwitch without relying on FortiLink to a local FortiGate. Which administrative action meets this acceptance criterion?
- Apply FortiSwitch port configuration from FortiGate
- Enable neighbor detection appropriate for the FortiLink deployment
- Enable automatic FortiSwitch authorization where appropriate
- Use FortiEdge Cloud management for a supported switch
Explanation
Correct Answer
D:The deciding detail is that a cloud management workflow connects the registered switch to the appropriate Fortinet service. This distinction is material to the training center, where the stated goal is to administer an eligible cloud-managed FortiSwitch without relying on FortiLink to a local FortiGate.
Incorrect Answers
A:For the training center, “Apply FortiSwitch port configuration from FortiGate” is a different type of control from “Use FortiEdge Cloud management for a supported switch”: 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 administer an eligible cloud-managed FortiSwitch without relying on FortiLink to a local FortiGate.
B:Compared with the requested “Use FortiEdge Cloud management for a supported switch” at the training center, 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 training center, the operational proof would instead be to confirm device registration, service connectivity and cloud-visible online state, 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.
C:Compared with the requested “Use FortiEdge Cloud management for a supported switch” at the training center, 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 training center, the operational proof would instead be to confirm device registration, service connectivity and cloud-visible online state, 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 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.