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

Question 310

When engineers configure remote monitoring through SNMP at the airport office, which forwarding, security, management or diagnostic outcome follows from that action?

  1. SNMP provides structured operational measurements without becoming the forwarding control plane
  2. A cloud management workflow connects the registered switch to the appropriate Fortinet service
  3. Controller authorization allows the FortiGate to provision and manage that switch via FortiLink
  4. A reachable NTP source supplies consistent time to switch and controller management processes

Explanation

Correct Answer

A:

Given the described goal, the configured operation is meant to expose interface and switch health telemetry to an authorized monitoring collector. The most relevant validation is to poll system and interface identifiers from the configured monitoring station for the equipment at the airport office.

Incorrect Answers

B:

That behavior applies when engineers “Use FortiEdge Cloud management for a supported switch”; the different operation “Configure remote monitoring through SNMP” is intended to expose interface and switch health telemetry to an authorized monitoring collector. That different feature is verified by confirm device registration, service connectivity and cloud-visible online state; for “Configure remote monitoring through SNMP” on a central switching stack, the relevant evidence is to poll system and interface identifiers from the configured monitoring station.

C:

That behavior applies when engineers “Authorize a discovered FortiSwitch on FortiGate”; the different operation “Configure remote monitoring through SNMP” is intended to expose interface and switch health telemetry to an authorized monitoring collector. That different feature is verified by check the managed-switch inventory for an authorized state and configuration synchronization; for “Configure remote monitoring through SNMP” on a central switching stack, the relevant evidence is to poll system and interface identifiers from the configured monitoring station.

D:

This outcome would be relevant to “Enable time synchronization for managed units” at the airport office, not the task “Configure remote monitoring through SNMP”; the other task is to prevent clock drift from confusing authentication and event correlation. The action “Configure remote monitoring through SNMP” targets a different result: SNMP provides structured operational measurements without becoming the forwarding control plane; the proposed alternative would instead be checked by compare FortiGate and FortiSwitch system clocks and NTP association state.

Question 311

A FortiSwitch engineer in the conference venue is documenting successful operation of “Configure remote monitoring through SNMP.” Which measurement or inspection confirms it?

  1. Diff the required old settings against the resulting controller-managed configuration
  2. Match the serial in the physical inventory with the FortiGate discovery listing
  3. Check each intended serial number's group membership and inherited configuration
  4. Poll system and interface identifiers from the configured monitoring station

Explanation

Correct Answer

D:

The switch behavior that matters is: SNMP provides structured operational measurements without becoming the forwarding control plane. Directly measuring that result demonstrates whether the step to expose interface and switch health telemetry to an authorized monitoring collector succeeded on a FortiSwitch connected to the security edge.

Incorrect Answers

A:

The proposed check concerns “Migrate standalone settings with an approved script” rather than “Configure remote monitoring through SNMP”: a migration script can translate and reapply supported standalone settings for managed deployment. For “Configure remote monitoring through SNMP” on a FortiSwitch connected to the security edge, a better test would be to poll system and interface identifiers from the configured monitoring station, which targets expose interface and switch health telemetry to an authorized monitoring collector rather than the alternative diagnostic “Migrate standalone settings with an approved script”.

B:

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 “Configure remote monitoring through SNMP” at the conference venue. Checking “Configure remote monitoring through SNMP” at the conference venue requires evidence of its own mechanism: SNMP provides structured operational measurements without becoming the forwarding control plane; that is not the outcome measured by “Review FortiSwitch serial number during onboarding”.

C:

This check is suited to “Create a FortiSwitch group for common administration” when trying to apply shared settings to several managed switches with related roles, not to verify “Configure remote monitoring through SNMP” at the conference venue. Checking “Configure remote monitoring through SNMP” at the conference venue requires evidence of its own mechanism: SNMP provides structured operational measurements without becoming the forwarding control plane; that is not the outcome measured by “Create a FortiSwitch group for common administration”.

Question 312

On an access switch in routine maintenance in the campus, the next task is to retain switch events outside the device for investigation and retention. What is the appropriate configuration decision?

  1. Send operational messages to an external syslog collector
  2. Integrate switch status with the Security Fabric
  3. Restore the saved standalone configuration locally
  4. Check managed-switch configuration synchronization

Explanation

Correct Answer

A:

At this network boundary, syslog forwarding exports event records to a reachable collector rather than changing packet forwarding. The operator can test this claim by the specific check: check the collector for test link or authentication events with correct timestamps.

Incorrect Answers

B:

For the campus, “Integrate switch status with the Security Fabric” is a different type of control from “Send operational messages to an external syslog collector”: controller and Fabric integration correlate switch topology and endpoint observations with FortiGate management. Unlike the requested feature, that setting addresses the need to provide visibility of managed access infrastructure in the Fortinet environment, not the objective to retain switch events outside the device for investigation and retention.

C:

Compared with the requested “Send operational messages to an external syslog collector” at the campus, 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 campus, the operational proof would instead be to check the collector for test link or authentication events with correct timestamps, 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.

D:

Compared with the requested “Send operational messages to an external syslog collector” at the campus, 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 campus, the operational proof would instead be to check the collector for test link or authentication events with correct timestamps, whereas “Check managed-switch configuration synchronization” is validated by a different test: compare controller-configured port values with device status and sync indicators.

Question 313

A colleague asks about the effect of “Send operational messages to an external syslog collector” on a newly racked distribution unit. Which behavior best characterizes that feature?

  1. Role or access profiles restrict management menus and configuration privileges
  2. FortiLink discovery uses configured neighbor detection; FortiOS 7.6.1 uses LLDP as its default method
  3. Syslog forwarding exports event records to a reachable collector rather than changing packet forwarding
  4. The FortiLink controller can authorize discovered devices automatically when that setting is enabled
  5. FortiGate pushes intended FortiSwitch configuration rather than relying on untracked local edits

Explanation

Correct Answer

C:

In this deployment, the configured operation is meant to retain switch events outside the device for investigation and retention. The most relevant validation is to check the collector for test link or authentication events with correct timestamps for the equipment at the remote depot.

Incorrect Answers

A:

That behavior applies when engineers “Apply an administrative access profile”; the different operation “Send operational messages to an external syslog collector” is intended to retain switch events outside the device for investigation and retention. That different feature is verified by test which GUI menus and CLI commands are available to the assigned administrator; for “Send operational messages to an external syslog collector” on a newly racked distribution unit, the relevant evidence is to check the collector for test link or authentication events with correct timestamps.

B:

This outcome would be relevant to “Enable neighbor detection appropriate for the FortiLink deployment” at the remote depot, not the task “Send operational messages to an external syslog collector”; the other task is to make discovery consistent with the actual supported port and neighbor behavior. The action “Send operational messages to an external syslog collector” targets a different result: syslog forwarding exports event records to a reachable collector rather than changing packet forwarding; the proposed alternative would instead be checked by inspect the neighbor-detection method and observed adjacency in the active FortiLink connection.

D:

That behavior applies when engineers “Enable automatic FortiSwitch authorization where appropriate”; the different operation “Send operational messages to an external syslog collector” is intended to retain switch events outside the device for investigation and retention. That different feature is verified by observe whether a newly discovered serial number becomes authorized without manual action; for “Send operational messages to an external syslog collector” on a newly racked distribution unit, the relevant evidence is to check the collector for test link or authentication events with correct timestamps.

E:

That behavior applies when engineers “Apply FortiSwitch port configuration from FortiGate”; the different operation “Send operational messages to an external syslog collector” is intended to retain switch events outside the device for investigation and retention. That different feature is verified by compare the controller's managed-port settings with the provisioned running state; for “Send operational messages to an external syslog collector” on a newly racked distribution unit, the relevant evidence is to check the collector for test link or authentication events with correct timestamps.

Question 314

A feature acceptance test on two distribution switches concerns “Send operational messages to an external syslog collector.” What should be checked to establish its expected operation?

  1. Check the port's model-dependent auto-discovery support and switch discovery event
  2. Compare the exact SKU and FortiSwitchOS release against the target feature documentation
  3. Inspect the switch-controller managed-switch list before editing the target unit
  4. Check the collector for test link or authentication events with correct timestamps

Explanation

Correct Answer

D:

For the stated requirement, syslog forwarding exports event records to a reachable collector rather than changing packet forwarding. Directly measuring that result demonstrates whether the step to retain switch events outside the device for investigation and retention succeeded on two distribution switches.

Incorrect Answers

A:

The proposed check concerns “Use a supported auto-discovery FortiSwitch port” rather than “Send operational messages to an external syslog collector”: discovery-capable ports advertise and detect controller connectivity without preprogramming the full local switch. For “Send operational messages to an external syslog collector” on two distribution switches, a better test would be to check the collector for test link or authentication events with correct timestamps, which targets retain switch events outside the device for investigation and retention rather than the alternative diagnostic “Use a supported auto-discovery FortiSwitch port”.

B:

This check is suited to “Check supported model and feature availability before provisioning” when trying to avoid issuing settings to an unsupported FortiSwitch platform, not to verify “Send operational messages to an external syslog collector” at the branch office. Checking “Send operational messages to an external syslog collector” at the branch office requires evidence of its own mechanism: syslog forwarding exports event records to a reachable collector rather than changing packet forwarding; that is not the outcome measured by “Check supported model and feature availability before provisioning”.

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 “Send operational messages to an external syslog collector” at the branch office. Checking “Send operational messages to an external syslog collector” at the branch office requires evidence of its own mechanism: syslog forwarding exports event records to a reachable collector rather than changing packet forwarding; that is not the outcome measured by “Use the FortiGate switch-controller GUI”.

Question 315

A production incident in the factory reveals the need to provide visibility of managed access infrastructure in the Fortinet environment. Which targeted FortiSwitch setting or method should the team use?

  1. Use a supported auto-discovery FortiSwitch port
  2. Integrate switch status with the Security Fabric
  3. Migrate a standalone FortiSwitch into FortiGate management
  4. Use the FortiGate switch-controller GUI

Explanation

Correct Answer

B:

The deciding detail is that controller and Fabric integration correlate switch topology and endpoint observations with FortiGate management. This distinction is material to the factory, where the stated goal is to provide visibility of managed access infrastructure in the Fortinet environment.

Incorrect Answers

A:

Compared with the requested “Integrate switch status with the Security Fabric” at the factory, this would allow an unconfigured switch to find its FortiLink controller during installation instead: discovery-capable ports advertise and detect controller connectivity without preprogramming the full local switch. At the factory, the operational proof would instead be to look for switch presence and expected topology information in the Fabric view, whereas “Use a supported auto-discovery FortiSwitch port” is validated by a different test: check the port's model-dependent auto-discovery support and switch discovery event.

C:

For the factory, “Migrate a standalone FortiSwitch into FortiGate management” is a different type of control from “Integrate switch status with the Security Fabric”: the migration sequence transfers supported switch settings into the FortiGate management context. Unlike the requested feature, that setting addresses the need to replace independent local administration with centralized provisioning, not the objective to provide visibility of managed access infrastructure in the Fortinet environment.

D:

Compared with the requested “Integrate switch status with the Security Fabric” at the factory, this would perform routine managed-switch edits through the centralized user interface instead: the GUI presents managed-switch topology, port settings and status in the controller context. At the factory, the operational proof would instead be to look for switch presence and expected topology information in the Fabric view, whereas “Use the FortiGate switch-controller GUI” is validated by a different test: inspect the switch-controller managed-switch list before editing the target unit.

Question 316

When engineers integrate switch status with the Security Fabric at the distribution floor, which forwarding, security, management or diagnostic outcome follows from that action?

  1. Controller and Fabric integration correlate switch topology and endpoint observations with FortiGate management
  2. SNMP provides structured operational measurements without becoming the forwarding control plane
  3. Firmware maintenance for managed switches should be coordinated through the FortiGate management workflow
  4. A cloud management workflow connects the registered switch to the appropriate Fortinet service

Explanation

Correct Answer

A:

The relevant mechanism is: the configured operation is meant to provide visibility of managed access infrastructure in the Fortinet environment. The most relevant validation is to look for switch presence and expected topology information in the Fabric view for the equipment at the distribution floor.

Incorrect Answers

B:

That behavior applies when engineers “Configure remote monitoring through SNMP”; the different operation “Integrate switch status with the Security Fabric” is intended to provide visibility of managed access infrastructure in the Fortinet environment. That different feature is verified by poll system and interface identifiers from the configured monitoring station; for “Integrate switch status with the Security Fabric” on a carefully segmented Layer 2 network, the relevant evidence is to look for switch presence and expected topology information in the Fabric view.

C:

This outcome would be relevant to “Perform a centrally coordinated FortiSwitch firmware update” at the distribution floor, not the task “Integrate switch status with the Security Fabric”; the other task is to keep controller-managed units on a planned supported release. The action “Integrate switch status with the Security Fabric” targets a different result: controller and Fabric integration correlate switch topology and endpoint observations with FortiGate management; the proposed alternative would instead be checked by verify intended image version, upgrade status and post-reboot switch connectivity.

D:

That behavior applies when engineers “Use FortiEdge Cloud management for a supported switch”; the different operation “Integrate switch status with the Security Fabric” is intended to provide visibility of managed access infrastructure in the Fortinet environment. That different feature is verified by confirm device registration, service connectivity and cloud-visible online state; for “Integrate switch status with the Security Fabric” on a carefully segmented Layer 2 network, the relevant evidence is to look for switch presence and expected topology information in the Fabric view.

Question 317

On a central switching stack at the media studio, the team reports that it has configured “Integrate switch status with the Security Fabric.” Which verification provides the strongest direct evidence that the intended function is working?

  1. Match the serial in the physical inventory with the FortiGate discovery listing
  2. Compare FortiGate and FortiSwitch system clocks and NTP association state
  3. Look for switch presence and expected topology information in the Fabric view
  4. Check the managed-switch inventory for an authorized state and configuration synchronization
  5. Verify the applied profile and successful login using the assigned administrator credentials

Explanation

Correct Answer

C:

This approach fits because controller and Fabric integration correlate switch topology and endpoint observations with FortiGate management. Directly measuring that result demonstrates whether the step to provide visibility of managed access infrastructure in the Fortinet environment succeeded on a central switching stack.

Incorrect Answers

A:

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 “Integrate switch status with the Security Fabric” at the media studio. Checking “Integrate switch status with the Security Fabric” at the media studio requires evidence of its own mechanism: controller and Fabric integration correlate switch topology and endpoint observations with FortiGate management; that is not the outcome measured by “Review FortiSwitch serial number during onboarding”.

B:

The proposed check concerns “Enable time synchronization for managed units” rather than “Integrate switch status with the Security Fabric”: a reachable NTP source supplies consistent time to switch and controller management processes. For “Integrate switch status with the Security Fabric” on a central switching stack, a better test would be to look for switch presence and expected topology information in the Fabric view, which targets provide visibility of managed access infrastructure in the Fortinet environment rather than the alternative diagnostic “Enable time synchronization for managed units”.

D:

This check is suited to “Authorize a discovered FortiSwitch on FortiGate” when trying to move an already discovered unit into centrally managed service, not to verify “Integrate switch status with the Security Fabric” at the media studio. Checking “Integrate switch status with the Security Fabric” at the media studio requires evidence of its own mechanism: controller and Fabric integration correlate switch topology and endpoint observations with FortiGate management; that is not the outcome measured by “Authorize a discovered FortiSwitch on FortiGate”.

E:

The proposed check concerns “Select a FortiSwitch profile with a managed admin password” rather than “Integrate switch status with the Security Fabric”: FortiGate switch profiles can set managed switch administrative credentials centrally. For “Integrate switch status with the Security Fabric” on a central switching stack, a better test would be to look for switch presence and expected topology information in the Fabric view, which targets provide visibility of managed access infrastructure in the Fortinet environment rather than the alternative diagnostic “Select a FortiSwitch profile with a managed admin password”.

Question 318

A switch rollout in the data hall will be approved only if it can give authorized operators controlled switch access without depending on an empty local password. Which administrative action meets this acceptance criterion?

  1. Back up FortiSwitch configuration before upgrades
  2. Restrict administrative protocols on switch management interfaces
  3. Deauthorize a retired managed switch deliberately
  4. Select a FortiSwitch profile with a managed admin password

Explanation

Correct Answer

D:

The critical distinction is that FortiGate switch profiles can set managed switch administrative credentials centrally. The operator can test this claim by the specific check: verify the applied profile and successful login using the assigned administrator credentials.

Incorrect Answers

A:

Compared with the requested “Select a FortiSwitch profile with a managed admin password” at the data hall, this would make recovery possible if a firmware or policy change fails instead: a configuration export preserves management settings independently of the device's current runtime state. At the data hall, the operational proof would instead be to verify the applied profile and successful login using the assigned administrator credentials, whereas “Back up FortiSwitch configuration before upgrades” is validated by a different test: check the backup file timestamp and availability before starting maintenance.

B:

Compared with the requested “Select a FortiSwitch profile with a managed admin password” at the data hall, this would reduce exposure of the switch control plane to unauthorized clients instead: management-access settings decide which administrative services are accepted on an interface. At the data hall, the operational proof would instead be to verify the applied profile and successful login using the assigned administrator credentials, whereas “Restrict administrative protocols on switch management interfaces” is validated by a different test: inspect enabled administrative protocols and test reachability from an approved source.

C:

For the data hall, “Deauthorize a retired managed switch deliberately” is a different type of control from “Select a FortiSwitch profile with a managed admin password”: controller deauthorization changes the authorization relationship and may affect switch reset or password retention. Unlike the requested feature, that setting addresses the need to remove an old device from centralized switch management without accidentally changing a replacement unit, not the objective to give authorized operators controlled switch access without depending on an empty local password.

Question 319

A colleague asks about the effect of “Select a FortiSwitch profile with a managed admin password” on an access switch in routine maintenance. Which behavior best characterizes that feature?

  1. The controller interface provides management addressing and reachability for connected managed units
  2. Syslog forwarding exports event records to a reachable collector rather than changing packet forwarding
  3. FortiGate switch profiles can set managed switch administrative credentials centrally
  4. Standalone mode exposes local configuration and administration on the switch itself

Explanation

Correct Answer

C:

That setting is appropriate here because the configured operation is meant to give authorized operators controlled switch access without depending on an empty local password. The most relevant validation is to verify the applied profile and successful login using the assigned administrator credentials for the equipment at the development floor.

Incorrect Answers

A:

That behavior applies when engineers “Assign a reachable FortiLink interface IP subnet”; the different operation “Select a FortiSwitch profile with a managed admin password” is intended to give authorized operators controlled switch access without depending on an empty local password. That different feature is verified by examine controller interface IP settings and switch management address assignment; for “Select a FortiSwitch profile with a managed admin password” on an access switch in routine maintenance, the relevant evidence is to verify the applied profile and successful login using the assigned administrator credentials.

B:

That behavior applies when engineers “Send operational messages to an external syslog collector”; the different operation “Select a FortiSwitch profile with a managed admin password” is intended to give authorized operators controlled switch access without depending on an empty local password. That different feature is verified by check the collector for test link or authentication events with correct timestamps; for “Select a FortiSwitch profile with a managed admin password” on an access switch in routine maintenance, the relevant evidence is to verify the applied profile and successful login using the assigned administrator credentials.

D:

This outcome would be relevant to “Operate a FortiSwitch in standalone mode” at the development floor, not the task “Select a FortiSwitch profile with a managed admin password”; the other task is to manage a switch locally without delegating configuration to a FortiGate. The action “Select a FortiSwitch profile with a managed admin password” targets a different result: FortiGate switch profiles can set managed switch administrative credentials centrally; the proposed alternative would instead be checked by confirm local management access and that the unit is not assigned to a FortiGate controller.

Question 320

The work order to give authorized operators controlled switch access without depending on an empty local password is marked complete on a managed campus switch. Which observation most directly tests the completed configuration?

  1. Compare controller-configured port values with device status and sync indicators
  2. Inspect the restored local settings and confirm there is no controller configuration conflict
  3. Compare the controller's managed-port settings with the provisioned running state
  4. Check the collector for test link or authentication events with correct timestamps
  5. Verify the applied profile and successful login using the assigned administrator credentials
  6. Observe whether a newly discovered serial number becomes authorized without manual action

Explanation

Correct Answer

E:

This is the precise control because FortiGate switch profiles can set managed switch administrative credentials centrally. Directly measuring that result demonstrates whether the step to give authorized operators controlled switch access without depending on an empty local password succeeded on a managed campus switch.

Incorrect Answers

A:

The proposed check concerns “Check managed-switch configuration synchronization” rather than “Select a FortiSwitch profile with a managed admin password”: synchronization status identifies divergence between controller intent and provisioned switch state. For “Select a FortiSwitch profile with a managed admin password” on a managed campus switch, a better test would be to verify the applied profile and successful login using the assigned administrator credentials, which targets give authorized operators controlled switch access without depending on an empty local password rather than the alternative diagnostic “Check managed-switch configuration synchronization”.

B:

This check is suited to “Restore the saved standalone configuration locally” when trying to recover a locally administered switch after a failed change, not to verify “Select a FortiSwitch profile with a managed admin password” at the conference venue. Checking “Select a FortiSwitch profile with a managed admin password” at the conference venue requires evidence of its own mechanism: FortiGate switch profiles can set managed switch administrative credentials centrally; that is not the outcome measured by “Restore the saved standalone configuration locally”.

C:

The proposed check concerns “Apply FortiSwitch port configuration from FortiGate” rather than “Select a FortiSwitch profile with a managed admin password”: FortiGate pushes intended FortiSwitch configuration rather than relying on untracked local edits. For “Select a FortiSwitch profile with a managed admin password” on a managed campus switch, a better test would be to verify the applied profile and successful login using the assigned administrator credentials, which targets give authorized operators controlled switch access without depending on an empty local password rather than the alternative diagnostic “Apply FortiSwitch port configuration from FortiGate”.

D:

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 “Select a FortiSwitch profile with a managed admin password” at the conference venue. Checking “Select a FortiSwitch profile with a managed admin password” at the conference venue requires evidence of its own mechanism: FortiGate switch profiles can set managed switch administrative credentials centrally; that is not the outcome measured by “Send operational messages to an external syslog collector”.

F:

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 “Select a FortiSwitch profile with a managed admin password” at the conference venue. Checking “Select a FortiSwitch profile with a managed admin password” at the conference venue requires evidence of its own mechanism: FortiGate switch profiles can set managed switch administrative credentials centrally; that is not the outcome measured by “Enable automatic FortiSwitch authorization where appropriate”.

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