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

Question 670

During validation of a recently upgraded FortiSwitch at the conference venue, the team asks what the change “Verify NTP and clock consistency” actually does. Which outcome is correct?

  1. The controller's desired configuration may not have been successfully delivered or accepted
  2. Clock synchronization is important for time-sensitive authentication and interpreting management logs
  3. A targeted capture can show whether expected controller/discovery exchanges traverse the selected interface
  4. Discovery detects the unit; authorization controls whether it becomes a managed device

Explanation

Correct Answer

B:

Given the described goal, the configured operation is meant to understand authentication failures or event timestamps that do not align with controller records. The most relevant validation is to compare actual switch/controller time and NTP association status for the equipment at the conference venue.

Incorrect Answers

A:

This outcome would be relevant to “Inspect FortiSwitch configuration synchronization” at the conference venue, not the task “Verify NTP and clock consistency”; the other task is to explain why a VLAN edit appears on FortiGate but not on a managed switch. The action “Verify NTP and clock consistency” targets a different result: clock synchronization is important for time-sensitive authentication and interpreting management logs; the proposed alternative would instead be checked by compare synchronization state and intended versus applied port properties.

C:

That behavior applies when engineers “Check FortiLink control traffic with a sniffer”; the different operation “Verify NTP and clock consistency” is intended to understand authentication failures or event timestamps that do not align with controller records. That different feature is verified by observe control-plane packets at both ends while restarting discovery; for “Verify NTP and clock consistency” on a recently upgraded FortiSwitch, the relevant evidence is to compare actual switch/controller time and NTP association status.

D:

That behavior applies when engineers “Check FortiSwitch discovery and authorization state”; the different operation “Verify NTP and clock consistency” is intended to understand authentication failures or event timestamps that do not align with controller records. That different feature is verified by compare detected serials with authorized managed-switch inventory; for “Verify NTP and clock consistency” on a recently upgraded FortiSwitch, the relevant evidence is to compare actual switch/controller time and NTP association status.

Question 671

On a FortiLink-managed access switch at the campus, the team reports that it has configured “Verify NTP and clock consistency.” Which verification provides the strongest direct evidence that the intended function is working?

  1. Compare actual switch/controller time and NTP association status
  2. Compare exact releases and model against the applicable FortiLink compatibility information
  3. Trace the missing switch's upstream path and each intervening ISL state
  4. Test management-path connectivity and inspect assigned addresses

Explanation

Correct Answer

A:

The switch behavior that matters is: clock synchronization is important for time-sensitive authentication and interpreting management logs. Directly measuring that result demonstrates whether the step to understand authentication failures or event timestamps that do not align with controller records succeeded on a FortiLink-managed access switch.

Incorrect Answers

B:

This check is suited to “Check firmware compatibility and supported switch model” when trying to investigate managed-switch instability after a firmware change, not to verify “Verify NTP and clock consistency” at the campus. Checking “Verify NTP and clock consistency” at the campus requires evidence of its own mechanism: clock synchronization is important for time-sensitive authentication and interpreting management logs; that is not the outcome measured by “Check firmware compatibility and supported switch model”.

C:

This check is suited to “Inspect topology view for a missing descendant” when trying to locate the ISL segment that interrupts downstream FortiSwitch discovery, not to verify “Verify NTP and clock consistency” at the campus. Checking “Verify NTP and clock consistency” at the campus requires evidence of its own mechanism: clock synchronization is important for time-sensitive authentication and interpreting management logs; that is not the outcome measured by “Inspect topology view for a missing descendant”.

D:

The proposed check concerns “Verify FortiLink management address reachability” rather than “Verify NTP and clock consistency”: controller communication depends on valid IP settings or the supported Layer 2 FortiLink path. For “Verify NTP and clock consistency” on a FortiLink-managed access switch, a better test would be to compare actual switch/controller time and NTP association status, which targets understand authentication failures or event timestamps that do not align with controller records rather than the alternative diagnostic “Verify FortiLink management address reachability”.

Question 672

The accepted design for the remote depot requires the ability to locate the ISL segment that interrupts downstream FortiSwitch discovery. Which switch feature is the closest fit?

  1. Confirm FortiLink physical and logical interface status
  2. Inspect topology view for a missing descendant
  3. Check FortiLink control traffic with a sniffer
  4. Check FortiSwitch discovery and authorization state
  5. Inspect FortiSwitch configuration synchronization

Explanation

Correct Answer

B:

At this network boundary, the stack topology identifies parent and child switch relationships and intermediate uplinks. The operator can test this claim by the specific check: trace the missing switch's upstream path and each intervening ISL state.

Incorrect Answers

A:

Compared with the requested “Inspect topology view for a missing descendant” at the remote depot, this would distinguish a dead uplink from a controller configuration problem instead: operational link members and FortiLink interface status must be healthy before management can synchronize. At the remote depot, the operational proof would instead be to trace the missing switch's upstream path and each intervening ISL state, whereas “Confirm FortiLink physical and logical interface status” is validated by a different test: inspect FortiGate member links and the corresponding switch-facing ports.

C:

Compared with the requested “Inspect topology view for a missing descendant” at the remote depot, this would distinguish absent discovery packets from failed authorization or policy processing instead: a targeted capture can show whether expected controller/discovery exchanges traverse the selected interface. At the remote depot, the operational proof would instead be to trace the missing switch's upstream path and each intervening ISL state, whereas “Check FortiLink control traffic with a sniffer” is validated by a different test: observe control-plane packets at both ends while restarting discovery.

D:

Compared with the requested “Inspect topology view for a missing descendant” at the remote depot, this would explain why a physically connected new switch does not receive central configuration instead: discovery detects the unit; authorization controls whether it becomes a managed device. At the remote depot, the operational proof would instead be to trace the missing switch's upstream path and each intervening ISL state, whereas “Check FortiSwitch discovery and authorization state” is validated by a different test: compare detected serials with authorized managed-switch inventory.

E:

For the remote depot, “Inspect FortiSwitch configuration synchronization” is a different type of control from “Inspect topology view for a missing descendant”: the controller's desired configuration may not have been successfully delivered or accepted. Unlike the requested feature, that setting addresses the need to explain why a VLAN edit appears on FortiGate but not on a managed switch, not the objective to locate the ISL segment that interrupts downstream FortiSwitch discovery.

Question 673

Before applying the planned operation “Inspect topology view for a missing descendant” at the branch office, the administrator must predict its impact. Which prediction is sound?

  1. Discovery detects the unit; authorization controls whether it becomes a managed device
  2. The stack topology identifies parent and child switch relationships and intermediate uplinks
  3. Controller communication depends on valid IP settings or the supported Layer 2 FortiLink path
  4. Clock synchronization is important for time-sensitive authentication and interpreting management logs

Explanation

Correct Answer

B:

In this deployment, the configured operation is meant to locate the ISL segment that interrupts downstream FortiSwitch discovery. The most relevant validation is to trace the missing switch's upstream path and each intervening ISL state for the equipment at the branch office.

Incorrect Answers

A:

That behavior applies when engineers “Check FortiSwitch discovery and authorization state”; the different operation “Inspect topology view for a missing descendant” is intended to locate the ISL segment that interrupts downstream FortiSwitch discovery. That different feature is verified by compare detected serials with authorized managed-switch inventory; for “Inspect topology view for a missing descendant” on a switch serving a high-density endpoint area, the relevant evidence is to trace the missing switch's upstream path and each intervening ISL state.

C:

That behavior applies when engineers “Verify FortiLink management address reachability”; the different operation “Inspect topology view for a missing descendant” is intended to locate the ISL segment that interrupts downstream FortiSwitch discovery. That different feature is verified by test management-path connectivity and inspect assigned addresses; for “Inspect topology view for a missing descendant” on a switch serving a high-density endpoint area, the relevant evidence is to trace the missing switch's upstream path and each intervening ISL state.

D:

This outcome would be relevant to “Verify NTP and clock consistency” at the branch office, not the task “Inspect topology view for a missing descendant”; the other task is to understand authentication failures or event timestamps that do not align with controller records. The action “Inspect topology view for a missing descendant” targets a different result: the stack topology identifies parent and child switch relationships and intermediate uplinks; the proposed alternative would instead be checked by compare actual switch/controller time and NTP association status.

Question 674

The work order to locate the ISL segment that interrupts downstream FortiSwitch discovery is marked complete on a managed switch running FortiSwitchOS 7.6. Which observation most directly tests the completed configuration?

  1. Inspect FortiGate member links and the corresponding switch-facing ports
  2. Compare exact releases and model against the applicable FortiLink compatibility information
  3. Review controller process health and device management daemon logs
  4. Trace the missing switch's upstream path and each intervening ISL state

Explanation

Correct Answer

D:

For the stated requirement, the stack topology identifies parent and child switch relationships and intermediate uplinks. Directly measuring that result demonstrates whether the step to locate the ISL segment that interrupts downstream FortiSwitch discovery succeeded on a managed switch running FortiSwitchOS 7.6.

Incorrect Answers

A:

This check is suited to “Confirm FortiLink physical and logical interface status” when trying to distinguish a dead uplink from a controller configuration problem, not to verify “Inspect topology view for a missing descendant” at the factory. Checking “Inspect topology view for a missing descendant” at the factory requires evidence of its own mechanism: the stack topology identifies parent and child switch relationships and intermediate uplinks; that is not the outcome measured by “Confirm FortiLink physical and logical interface status”.

B:

This check is suited to “Check firmware compatibility and supported switch model” when trying to investigate managed-switch instability after a firmware change, not to verify “Inspect topology view for a missing descendant” at the factory. Checking “Inspect topology view for a missing descendant” at the factory requires evidence of its own mechanism: the stack topology identifies parent and child switch relationships and intermediate uplinks; that is not the outcome measured by “Check firmware compatibility and supported switch model”.

C:

The proposed check concerns “Check the switch-controller management process” rather than “Inspect topology view for a missing descendant”: controller and managed-switch processes operate separately from basic Layer 2 forwarding. For “Inspect topology view for a missing descendant” on a managed switch running FortiSwitchOS 7.6, a better test would be to trace the missing switch's upstream path and each intervening ISL state, which targets locate the ISL segment that interrupts downstream FortiSwitch discovery rather than the alternative diagnostic “Check the switch-controller management process”.

Question 675

An administrator responsible for a remote FortiSwitch installation in the research building must distinguish absent discovery packets from failed authorization or policy processing. Which configuration best matches that precise goal?

  1. Check firmware compatibility and supported switch model
  2. Verify NTP and clock consistency
  3. Verify FortiLink management address reachability
  4. Check FortiLink control traffic with a sniffer

Explanation

Correct Answer

D:

The deciding detail is that a targeted capture can show whether expected controller/discovery exchanges traverse the selected interface. This distinction is material to the research building, where the stated goal is to distinguish absent discovery packets from failed authorization or policy processing.

Incorrect Answers

A:

For the research building, “Check firmware compatibility and supported switch model” is a different type of control from “Check FortiLink control traffic with a sniffer”: controller and switch versions and model support affect feature provisioning and synchronization. Unlike the requested feature, that setting addresses the need to investigate managed-switch instability after a firmware change, not the objective to distinguish absent discovery packets from failed authorization or policy processing.

B:

Compared with the requested “Check FortiLink control traffic with a sniffer” at the research building, this would understand authentication failures or event timestamps that do not align with controller records instead: clock synchronization is important for time-sensitive authentication and interpreting management logs. At the research building, the operational proof would instead be to observe control-plane packets at both ends while restarting discovery, whereas “Verify NTP and clock consistency” is validated by a different test: compare actual switch/controller time and NTP association status.

C:

Compared with the requested “Check FortiLink control traffic with a sniffer” at the research building, this would determine whether switch control messages can reach the FortiGate instead: controller communication depends on valid IP settings or the supported Layer 2 FortiLink path. At the research building, the operational proof would instead be to observe control-plane packets at both ends while restarting discovery, whereas “Verify FortiLink management address reachability” is validated by a different test: test management-path connectivity and inspect assigned addresses.

Question 676

During validation of an endpoint-facing FortiSwitch port at the clinic, the team asks what the change “Check FortiLink control traffic with a sniffer” actually does. Which outcome is correct?

  1. Controller and managed-switch processes operate separately from basic Layer 2 forwarding
  2. A targeted capture can show whether expected controller/discovery exchanges traverse the selected interface
  3. The controller's desired configuration may not have been successfully delivered or accepted
  4. The stack topology identifies parent and child switch relationships and intermediate uplinks
  5. Operational link members and FortiLink interface status must be healthy before management can synchronize

Explanation

Correct Answer

B:

The relevant mechanism is: the configured operation is meant to distinguish absent discovery packets from failed authorization or policy processing. The most relevant validation is to observe control-plane packets at both ends while restarting discovery for the equipment at the clinic.

Incorrect Answers

A:

That behavior applies when engineers “Check the switch-controller management process”; the different operation “Check FortiLink control traffic with a sniffer” is intended to distinguish absent discovery packets from failed authorization or policy processing. That different feature is verified by review controller process health and device management daemon logs; for “Check FortiLink control traffic with a sniffer” on an endpoint-facing FortiSwitch port, the relevant evidence is to observe control-plane packets at both ends while restarting discovery.

C:

That behavior applies when engineers “Inspect FortiSwitch configuration synchronization”; the different operation “Check FortiLink control traffic with a sniffer” is intended to distinguish absent discovery packets from failed authorization or policy processing. That different feature is verified by compare synchronization state and intended versus applied port properties; for “Check FortiLink control traffic with a sniffer” on an endpoint-facing FortiSwitch port, the relevant evidence is to observe control-plane packets at both ends while restarting discovery.

D:

That behavior applies when engineers “Inspect topology view for a missing descendant”; the different operation “Check FortiLink control traffic with a sniffer” is intended to distinguish absent discovery packets from failed authorization or policy processing. That different feature is verified by trace the missing switch's upstream path and each intervening ISL state; for “Check FortiLink control traffic with a sniffer” on an endpoint-facing FortiSwitch port, the relevant evidence is to observe control-plane packets at both ends while restarting discovery.

E:

This outcome would be relevant to “Confirm FortiLink physical and logical interface status” at the clinic, not the task “Check FortiLink control traffic with a sniffer”; the other task is to distinguish a dead uplink from a controller configuration problem. The action “Check FortiLink control traffic with a sniffer” targets a different result: a targeted capture can show whether expected controller/discovery exchanges traverse the selected interface; the proposed alternative would instead be checked by inspect FortiGate member links and the corresponding switch-facing ports.

Question 677

A production incident in the data hall reveals the need to investigate managed-switch instability after a firmware change. Which targeted FortiSwitch setting or method should the team use?

  1. Check FortiSwitch discovery and authorization state
  2. Check firmware compatibility and supported switch model
  3. Inspect FortiSwitch configuration synchronization
  4. Verify NTP and clock consistency

Explanation

Correct Answer

B:

This approach fits because controller and switch versions and model support affect feature provisioning and synchronization. This distinction is material to the data hall, where the stated goal is to investigate managed-switch instability after a firmware change.

Incorrect Answers

A:

Compared with the requested “Check firmware compatibility and supported switch model” at the data hall, this would explain why a physically connected new switch does not receive central configuration instead: discovery detects the unit; authorization controls whether it becomes a managed device. At the data hall, the operational proof would instead be to compare exact releases and model against the applicable FortiLink compatibility information, whereas “Check FortiSwitch discovery and authorization state” is validated by a different test: compare detected serials with authorized managed-switch inventory.

C:

Compared with the requested “Check firmware compatibility and supported switch model” at the data hall, this would explain why a VLAN edit appears on FortiGate but not on a managed switch instead: the controller's desired configuration may not have been successfully delivered or accepted. At the data hall, the operational proof would instead be to compare exact releases and model against the applicable FortiLink compatibility information, whereas “Inspect FortiSwitch configuration synchronization” is validated by a different test: compare synchronization state and intended versus applied port properties.

D:

For the data hall, “Verify NTP and clock consistency” is a different type of control from “Check firmware compatibility and supported switch model”: clock synchronization is important for time-sensitive authentication and interpreting management logs. Unlike the requested feature, that setting addresses the need to understand authentication failures or event timestamps that do not align with controller records, not the objective to investigate managed-switch instability after a firmware change.

Question 678

During validation of a FortiLink-managed access switch at the development floor, the team asks what the change “Check firmware compatibility and supported switch model” actually does. Which outcome is correct?

  1. A targeted capture can show whether expected controller/discovery exchanges traverse the selected interface
  2. Controller and managed-switch processes operate separately from basic Layer 2 forwarding
  3. Controller and switch versions and model support affect feature provisioning and synchronization
  4. Controller communication depends on valid IP settings or the supported Layer 2 FortiLink path

Explanation

Correct Answer

C:

The critical distinction is that the configured operation is meant to investigate managed-switch instability after a firmware change. The most relevant validation is to compare exact releases and model against the applicable FortiLink compatibility information for the equipment at the development floor.

Incorrect Answers

A:

This outcome would be relevant to “Check FortiLink control traffic with a sniffer” at the development floor, not the task “Check firmware compatibility and supported switch model”; the other task is to distinguish absent discovery packets from failed authorization or policy processing. The action “Check firmware compatibility and supported switch model” targets a different result: controller and switch versions and model support affect feature provisioning and synchronization; the proposed alternative would instead be checked by observe control-plane packets at both ends while restarting discovery.

B:

That behavior applies when engineers “Check the switch-controller management process”; the different operation “Check firmware compatibility and supported switch model” is intended to investigate managed-switch instability after a firmware change. That different feature is verified by review controller process health and device management daemon logs; for “Check firmware compatibility and supported switch model” on a FortiLink-managed access switch, the relevant evidence is to compare exact releases and model against the applicable FortiLink compatibility information.

D:

That behavior applies when engineers “Verify FortiLink management address reachability”; the different operation “Check firmware compatibility and supported switch model” is intended to investigate managed-switch instability after a firmware change. That different feature is verified by test management-path connectivity and inspect assigned addresses; for “Check firmware compatibility and supported switch model” on a FortiLink-managed access switch, the relevant evidence is to compare exact releases and model against the applicable FortiLink compatibility information.

Question 679

An administrator responsible for a switch linked to a FortiGate running FortiOS 7.6 in the conference venue must differentiate a physical cable or optic fault from a VLAN policy problem. Which configuration best matches that precise goal?

  1. Inspect VLAN port membership and port PDUs
  2. Review system and crash logs
  3. Inspect the MAC address forwarding table
  4. Inspect port link status and error counters

Explanation

Correct Answer

D:

That setting is appropriate here because interface monitors expose operational status, packet errors and traffic totals. This distinction is material to the conference venue, where the stated goal is to differentiate a physical cable or optic fault from a VLAN policy problem.

Incorrect Answers

A:

Compared with the requested “Inspect port link status and error counters” at the conference venue, this would explain why frames with the expected VLAN tag do not traverse a specific link instead: VLAN membership and protocol data units show forwarding eligibility and neighbor protocol negotiation. At the conference venue, the operational proof would instead be to check link-up state, CRC/error counters and the remote peer's port statistics, whereas “Inspect VLAN port membership and port PDUs” is validated by a different test: compare allowed/native/untagged lists and captured LLDP or STP PDUs on the link.

B:

For the conference venue, “Review system and crash logs” is a different type of control from “Inspect port link status and error counters”: system logs and crash records give chronological evidence of faults that ordinary MAC counters miss. Unlike the requested feature, that setting addresses the need to determine whether a restart or process fault explains a sudden traffic interruption, not the objective to differentiate a physical cable or optic fault from a VLAN policy problem.

C:

Compared with the requested “Inspect port link status and error counters” at the conference venue, this would find which switch interface currently learns a particular endpoint MAC instead: MAC table entries associate destination reachability with VLAN and physical or trunk ports. At the conference venue, the operational proof would instead be to check link-up state, CRC/error counters and the remote peer's port statistics, whereas “Inspect the MAC address forwarding table” is validated by a different test: compare the endpoint's MAC/VLAN entry with the expected cabling.

Question 680

During validation of a switch serving a high-density endpoint area at the campus, the team asks what the change “Inspect port link status and error counters” actually does. Which outcome is correct?

  1. MAC table entries associate destination reachability with VLAN and physical or trunk ports
  2. ARP mappings associate an IPv4 neighbor address with a hardware destination on the relevant network
  3. VLAN membership and protocol data units show forwarding eligibility and neighbor protocol negotiation
  4. System logs and crash records give chronological evidence of faults that ordinary MAC counters miss
  5. Interface monitors expose operational status, packet errors and traffic totals

Explanation

Correct Answer

E:

This is the precise control because the configured operation is meant to differentiate a physical cable or optic fault from a VLAN policy problem. The most relevant validation is to check link-up state, CRC/error counters and the remote peer's port statistics for the equipment at the campus.

Incorrect Answers

A:

That behavior applies when engineers “Inspect the MAC address forwarding table”; the different operation “Inspect port link status and error counters” is intended to differentiate a physical cable or optic fault from a VLAN policy problem. That different feature is verified by compare the endpoint's MAC/VLAN entry with the expected cabling; for “Inspect port link status and error counters” on a switch serving a high-density endpoint area, the relevant evidence is to check link-up state, CRC/error counters and the remote peer's port statistics.

B:

That behavior applies when engineers “Inspect the ARP neighbor table”; the different operation “Inspect port link status and error counters” is intended to differentiate a physical cable or optic fault from a VLAN policy problem. That different feature is verified by check IP-to-MAC resolution and the reachable SVI or routed interface; for “Inspect port link status and error counters” on a switch serving a high-density endpoint area, the relevant evidence is to check link-up state, CRC/error counters and the remote peer's port statistics.

C:

This outcome would be relevant to “Inspect VLAN port membership and port PDUs” at the campus, not the task “Inspect port link status and error counters”; the other task is to explain why frames with the expected VLAN tag do not traverse a specific link. The action “Inspect port link status and error counters” targets a different result: interface monitors expose operational status, packet errors and traffic totals; the proposed alternative would instead be checked by compare allowed/native/untagged lists and captured LLDP or STP PDUs on the link.

D:

That behavior applies when engineers “Review system and crash logs”; the different operation “Inspect port link status and error counters” is intended to differentiate a physical cable or optic fault from a VLAN policy problem. That different feature is verified by correlate uptime, crash-event timestamps and the observed outage window; for “Inspect port link status and error counters” on a switch serving a high-density endpoint area, the relevant evidence is to check link-up state, CRC/error counters and the remote peer's port statistics.

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