Question 530
On a FortiSwitch connected to the security edge, “Enable dynamic ARP inspection on a VLAN” is configured for the conference venue. What effect should an administrator expect without assuming unrelated features are enabled?
- Dynamic source-guard entries depend on valid snooping bindings for the interface and source identity
- DAI consults valid binding information to reject spoofed ARP traffic before it can poison neighbors
- Untrusted ARP senders must match the permitted binding state to be forwarded
- MAC-based VLAN policies identify permitted source MAC addresses and map them to VLANs
Explanation
Correct Answer
B:For the stated requirement, the configured operation is meant to block ARP packets with invalid IP-to-MAC assertions on untrusted access ports. The most relevant validation is to inspect per-VLAN ARP inspection drops after sending an invalid ARP advertisement for the equipment at the conference venue.
Incorrect Answers
A:This outcome would be relevant to “Check DHCP-derived bindings for IP source guard” at the conference venue, not the task “Enable dynamic ARP inspection on a VLAN”; the other task is to explain why a recently moved DHCP client loses permitted IPv4 connectivity. The action “Enable dynamic ARP inspection on a VLAN” targets a different result: DAI consults valid binding information to reject spoofed ARP traffic before it can poison neighbors; the proposed alternative would instead be checked by read the active binding after the move and compare it with the client's new port.
C:That behavior applies when engineers “Keep DAI untrusted on endpoint interfaces”; the different operation “Enable dynamic ARP inspection on a VLAN” is intended to block ARP packets with invalid IP-to-MAC assertions on untrusted access ports. That different feature is verified by compare ARP inspection statistics for the endpoint port and the relevant VLAN; for “Enable dynamic ARP inspection on a VLAN” on a FortiSwitch connected to the security edge, the relevant evidence is to inspect per-VLAN ARP inspection drops after sending an invalid ARP advertisement.
D:That behavior applies when engineers “Use MAC-based VLAN classification”; the different operation “Enable dynamic ARP inspection on a VLAN” is intended to block ARP packets with invalid IP-to-MAC assertions on untrusted access ports. That different feature is verified by inspect the device MAC and the associated VLAN mapping rule; for “Enable dynamic ARP inspection on a VLAN” on a FortiSwitch connected to the security edge, the relevant evidence is to inspect per-VLAN ARP inspection drops after sending an invalid ARP advertisement.
Question 531
A FortiSwitch engineer in the campus is documenting successful operation of “Enable dynamic ARP inspection on a VLAN.” Which measurement or inspection confirms it?
- Send a test rogue offer and verify it is rejected on the client-facing port
- Inspect per-VLAN ARP inspection drops after sending an invalid ARP advertisement
- Correlate the rogue-server event with VLAN, port and packet source MAC
- Compare observed frame rates with the selected per-port storm-control threshold
Explanation
Correct Answer
B:The deciding detail is that DAI consults valid binding information to reject spoofed ARP traffic before it can poison neighbors. Directly measuring that result demonstrates whether the step to block ARP packets with invalid IP-to-MAC assertions on untrusted access ports succeeded on an access switch in routine maintenance.
Incorrect Answers
A: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 “Enable dynamic ARP inspection on a VLAN” at the campus. Checking “Enable dynamic ARP inspection on a VLAN” at the campus requires evidence of its own mechanism: DAI consults valid binding information to reject spoofed ARP traffic before it can poison neighbors; that is not the outcome measured by “Keep ordinary client ports DHCP-snooping untrusted”.
C:The proposed check concerns “Investigate rogue DHCP offer logs” rather than “Enable dynamic ARP inspection on a VLAN”: DHCP snooping can log the arrival of DHCP server packets on untrusted interfaces. For “Enable dynamic ARP inspection on a VLAN” on an access switch in routine maintenance, a better test would be to inspect per-VLAN ARP inspection drops after sending an invalid ARP advertisement, which targets block ARP packets with invalid IP-to-MAC assertions on untrusted access ports rather than the alternative diagnostic “Investigate rogue DHCP offer logs”.
D: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 “Enable dynamic ARP inspection on a VLAN” at the campus. Checking “Enable dynamic ARP inspection on a VLAN” at the campus requires evidence of its own mechanism: DAI consults valid binding information to reject spoofed ARP traffic before it can poison neighbors; that is not the outcome measured by “Set a storm-control threshold appropriate to link capacity”.
Question 532
A switch rollout in the remote depot will be approved only if it can verify ARP statements made by clients rather than exempting them from inspection. Which administrative action meets this acceptance criterion?
- Use storm control on a broadcast-heavy access port
- Use IP-subnet-based VLAN assignment
- Enable DHCP snooping before dynamic ARP inspection
- Keep DAI untrusted on endpoint interfaces
Explanation
Correct Answer
D:The relevant mechanism is: untrusted ARP senders must match the permitted binding state to be forwarded. The operator can test this claim by the specific check: compare ARP inspection statistics for the endpoint port and the relevant VLAN.
Incorrect Answers
A:Compared with the requested “Keep DAI untrusted on endpoint interfaces” at the remote depot, this would limit disruption from excessive broadcast, multicast or unknown-unicast traffic instead: storm control rate-limits selected Layer 2 traffic categories at a switch port. At the remote depot, the operational proof would instead be to compare ARP inspection statistics for the endpoint port and the relevant VLAN, whereas “Use storm control on a broadcast-heavy access port” is validated by a different test: read storm-control counters during the observed high-rate event.
B:For the remote depot, “Use IP-subnet-based VLAN assignment” is a different type of control from “Keep DAI untrusted on endpoint interfaces”: source subnet classification uses IP address information to select a configured VLAN association. Unlike the requested feature, that setting addresses the need to assign traffic from recognized source IPv4 subnets to specific VLANs where supported, not the objective to verify ARP statements made by clients rather than exempting them from inspection.
C:Compared with the requested “Keep DAI untrusted on endpoint interfaces” at the remote depot, 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 remote depot, the operational proof would instead be to compare ARP inspection statistics for the endpoint port and the relevant VLAN, 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.
Question 533
For the branch office, an administrator applies the action “Keep DAI untrusted on endpoint interfaces.” Which effect should appear when it operates as intended?
- Fortinet requires DHCP snooping to be configured before enabling DAI for the VLAN
- Snooping records lease-derived bindings that other protections can reference
- Untrusted ARP senders must match the permitted binding state to be forwarded
- RA guard filters IPv6 router advertisements originating from untrusted switch access links
- Snooping configuration must follow actual VLAN membership and trusted-port boundaries
Explanation
Correct Answer
C:This approach fits because the configured operation is meant to verify ARP statements made by clients rather than exempting them from inspection. The most relevant validation is to compare ARP inspection statistics for the endpoint port and the relevant VLAN for the equipment at the branch office.
Incorrect Answers
A:That behavior applies when engineers “Enable DHCP snooping before dynamic ARP inspection”; the different operation “Keep DAI untrusted on endpoint interfaces” is intended to verify ARP statements made by clients rather than exempting them from inspection. That different feature is verified by check both the VLAN's DHCP snooping setting and DAI enablement; for “Keep DAI untrusted on endpoint interfaces” on a recently upgraded FortiSwitch, the relevant evidence is to compare ARP inspection statistics for the endpoint port and the relevant VLAN.
B:That behavior applies when engineers “Use the DHCP-snooping binding table”; the different operation “Keep DAI untrusted on endpoint interfaces” is intended to verify ARP statements made by clients rather than exempting them from inspection. That different feature is verified by compare a client's address and MAC with the active binding database; for “Keep DAI untrusted on endpoint interfaces” on a recently upgraded FortiSwitch, the relevant evidence is to compare ARP inspection statistics for the endpoint port and the relevant VLAN.
D:That behavior applies when engineers “Apply IPv6 RA guard where supported”; the different operation “Keep DAI untrusted on endpoint interfaces” is intended to verify ARP statements made by clients rather than exempting them from inspection. That different feature is verified by capture unauthorized ICMPv6 router advertisements and monitor guard drops; for “Keep DAI untrusted on endpoint interfaces” on a recently upgraded FortiSwitch, the relevant evidence is to compare ARP inspection statistics for the endpoint port and the relevant VLAN.
E:This outcome would be relevant to “Audit DHCP snooping after VLAN redesign” at the branch office, not the task “Keep DAI untrusted on endpoint interfaces”; the other task is to avoid unintentionally permitting server traffic on newly repurposed host uplinks. The action “Keep DAI untrusted on endpoint interfaces” targets a different result: untrusted ARP senders must match the permitted binding state to be forwarded; the proposed alternative would instead be checked by compare current port trust, VLAN snooping enablement and the revised cabling diagram.
Question 534
A feature acceptance test on a staging FortiSwitch concerns “Keep DAI untrusted on endpoint interfaces.” What should be checked to establish its expected operation?
- Capture a forwarded DHCP discover and inspect its option-82 fields
- Compare ARP inspection statistics for the endpoint port and the relevant VLAN
- Inspect DHCP snooping status and the learned bindings for that VLAN
- Compare the source IP of rejected traffic with the allowed binding set
Explanation
Correct Answer
B:The critical distinction is that untrusted ARP senders must match the permitted binding state to be forwarded. Directly measuring that result demonstrates whether the step to verify ARP statements made by clients rather than exempting them from inspection succeeded on a staging FortiSwitch.
Incorrect Answers
A:The proposed check concerns “Include DHCP option 82 for relay-agent context” rather than “Keep DAI untrusted on endpoint interfaces”: option 82 carries relay-agent information such as circuit and remote identifiers toward the DHCP infrastructure. For “Keep DAI untrusted on endpoint interfaces” on a staging FortiSwitch, a better test would be to compare ARP inspection statistics for the endpoint port and the relevant VLAN, which targets verify ARP statements made by clients rather than exempting them from inspection rather than the alternative diagnostic “Include DHCP option 82 for relay-agent context”.
C:This check is suited to “Enable DHCP snooping on an access VLAN” when trying to stop an untrusted access port from supplying rogue DHCP server messages, not to verify “Keep DAI untrusted on endpoint interfaces” at the factory. Checking “Keep DAI untrusted on endpoint interfaces” at the factory requires evidence of its own mechanism: untrusted ARP senders must match the permitted binding state to be forwarded; that is not the outcome measured by “Enable DHCP snooping on an access VLAN”.
D:This check is suited to “Enable IPv4 source guard on an access port” when trying to discard host IP packets that use source addresses not authorized for that interface, not to verify “Keep DAI untrusted on endpoint interfaces” at the factory. Checking “Keep DAI untrusted on endpoint interfaces” at the factory requires evidence of its own mechanism: untrusted ARP senders must match the permitted binding state to be forwarded; that is not the outcome measured by “Enable IPv4 source guard on an access port”.
Question 535
An administrator responsible for a carefully segmented Layer 2 network in the research building must provide the binding information DAI needs for validating ARP on client networks. Which configuration best matches that precise goal?
- Provision a static IPv4 source guard entry
- Create a static DHCP-snooping binding for a fixed-IP host
- Enable DHCP snooping before dynamic ARP inspection
- Trust only the uplink toward a legitimate DHCP server
Explanation
Correct Answer
C:That setting is appropriate here because Fortinet requires DHCP snooping to be configured before enabling DAI for the VLAN. This distinction is material to the research building, where the stated goal is to provide the binding information DAI needs for validating ARP on client networks.
Incorrect Answers
A:For the research building, “Provision a static IPv4 source guard entry” is a different type of control from “Enable DHCP snooping before dynamic ARP inspection”: a manually configured source binding can permit a fixed IP/MAC identity without relying on a DHCP lease. Unlike the requested feature, that setting addresses the need to admit an appliance with a fixed address under source-guard enforcement, not the objective to provide the binding information DAI needs for validating ARP on client networks.
B:Compared with the requested “Enable DHCP snooping before dynamic ARP inspection” at the research building, this would protect an endpoint whose address was not learned through a DHCP lease instead: a static port/IP/MAC binding supplies known information for binding-aware protections. At the research building, the operational proof would instead be to check both the VLAN's DHCP snooping setting and DAI enablement, whereas “Create a static DHCP-snooping binding for a fixed-IP host” is validated by a different test: inspect the configured static binding and verify the endpoint's actual source identity.
D:Compared with the requested “Enable DHCP snooping before dynamic ARP inspection” at the research building, this would allow server responses on an approved infrastructure-facing interface instead: a DHCP-snooping trusted port may convey legitimate server replies while host-facing ports remain untrusted. At the research building, the operational proof would instead be to check both the VLAN's DHCP snooping setting and DAI enablement, whereas “Trust only the uplink toward a legitimate DHCP server” is validated by a different test: check configured trusted interfaces and the source port of DHCP offers.
Question 536
On a central switching stack, “Enable DHCP snooping before dynamic ARP inspection” is configured for the clinic. What effect should an administrator expect without assuming unrelated features are enabled?
- Source subnet classification uses IP address information to select a configured VLAN association
- Storm control rate-limits selected Layer 2 traffic categories at a switch port
- Fortinet requires DHCP snooping to be configured before enabling DAI for the VLAN
- Untrusted ARP senders must match the permitted binding state to be forwarded
Explanation
Correct Answer
C:This is the precise control because the configured operation is meant to provide the binding information DAI needs for validating ARP on client networks. The most relevant validation is to check both the VLAN's DHCP snooping setting and DAI enablement for the equipment at the clinic.
Incorrect Answers
A:That behavior applies when engineers “Use IP-subnet-based VLAN assignment”; the different operation “Enable DHCP snooping before dynamic ARP inspection” is intended to provide the binding information DAI needs for validating ARP on client networks. That different feature is verified by compare received source IP with configured IP-based VLAN mapping; for “Enable DHCP snooping before dynamic ARP inspection” on a central switching stack, the relevant evidence is to check both the VLAN's DHCP snooping setting and DAI enablement.
B:This outcome would be relevant to “Use storm control on a broadcast-heavy access port” at the clinic, not the task “Enable DHCP snooping before dynamic ARP inspection”; the other task is to limit disruption from excessive broadcast, multicast or unknown-unicast traffic. The action “Enable DHCP snooping before dynamic ARP inspection” targets a different result: Fortinet requires DHCP snooping to be configured before enabling DAI for the VLAN; the proposed alternative would instead be checked by read storm-control counters during the observed high-rate event.
D:That behavior applies when engineers “Keep DAI untrusted on endpoint interfaces”; the different operation “Enable DHCP snooping before dynamic ARP inspection” is intended to provide the binding information DAI needs for validating ARP on client networks. That different feature is verified by compare ARP inspection statistics for the endpoint port and the relevant VLAN; for “Enable DHCP snooping before dynamic ARP inspection” on a central switching stack, the relevant evidence is to check both the VLAN's DHCP snooping setting and DAI enablement.
Question 537
On a FortiSwitch connected to the security edge at the data hall, the team reports that it has configured “Enable DHCP snooping before dynamic ARP inspection.” Which verification provides the strongest direct evidence that the intended function is working?
- Capture unauthorized ICMPv6 router advertisements and monitor guard drops
- Check both the VLAN's DHCP snooping setting and DAI enablement
- Compare a client's address and MAC with the active binding database
- Compare ARP inspection statistics for the endpoint port and the relevant VLAN
- Compare current port trust, VLAN snooping enablement and the revised cabling diagram
Explanation
Correct Answer
B:The implementation works because Fortinet requires DHCP snooping to be configured before enabling DAI for the VLAN. Directly measuring that result demonstrates whether the step to provide the binding information DAI needs for validating ARP on client networks succeeded on a FortiSwitch connected to the security edge.
Incorrect Answers
A:This check is suited to “Apply IPv6 RA guard where supported” when trying to block unauthorized IPv6 router advertisements on user-facing ports, not to verify “Enable DHCP snooping before dynamic ARP inspection” at the data hall. Checking “Enable DHCP snooping before dynamic ARP inspection” at the data hall requires evidence of its own mechanism: Fortinet requires DHCP snooping to be configured before enabling DAI for the VLAN; that is not the outcome measured by “Apply IPv6 RA guard where supported”.
C: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 “Enable DHCP snooping before dynamic ARP inspection” at the data hall. Checking “Enable DHCP snooping before dynamic ARP inspection” at the data hall requires evidence of its own mechanism: Fortinet requires DHCP snooping to be configured before enabling DAI for the VLAN; that is not the outcome measured by “Use the DHCP-snooping binding table”.
D:The proposed check concerns “Keep DAI untrusted on endpoint interfaces” rather than “Enable DHCP snooping before dynamic ARP inspection”: untrusted ARP senders must match the permitted binding state to be forwarded. For “Enable DHCP snooping before dynamic ARP inspection” on a FortiSwitch connected to the security edge, a better test would be to check both the VLAN's DHCP snooping setting and DAI enablement, which targets provide the binding information DAI needs for validating ARP on client networks rather than the alternative diagnostic “Keep DAI untrusted on endpoint interfaces”.
E:The proposed check concerns “Audit DHCP snooping after VLAN redesign” rather than “Enable DHCP snooping before dynamic ARP inspection”: snooping configuration must follow actual VLAN membership and trusted-port boundaries. For “Enable DHCP snooping before dynamic ARP inspection” on a FortiSwitch connected to the security edge, a better test would be to check both the VLAN's DHCP snooping setting and DAI enablement, which targets provide the binding information DAI needs for validating ARP on client networks rather than the alternative diagnostic “Audit DHCP snooping after VLAN redesign”.
Question 538
A peer review of the development floor asks how the design will avoid inspecting ARP coming from an explicitly trusted network segment. Which FortiSwitch technique is the correct response?
- Keep ordinary client ports DHCP-snooping untrusted
- Enable dynamic ARP inspection on a VLAN
- Investigate rogue DHCP offer logs
- Trust an infrastructure port for ARP inspection when justified
Explanation
Correct Answer
D:Given the described goal, the switch can designate trusted ARP interfaces when the network design warrants an exception. The operator can test this claim by the specific check: review ARP trust state on the uplink and confirm that host ports remain untrusted.
Incorrect Answers
A:Compared with the requested “Trust an infrastructure port for ARP inspection when justified” at the development floor, this would prevent a connected endpoint from acting as an unauthorized address server instead: untrusted ports are checked for invalid DHCP server activity and may log rogue-server detection. At the development floor, the operational proof would instead be to review ARP trust state on the uplink and confirm that host ports remain untrusted, whereas “Keep ordinary client ports DHCP-snooping untrusted” is validated by a different test: send a test rogue offer and verify it is rejected on the client-facing port.
B:For the development floor, “Enable dynamic ARP inspection on a VLAN” is a different type of control from “Trust an infrastructure port for ARP inspection when justified”: DAI consults valid binding information to reject spoofed ARP traffic before it can poison neighbors. Unlike the requested feature, that setting addresses the need to block ARP packets with invalid IP-to-MAC assertions on untrusted access ports, not the objective to avoid inspecting ARP coming from an explicitly trusted network segment.
C:Compared with the requested “Trust an infrastructure port for ARP inspection when justified” at the development floor, this would locate an untrusted server attached to a client-facing port instead: DHCP snooping can log the arrival of DHCP server packets on untrusted interfaces. At the development floor, the operational proof would instead be to review ARP trust state on the uplink and confirm that host ports remain untrusted, whereas “Investigate rogue DHCP offer logs” is validated by a different test: correlate the rogue-server event with VLAN, port and packet source MAC.
Question 539
For the conference venue, an administrator applies the action “Trust an infrastructure port for ARP inspection when justified.” Which effect should appear when it operates as intended?
- Server whitelisting can narrow acceptable DHCP sources beyond the physical trust-port arrangement
- The switch can designate trusted ARP interfaces when the network design warrants an exception
- Fortinet requires DHCP snooping to be configured before enabling DAI for the VLAN
- A configured rate threshold distinguishes permitted traffic load from a sustained storm
Explanation
Correct Answer
B:The switch behavior that matters is: the configured operation is meant to avoid inspecting ARP coming from an explicitly trusted network segment. The most relevant validation is to review ARP trust state on the uplink and confirm that host ports remain untrusted for the equipment at the conference venue.
Incorrect Answers
A:That behavior applies when engineers “Configure an authorized DHCP server list”; the different operation “Trust an infrastructure port for ARP inspection when justified” is intended to avoid inspecting ARP coming from an explicitly trusted network segment. That different feature is verified by inspect the configured allowlist and observe whether an unlisted server offer is accepted; for “Trust an infrastructure port for ARP inspection when justified” on a managed campus switch, the relevant evidence is to review ARP trust state on the uplink and confirm that host ports remain untrusted.
C:This outcome would be relevant to “Enable DHCP snooping before dynamic ARP inspection” at the conference venue, not the task “Trust an infrastructure port for ARP inspection when justified”; the other task is to provide the binding information DAI needs for validating ARP on client networks. The action “Trust an infrastructure port for ARP inspection when justified” targets a different result: the switch can designate trusted ARP interfaces when the network design warrants an exception; the proposed alternative would instead be checked by check both the VLAN's DHCP snooping setting and DAI enablement.
D:That behavior applies when engineers “Set a storm-control threshold appropriate to link capacity”; the different operation “Trust an infrastructure port for ARP inspection when justified” is intended to avoid inspecting ARP coming from an explicitly trusted network segment. That different feature is verified by compare observed frame rates with the selected per-port storm-control threshold; for “Trust an infrastructure port for ARP inspection when justified” on a managed campus switch, the relevant evidence is to review ARP trust state on the uplink and confirm that host ports remain untrusted.
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?
- Capture whether the spoof is ordinary IPv4 payload traffic or ARP control traffic
- Capture a packet's EtherType and compare it with protocol-VLAN policy entries
- Review ARP trust state on the uplink and confirm that host ports remain untrusted
- Inspect the static entry and compare its interface, IPv4 address and MAC
- 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”.