Question 260
At the campus, a dashboard shows ordinary link-up state, but the team also needs proof for “Use a supported auto-discovery FortiSwitch port.” Which targeted check should be used?
- Inspect the switch-controller managed-switch list before editing the target unit
- Confirm the intended serial number is no longer authorized and review the deauthorization policy
- Check the port's model-dependent auto-discovery support and switch discovery event
- Inspect the interface's FortiLink dedication and switch discovery on the connected port
Explanation
Correct Answer
C:This is the precise control because discovery-capable ports advertise and detect controller connectivity without preprogramming the full local switch. Directly measuring that result demonstrates whether the step to allow an unconfigured switch to find its FortiLink controller during installation succeeded on a staging FortiSwitch.
Incorrect Answers
A: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 “Use a supported auto-discovery FortiSwitch port” at the campus. Checking “Use a supported auto-discovery FortiSwitch port” at the campus requires evidence of its own mechanism: discovery-capable ports advertise and detect controller connectivity without preprogramming the full local switch; that is not the outcome measured by “Use the FortiGate switch-controller GUI”.
B:This check is suited to “Deauthorize a retired managed switch deliberately” when trying to remove an old device from centralized switch management without accidentally changing a replacement unit, not to verify “Use a supported auto-discovery FortiSwitch port” at the campus. Checking “Use a supported auto-discovery FortiSwitch port” at the campus requires evidence of its own mechanism: discovery-capable ports advertise and detect controller connectivity without preprogramming the full local switch; that is not the outcome measured by “Deauthorize a retired managed switch deliberately”.
D:The proposed check concerns “Mark a FortiGate interface as dedicated to FortiSwitch” rather than “Use a supported auto-discovery FortiSwitch port”: FortiLink enablement distinguishes the switch-controller link from an ordinary production interface. For “Use a supported auto-discovery FortiSwitch port” on a staging FortiSwitch, a better test would be to check the port's model-dependent auto-discovery support and switch discovery event, which targets allow an unconfigured switch to find its FortiLink controller during installation rather than the alternative diagnostic “Mark a FortiGate interface as dedicated to FortiSwitch”.
Question 261
A network architect documents a single goal for a newly commissioned floor switch: support switch-controller management communication over the FortiLink connection. Which listed procedure provides that capability?
- Migrate a standalone FortiSwitch into FortiGate management
- Select a FortiSwitch profile with a managed admin password
- Assign a reachable FortiLink interface IP subnet
- Apply an administrative access profile
Explanation
Correct Answer
C:The implementation works because the controller interface provides management addressing and reachability for connected managed units. This distinction is material to the remote depot, where the stated goal is to support switch-controller management communication over the FortiLink connection.
Incorrect Answers
A:Compared with the requested “Assign a reachable FortiLink interface IP subnet” at the remote depot, this would replace independent local administration with centralized provisioning instead: the migration sequence transfers supported switch settings into the FortiGate management context. At the remote depot, the operational proof would instead be to examine controller interface IP settings and switch management address assignment, 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.
B:For the remote depot, “Select a FortiSwitch profile with a managed admin password” is a different type of control from “Assign a reachable FortiLink interface IP subnet”: FortiGate switch profiles can set managed switch administrative credentials centrally. Unlike the requested feature, that setting addresses the need to give authorized operators controlled switch access without depending on an empty local password, not the objective to support switch-controller management communication over the FortiLink connection.
D:Compared with the requested “Assign a reachable FortiLink interface IP subnet” at the remote depot, this would limit which administrators can change switch management and networking features instead: role or access profiles restrict management menus and configuration privileges. At the remote depot, the operational proof would instead be to examine controller interface IP settings and switch management address assignment, whereas “Apply an administrative access profile” is validated by a different test: test which GUI menus and CLI commands are available to the assigned administrator.
Question 262
The operator has decided to assign a reachable FortiLink interface IP subnet on a local switch administering branch clients at the lab. Which operational behavior is the most reasonable expectation of that specific feature?
- The GUI presents managed-switch topology, port settings and status in the controller context
- FortiLink enablement distinguishes the switch-controller link from an ordinary production interface
- The migration sequence transfers supported switch settings into the FortiGate management context
- The controller interface provides management addressing and reachability for connected managed units
- Controller deauthorization changes the authorization relationship and may affect switch reset or password retention
- SNMP provides structured operational measurements without becoming the forwarding control plane
Explanation
Correct Answer
D:Given the described goal, the configured operation is meant to support switch-controller management communication over the FortiLink connection. The most relevant validation is to examine controller interface IP settings and switch management address assignment for the equipment at the lab.
Incorrect Answers
A:That behavior applies when engineers “Use the FortiGate switch-controller GUI”; the different operation “Assign a reachable FortiLink interface IP subnet” is intended to support switch-controller management communication over the FortiLink connection. That different feature is verified by inspect the switch-controller managed-switch list before editing the target unit; for “Assign a reachable FortiLink interface IP subnet” on a local switch administering branch clients, the relevant evidence is to examine controller interface IP settings and switch management address assignment.
B:That behavior applies when engineers “Mark a FortiGate interface as dedicated to FortiSwitch”; the different operation “Assign a reachable FortiLink interface IP subnet” is intended to support switch-controller management communication over the FortiLink connection. That different feature is verified by inspect the interface's FortiLink dedication and switch discovery on the connected port; for “Assign a reachable FortiLink interface IP subnet” on a local switch administering branch clients, the relevant evidence is to examine controller interface IP settings and switch management address assignment.
C:This outcome would be relevant to “Migrate a standalone FortiSwitch into FortiGate management” at the lab, not the task “Assign a reachable FortiLink interface IP subnet”; the other task is to replace independent local administration with centralized provisioning. The action “Assign a reachable FortiLink interface IP subnet” targets a different result: the controller interface provides management addressing and reachability for connected managed units; the proposed alternative would instead be checked by confirm the switch is authorized and that critical port/VLAN values match the intended migration.
E:This outcome would be relevant to “Deauthorize a retired managed switch deliberately” at the lab, not the task “Assign a reachable FortiLink interface IP subnet”; the other task is to remove an old device from centralized switch management without accidentally changing a replacement unit. The action “Assign a reachable FortiLink interface IP subnet” targets a different result: the controller interface provides management addressing and reachability for connected managed units; the proposed alternative would instead be checked by confirm the intended serial number is no longer authorized and review the deauthorization policy.
F:That behavior applies when engineers “Configure remote monitoring through SNMP”; the different operation “Assign a reachable FortiLink interface IP subnet” is intended to support switch-controller management communication over the FortiLink connection. That different feature is verified by poll system and interface identifiers from the configured monitoring station; for “Assign a reachable FortiLink interface IP subnet” on a local switch administering branch clients, the relevant evidence is to examine controller interface IP settings and switch management address assignment.
Question 263
The change-control ticket for a switch used by multiple office teams requires one validation of the goal to support switch-controller management communication over the FortiLink connection. Which evidence should be collected?
- Examine controller interface IP settings and switch management address assignment
- Confirm local management access and that the unit is not assigned to a FortiGate controller
- Confirm device registration, service connectivity and cloud-visible online state
- Compare FortiGate and FortiSwitch system clocks and NTP association state
Explanation
Correct Answer
A:The switch behavior that matters is: the controller interface provides management addressing and reachability for connected managed units. Directly measuring that result demonstrates whether the step to support switch-controller management communication over the FortiLink connection succeeded on a switch used by multiple office teams.
Incorrect Answers
B:This check is suited to “Operate a FortiSwitch in standalone mode” when trying to manage a switch locally without delegating configuration to a FortiGate, not to verify “Assign a reachable FortiLink interface IP subnet” at the staging rack. Checking “Assign a reachable FortiLink interface IP subnet” at the staging rack requires evidence of its own mechanism: the controller interface provides management addressing and reachability for connected managed units; that is not the outcome measured by “Operate a FortiSwitch in standalone mode”.
C: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 “Assign a reachable FortiLink interface IP subnet” at the staging rack. Checking “Assign a reachable FortiLink interface IP subnet” at the staging rack requires evidence of its own mechanism: the controller interface provides management addressing and reachability for connected managed units; that is not the outcome measured by “Use FortiEdge Cloud management for a supported switch”.
D:The proposed check concerns “Enable time synchronization for managed units” rather than “Assign a reachable FortiLink interface IP subnet”: a reachable NTP source supplies consistent time to switch and controller management processes. For “Assign a reachable FortiLink interface IP subnet” on a switch used by multiple office teams, a better test would be to examine controller interface IP settings and switch management address assignment, which targets support switch-controller management communication over the FortiLink connection rather than the alternative diagnostic “Enable time synchronization for managed units”.
Question 264
The operational requirement for a production FortiSwitch fabric at the research building is to prevent clock drift from confusing authentication and event correlation. Which FortiSwitch choice directly targets it?
- Check managed-switch configuration synchronization
- Send operational messages to an external syslog collector
- Restore the saved standalone configuration locally
- Enable time synchronization for managed units
Explanation
Correct Answer
D:At this network boundary, a reachable NTP source supplies consistent time to switch and controller management processes. The operator can test this claim by the specific check: compare FortiGate and FortiSwitch system clocks and NTP association state.
Incorrect Answers
A:Compared with the requested “Enable time synchronization for managed units” at the research building, this would detect a switch that has not accepted the controller's latest changes instead: synchronization status identifies divergence between controller intent and provisioned switch state. At the research building, the operational proof would instead be to compare FortiGate and FortiSwitch system clocks and NTP association state, whereas “Check managed-switch configuration synchronization” is validated by a different test: compare controller-configured port values with device status and sync indicators.
B:For the research building, “Send operational messages to an external syslog collector” is a different type of control from “Enable time synchronization for managed units”: syslog forwarding exports event records to a reachable collector rather than changing packet forwarding. Unlike the requested feature, that setting addresses the need to retain switch events outside the device for investigation and retention, not the objective to prevent clock drift from confusing authentication and event correlation.
C:Compared with the requested “Enable time synchronization for managed units” at the research building, this would recover a locally administered switch after a failed change instead: standalone backup/restore reloads a saved device configuration rather than rebuilding a FortiGate-managed object. At the research building, the operational proof would instead be to compare FortiGate and FortiSwitch system clocks and NTP association state, whereas “Restore the saved standalone configuration locally” is validated by a different test: inspect the restored local settings and confirm there is no controller configuration conflict.
Question 265
A switch change for the clinic consists of this step: enable time synchronization for managed units. Which behavior reflects the purpose of that change?
- FortiGate pushes intended FortiSwitch configuration rather than relying on untracked local edits
- Controller authorization allows the FortiGate to provision and manage that switch via FortiLink
- Role or access profiles restrict management menus and configuration privileges
- FortiGate switch profiles can set managed switch administrative credentials centrally
- A reachable NTP source supplies consistent time to switch and controller management processes
Explanation
Correct Answer
E:In this deployment, the configured operation is meant to prevent clock drift from confusing authentication and event correlation. The most relevant validation is to compare FortiGate and FortiSwitch system clocks and NTP association state for the equipment at the clinic.
Incorrect Answers
A:That behavior applies when engineers “Apply FortiSwitch port configuration from FortiGate”; the different operation “Enable time synchronization for managed units” is intended to prevent clock drift from confusing authentication and event correlation. That different feature is verified by compare the controller's managed-port settings with the provisioned running state; for “Enable time synchronization for managed units” on a newly racked distribution unit, the relevant evidence is to compare FortiGate and FortiSwitch system clocks and NTP association state.
B:That behavior applies when engineers “Authorize a discovered FortiSwitch on FortiGate”; the different operation “Enable time synchronization for managed units” is intended to prevent clock drift from confusing authentication and event correlation. That different feature is verified by check the managed-switch inventory for an authorized state and configuration synchronization; for “Enable time synchronization for managed units” on a newly racked distribution unit, the relevant evidence is to compare FortiGate and FortiSwitch system clocks and NTP association state.
C:That behavior applies when engineers “Apply an administrative access profile”; the different operation “Enable time synchronization for managed units” is intended to prevent clock drift from confusing authentication and event correlation. That different feature is verified by test which GUI menus and CLI commands are available to the assigned administrator; for “Enable time synchronization for managed units” on a newly racked distribution unit, the relevant evidence is to compare FortiGate and FortiSwitch system clocks and NTP association state.
D:This outcome would be relevant to “Select a FortiSwitch profile with a managed admin password” at the clinic, not the task “Enable time synchronization for managed units”; the other task is to give authorized operators controlled switch access without depending on an empty local password. The action “Enable time synchronization for managed units” targets a different result: a reachable NTP source supplies consistent time to switch and controller management processes; the proposed alternative would instead be checked by verify the applied profile and successful login using the assigned administrator credentials.
Question 266
A feature acceptance test on two distribution switches concerns “Enable time synchronization for managed units.” What should be checked to establish its expected operation?
- Inspect the interface's FortiLink dedication and switch discovery on the connected port
- Compare FortiGate and FortiSwitch system clocks and NTP association state
- Inspect the switch-controller managed-switch list before editing the target unit
- Confirm the intended serial number is no longer authorized and review the deauthorization policy
Explanation
Correct Answer
B:For the stated requirement, a reachable NTP source supplies consistent time to switch and controller management processes. Directly measuring that result demonstrates whether the step to prevent clock drift from confusing authentication and event correlation succeeded on two distribution switches.
Incorrect Answers
A:The proposed check concerns “Mark a FortiGate interface as dedicated to FortiSwitch” rather than “Enable time synchronization for managed units”: FortiLink enablement distinguishes the switch-controller link from an ordinary production interface. For “Enable time synchronization for managed units” on two distribution switches, a better test would be to compare FortiGate and FortiSwitch system clocks and NTP association state, which targets prevent clock drift from confusing authentication and event correlation rather than the alternative diagnostic “Mark a FortiGate interface as dedicated to FortiSwitch”.
C: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 “Enable time synchronization for managed units” at the data hall. Checking “Enable time synchronization for managed units” at the data hall requires evidence of its own mechanism: a reachable NTP source supplies consistent time to switch and controller management processes; that is not the outcome measured by “Use the FortiGate switch-controller GUI”.
D:This check is suited to “Deauthorize a retired managed switch deliberately” when trying to remove an old device from centralized switch management without accidentally changing a replacement unit, not to verify “Enable time synchronization for managed units” at the data hall. Checking “Enable time synchronization for managed units” at the data hall requires evidence of its own mechanism: a reachable NTP source supplies consistent time to switch and controller management processes; that is not the outcome measured by “Deauthorize a retired managed switch deliberately”.
Question 267
The accepted design for the development floor requires the ability to keep managed port and VLAN settings under centralized change control. Which switch feature is the closest fit?
- Authorize a discovered FortiSwitch on FortiGate
- Select a FortiSwitch profile with a managed admin password
- Apply FortiSwitch port configuration from FortiGate
- Apply an administrative access profile
Explanation
Correct Answer
C:The deciding detail is that FortiGate pushes intended FortiSwitch configuration rather than relying on untracked local edits. This distinction is material to the development floor, where the stated goal is to keep managed port and VLAN settings under centralized change control.
Incorrect Answers
A:For the development floor, “Authorize a discovered FortiSwitch on FortiGate” is a different type of control from “Apply FortiSwitch port configuration from FortiGate”: controller authorization allows the FortiGate to provision and manage that switch via FortiLink. Unlike the requested feature, that setting addresses the need to move an already discovered unit into centrally managed service, not the objective to keep managed port and VLAN settings under centralized change control.
B:Compared with the requested “Apply FortiSwitch port configuration from FortiGate” at the development floor, 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 development floor, the operational proof would instead be to compare the controller's managed-port settings with the provisioned running state, whereas “Select a FortiSwitch profile with a managed admin password” is validated by a different test: verify the applied profile and successful login using the assigned administrator credentials.
D:Compared with the requested “Apply FortiSwitch port configuration from FortiGate” at the development floor, this would limit which administrators can change switch management and networking features instead: role or access profiles restrict management menus and configuration privileges. At the development floor, the operational proof would instead be to compare the controller's managed-port settings with the provisioned running state, whereas “Apply an administrative access profile” is validated by a different test: test which GUI menus and CLI commands are available to the assigned administrator.
Question 268
The operator has decided to apply FortiSwitch port configuration from FortiGate on a carefully segmented Layer 2 network at the conference venue. Which operational behavior is the most reasonable expectation of that specific feature?
- Controller deauthorization changes the authorization relationship and may affect switch reset or password retention
- FortiGate pushes intended FortiSwitch configuration rather than relying on untracked local edits
- FortiLink enablement distinguishes the switch-controller link from an ordinary production interface
- The GUI presents managed-switch topology, port settings and status in the controller context
Explanation
Correct Answer
B:The relevant mechanism is: the configured operation is meant to keep managed port and VLAN settings under centralized change control. The most relevant validation is to compare the controller's managed-port settings with the provisioned running state for the equipment at the conference venue.
Incorrect Answers
A:That behavior applies when engineers “Deauthorize a retired managed switch deliberately”; the different operation “Apply FortiSwitch port configuration from FortiGate” is intended to keep managed port and VLAN settings under centralized change control. That different feature is verified by confirm the intended serial number is no longer authorized and review the deauthorization policy; for “Apply FortiSwitch port configuration from FortiGate” on a carefully segmented Layer 2 network, the relevant evidence is to compare the controller's managed-port settings with the provisioned running state.
C:This outcome would be relevant to “Mark a FortiGate interface as dedicated to FortiSwitch” at the conference venue, not the task “Apply FortiSwitch port configuration from FortiGate”; the other task is to make a chosen Ethernet interface function as a FortiLink management attachment. The action “Apply FortiSwitch port configuration from FortiGate” targets a different result: FortiGate pushes intended FortiSwitch configuration rather than relying on untracked local edits; the proposed alternative would instead be checked by inspect the interface's FortiLink dedication and switch discovery on the connected port.
D:That behavior applies when engineers “Use the FortiGate switch-controller GUI”; the different operation “Apply FortiSwitch port configuration from FortiGate” is intended to keep managed port and VLAN settings under centralized change control. That different feature is verified by inspect the switch-controller managed-switch list before editing the target unit; for “Apply FortiSwitch port configuration from FortiGate” on a carefully segmented Layer 2 network, the relevant evidence is to compare the controller's managed-port settings with the provisioned running state.
Question 269
On a central switching stack at the hospital wing, the team reports that it has configured “Apply FortiSwitch port configuration from FortiGate.” Which verification provides the strongest direct evidence that the intended function is working?
- Examine controller interface IP settings and switch management address assignment
- Poll system and interface identifiers from the configured monitoring station
- Verify intended image version, upgrade status and post-reboot switch connectivity
- Compare the controller's managed-port settings with the provisioned running state
- Confirm device registration, service connectivity and cloud-visible online state
Explanation
Correct Answer
D:This approach fits because FortiGate pushes intended FortiSwitch configuration rather than relying on untracked local edits. Directly measuring that result demonstrates whether the step to keep managed port and VLAN settings under centralized change control succeeded on a central switching stack.
Incorrect Answers
A: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 “Apply FortiSwitch port configuration from FortiGate” at the hospital wing. Checking “Apply FortiSwitch port configuration from FortiGate” at the hospital wing requires evidence of its own mechanism: FortiGate pushes intended FortiSwitch configuration rather than relying on untracked local edits; that is not the outcome measured by “Assign a reachable FortiLink interface IP subnet”.
B:The proposed check concerns “Configure remote monitoring through SNMP” rather than “Apply FortiSwitch port configuration from FortiGate”: SNMP provides structured operational measurements without becoming the forwarding control plane. For “Apply FortiSwitch port configuration from FortiGate” on a central switching stack, a better test would be to compare the controller's managed-port settings with the provisioned running state, which targets keep managed port and VLAN settings under centralized change control rather than the alternative diagnostic “Configure remote monitoring through SNMP”.
C:This check is suited to “Perform a centrally coordinated FortiSwitch firmware update” when trying to keep controller-managed units on a planned supported release, not to verify “Apply FortiSwitch port configuration from FortiGate” at the hospital wing. Checking “Apply FortiSwitch port configuration from FortiGate” at the hospital wing requires evidence of its own mechanism: FortiGate pushes intended FortiSwitch configuration rather than relying on untracked local edits; that is not the outcome measured by “Perform a centrally coordinated FortiSwitch firmware update”.
E:The proposed check concerns “Use FortiEdge Cloud management for a supported switch” rather than “Apply FortiSwitch port configuration from FortiGate”: a cloud management workflow connects the registered switch to the appropriate Fortinet service. For “Apply FortiSwitch port configuration from FortiGate” on a central switching stack, a better test would be to compare the controller's managed-port settings with the provisioned running state, which targets keep managed port and VLAN settings under centralized change control rather than the alternative diagnostic “Use FortiEdge Cloud management for a supported switch”.
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.