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

Question 540

The work order to avoid inspecting ARP coming from an explicitly trusted network segment is marked complete on a recently upgraded FortiSwitch. Which observation most directly tests the completed configuration?

  1. Capture whether the spoof is ordinary IPv4 payload traffic or ARP control traffic
  2. Capture a packet's EtherType and compare it with protocol-VLAN policy entries
  3. Review ARP trust state on the uplink and confirm that host ports remain untrusted
  4. Inspect the static entry and compare its interface, IPv4 address and MAC
  5. Inspect the configured allowlist and observe whether an unlisted server offer is accepted

Explanation

Correct Answer

C:

At this network boundary, the switch can designate trusted ARP interfaces when the network design warrants an exception. Directly measuring that result demonstrates whether the step to avoid inspecting ARP coming from an explicitly trusted network segment succeeded on a recently upgraded FortiSwitch.

Incorrect Answers

A:

This check is suited to “Avoid using source guard as an ARP-only inspection replacement” when trying to protect both IPv4 data-source integrity and ARP neighbor claims using the appropriate separate controls, not to verify “Trust an infrastructure port for ARP inspection when justified” at the campus. Checking “Trust an infrastructure port for ARP inspection when justified” at the campus requires evidence of its own mechanism: the switch can designate trusted ARP interfaces when the network design warrants an exception; that is not the outcome measured by “Avoid using source guard as an ARP-only inspection replacement”.

B:

The proposed check concerns “Use protocol-based VLAN classification” rather than “Trust an infrastructure port for ARP inspection when justified”: protocol-based classification maps matching frame protocol to the configured VLAN policy. For “Trust an infrastructure port for ARP inspection when justified” on a recently upgraded FortiSwitch, a better test would be to review ARP trust state on the uplink and confirm that host ports remain untrusted, which targets avoid inspecting ARP coming from an explicitly trusted network segment rather than the alternative diagnostic “Use protocol-based VLAN classification”.

D:

This check is suited to “Provision a static IPv4 source guard entry” when trying to admit an appliance with a fixed address under source-guard enforcement, not to verify “Trust an infrastructure port for ARP inspection when justified” at the campus. Checking “Trust an infrastructure port for ARP inspection when justified” at the campus requires evidence of its own mechanism: the switch can designate trusted ARP interfaces when the network design warrants an exception; that is not the outcome measured by “Provision a static IPv4 source guard entry”.

E:

The proposed check concerns “Configure an authorized DHCP server list” rather than “Trust an infrastructure port for ARP inspection when justified”: server whitelisting can narrow acceptable DHCP sources beyond the physical trust-port arrangement. For “Trust an infrastructure port for ARP inspection when justified” on a recently upgraded FortiSwitch, a better test would be to review ARP trust state on the uplink and confirm that host ports remain untrusted, which targets avoid inspecting ARP coming from an explicitly trusted network segment rather than the alternative diagnostic “Configure an authorized DHCP server list”.

Question 541

A network architect documents a single goal for a FortiLink-managed access switch: discard host IP packets that use source addresses not authorized for that interface. Which listed procedure provides that capability?

  1. Trust an infrastructure port for ARP inspection when justified
  2. Enable IPv4 source guard on an access port
  3. Apply IPv6 RA guard where supported
  4. Include DHCP option 82 for relay-agent context

Explanation

Correct Answer

B:

In this deployment, IP source guard matches IPv4 origin against static or DHCP-snooping-learned source bindings. This distinction is material to the remote depot, where the stated goal is to discard host IP packets that use source addresses not authorized for that interface.

Incorrect Answers

A:

Compared with the requested “Enable IPv4 source guard on an access port” at the remote depot, this would avoid inspecting ARP coming from an explicitly trusted network segment instead: the switch can designate trusted ARP interfaces when the network design warrants an exception. At the remote depot, the operational proof would instead be to compare the source IP of rejected traffic with the allowed binding set, whereas “Trust an infrastructure port for ARP inspection when justified” is validated by a different test: review ARP trust state on the uplink and confirm that host ports remain untrusted.

C:

For the remote depot, “Apply IPv6 RA guard where supported” is a different type of control from “Enable IPv4 source guard on an access port”: RA guard filters IPv6 router advertisements originating from untrusted switch access links. Unlike the requested feature, that setting addresses the need to block unauthorized IPv6 router advertisements on user-facing ports, not the objective to discard host IP packets that use source addresses not authorized for that interface.

D:

Compared with the requested “Enable IPv4 source guard on an access port” at the remote depot, this would identify the access circuit or switch involved in a DHCP client request instead: option 82 carries relay-agent information such as circuit and remote identifiers toward the DHCP infrastructure. At the remote depot, the operational proof would instead be to compare the source IP of rejected traffic with the allowed binding set, whereas “Include DHCP option 82 for relay-agent context” is validated by a different test: capture a forwarded DHCP discover and inspect its option-82 fields.

Question 542

On a switch linked to a FortiGate running FortiOS 7.6, “Enable IPv4 source guard on an access port” is configured for the lab. What effect should an administrator expect without assuming unrelated features are enabled?

  1. DHCP snooping checks DHCP packets on the VLAN and builds trusted IP-to-MAC lease bindings
  2. IP source guard matches IPv4 origin against static or DHCP-snooping-learned source bindings
  3. MAC-based VLAN policies identify permitted source MAC addresses and map them to VLANs
  4. Dynamic source-guard entries depend on valid snooping bindings for the interface and source identity

Explanation

Correct Answer

B:

For the stated requirement, the configured operation is meant to discard host IP packets that use source addresses not authorized for that interface. The most relevant validation is to compare the source IP of rejected traffic with the allowed binding set for the equipment at the lab.

Incorrect Answers

A:

That behavior applies when engineers “Enable DHCP snooping on an access VLAN”; the different operation “Enable IPv4 source guard on an access port” is intended to discard host IP packets that use source addresses not authorized for that interface. That different feature is verified by inspect DHCP snooping status and the learned bindings for that VLAN; for “Enable IPv4 source guard on an access port” on a switch linked to a FortiGate running FortiOS 7.6, the relevant evidence is to compare the source IP of rejected traffic with the allowed binding set.

C:

This outcome would be relevant to “Use MAC-based VLAN classification” at the lab, not the task “Enable IPv4 source guard on an access port”; the other task is to assign a known endpoint to its designated VLAN independent of the access-port default. The action “Enable IPv4 source guard on an access port” targets a different result: IP source guard matches IPv4 origin against static or DHCP-snooping-learned source bindings; the proposed alternative would instead be checked by inspect the device MAC and the associated VLAN mapping rule.

D:

That behavior applies when engineers “Check DHCP-derived bindings for IP source guard”; the different operation “Enable IPv4 source guard on an access port” is intended to discard host IP packets that use source addresses not authorized for that interface. That different feature is verified by read the active binding after the move and compare it with the client's new port; for “Enable IPv4 source guard on an access port” on a switch linked to a FortiGate running FortiOS 7.6, the relevant evidence is to compare the source IP of rejected traffic with the allowed binding set.

Question 543

An auditor wants operational evidence for the switch action “Enable IPv4 source guard on an access port” at the staging rack. Which check is relevant?

  1. Send a test rogue offer and verify it is rejected on the client-facing port
  2. Correlate the rogue-server event with VLAN, port and packet source MAC
  3. Compare the source IP of rejected traffic with the allowed binding set
  4. Inspect per-VLAN ARP inspection drops after sending an invalid ARP advertisement

Explanation

Correct Answer

C:

The deciding detail is that IP source guard matches IPv4 origin against static or DHCP-snooping-learned source bindings. Directly measuring that result demonstrates whether the step to discard host IP packets that use source addresses not authorized for that interface succeeded on a switch serving a high-density endpoint area.

Incorrect Answers

A:

The proposed check concerns “Keep ordinary client ports DHCP-snooping untrusted” rather than “Enable IPv4 source guard on an access port”: untrusted ports are checked for invalid DHCP server activity and may log rogue-server detection. For “Enable IPv4 source guard on an access port” on a switch serving a high-density endpoint area, a better test would be to compare the source IP of rejected traffic with the allowed binding set, which targets discard host IP packets that use source addresses not authorized for that interface rather than the alternative diagnostic “Keep ordinary client ports DHCP-snooping untrusted”.

B:

This check is suited to “Investigate rogue DHCP offer logs” when trying to locate an untrusted server attached to a client-facing port, not to verify “Enable IPv4 source guard on an access port” at the staging rack. Checking “Enable IPv4 source guard on an access port” at the staging rack requires evidence of its own mechanism: IP source guard matches IPv4 origin against static or DHCP-snooping-learned source bindings; that is not the outcome measured by “Investigate rogue DHCP offer logs”.

D:

This check is suited to “Enable dynamic ARP inspection on a VLAN” when trying to block ARP packets with invalid IP-to-MAC assertions on untrusted access ports, not to verify “Enable IPv4 source guard on an access port” at the staging rack. Checking “Enable IPv4 source guard on an access port” at the staging rack requires evidence of its own mechanism: IP source guard matches IPv4 origin against static or DHCP-snooping-learned source bindings; that is not the outcome measured by “Enable dynamic ARP inspection on a VLAN”.

Question 544

The operational requirement for a managed switch running FortiSwitchOS 7.6 at the research building is to admit an appliance with a fixed address under source-guard enforcement. Which FortiSwitch choice directly targets it?

  1. Configure an authorized DHCP server list
  2. Provision a static IPv4 source guard entry
  3. Avoid using source guard as an ARP-only inspection replacement
  4. Use protocol-based VLAN classification
  5. Enable IPv4 source guard on an access port

Explanation

Correct Answer

B:

The relevant mechanism is: a manually configured source binding can permit a fixed IP/MAC identity without relying on a DHCP lease. The operator can test this claim by the specific check: inspect the static entry and compare its interface, IPv4 address and MAC.

Incorrect Answers

A:

Compared with the requested “Provision a static IPv4 source guard entry” at the research building, this would limit DHCP server acceptance to specified legitimate server addresses instead: server whitelisting can narrow acceptable DHCP sources beyond the physical trust-port arrangement. At the research building, the operational proof would instead be to inspect the static entry and compare its interface, IPv4 address and MAC, whereas “Configure an authorized DHCP server list” is validated by a different test: inspect the configured allowlist and observe whether an unlisted server offer is accepted.

C:

For the research building, “Avoid using source guard as an ARP-only inspection replacement” is a different type of control from “Provision a static IPv4 source guard entry”: IPSG filters IPv4 packet sources while DAI validates ARP IP/MAC statements; they address different packet classes. Unlike the requested feature, that setting addresses the need to protect both IPv4 data-source integrity and ARP neighbor claims using the appropriate separate controls, not the objective to admit an appliance with a fixed address under source-guard enforcement.

D:

Compared with the requested “Provision a static IPv4 source guard entry” at the research building, this would assign inbound traffic to a VLAN based on its protocol identifier when required instead: protocol-based classification maps matching frame protocol to the configured VLAN policy. At the research building, the operational proof would instead be to inspect the static entry and compare its interface, IPv4 address and MAC, whereas “Use protocol-based VLAN classification” is validated by a different test: capture a packet's EtherType and compare it with protocol-VLAN policy entries.

E:

Compared with the requested “Provision a static IPv4 source guard entry” at the research building, this would discard host IP packets that use source addresses not authorized for that interface instead: IP source guard matches IPv4 origin against static or DHCP-snooping-learned source bindings. At the research building, the operational proof would instead be to inspect the static entry and compare its interface, IPv4 address and MAC, whereas “Enable IPv4 source guard on an access port” is validated by a different test: compare the source IP of rejected traffic with the allowed binding set.

Question 545

A change record for a remote FortiSwitch installation states “Provision a static IPv4 source guard entry.” Which description correctly explains what this will accomplish?

  1. A static port/IP/MAC binding supplies known information for binding-aware protections
  2. Source subnet classification uses IP address information to select a configured VLAN association
  3. A manually configured source binding can permit a fixed IP/MAC identity without relying on a DHCP lease
  4. A DHCP-snooping trusted port may convey legitimate server replies while host-facing ports remain untrusted

Explanation

Correct Answer

C:

This approach fits because the configured operation is meant to admit an appliance with a fixed address under source-guard enforcement. The most relevant validation is to inspect the static entry and compare its interface, IPv4 address and MAC for the equipment at the clinic.

Incorrect Answers

A:

That behavior applies when engineers “Create a static DHCP-snooping binding for a fixed-IP host”; the different operation “Provision a static IPv4 source guard entry” is intended to admit an appliance with a fixed address under source-guard enforcement. That different feature is verified by inspect the configured static binding and verify the endpoint's actual source identity; for “Provision a static IPv4 source guard entry” on a remote FortiSwitch installation, the relevant evidence is to inspect the static entry and compare its interface, IPv4 address and MAC.

B:

That behavior applies when engineers “Use IP-subnet-based VLAN assignment”; the different operation “Provision a static IPv4 source guard entry” is intended to admit an appliance with a fixed address under source-guard enforcement. That different feature is verified by compare received source IP with configured IP-based VLAN mapping; for “Provision a static IPv4 source guard entry” on a remote FortiSwitch installation, the relevant evidence is to inspect the static entry and compare its interface, IPv4 address and MAC.

D:

This outcome would be relevant to “Trust only the uplink toward a legitimate DHCP server” at the clinic, not the task “Provision a static IPv4 source guard entry”; the other task is to allow server responses on an approved infrastructure-facing interface. The action “Provision a static IPv4 source guard entry” targets a different result: a manually configured source binding can permit a fixed IP/MAC identity without relying on a DHCP lease; the proposed alternative would instead be checked by check configured trusted interfaces and the source port of DHCP offers.

Question 546

A technician says “Provision a static IPv4 source guard entry” has solved the issue at the data hall. Which diagnostic step would substantiate that claim?

  1. Compare ARP inspection statistics for the endpoint port and the relevant VLAN
  2. Compare a client's address and MAC with the active binding database
  3. Read storm-control counters during the observed high-rate event
  4. Inspect the static entry and compare its interface, IPv4 address and MAC

Explanation

Correct Answer

D:

The critical distinction is that a manually configured source binding can permit a fixed IP/MAC identity without relying on a DHCP lease. Directly measuring that result demonstrates whether the step to admit an appliance with a fixed address under source-guard enforcement succeeded on an endpoint-facing FortiSwitch port.

Incorrect Answers

A:

The proposed check concerns “Keep DAI untrusted on endpoint interfaces” rather than “Provision a static IPv4 source guard entry”: untrusted ARP senders must match the permitted binding state to be forwarded. For “Provision a static IPv4 source guard entry” on an endpoint-facing FortiSwitch port, a better test would be to inspect the static entry and compare its interface, IPv4 address and MAC, which targets admit an appliance with a fixed address under source-guard enforcement rather than the alternative diagnostic “Keep DAI untrusted on endpoint interfaces”.

B:

This check is suited to “Use the DHCP-snooping binding table” when trying to associate leased IPv4 identities with particular MAC addresses and ports, not to verify “Provision a static IPv4 source guard entry” at the data hall. Checking “Provision a static IPv4 source guard entry” at the data hall requires evidence of its own mechanism: a manually configured source binding can permit a fixed IP/MAC identity without relying on a DHCP lease; that is not the outcome measured by “Use the DHCP-snooping binding table”.

C:

This check is suited to “Use storm control on a broadcast-heavy access port” when trying to limit disruption from excessive broadcast, multicast or unknown-unicast traffic, not to verify “Provision a static IPv4 source guard entry” at the data hall. Checking “Provision a static IPv4 source guard entry” at the data hall requires evidence of its own mechanism: a manually configured source binding can permit a fixed IP/MAC identity without relying on a DHCP lease; that is not the outcome measured by “Use storm control on a broadcast-heavy access port”.

Question 547

During a change window in the development floor, engineers are asked to explain why a recently moved DHCP client loses permitted IPv4 connectivity. What should they configure rather than using a feature for an adjacent purpose?

  1. Check DHCP-derived bindings for IP source guard
  2. Include DHCP option 82 for relay-agent context
  3. Enable DHCP snooping on an access VLAN
  4. Trust an infrastructure port for ARP inspection when justified

Explanation

Correct Answer

A:

That setting is appropriate here because dynamic source-guard entries depend on valid snooping bindings for the interface and source identity. This distinction is material to the development floor, where the stated goal is to explain why a recently moved DHCP client loses permitted IPv4 connectivity.

Incorrect Answers

B:

Compared with the requested “Check DHCP-derived bindings for IP source guard” at the development floor, this would identify the access circuit or switch involved in a DHCP client request instead: option 82 carries relay-agent information such as circuit and remote identifiers toward the DHCP infrastructure. At the development floor, the operational proof would instead be to read the active binding after the move and compare it with the client's new port, whereas “Include DHCP option 82 for relay-agent context” is validated by a different test: capture a forwarded DHCP discover and inspect its option-82 fields.

C:

Compared with the requested “Check DHCP-derived bindings for IP source guard” at the development floor, this would stop an untrusted access port from supplying rogue DHCP server messages instead: DHCP snooping checks DHCP packets on the VLAN and builds trusted IP-to-MAC lease bindings. At the development floor, the operational proof would instead be to read the active binding after the move and compare it with the client's new port, whereas “Enable DHCP snooping on an access VLAN” is validated by a different test: inspect DHCP snooping status and the learned bindings for that VLAN.

D:

For the development floor, “Trust an infrastructure port for ARP inspection when justified” is a different type of control from “Check DHCP-derived bindings for IP source guard”: the switch can designate trusted ARP interfaces when the network design warrants an exception. Unlike the requested feature, that setting addresses the need to avoid inspecting ARP coming from an explicitly trusted network segment, not the objective to explain why a recently moved DHCP client loses permitted IPv4 connectivity.

Question 548

An operations log records this activity at the conference venue: check DHCP-derived bindings for IP source guard. Which result is specifically attributable to that action?

  1. DAI consults valid binding information to reject spoofed ARP traffic before it can poison neighbors
  2. MAC-based VLAN policies identify permitted source MAC addresses and map them to VLANs
  3. A manually configured source binding can permit a fixed IP/MAC identity without relying on a DHCP lease
  4. Dynamic source-guard entries depend on valid snooping bindings for the interface and source identity
  5. DHCP snooping checks DHCP packets on the VLAN and builds trusted IP-to-MAC lease bindings

Explanation

Correct Answer

D:

This is the precise control because the configured operation is meant to explain why a recently moved DHCP client loses permitted IPv4 connectivity. The most relevant validation is to read the active binding after the move and compare it with the client's new port for the equipment at the conference venue.

Incorrect Answers

A:

That behavior applies when engineers “Enable dynamic ARP inspection on a VLAN”; the different operation “Check DHCP-derived bindings for IP source guard” is intended to explain why a recently moved DHCP client loses permitted IPv4 connectivity. That different feature is verified by inspect per-VLAN ARP inspection drops after sending an invalid ARP advertisement; for “Check DHCP-derived bindings for IP source guard” on a FortiLink-managed access switch, the relevant evidence is to read the active binding after the move and compare it with the client's new port.

B:

That behavior applies when engineers “Use MAC-based VLAN classification”; the different operation “Check DHCP-derived bindings for IP source guard” is intended to explain why a recently moved DHCP client loses permitted IPv4 connectivity. That different feature is verified by inspect the device MAC and the associated VLAN mapping rule; for “Check DHCP-derived bindings for IP source guard” on a FortiLink-managed access switch, the relevant evidence is to read the active binding after the move and compare it with the client's new port.

C:

This outcome would be relevant to “Provision a static IPv4 source guard entry” at the conference venue, not the task “Check DHCP-derived bindings for IP source guard”; the other task is to admit an appliance with a fixed address under source-guard enforcement. The action “Check DHCP-derived bindings for IP source guard” targets a different result: dynamic source-guard entries depend on valid snooping bindings for the interface and source identity; the proposed alternative would instead be checked by inspect the static entry and compare its interface, IPv4 address and MAC.

E:

That behavior applies when engineers “Enable DHCP snooping on an access VLAN”; the different operation “Check DHCP-derived bindings for IP source guard” is intended to explain why a recently moved DHCP client loses permitted IPv4 connectivity. That different feature is verified by inspect DHCP snooping status and the learned bindings for that VLAN; for “Check DHCP-derived bindings for IP source guard” on a FortiLink-managed access switch, the relevant evidence is to read the active binding after the move and compare it with the client's new port.

Question 549

After implementing “Check DHCP-derived bindings for IP source guard,” the site engineer needs to assess its actual effect on a switch linked to a FortiGate running FortiOS 7.6. Which test is the best match?

  1. Compare observed frame rates with the selected per-port storm-control threshold
  2. Send a test rogue offer and verify it is rejected on the client-facing port
  3. Read the active binding after the move and compare it with the client's new port
  4. Correlate the rogue-server event with VLAN, port and packet source MAC

Explanation

Correct Answer

C:

The implementation works because dynamic source-guard entries depend on valid snooping bindings for the interface and source identity. Directly measuring that result demonstrates whether the step to explain why a recently moved DHCP client loses permitted IPv4 connectivity succeeded on a switch linked to a FortiGate running FortiOS 7.6.

Incorrect Answers

A:

This check is suited to “Set a storm-control threshold appropriate to link capacity” when trying to contain traffic bursts without discarding ordinary service announcements, not to verify “Check DHCP-derived bindings for IP source guard” at the hospital wing. Checking “Check DHCP-derived bindings for IP source guard” at the hospital wing requires evidence of its own mechanism: dynamic source-guard entries depend on valid snooping bindings for the interface and source identity; that is not the outcome measured by “Set a storm-control threshold appropriate to link capacity”.

B:

This check is suited to “Keep ordinary client ports DHCP-snooping untrusted” when trying to prevent a connected endpoint from acting as an unauthorized address server, not to verify “Check DHCP-derived bindings for IP source guard” at the hospital wing. Checking “Check DHCP-derived bindings for IP source guard” at the hospital wing requires evidence of its own mechanism: dynamic source-guard entries depend on valid snooping bindings for the interface and source identity; that is not the outcome measured by “Keep ordinary client ports DHCP-snooping untrusted”.

D:

The proposed check concerns “Investigate rogue DHCP offer logs” rather than “Check DHCP-derived bindings for IP source guard”: DHCP snooping can log the arrival of DHCP server packets on untrusted interfaces. For “Check DHCP-derived bindings for IP source guard” on a switch linked to a FortiGate running FortiOS 7.6, a better test would be to read the active binding after the move and compare it with the client's new port, which targets explain why a recently moved DHCP client loses permitted IPv4 connectivity rather than the alternative diagnostic “Investigate rogue DHCP offer logs”.

Question 550

For the training center, the network team needs to limit disruption from excessive broadcast, multicast or unknown-unicast traffic. Which change is the most direct way to implement that requirement on a switch serving a high-density endpoint area?

  1. Set a storm-control threshold appropriate to link capacity
  2. Investigate rogue DHCP offer logs
  3. Enable DHCP snooping before dynamic ARP inspection
  4. Use storm control on a broadcast-heavy access port

Explanation

Correct Answer

D:

Given the described goal, storm control rate-limits selected Layer 2 traffic categories at a switch port. The operator can test this claim by the specific check: read storm-control counters during the observed high-rate event.

Incorrect Answers

A:

Compared with the requested “Use storm control on a broadcast-heavy access port” at the training center, this would contain traffic bursts without discarding ordinary service announcements instead: a configured rate threshold distinguishes permitted traffic load from a sustained storm. At the training center, the operational proof would instead be to read storm-control counters during the observed high-rate event, whereas “Set a storm-control threshold appropriate to link capacity” is validated by a different test: compare observed frame rates with the selected per-port storm-control threshold.

B:

For the training center, “Investigate rogue DHCP offer logs” is a different type of control from “Use storm control on a broadcast-heavy access port”: DHCP snooping can log the arrival of DHCP server packets on untrusted interfaces. Unlike the requested feature, that setting addresses the need to locate an untrusted server attached to a client-facing port, not the objective to limit disruption from excessive broadcast, multicast or unknown-unicast traffic.

C:

Compared with the requested “Use storm control on a broadcast-heavy access port” at the training center, this would provide the binding information DAI needs for validating ARP on client networks instead: Fortinet requires DHCP snooping to be configured before enabling DAI for the VLAN. At the training center, the operational proof would instead be to read storm-control counters during the observed high-rate event, whereas “Enable DHCP snooping before dynamic ARP inspection” is validated by a different test: check both the VLAN's DHCP snooping setting and DAI enablement.

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