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

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.

Question 681

A design review at the remote depot discusses “Inspect port link status and error counters.” Select the TWO characteristics that belong to this feature. (Choose TWO.)

  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. Check link-up state, CRC/error counters and the remote peer's port statistics
  4. VLAN membership and protocol data units show forwarding eligibility and neighbor protocol negotiation
  5. MAC table entries associate destination reachability with VLAN and physical or trunk ports

Explanation

Correct Answers

A:

The implementation works because the described mechanism corresponds to the operation that administrators use to differentiate a physical cable or optic fault from a VLAN policy problem. The result should be observable on a managed switch running FortiSwitchOS 7.6.

C:

The stated check directly tests whether the intended function is active at the remote depot. It provides evidence about “Inspect port link status and error counters” beyond ordinary link-up state on a managed switch running FortiSwitchOS 7.6.

Incorrect Answers

B:

That characteristic reflects “Review system and crash logs” rather than “Inspect port link status and error counters” at the remote depot. Its actual role is to determine whether a restart or process fault explains a sudden traffic interruption, a different configuration need.

D:

That characteristic reflects “Inspect VLAN port membership and port PDUs” rather than “Inspect port link status and error counters” at the remote depot. Its actual role is to explain why frames with the expected VLAN tag do not traverse a specific link, a different configuration need.

E:

That characteristic reflects “Inspect the MAC address forwarding table” rather than “Inspect port link status and error counters” at the remote depot. Its actual role is to find which switch interface currently learns a particular endpoint MAC, a different configuration need.

Question 682

A peer review of the lab asks how the design will identify whether a congested uplink is responsible for poor application performance. Which FortiSwitch technique is the correct response?

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

Explanation

Correct Answer

C:

Given the described goal, port traffic counters show observed utilization trends and potential saturation. The operator can test this claim by the specific check: compare ingress and egress rates with the port's negotiated capacity.

Incorrect Answers

A:

Compared with the requested “Review real-time interface bandwidth” 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 ingress and egress rates with the port's negotiated capacity, 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:

Compared with the requested “Review real-time interface bandwidth” 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 ingress and egress rates with the port's negotiated capacity, whereas “Inspect the MAC address forwarding table” is validated by a different test: compare the endpoint's MAC/VLAN entry with the expected cabling.

D:

For the lab, “Review system and crash logs” is a different type of control from “Review real-time interface bandwidth”: 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 identify whether a congested uplink is responsible for poor application performance.

Question 683

The operator has decided to review real-time interface bandwidth on an endpoint-facing FortiSwitch port at the staging rack. Which operational behavior is the most reasonable expectation of that specific feature?

  1. System logs and crash records give chronological evidence of faults that ordinary MAC counters miss
  2. VLAN membership and protocol data units show forwarding eligibility and neighbor protocol negotiation
  3. MAC table entries associate destination reachability with VLAN and physical or trunk ports
  4. Port traffic counters show observed utilization trends and potential saturation
  5. ARP mappings associate an IPv4 neighbor address with a hardware destination on the relevant network

Explanation

Correct Answer

D:

The switch behavior that matters is: the configured operation is meant to identify whether a congested uplink is responsible for poor application performance. The most relevant validation is to compare ingress and egress rates with the port's negotiated capacity for the equipment at the staging rack.

Incorrect Answers

A:

That behavior applies when engineers “Review system and crash logs”; the different operation “Review real-time interface bandwidth” is intended to identify whether a congested uplink is responsible for poor application performance. That different feature is verified by correlate uptime, crash-event timestamps and the observed outage window; for “Review real-time interface bandwidth” on an endpoint-facing FortiSwitch port, the relevant evidence is to compare ingress and egress rates with the port's negotiated capacity.

B:

This outcome would be relevant to “Inspect VLAN port membership and port PDUs” at the staging rack, not the task “Review real-time interface bandwidth”; the other task is to explain why frames with the expected VLAN tag do not traverse a specific link. The action “Review real-time interface bandwidth” targets a different result: port traffic counters show observed utilization trends and potential saturation; 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 “Inspect the MAC address forwarding table”; the different operation “Review real-time interface bandwidth” is intended to identify whether a congested uplink is responsible for poor application performance. That different feature is verified by compare the endpoint's MAC/VLAN entry with the expected cabling; for “Review real-time interface bandwidth” on an endpoint-facing FortiSwitch port, the relevant evidence is to compare ingress and egress rates with the port's negotiated capacity.

E:

That behavior applies when engineers “Inspect the ARP neighbor table”; the different operation “Review real-time interface bandwidth” is intended to identify whether a congested uplink is responsible for poor application performance. That different feature is verified by check IP-to-MAC resolution and the reachable SVI or routed interface; for “Review real-time interface bandwidth” on an endpoint-facing FortiSwitch port, the relevant evidence is to compare ingress and egress rates with the port's negotiated capacity.

Question 684

An auditor wants operational evidence for the switch action “Review real-time interface bandwidth” at the research building. Which check is relevant?

  1. Correlate uptime, crash-event timestamps and the observed outage window
  2. Compare allowed/native/untagged lists and captured LLDP or STP PDUs on the link
  3. Compare the endpoint's MAC/VLAN entry with the expected cabling
  4. Compare ingress and egress rates with the port's negotiated capacity

Explanation

Correct Answer

D:

At this network boundary, port traffic counters show observed utilization trends and potential saturation. Directly measuring that result demonstrates whether the step to identify whether a congested uplink is responsible for poor application performance succeeded on a standalone FortiSwitch appliance.

Incorrect Answers

A:

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 “Review real-time interface bandwidth” at the research building. Checking “Review real-time interface bandwidth” at the research building requires evidence of its own mechanism: port traffic counters show observed utilization trends and potential saturation; that is not the outcome measured by “Review system and crash logs”.

B:

The proposed check concerns “Inspect VLAN port membership and port PDUs” rather than “Review real-time interface bandwidth”: VLAN membership and protocol data units show forwarding eligibility and neighbor protocol negotiation. For “Review real-time interface bandwidth” on a standalone FortiSwitch appliance, a better test would be to compare ingress and egress rates with the port's negotiated capacity, which targets identify whether a congested uplink is responsible for poor application performance rather than the alternative diagnostic “Inspect VLAN port membership and port PDUs”.

C:

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 “Review real-time interface bandwidth” at the research building. Checking “Review real-time interface bandwidth” at the research building requires evidence of its own mechanism: port traffic counters show observed utilization trends and potential saturation; that is not the outcome measured by “Inspect the MAC address forwarding table”.

Question 685

A network architect documents a single goal for a newly commissioned floor switch: find which switch interface currently learns a particular endpoint MAC. Which listed procedure provides that capability?

  1. Inspect LLDP neighbors
  2. Monitor switch processes and resource use
  3. Inspect the MAC address forwarding table
  4. Review real-time interface bandwidth

Explanation

Correct Answer

C:

In this deployment, MAC table entries associate destination reachability with VLAN and physical or trunk ports. This distinction is material to the clinic, where the stated goal is to find which switch interface currently learns a particular endpoint MAC.

Incorrect Answers

A:

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

B:

Compared with the requested “Inspect the MAC address forwarding table” 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 compare the endpoint's MAC/VLAN entry with the expected cabling, whereas “Monitor switch processes and resource use” is validated by a different test: check CPU/memory/process utilization during the delay.

D:

For the clinic, “Review real-time interface bandwidth” is a different type of control from “Inspect the MAC address forwarding table”: port traffic counters show observed utilization trends and potential saturation. Unlike the requested feature, that setting addresses the need to identify whether a congested uplink is responsible for poor application performance, not the objective to find which switch interface currently learns a particular endpoint MAC.

Question 686

A switch change for the data hall consists of this step: inspect the MAC address forwarding table. Which behavior reflects the purpose of that change?

  1. LLDP neighbor records identify the chassis and remote port discovered on a local link
  2. Process and resource observations expose control-plane load separately from forwarding counters
  3. Port traffic counters show observed utilization trends and potential saturation
  4. MAC table entries associate destination reachability with VLAN and physical or trunk ports

Explanation

Correct Answer

D:

For the stated requirement, the configured operation is meant to find which switch interface currently learns a particular endpoint MAC. The most relevant validation is to compare the endpoint's MAC/VLAN entry with the expected cabling for the equipment at the data hall.

Incorrect Answers

A:

This outcome would be relevant to “Inspect LLDP neighbors” at the data hall, not the task “Inspect the MAC address forwarding table”; the other task is to locate a cable connected to an unexpected adjacent switch or access endpoint. The action “Inspect the MAC address forwarding table” targets a different result: MAC table entries associate destination reachability with VLAN and physical or trunk ports; the proposed alternative would instead be checked by compare local port IDs with advertised remote chassis/port identifiers.

B:

That behavior applies when engineers “Monitor switch processes and resource use”; the different operation “Inspect the MAC address forwarding table” is intended to find which switch interface currently learns a particular endpoint MAC. That different feature is verified by check CPU/memory/process utilization during the delay; for “Inspect the MAC address forwarding table” on a local switch administering branch clients, the relevant evidence is to compare the endpoint's MAC/VLAN entry with the expected cabling.

C:

That behavior applies when engineers “Review real-time interface bandwidth”; the different operation “Inspect the MAC address forwarding table” is intended to find which switch interface currently learns a particular endpoint MAC. That different feature is verified by compare ingress and egress rates with the port's negotiated capacity; for “Inspect the MAC address forwarding table” on a local switch administering branch clients, the relevant evidence is to compare the endpoint's MAC/VLAN entry with the expected cabling.

Question 687

A technician says “Inspect the MAC address forwarding table” has solved the issue at the development floor. Which diagnostic step would substantiate that claim?

  1. Check CPU/memory/process utilization during the delay
  2. Compare ingress and egress rates with the port's negotiated capacity
  3. Compare the endpoint's MAC/VLAN entry with the expected cabling
  4. Compare allowed/native/untagged lists and captured LLDP or STP PDUs on the link
  5. Compare local port IDs with advertised remote chassis/port identifiers

Explanation

Correct Answer

C:

The deciding detail is that MAC table entries associate destination reachability with VLAN and physical or trunk ports. Directly measuring that result demonstrates whether the step to find which switch interface currently learns a particular endpoint MAC succeeded on a switch used by multiple office teams.

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 MAC address forwarding table” at the development floor. Checking “Inspect the MAC address forwarding table” at the development floor requires evidence of its own mechanism: MAC table entries associate destination reachability with VLAN and physical or trunk ports; that is not the outcome measured by “Monitor switch processes and resource use”.

B:

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 the MAC address forwarding table” at the development floor. Checking “Inspect the MAC address forwarding table” at the development floor requires evidence of its own mechanism: MAC table entries associate destination reachability with VLAN and physical or trunk ports; that is not the outcome measured by “Review real-time interface bandwidth”.

D:

The proposed check concerns “Inspect VLAN port membership and port PDUs” rather than “Inspect the MAC address forwarding table”: VLAN membership and protocol data units show forwarding eligibility and neighbor protocol negotiation. For “Inspect the MAC address forwarding table” on a switch used by multiple office teams, a better test would be to compare the endpoint's MAC/VLAN entry with the expected cabling, which targets find which switch interface currently learns a particular endpoint MAC rather than the alternative diagnostic “Inspect VLAN port membership and port PDUs”.

E:

The proposed check concerns “Inspect LLDP neighbors” rather than “Inspect the MAC address forwarding table”: LLDP neighbor records identify the chassis and remote port discovered on a local link. For “Inspect the MAC address forwarding table” on a switch used by multiple office teams, a better test would be to compare the endpoint's MAC/VLAN entry with the expected cabling, which targets find which switch interface currently learns a particular endpoint MAC rather than the alternative diagnostic “Inspect LLDP neighbors”.

Question 688

The operational requirement for a production FortiSwitch fabric at the conference venue is to investigate missing IPv4 adjacency at a routed switch interface. Which FortiSwitch choice directly targets it?

  1. Inspect the ARP neighbor table
  2. Monitor switch processes and resource use
  3. Inspect port link status and error counters
  4. Inspect the MAC address forwarding table

Explanation

Correct Answer

A:

The relevant mechanism is: ARP mappings associate an IPv4 neighbor address with a hardware destination on the relevant network. The operator can test this claim by the specific check: check IP-to-MAC resolution and the reachable SVI or routed interface.

Incorrect Answers

B:

For the conference venue, “Monitor switch processes and resource use” is a different type of control from “Inspect the ARP neighbor table”: process and resource observations expose control-plane load separately from forwarding counters. Unlike the requested feature, that setting addresses the need to diagnose slow management responsiveness despite links remaining operational, not the objective to investigate missing IPv4 adjacency at a routed switch interface.

C:

Compared with the requested “Inspect the ARP neighbor table” at the conference venue, 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 conference venue, the operational proof would instead be to check IP-to-MAC resolution and the reachable SVI or routed interface, 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 the ARP neighbor table” 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 IP-to-MAC resolution and the reachable SVI or routed interface, 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 689

The operator has decided to inspect the ARP neighbor table on a newly racked distribution unit at the hospital wing. Which operational behavior is the most reasonable expectation of that specific feature?

  1. Interface monitors expose operational status, packet errors and traffic totals
  2. Process and resource observations expose control-plane load separately from forwarding counters
  3. MAC table entries associate destination reachability with VLAN and physical or trunk ports
  4. ARP mappings associate an IPv4 neighbor address with a hardware destination on the relevant network

Explanation

Correct Answer

D:

This approach fits because the configured operation is meant to investigate missing IPv4 adjacency at a routed switch interface. The most relevant validation is to check IP-to-MAC resolution and the reachable SVI or routed interface for the equipment at the hospital wing.

Incorrect Answers

A:

This outcome would be relevant to “Inspect port link status and error counters” at the hospital wing, not the task “Inspect the ARP neighbor table”; the other task is to differentiate a physical cable or optic fault from a VLAN policy problem. The action “Inspect the ARP neighbor table” targets a different result: ARP mappings associate an IPv4 neighbor address with a hardware destination on the relevant network; the proposed alternative would instead be checked by check link-up state, CRC/error counters and the remote peer's port statistics.

B:

That behavior applies when engineers “Monitor switch processes and resource use”; the different operation “Inspect the ARP neighbor table” is intended to investigate missing IPv4 adjacency at a routed switch interface. That different feature is verified by check CPU/memory/process utilization during the delay; for “Inspect the ARP neighbor table” on a newly racked distribution unit, the relevant evidence is to check IP-to-MAC resolution and the reachable SVI or routed interface.

C:

That behavior applies when engineers “Inspect the MAC address forwarding table”; the different operation “Inspect the ARP neighbor table” is intended to investigate missing IPv4 adjacency at a routed switch interface. That different feature is verified by compare the endpoint's MAC/VLAN entry with the expected cabling; for “Inspect the ARP neighbor table” on a newly racked distribution unit, the relevant evidence is to check IP-to-MAC resolution and the reachable SVI or routed interface.

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

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