Fortinet NSE5_FSW_AD-7.6 (Fortinet NSE 5 - FortiSwitch 7.6 Administrator) Practice Test 30

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.)

  1. FortiLink discovery uses configured neighbor detection; FortiOS 7.6.1 uses LLDP as its default method
  2. The migration sequence transfers supported switch settings into the FortiGate management context
  3. The FortiLink controller can authorize discovered devices automatically when that setting is enabled
  4. Confirm the switch is authorized and that critical port/VLAN values match the intended migration
  5. 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.

Question 291

The operational requirement for a managed switch running FortiSwitchOS 7.6 at the retail site is to make recovery possible if a firmware or policy change fails. Which FortiSwitch choice directly targets it?

  1. Back up FortiSwitch configuration before upgrades
  2. Apply FortiSwitch port configuration from FortiGate
  3. Enable automatic FortiSwitch authorization where appropriate
  4. Review FortiSwitch serial number during onboarding
  5. Enable neighbor detection appropriate for the FortiLink deployment
  6. Restore the saved standalone configuration locally

Explanation

Correct Answer

A:

The deciding detail is that a configuration export preserves management settings independently of the device's current runtime state. This distinction is material to the retail site, where the stated goal is to make recovery possible if a firmware or policy change fails.

Incorrect Answers

B:

For the retail site, “Apply FortiSwitch port configuration from FortiGate” is a different type of control from “Back up FortiSwitch configuration before upgrades”: FortiGate pushes intended FortiSwitch configuration rather than relying on untracked local edits. Unlike the requested feature, that setting addresses the need to keep managed port and VLAN settings under centralized change control, not the objective to make recovery possible if a firmware or policy change fails.

C:

Compared with the requested “Back up FortiSwitch configuration before upgrades” at the retail site, 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 retail site, the operational proof would instead be to check the backup file timestamp and availability before starting maintenance, 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.

D:

Compared with the requested “Back up FortiSwitch configuration before upgrades” at the retail site, this would avoid configuring a similarly named but different discovered unit instead: a unique hardware serial number identifies the FortiSwitch object managed by the controller. At the retail site, the operational proof would instead be to check the backup file timestamp and availability before starting maintenance, whereas “Review FortiSwitch serial number during onboarding” is validated by a different test: match the serial in the physical inventory with the FortiGate discovery listing.

E:

Compared with the requested “Back up FortiSwitch configuration before upgrades” at the retail site, 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 retail site, the operational proof would instead be to check the backup file timestamp and availability before starting maintenance, 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.

F:

Compared with the requested “Back up FortiSwitch configuration before upgrades” at the retail site, 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 retail site, the operational proof would instead be to check the backup file timestamp and availability before starting maintenance, 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 292

A change record for a remote FortiSwitch installation states “Back up FortiSwitch configuration before upgrades.” Which description correctly explains what this will accomplish?

  1. Discovery-capable ports advertise and detect controller connectivity without preprogramming the full local switch
  2. The GUI presents managed-switch topology, port settings and status in the controller context
  3. A configuration export preserves management settings independently of the device's current runtime state
  4. The migration sequence transfers supported switch settings into the FortiGate management context

Explanation

Correct Answer

C:

The relevant mechanism is: the configured operation is meant to make recovery possible if a firmware or policy change fails. The most relevant validation is to check the backup file timestamp and availability before starting maintenance for the equipment at the airport office.

Incorrect Answers

A:

That behavior applies when engineers “Use a supported auto-discovery FortiSwitch port”; the different operation “Back up FortiSwitch configuration before upgrades” is intended to make recovery possible if a firmware or policy change fails. That different feature is verified by check the port's model-dependent auto-discovery support and switch discovery event; for “Back up FortiSwitch configuration before upgrades” on a remote FortiSwitch installation, the relevant evidence is to check the backup file timestamp and availability before starting maintenance.

B:

This outcome would be relevant to “Use the FortiGate switch-controller GUI” at the airport office, not the task “Back up FortiSwitch configuration before upgrades”; the other task is to perform routine managed-switch edits through the centralized user interface. The action “Back up FortiSwitch configuration before upgrades” targets a different result: a configuration export preserves management settings independently of the device's current runtime state; 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 “Migrate a standalone FortiSwitch into FortiGate management”; the different operation “Back up FortiSwitch configuration before upgrades” is intended to make recovery possible if a firmware or policy change fails. That different feature is verified by confirm the switch is authorized and that critical port/VLAN values match the intended migration; for “Back up FortiSwitch configuration before upgrades” on a remote FortiSwitch installation, the relevant evidence is to check the backup file timestamp and availability before starting maintenance.

Question 293

On an endpoint-facing FortiSwitch port at the operations center, the team reports that it has configured “Back up FortiSwitch configuration before upgrades.” Which verification provides the strongest direct evidence that the intended function is working?

  1. Check the backup file timestamp and availability before starting maintenance
  2. Check the collector for test link or authentication events with correct timestamps
  3. Compare controller-configured port values with device status and sync indicators
  4. Confirm device registration, service connectivity and cloud-visible online state

Explanation

Correct Answer

A:

This approach fits because a configuration export preserves management settings independently of the device's current runtime state. Directly measuring that result demonstrates whether the step to make recovery possible if a firmware or policy change fails succeeded on an endpoint-facing FortiSwitch port.

Incorrect Answers

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 “Back up FortiSwitch configuration before upgrades” at the operations center. Checking “Back up FortiSwitch configuration before upgrades” at the operations center requires evidence of its own mechanism: a configuration export preserves management settings independently of the device's current runtime state; that is not the outcome measured by “Send operational messages to an external syslog collector”.

C:

The proposed check concerns “Check managed-switch configuration synchronization” rather than “Back up FortiSwitch configuration before upgrades”: synchronization status identifies divergence between controller intent and provisioned switch state. For “Back up FortiSwitch configuration before upgrades” on an endpoint-facing FortiSwitch port, a better test would be to check the backup file timestamp and availability before starting maintenance, which targets make recovery possible if a firmware or policy change fails rather than the alternative diagnostic “Check managed-switch configuration synchronization”.

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 “Back up FortiSwitch configuration before upgrades” at the operations center. Checking “Back up FortiSwitch configuration before upgrades” at the operations center requires evidence of its own mechanism: a configuration export preserves management settings independently of the device's current runtime state; that is not the outcome measured by “Use FortiEdge Cloud management for a supported switch”.

Question 294

During a change window in the warehouse, engineers are asked to keep controller-managed units on a planned supported release. What should they configure rather than using a feature for an adjacent purpose?

  1. Apply an administrative access profile
  2. Create a FortiSwitch group for common administration
  3. Perform a centrally coordinated FortiSwitch firmware update
  4. Migrate standalone settings with an approved script

Explanation

Correct Answer

C:

The critical distinction is that firmware maintenance for managed switches should be coordinated through the FortiGate management workflow. The operator can test this claim by the specific check: verify intended image version, upgrade status and post-reboot switch connectivity.

Incorrect Answers

A:

For the warehouse, “Apply an administrative access profile” is a different type of control from “Perform a centrally coordinated FortiSwitch firmware update”: 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 keep controller-managed units on a planned supported release.

B:

Compared with the requested “Perform a centrally coordinated FortiSwitch firmware update” at the warehouse, 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 warehouse, the operational proof would instead be to verify intended image version, upgrade status and post-reboot switch connectivity, 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.

D:

Compared with the requested “Perform a centrally coordinated FortiSwitch firmware update” at the warehouse, this would retain required VLAN or port values when converting administration mode instead: a migration script can translate and reapply supported standalone settings for managed deployment. At the warehouse, the operational proof would instead be to verify intended image version, upgrade status and post-reboot switch connectivity, whereas “Migrate standalone settings with an approved script” is validated by a different test: diff the required old settings against the resulting controller-managed configuration.

Question 295

An operations log records this activity at the headquarters: perform a centrally coordinated FortiSwitch firmware update. Which result is specifically attributable to that action?

  1. Controller deauthorization changes the authorization relationship and may affect switch reset or password retention
  2. Firmware maintenance for managed switches should be coordinated through the FortiGate management workflow
  3. SNMP provides structured operational measurements without becoming the forwarding control plane
  4. A configuration export preserves management settings independently of the device's current runtime state
  5. FortiLink enablement distinguishes the switch-controller link from an ordinary production interface

Explanation

Correct Answer

B:

That setting is appropriate here because the configured operation is meant to keep controller-managed units on a planned supported release. The most relevant validation is to verify intended image version, upgrade status and post-reboot switch connectivity for the equipment at the headquarters.

Incorrect Answers

A:

That behavior applies when engineers “Deauthorize a retired managed switch deliberately”; the different operation “Perform a centrally coordinated FortiSwitch firmware update” is intended to keep controller-managed units on a planned supported release. That different feature is verified by confirm the intended serial number is no longer authorized and review the deauthorization policy; for “Perform a centrally coordinated FortiSwitch firmware update” on a newly commissioned floor switch, the relevant evidence is to verify intended image version, upgrade status and post-reboot switch connectivity.

C:

This outcome would be relevant to “Configure remote monitoring through SNMP” at the headquarters, not the task “Perform a centrally coordinated FortiSwitch firmware update”; the other task is to expose interface and switch health telemetry to an authorized monitoring collector. The action “Perform a centrally coordinated FortiSwitch firmware update” targets a different result: firmware maintenance for managed switches should be coordinated through the FortiGate management workflow; the proposed alternative would instead be checked by poll system and interface identifiers from the configured monitoring station.

D:

That behavior applies when engineers “Back up FortiSwitch configuration before upgrades”; the different operation “Perform a centrally coordinated FortiSwitch firmware update” is intended to keep controller-managed units on a planned supported release. That different feature is verified by check the backup file timestamp and availability before starting maintenance; for “Perform a centrally coordinated FortiSwitch firmware update” on a newly commissioned floor switch, the relevant evidence is to verify intended image version, upgrade status and post-reboot switch connectivity.

E:

That behavior applies when engineers “Mark a FortiGate interface as dedicated to FortiSwitch”; the different operation “Perform a centrally coordinated FortiSwitch firmware update” is intended to keep controller-managed units on a planned supported release. That different feature is verified by inspect the interface's FortiLink dedication and switch discovery on the connected port; for “Perform a centrally coordinated FortiSwitch firmware update” on a newly commissioned floor switch, the relevant evidence is to verify intended image version, upgrade status and post-reboot switch connectivity.

Question 296

A post-change review at the hospital wing must validate the implementation of “Perform a centrally coordinated FortiSwitch firmware update.” What should the reviewer inspect first?

  1. Examine controller interface IP settings and switch management address assignment
  2. Confirm local management access and that the unit is not assigned to a FortiGate controller
  3. Look for switch presence and expected topology information in the Fabric view
  4. Verify intended image version, upgrade status and post-reboot switch connectivity

Explanation

Correct Answer

D:

This is the precise control because firmware maintenance for managed switches should be coordinated through the FortiGate management workflow. Directly measuring that result demonstrates whether the step to keep controller-managed units on a planned supported release succeeded on a local switch administering branch clients.

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 “Perform a centrally coordinated FortiSwitch firmware update” at the hospital wing. Checking “Perform a centrally coordinated FortiSwitch firmware update” at the hospital wing requires evidence of its own mechanism: firmware maintenance for managed switches should be coordinated through the FortiGate management workflow; that is not the outcome measured by “Assign a reachable FortiLink interface IP subnet”.

B:

The proposed check concerns “Operate a FortiSwitch in standalone mode” rather than “Perform a centrally coordinated FortiSwitch firmware update”: standalone mode exposes local configuration and administration on the switch itself. For “Perform a centrally coordinated FortiSwitch firmware update” on a local switch administering branch clients, a better test would be to verify intended image version, upgrade status and post-reboot switch connectivity, which targets keep controller-managed units on a planned supported release rather than the alternative diagnostic “Operate a FortiSwitch in standalone mode”.

C:

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 “Perform a centrally coordinated FortiSwitch firmware update” at the hospital wing. Checking “Perform a centrally coordinated FortiSwitch firmware update” at the hospital wing requires evidence of its own mechanism: firmware maintenance for managed switches should be coordinated through the FortiGate management workflow; that is not the outcome measured by “Integrate switch status with the Security Fabric”.

Question 297

For the factory, the network team needs to detect a switch that has not accepted the controller's latest changes. Which change is the most direct way to implement that requirement on a switch used by multiple office teams?

  1. Use FortiGate switch-controller CLI
  2. Operate a FortiSwitch in standalone mode
  3. Assign a reachable FortiLink interface IP subnet
  4. Check managed-switch configuration synchronization

Explanation

Correct Answer

D:

The implementation works because synchronization status identifies divergence between controller intent and provisioned switch state. This distinction is material to the factory, where the stated goal is to detect a switch that has not accepted the controller's latest changes.

Incorrect Answers

A:

For the factory, “Use FortiGate switch-controller CLI” is a different type of control from “Check managed-switch configuration synchronization”: the controller CLI provides managed-switch objects and port settings that can be provisioned to switches. Unlike the requested feature, that setting addresses the need to carry out a repeatable centrally managed configuration using commands, not the objective to detect a switch that has not accepted the controller's latest changes.

B:

Compared with the requested “Check managed-switch configuration synchronization” at the factory, 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 factory, the operational proof would instead be to compare controller-configured port values with device status and sync indicators, 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.

C:

Compared with the requested “Check managed-switch configuration synchronization” at the factory, 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 factory, the operational proof would instead be to compare controller-configured port values with device status and sync indicators, whereas “Assign a reachable FortiLink interface IP subnet” is validated by a different test: examine controller interface IP settings and switch management address assignment.

Question 298

A change record for a production FortiSwitch fabric states “Check managed-switch configuration synchronization.” Which description correctly explains what this will accomplish?

  1. FortiGate pushes intended FortiSwitch configuration rather than relying on untracked local edits
  2. A unique hardware serial number identifies the FortiSwitch object managed by the controller
  3. Controller and Fabric integration correlate switch topology and endpoint observations with FortiGate management
  4. Standalone backup/restore reloads a saved device configuration rather than rebuilding a FortiGate-managed object
  5. Synchronization status identifies divergence between controller intent and provisioned switch state

Explanation

Correct Answer

E:

Given the described goal, the configured operation is meant to detect a switch that has not accepted the controller's latest changes. The most relevant validation is to compare controller-configured port values with device status and sync indicators for the equipment at the distribution floor.

Incorrect Answers

A:

That behavior applies when engineers “Apply FortiSwitch port configuration from FortiGate”; the different operation “Check managed-switch configuration synchronization” is intended to detect a switch that has not accepted the controller's latest changes. That different feature is verified by compare the controller's managed-port settings with the provisioned running state; for “Check managed-switch configuration synchronization” on a production FortiSwitch fabric, the relevant evidence is to compare controller-configured port values with device status and sync indicators.

B:

That behavior applies when engineers “Review FortiSwitch serial number during onboarding”; the different operation “Check managed-switch configuration synchronization” is intended to detect a switch that has not accepted the controller's latest changes. That different feature is verified by match the serial in the physical inventory with the FortiGate discovery listing; for “Check managed-switch configuration synchronization” on a production FortiSwitch fabric, the relevant evidence is to compare controller-configured port values with device status and sync indicators.

C:

That behavior applies when engineers “Integrate switch status with the Security Fabric”; the different operation “Check managed-switch configuration synchronization” is intended to detect a switch that has not accepted the controller's latest changes. That different feature is verified by look for switch presence and expected topology information in the Fabric view; for “Check managed-switch configuration synchronization” on a production FortiSwitch fabric, the relevant evidence is to compare controller-configured port values with device status and sync indicators.

D:

This outcome would be relevant to “Restore the saved standalone configuration locally” at the distribution floor, not the task “Check managed-switch configuration synchronization”; the other task is to recover a locally administered switch after a failed change. The action “Check managed-switch configuration synchronization” targets a different result: synchronization status identifies divergence between controller intent and provisioned switch state; the proposed alternative would instead be checked by inspect the restored local settings and confirm there is no controller configuration conflict.

Question 299

An auditor wants operational evidence for the switch action “Check managed-switch configuration synchronization” at the media studio. Which check is relevant?

  1. Compare controller-configured port values with device status and sync indicators
  2. Confirm the switch is authorized and that critical port/VLAN values match the intended migration
  3. Inspect enabled administrative protocols and test reachability from an approved source
  4. Inspect the neighbor-detection method and observed adjacency in the active FortiLink connection

Explanation

Correct Answer

A:

The switch behavior that matters is: synchronization status identifies divergence between controller intent and provisioned switch state. Directly measuring that result demonstrates whether the step to detect a switch that has not accepted the controller's latest changes succeeded on a newly racked distribution unit.

Incorrect Answers

B:

This check is suited to “Migrate a standalone FortiSwitch into FortiGate management” when trying to replace independent local administration with centralized provisioning, not to verify “Check managed-switch configuration synchronization” at the media studio. Checking “Check managed-switch configuration synchronization” at the media studio requires evidence of its own mechanism: synchronization status identifies divergence between controller intent and provisioned switch state; that is not the outcome measured by “Migrate a standalone FortiSwitch into FortiGate management”.

C:

The proposed check concerns “Restrict administrative protocols on switch management interfaces” rather than “Check managed-switch configuration synchronization”: management-access settings decide which administrative services are accepted on an interface. For “Check managed-switch configuration synchronization” on a newly racked distribution unit, a better test would be to compare controller-configured port values with device status and sync indicators, which targets detect a switch that has not accepted the controller's latest changes rather than the alternative diagnostic “Restrict administrative protocols on switch management interfaces”.

D:

This check is suited to “Enable neighbor detection appropriate for the FortiLink deployment” when trying to make discovery consistent with the actual supported port and neighbor behavior, not to verify “Check managed-switch configuration synchronization” at the media studio. Checking “Check managed-switch configuration synchronization” at the media studio requires evidence of its own mechanism: synchronization status identifies divergence between controller intent and provisioned switch state; that is not the outcome measured by “Enable neighbor detection appropriate for the FortiLink deployment”.

Question 300

A network architect documents a single goal for an endpoint-facing FortiSwitch port: avoid configuring a similarly named but different discovered unit. Which listed procedure provides that capability?

  1. Use FortiEdge Cloud management for a supported switch
  2. Review FortiSwitch serial number during onboarding
  3. Enable time synchronization for managed units
  4. Authorize a discovered FortiSwitch on FortiGate

Explanation

Correct Answer

B:

At this network boundary, a unique hardware serial number identifies the FortiSwitch object managed by the controller. The operator can test this claim by the specific check: match the serial in the physical inventory with the FortiGate discovery listing.

Incorrect Answers

A:

For the retail site, “Use FortiEdge Cloud management for a supported switch” is a different type of control from “Review FortiSwitch serial number during onboarding”: a cloud management workflow connects the registered switch to the appropriate Fortinet service. Unlike the requested feature, that setting addresses the need to administer an eligible cloud-managed FortiSwitch without relying on FortiLink to a local FortiGate, not the objective to avoid configuring a similarly named but different discovered unit.

C:

Compared with the requested “Review FortiSwitch serial number during onboarding” at the retail site, this would prevent clock drift from confusing authentication and event correlation instead: a reachable NTP source supplies consistent time to switch and controller management processes. At the retail site, the operational proof would instead be to match the serial in the physical inventory with the FortiGate discovery listing, whereas “Enable time synchronization for managed units” is validated by a different test: compare FortiGate and FortiSwitch system clocks and NTP association state.

D:

Compared with the requested “Review FortiSwitch serial number during onboarding” at the retail site, this would move an already discovered unit into centrally managed service instead: controller authorization allows the FortiGate to provision and manage that switch via FortiLink. At the retail site, the operational proof would instead be to match the serial in the physical inventory with the FortiGate discovery listing, whereas “Authorize a discovered FortiSwitch on FortiGate” is validated by a different test: check the managed-switch inventory for an authorized state and configuration synchronization.

Fortinet NSE 5 - FortiSwitch 7.6 Administrator (NSE5_FSW_AD-7.6) Practice Tests