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

Question 690

After implementing “Inspect the ARP neighbor table,” the site engineer needs to assess its actual effect on an endpoint-facing FortiSwitch port. Which test is the best match?

  1. Check CPU/memory/process utilization during the delay
  2. Compare the endpoint's MAC/VLAN entry with the expected cabling
  3. Check IP-to-MAC resolution and the reachable SVI or routed interface
  4. Check link-up state, CRC/error counters and the remote peer's port statistics

Explanation

Correct Answer

C:

The critical distinction is that ARP mappings associate an IPv4 neighbor address with a hardware destination on the relevant network. Directly measuring that result demonstrates whether the step to investigate missing IPv4 adjacency at a routed switch interface succeeded on an endpoint-facing FortiSwitch port.

Incorrect Answers

A:

This check is suited to “Monitor switch processes and resource use” when trying to diagnose slow management responsiveness despite links remaining operational, not to verify “Inspect the ARP neighbor table” at the training center. Checking “Inspect the ARP neighbor table” at the training center requires evidence of its own mechanism: ARP mappings associate an IPv4 neighbor address with a hardware destination on the relevant network; that is not the outcome measured by “Monitor switch processes and resource use”.

B:

This check is suited to “Inspect the MAC address forwarding table” when trying to find which switch interface currently learns a particular endpoint MAC, not to verify “Inspect the ARP neighbor table” at the training center. Checking “Inspect the ARP neighbor table” at the training center requires evidence of its own mechanism: ARP mappings associate an IPv4 neighbor address with a hardware destination on the relevant network; that is not the outcome measured by “Inspect the MAC address forwarding table”.

D:

The proposed check concerns “Inspect port link status and error counters” rather than “Inspect the ARP neighbor table”: interface monitors expose operational status, packet errors and traffic totals. For “Inspect the ARP neighbor table” on an endpoint-facing FortiSwitch port, a better test would be to check IP-to-MAC resolution and the reachable SVI or routed interface, which targets investigate missing IPv4 adjacency at a routed switch interface rather than the alternative diagnostic “Inspect port link status and error counters”.

Question 691

During a change window in the lab, engineers are asked to locate a cable connected to an unexpected adjacent switch or access endpoint. What should they configure rather than using a feature for an adjacent purpose?

  1. Inspect the MAC address forwarding table
  2. Inspect LLDP neighbors
  3. Review real-time interface bandwidth
  4. Inspect VLAN port membership and port PDUs
  5. Review system and crash logs

Explanation

Correct Answer

B:

That setting is appropriate here because LLDP neighbor records identify the chassis and remote port discovered on a local link. This distinction is material to the lab, where the stated goal is to locate a cable connected to an unexpected adjacent switch or access endpoint.

Incorrect Answers

A:

Compared with the requested “Inspect LLDP neighbors” at the lab, 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 lab, the operational proof would instead be to compare local port IDs with advertised remote chassis/port identifiers, whereas “Inspect the MAC address forwarding table” is validated by a different test: compare the endpoint's MAC/VLAN entry with the expected cabling.

C:

Compared with the requested “Inspect LLDP neighbors” at the lab, this would identify whether a congested uplink is responsible for poor application performance instead: port traffic counters show observed utilization trends and potential saturation. At the lab, the operational proof would instead be to compare local port IDs with advertised remote chassis/port identifiers, whereas “Review real-time interface bandwidth” is validated by a different test: compare ingress and egress rates with the port's negotiated capacity.

D:

Compared with the requested “Inspect LLDP neighbors” at the lab, 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 lab, the operational proof would instead be to compare local port IDs with advertised remote chassis/port identifiers, 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.

E:

For the lab, “Review system and crash logs” is a different type of control from “Inspect LLDP neighbors”: 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 locate a cable connected to an unexpected adjacent switch or access endpoint.

Question 692

A switch change for the staging rack consists of this step: inspect LLDP neighbors. Which behavior reflects the purpose of that change?

  1. LLDP neighbor records identify the chassis and remote port discovered on a local link
  2. VLAN membership and protocol data units show forwarding eligibility and neighbor protocol negotiation
  3. Port traffic counters show observed utilization trends and potential saturation
  4. System logs and crash records give chronological evidence of faults that ordinary MAC counters miss

Explanation

Correct Answer

A:

This is the precise control because the configured operation is meant to locate a cable connected to an unexpected adjacent switch or access endpoint. The most relevant validation is to compare local port IDs with advertised remote chassis/port identifiers for the equipment at the staging rack.

Incorrect Answers

B:

This outcome would be relevant to “Inspect VLAN port membership and port PDUs” at the staging rack, not the task “Inspect LLDP neighbors”; the other task is to explain why frames with the expected VLAN tag do not traverse a specific link. The action “Inspect LLDP neighbors” targets a different result: LLDP neighbor records identify the chassis and remote port discovered on a local link; the proposed alternative would instead be checked by compare allowed/native/untagged lists and captured LLDP or STP PDUs on the link.

C:

That behavior applies when engineers “Review real-time interface bandwidth”; the different operation “Inspect LLDP neighbors” is intended to locate a cable connected to an unexpected adjacent switch or access endpoint. That different feature is verified by compare ingress and egress rates with the port's negotiated capacity; for “Inspect LLDP neighbors” on a newly commissioned floor switch, the relevant evidence is to compare local port IDs with advertised remote chassis/port identifiers.

D:

That behavior applies when engineers “Review system and crash logs”; the different operation “Inspect LLDP neighbors” is intended to locate a cable connected to an unexpected adjacent switch or access endpoint. That different feature is verified by correlate uptime, crash-event timestamps and the observed outage window; for “Inspect LLDP neighbors” on a newly commissioned floor switch, the relevant evidence is to compare local port IDs with advertised remote chassis/port identifiers.

Question 693

At the research building, a dashboard shows ordinary link-up state, but the team also needs proof for “Inspect LLDP neighbors.” Which targeted check should be used?

  1. Compare ingress and egress rates with the port's negotiated capacity
  2. Compare local port IDs with advertised remote chassis/port identifiers
  3. Correlate uptime, crash-event timestamps and the observed outage window
  4. Compare allowed/native/untagged lists and captured LLDP or STP PDUs on the link

Explanation

Correct Answer

B:

The implementation works because LLDP neighbor records identify the chassis and remote port discovered on a local link. Directly measuring that result demonstrates whether the step to locate a cable connected to an unexpected adjacent switch or access endpoint succeeded on a local switch administering branch clients.

Incorrect Answers

A:

This check is suited to “Review real-time interface bandwidth” when trying to identify whether a congested uplink is responsible for poor application performance, not to verify “Inspect LLDP neighbors” at the research building. Checking “Inspect LLDP neighbors” at the research building requires evidence of its own mechanism: LLDP neighbor records identify the chassis and remote port discovered on a local link; that is not the outcome measured by “Review real-time interface bandwidth”.

C:

This check is suited to “Review system and crash logs” when trying to determine whether a restart or process fault explains a sudden traffic interruption, not to verify “Inspect LLDP neighbors” at the research building. Checking “Inspect LLDP neighbors” at the research building requires evidence of its own mechanism: LLDP neighbor records identify the chassis and remote port discovered on a local link; that is not the outcome measured by “Review system and crash logs”.

D:

The proposed check concerns “Inspect VLAN port membership and port PDUs” rather than “Inspect LLDP neighbors”: VLAN membership and protocol data units show forwarding eligibility and neighbor protocol negotiation. For “Inspect LLDP neighbors” on a local switch administering branch clients, a better test would be to compare local port IDs with advertised remote chassis/port identifiers, which targets locate a cable connected to an unexpected adjacent switch or access endpoint rather than the alternative diagnostic “Inspect VLAN port membership and port PDUs”.

Question 694

For the clinic, the network team needs to determine whether a restart or process fault explains a sudden traffic interruption. Which change is the most direct way to implement that requirement on a switch used by multiple office teams?

  1. Review real-time interface bandwidth
  2. Review system and crash logs
  3. Monitor switch processes and resource use
  4. Inspect port link status and error counters
  5. Inspect the ARP neighbor table

Explanation

Correct Answer

B:

Given the described goal, system logs and crash records give chronological evidence of faults that ordinary MAC counters miss. The operator can test this claim by the specific check: correlate uptime, crash-event timestamps and the observed outage window.

Incorrect Answers

A:

Compared with the requested “Review system and crash logs” at the clinic, this would identify whether a congested uplink is responsible for poor application performance instead: port traffic counters show observed utilization trends and potential saturation. At the clinic, the operational proof would instead be to correlate uptime, crash-event timestamps and the observed outage window, whereas “Review real-time interface bandwidth” is validated by a different test: compare ingress and egress rates with the port's negotiated capacity.

C:

Compared with the requested “Review system and crash logs” at the clinic, this would diagnose slow management responsiveness despite links remaining operational instead: process and resource observations expose control-plane load separately from forwarding counters. At the clinic, the operational proof would instead be to correlate uptime, crash-event timestamps and the observed outage window, whereas “Monitor switch processes and resource use” is validated by a different test: check CPU/memory/process utilization during the delay.

D:

Compared with the requested “Review system and crash logs” at the clinic, this would differentiate a physical cable or optic fault from a VLAN policy problem instead: interface monitors expose operational status, packet errors and traffic totals. At the clinic, the operational proof would instead be to correlate uptime, crash-event timestamps and the observed outage window, whereas “Inspect port link status and error counters” is validated by a different test: check link-up state, CRC/error counters and the remote peer's port statistics.

E:

For the clinic, “Inspect the ARP neighbor table” is a different type of control from “Review system and crash logs”: ARP mappings associate an IPv4 neighbor address with a hardware destination on the relevant network. Unlike the requested feature, that setting addresses the need to investigate missing IPv4 adjacency at a routed switch interface, not the objective to determine whether a restart or process fault explains a sudden traffic interruption.

Question 695

The operator has decided to review system and crash logs on a production FortiSwitch fabric at the data hall. Which operational behavior is the most reasonable expectation of that specific feature?

  1. Interface monitors expose operational status, packet errors and traffic totals
  2. System logs and crash records give chronological evidence of faults that ordinary MAC counters miss
  3. ARP mappings associate an IPv4 neighbor address with a hardware destination on the relevant network
  4. Process and resource observations expose control-plane load separately from forwarding counters

Explanation

Correct Answer

B:

The switch behavior that matters is: the configured operation is meant to determine whether a restart or process fault explains a sudden traffic interruption. The most relevant validation is to correlate uptime, crash-event timestamps and the observed outage window for the equipment at the data hall.

Incorrect Answers

A:

That behavior applies when engineers “Inspect port link status and error counters”; the different operation “Review system and crash logs” is intended to determine whether a restart or process fault explains a sudden traffic interruption. That different feature is verified by check link-up state, CRC/error counters and the remote peer's port statistics; for “Review system and crash logs” on a production FortiSwitch fabric, the relevant evidence is to correlate uptime, crash-event timestamps and the observed outage window.

C:

That behavior applies when engineers “Inspect the ARP neighbor table”; the different operation “Review system and crash logs” is intended to determine whether a restart or process fault explains a sudden traffic interruption. That different feature is verified by check IP-to-MAC resolution and the reachable SVI or routed interface; for “Review system and crash logs” on a production FortiSwitch fabric, the relevant evidence is to correlate uptime, crash-event timestamps and the observed outage window.

D:

This outcome would be relevant to “Monitor switch processes and resource use” at the data hall, not the task “Review system and crash logs”; the other task is to diagnose slow management responsiveness despite links remaining operational. The action “Review system and crash logs” targets a different result: system logs and crash records give chronological evidence of faults that ordinary MAC counters miss; the proposed alternative would instead be checked by check CPU/memory/process utilization during the delay.

Question 696

A FortiSwitch engineer in the warehouse is documenting successful operation of “Review system and crash logs.” Which measurement or inspection confirms it?

  1. Check link-up state, CRC/error counters and the remote peer's port statistics
  2. Check IP-to-MAC resolution and the reachable SVI or routed interface
  3. Correlate uptime, crash-event timestamps and the observed outage window
  4. Check CPU/memory/process utilization during the delay

Explanation

Correct Answer

C:

At this network boundary, system logs and crash records give chronological evidence of faults that ordinary MAC counters miss. Directly measuring that result demonstrates whether the step to determine whether a restart or process fault explains a sudden traffic interruption succeeded on a newly racked distribution unit.

Incorrect Answers

A:

This check is suited to “Inspect port link status and error counters” when trying to differentiate a physical cable or optic fault from a VLAN policy problem, not to verify “Review system and crash logs” at the warehouse. Checking “Review system and crash logs” at the warehouse requires evidence of its own mechanism: system logs and crash records give chronological evidence of faults that ordinary MAC counters miss; that is not the outcome measured by “Inspect port link status and error counters”.

B:

This check is suited to “Inspect the ARP neighbor table” when trying to investigate missing IPv4 adjacency at a routed switch interface, not to verify “Review system and crash logs” at the warehouse. Checking “Review system and crash logs” at the warehouse requires evidence of its own mechanism: system logs and crash records give chronological evidence of faults that ordinary MAC counters miss; that is not the outcome measured by “Inspect the ARP neighbor table”.

D:

The proposed check concerns “Monitor switch processes and resource use” rather than “Review system and crash logs”: process and resource observations expose control-plane load separately from forwarding counters. For “Review system and crash logs” on a newly racked distribution unit, a better test would be to correlate uptime, crash-event timestamps and the observed outage window, which targets determine whether a restart or process fault explains a sudden traffic interruption rather than the alternative diagnostic “Monitor switch processes and resource use”.

Question 697

On two distribution switches in the headquarters, the next task is to diagnose slow management responsiveness despite links remaining operational. What is the appropriate configuration decision?

  1. Monitor switch processes and resource use
  2. Inspect LLDP neighbors
  3. Inspect the MAC address forwarding table
  4. Inspect VLAN port membership and port PDUs

Explanation

Correct Answer

A:

In this deployment, process and resource observations expose control-plane load separately from forwarding counters. This distinction is material to the headquarters, where the stated goal is to diagnose slow management responsiveness despite links remaining operational.

Incorrect Answers

B:

Compared with the requested “Monitor switch processes and resource use” at the headquarters, this would locate a cable connected to an unexpected adjacent switch or access endpoint instead: LLDP neighbor records identify the chassis and remote port discovered on a local link. At the headquarters, the operational proof would instead be to check CPU/memory/process utilization during the delay, whereas “Inspect LLDP neighbors” is validated by a different test: compare local port IDs with advertised remote chassis/port identifiers.

C:

For the headquarters, “Inspect the MAC address forwarding table” is a different type of control from “Monitor switch processes and resource use”: MAC table entries associate destination reachability with VLAN and physical or trunk ports. Unlike the requested feature, that setting addresses the need to find which switch interface currently learns a particular endpoint MAC, not the objective to diagnose slow management responsiveness despite links remaining operational.

D:

Compared with the requested “Monitor switch processes and resource use” at the headquarters, 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 headquarters, the operational proof would instead be to check CPU/memory/process utilization during the delay, 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.

Question 698

On a staging FortiSwitch, “Monitor switch processes and resource use” is configured for the hospital wing. What effect should an administrator expect without assuming unrelated features are enabled?

  1. Interface monitors expose operational status, packet errors and traffic totals
  2. LLDP neighbor records identify the chassis and remote port discovered on a local link
  3. MAC table entries associate destination reachability with VLAN and physical or trunk ports
  4. VLAN membership and protocol data units show forwarding eligibility and neighbor protocol negotiation
  5. Process and resource observations expose control-plane load separately from forwarding counters

Explanation

Correct Answer

E:

For the stated requirement, the configured operation is meant to diagnose slow management responsiveness despite links remaining operational. The most relevant validation is to check CPU/memory/process utilization during the delay for the equipment at the hospital wing.

Incorrect Answers

A:

That behavior applies when engineers “Inspect port link status and error counters”; the different operation “Monitor switch processes and resource use” is intended to diagnose slow management responsiveness despite links remaining operational. That different feature is verified by check link-up state, CRC/error counters and the remote peer's port statistics; for “Monitor switch processes and resource use” on a staging FortiSwitch, the relevant evidence is to check CPU/memory/process utilization during the delay.

B:

This outcome would be relevant to “Inspect LLDP neighbors” at the hospital wing, not the task “Monitor switch processes and resource use”; the other task is to locate a cable connected to an unexpected adjacent switch or access endpoint. The action “Monitor switch processes and resource use” targets a different result: process and resource observations expose control-plane load separately from forwarding counters; the proposed alternative would instead be checked by compare local port IDs with advertised remote chassis/port identifiers.

C:

That behavior applies when engineers “Inspect the MAC address forwarding table”; the different operation “Monitor switch processes and resource use” is intended to diagnose slow management responsiveness despite links remaining operational. That different feature is verified by compare the endpoint's MAC/VLAN entry with the expected cabling; for “Monitor switch processes and resource use” on a staging FortiSwitch, the relevant evidence is to check CPU/memory/process utilization during the delay.

D:

That behavior applies when engineers “Inspect VLAN port membership and port PDUs”; the different operation “Monitor switch processes and resource use” is intended to diagnose slow management responsiveness despite links remaining operational. That different feature is verified by compare allowed/native/untagged lists and captured LLDP or STP PDUs on the link; for “Monitor switch processes and resource use” on a staging FortiSwitch, the relevant evidence is to check CPU/memory/process utilization during the delay.

Question 699

The accepted design for the training center requires the ability to explain why frames with the expected VLAN tag do not traverse a specific link. Which switch feature is the closest fit?

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

Explanation

Correct Answer

C:

The deciding detail is that VLAN membership and protocol data units show forwarding eligibility and neighbor protocol negotiation. This distinction is material to the training center, where the stated goal is to explain why frames with the expected VLAN tag do not traverse a specific link.

Incorrect Answers

A:

For the training center, “Inspect the ARP neighbor table” is a different type of control from “Inspect VLAN port membership and port PDUs”: ARP mappings associate an IPv4 neighbor address with a hardware destination on the relevant network. Unlike the requested feature, that setting addresses the need to investigate missing IPv4 adjacency at a routed switch interface, not the objective to explain why frames with the expected VLAN tag do not traverse a specific link.

B:

Compared with the requested “Inspect VLAN port membership and port PDUs” at the training center, this would differentiate a physical cable or optic fault from a VLAN policy problem instead: interface monitors expose operational status, packet errors and traffic totals. At the training center, the operational proof would instead be to compare allowed/native/untagged lists and captured LLDP or STP PDUs on the link, whereas “Inspect port link status and error counters” is validated by a different test: check link-up state, CRC/error counters and the remote peer's port statistics.

D:

Compared with the requested “Inspect VLAN port membership and port PDUs” at the training center, this would determine whether a restart or process fault explains a sudden traffic interruption instead: system logs and crash records give chronological evidence of faults that ordinary MAC counters miss. At the training center, the operational proof would instead be to compare allowed/native/untagged lists and captured LLDP or STP PDUs on the link, whereas “Review system and crash logs” is validated by a different test: correlate uptime, crash-event timestamps and the observed outage window.

Question 700

On a central switching stack, “Inspect VLAN port membership and port PDUs” is configured for the lab. What effect should an administrator expect without assuming unrelated features are enabled?

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

Explanation

Correct Answer

C:

The relevant mechanism is: the configured operation is meant to explain why frames with the expected VLAN tag do not traverse a specific link. The most relevant validation is to compare allowed/native/untagged lists and captured LLDP or STP PDUs on the link for the equipment at the lab.

Incorrect Answers

A:

That behavior applies when engineers “Inspect the ARP neighbor table”; the different operation “Inspect VLAN port membership and port PDUs” is intended to explain why frames with the expected VLAN tag do not traverse a specific link. That different feature is verified by check IP-to-MAC resolution and the reachable SVI or routed interface; for “Inspect VLAN port membership and port PDUs” on a central switching stack, the relevant evidence is to compare allowed/native/untagged lists and captured LLDP or STP PDUs on the link.

B:

This outcome would be relevant to “Review system and crash logs” at the lab, not the task “Inspect VLAN port membership and port PDUs”; the other task is to determine whether a restart or process fault explains a sudden traffic interruption. The action “Inspect VLAN port membership and port PDUs” targets a different result: VLAN membership and protocol data units show forwarding eligibility and neighbor protocol negotiation; the proposed alternative would instead be checked by correlate uptime, crash-event timestamps and the observed outage window.

D:

That behavior applies when engineers “Inspect port link status and error counters”; the different operation “Inspect VLAN port membership and port PDUs” is intended to explain why frames with the expected VLAN tag do not traverse a specific link. That different feature is verified by check link-up state, CRC/error counters and the remote peer's port statistics; for “Inspect VLAN port membership and port PDUs” on a central switching stack, the relevant evidence is to compare allowed/native/untagged lists and captured LLDP or STP PDUs on the link.

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