Question 510
A feature acceptance test on a managed switch running FortiSwitchOS 7.6 concerns “Enable DHCP snooping on an access VLAN.” What should be checked to establish its expected operation?
- Capture unauthorized ICMPv6 router advertisements and monitor guard drops
- Compare current port trust, VLAN snooping enablement and the revised cabling diagram
- Inspect DHCP snooping status and the learned bindings for that VLAN
- Inspect the configured allowlist and observe whether an unlisted server offer is accepted
Explanation
Correct Answer
C:The critical distinction is that DHCP snooping checks DHCP packets on the VLAN and builds trusted IP-to-MAC lease bindings. Directly measuring that result demonstrates whether the step to stop an untrusted access port from supplying rogue DHCP server messages succeeded on a managed switch running FortiSwitchOS 7.6.
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 on an access VLAN” at the retail site. Checking “Enable DHCP snooping on an access VLAN” at the retail site requires evidence of its own mechanism: DHCP snooping checks DHCP packets on the VLAN and builds trusted IP-to-MAC lease bindings; that is not the outcome measured by “Apply IPv6 RA guard where supported”.
B:The proposed check concerns “Audit DHCP snooping after VLAN redesign” rather than “Enable DHCP snooping on an access VLAN”: snooping configuration must follow actual VLAN membership and trusted-port boundaries. For “Enable DHCP snooping on an access VLAN” on a managed switch running FortiSwitchOS 7.6, a better test would be to inspect DHCP snooping status and the learned bindings for that VLAN, which targets stop an untrusted access port from supplying rogue DHCP server messages rather than the alternative diagnostic “Audit DHCP snooping after VLAN redesign”.
D:This check is suited to “Configure an authorized DHCP server list” when trying to limit DHCP server acceptance to specified legitimate server addresses, not to verify “Enable DHCP snooping on an access VLAN” at the retail site. Checking “Enable DHCP snooping on an access VLAN” at the retail site requires evidence of its own mechanism: DHCP snooping checks DHCP packets on the VLAN and builds trusted IP-to-MAC lease bindings; that is not the outcome measured by “Configure an authorized DHCP server list”.
Question 511
For the airport office, the network team needs to allow server responses on an approved infrastructure-facing interface. Which change is the most direct way to implement that requirement on a remote FortiSwitch installation?
- Enable IPv4 source guard on an access port
- Apply IPv6 RA guard where supported
- Create a static DHCP-snooping binding for a fixed-IP host
- Trust only the uplink toward a legitimate DHCP server
- Enable DHCP snooping on an access VLAN
Explanation
Correct Answer
D:That setting is appropriate here because a DHCP-snooping trusted port may convey legitimate server replies while host-facing ports remain untrusted. This distinction is material to the airport office, where the stated goal is to allow server responses on an approved infrastructure-facing interface.
Incorrect Answers
A:For the airport office, “Enable IPv4 source guard on an access port” is a different type of control from “Trust only the uplink toward a legitimate DHCP server”: IP source guard matches IPv4 origin against static or DHCP-snooping-learned source bindings. Unlike the requested feature, that setting addresses the need to discard host IP packets that use source addresses not authorized for that interface, not the objective to allow server responses on an approved infrastructure-facing interface.
B:Compared with the requested “Trust only the uplink toward a legitimate DHCP server” at the airport office, this would block unauthorized IPv6 router advertisements on user-facing ports instead: RA guard filters IPv6 router advertisements originating from untrusted switch access links. At the airport office, the operational proof would instead be to check configured trusted interfaces and the source port of DHCP offers, whereas “Apply IPv6 RA guard where supported” is validated by a different test: capture unauthorized ICMPv6 router advertisements and monitor guard drops.
C:Compared with the requested “Trust only the uplink toward a legitimate DHCP server” at the airport office, 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 airport office, the operational proof would instead be to check configured trusted interfaces and the source port of DHCP offers, 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.
E:Compared with the requested “Trust only the uplink toward a legitimate DHCP server” at the airport office, 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 airport office, the operational proof would instead be to check configured trusted interfaces and the source port of DHCP offers, 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.
Question 512
A switch change for the operations center consists of this step: trust only the uplink toward a legitimate DHCP server. Which behavior reflects the purpose of that change?
- Dynamic source-guard entries depend on valid snooping bindings for the interface and source identity
- MAC-based VLAN policies identify permitted source MAC addresses and map them to VLANs
- A DHCP-snooping trusted port may convey legitimate server replies while host-facing ports remain untrusted
- 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 allow server responses on an approved infrastructure-facing interface. The most relevant validation is to check configured trusted interfaces and the source port of DHCP offers for the equipment at the operations center.
Incorrect Answers
A:This outcome would be relevant to “Check DHCP-derived bindings for IP source guard” at the operations center, not the task “Trust only the uplink toward a legitimate DHCP server”; the other task is to explain why a recently moved DHCP client loses permitted IPv4 connectivity. The action “Trust only the uplink toward a legitimate DHCP server” targets a different result: a DHCP-snooping trusted port may convey legitimate server replies while host-facing ports remain untrusted; the proposed alternative would instead be checked by 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 “Trust only the uplink toward a legitimate DHCP server” is intended to allow server responses on an approved infrastructure-facing interface. That different feature is verified by inspect the device MAC and the associated VLAN mapping rule; for “Trust only the uplink toward a legitimate DHCP server” on an endpoint-facing FortiSwitch port, the relevant evidence is to check configured trusted interfaces and the source port of DHCP offers.
D:That behavior applies when engineers “Keep DAI untrusted on endpoint interfaces”; the different operation “Trust only the uplink toward a legitimate DHCP server” is intended to allow server responses on an approved infrastructure-facing interface. That different feature is verified by compare ARP inspection statistics for the endpoint port and the relevant VLAN; for “Trust only the uplink toward a legitimate DHCP server” on an endpoint-facing FortiSwitch port, the relevant evidence is to check configured trusted interfaces and the source port of DHCP offers.
Question 513
On a standalone FortiSwitch appliance at the warehouse, the team reports that it has configured “Trust only the uplink toward a legitimate DHCP server.” Which verification provides the strongest direct evidence that the intended function is working?
- Compare a client's address and MAC with the active binding database
- Compare observed frame rates with the selected per-port storm-control threshold
- Check configured trusted interfaces and the source port of DHCP offers
- Correlate the rogue-server event with VLAN, port and packet source MAC
Explanation
Correct Answer
C:The implementation works because a DHCP-snooping trusted port may convey legitimate server replies while host-facing ports remain untrusted. Directly measuring that result demonstrates whether the step to allow server responses on an approved infrastructure-facing interface succeeded on a standalone FortiSwitch appliance.
Incorrect Answers
A: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 “Trust only the uplink toward a legitimate DHCP server” at the warehouse. Checking “Trust only the uplink toward a legitimate DHCP server” at the warehouse requires evidence of its own mechanism: a DHCP-snooping trusted port may convey legitimate server replies while host-facing ports remain untrusted; that is not the outcome measured by “Use the DHCP-snooping binding table”.
B: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 “Trust only the uplink toward a legitimate DHCP server” at the warehouse. Checking “Trust only the uplink toward a legitimate DHCP server” at the warehouse requires evidence of its own mechanism: a DHCP-snooping trusted port may convey legitimate server replies while host-facing ports remain untrusted; that is not the outcome measured by “Set a storm-control threshold appropriate to link capacity”.
D:The proposed check concerns “Investigate rogue DHCP offer logs” rather than “Trust only the uplink toward a legitimate DHCP server”: DHCP snooping can log the arrival of DHCP server packets on untrusted interfaces. For “Trust only the uplink toward a legitimate DHCP server” on a standalone FortiSwitch appliance, a better test would be to check configured trusted interfaces and the source port of DHCP offers, which targets allow server responses on an approved infrastructure-facing interface rather than the alternative diagnostic “Investigate rogue DHCP offer logs”.
Question 514
A network architect documents a single goal for a newly commissioned floor switch: prevent a connected endpoint from acting as an unauthorized address server. Which listed procedure provides that capability?
- Use storm control on a broadcast-heavy access port
- Keep ordinary client ports DHCP-snooping untrusted
- Enable DHCP snooping before dynamic ARP inspection
- Configure an authorized DHCP server list
Explanation
Correct Answer
B:Given the described goal, untrusted ports are checked for invalid DHCP server activity and may log rogue-server detection. The operator can test this claim by the specific check: send a test rogue offer and verify it is rejected on the client-facing port.
Incorrect Answers
A:For the remote depot, “Use storm control on a broadcast-heavy access port” is a different type of control from “Keep ordinary client ports DHCP-snooping untrusted”: storm control rate-limits selected Layer 2 traffic categories at a switch port. Unlike the requested feature, that setting addresses the need to limit disruption from excessive broadcast, multicast or unknown-unicast traffic, not the objective to prevent a connected endpoint from acting as an unauthorized address server.
C:Compared with the requested “Keep ordinary client ports DHCP-snooping untrusted” 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 send a test rogue offer and verify it is rejected on the client-facing port, 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.
D:Compared with the requested “Keep ordinary client ports DHCP-snooping untrusted” at the remote depot, 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 remote depot, the operational proof would instead be to send a test rogue offer and verify it is rejected on the client-facing port, 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.
Question 515
The operator has decided to keep ordinary client ports DHCP-snooping untrusted on a local switch administering branch clients at the branch office. Which operational behavior is the most reasonable expectation of that specific feature?
- Server whitelisting can narrow acceptable DHCP sources beyond the physical trust-port arrangement
- RA guard filters IPv6 router advertisements originating from untrusted switch access links
- Snooping configuration must follow actual VLAN membership and trusted-port boundaries
- Untrusted ports are checked for invalid DHCP server activity and may log rogue-server detection
- IP source guard matches IPv4 origin against static or DHCP-snooping-learned source bindings
Explanation
Correct Answer
D:The switch behavior that matters is: the configured operation is meant to prevent a connected endpoint from acting as an unauthorized address server. The most relevant validation is to send a test rogue offer and verify it is rejected on the client-facing port for the equipment at the branch office.
Incorrect Answers
A:That behavior applies when engineers “Configure an authorized DHCP server list”; the different operation “Keep ordinary client ports DHCP-snooping untrusted” is intended to prevent a connected endpoint from acting as an unauthorized address server. That different feature is verified by inspect the configured allowlist and observe whether an unlisted server offer is accepted; for “Keep ordinary client ports DHCP-snooping untrusted” on a local switch administering branch clients, the relevant evidence is to send a test rogue offer and verify it is rejected on the client-facing port.
B:This outcome would be relevant to “Apply IPv6 RA guard where supported” at the branch office, not the task “Keep ordinary client ports DHCP-snooping untrusted”; the other task is to block unauthorized IPv6 router advertisements on user-facing ports. The action “Keep ordinary client ports DHCP-snooping untrusted” targets a different result: untrusted ports are checked for invalid DHCP server activity and may log rogue-server detection; the proposed alternative would instead be checked by capture unauthorized ICMPv6 router advertisements and monitor guard drops.
C:That behavior applies when engineers “Audit DHCP snooping after VLAN redesign”; the different operation “Keep ordinary client ports DHCP-snooping untrusted” is intended to prevent a connected endpoint from acting as an unauthorized address server. That different feature is verified by compare current port trust, VLAN snooping enablement and the revised cabling diagram; for “Keep ordinary client ports DHCP-snooping untrusted” on a local switch administering branch clients, the relevant evidence is to send a test rogue offer and verify it is rejected on the client-facing port.
E:That behavior applies when engineers “Enable IPv4 source guard on an access port”; the different operation “Keep ordinary client ports DHCP-snooping untrusted” is intended to prevent a connected endpoint from acting as an unauthorized address server. That different feature is verified by compare the source IP of rejected traffic with the allowed binding set; for “Keep ordinary client ports DHCP-snooping untrusted” on a local switch administering branch clients, the relevant evidence is to send a test rogue offer and verify it is rejected on the client-facing port.
Question 516
A post-change review at the factory must validate the implementation of “Keep ordinary client ports DHCP-snooping untrusted.” What should the reviewer inspect first?
- Inspect the configured static binding and verify the endpoint's actual source identity
- Send a test rogue offer and verify it is rejected on the client-facing port
- Inspect DHCP snooping status and the learned bindings for that VLAN
- Inspect the device MAC and the associated VLAN mapping rule
Explanation
Correct Answer
B:At this network boundary, untrusted ports are checked for invalid DHCP server activity and may log rogue-server detection. Directly measuring that result demonstrates whether the step to prevent a connected endpoint from acting as an unauthorized address server succeeded on a switch used by multiple office teams.
Incorrect Answers
A:This check is suited to “Create a static DHCP-snooping binding for a fixed-IP host” when trying to protect an endpoint whose address was not learned through a DHCP lease, not to verify “Keep ordinary client ports DHCP-snooping untrusted” at the factory. Checking “Keep ordinary client ports DHCP-snooping untrusted” at the factory requires evidence of its own mechanism: untrusted ports are checked for invalid DHCP server activity and may log rogue-server detection; that is not the outcome measured by “Create a static DHCP-snooping binding for a fixed-IP host”.
C:The proposed check concerns “Enable DHCP snooping on an access VLAN” rather than “Keep ordinary client ports DHCP-snooping untrusted”: DHCP snooping checks DHCP packets on the VLAN and builds trusted IP-to-MAC lease bindings. For “Keep ordinary client ports DHCP-snooping untrusted” on a switch used by multiple office teams, a better test would be to send a test rogue offer and verify it is rejected on the client-facing port, which targets prevent a connected endpoint from acting as an unauthorized address server rather than the alternative diagnostic “Enable DHCP snooping on an access VLAN”.
D:This check is suited to “Use MAC-based VLAN classification” when trying to assign a known endpoint to its designated VLAN independent of the access-port default, not to verify “Keep ordinary client ports DHCP-snooping untrusted” at the factory. Checking “Keep ordinary client ports DHCP-snooping untrusted” at the factory requires evidence of its own mechanism: untrusted ports are checked for invalid DHCP server activity and may log rogue-server detection; that is not the outcome measured by “Use MAC-based VLAN classification”.
Question 517
At the distribution floor, a technician is choosing between several switching features to associate leased IPv4 identities with particular MAC addresses and ports. Which one belongs in the implementation plan?
- Use the DHCP-snooping binding table
- Avoid using source guard as an ARP-only inspection replacement
- Use protocol-based VLAN classification
- Include DHCP option 82 for relay-agent context
Explanation
Correct Answer
A:In this deployment, snooping records lease-derived bindings that other protections can reference. This distinction is material to the distribution floor, where the stated goal is to associate leased IPv4 identities with particular MAC addresses and ports.
Incorrect Answers
B:Compared with the requested “Use the DHCP-snooping binding table” at the distribution floor, this would protect both IPv4 data-source integrity and ARP neighbor claims using the appropriate separate controls instead: IPSG filters IPv4 packet sources while DAI validates ARP IP/MAC statements; they address different packet classes. At the distribution floor, the operational proof would instead be to compare a client's address and MAC with the active binding database, whereas “Avoid using source guard as an ARP-only inspection replacement” is validated by a different test: capture whether the spoof is ordinary IPv4 payload traffic or ARP control traffic.
C:Compared with the requested “Use the DHCP-snooping binding table” at the distribution floor, 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 distribution floor, the operational proof would instead be to compare a client's address and MAC with the active binding database, 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.
D:For the distribution floor, “Include DHCP option 82 for relay-agent context” is a different type of control from “Use the DHCP-snooping binding table”: option 82 carries relay-agent information such as circuit and remote identifiers toward the DHCP infrastructure. Unlike the requested feature, that setting addresses the need to identify the access circuit or switch involved in a DHCP client request, not the objective to associate leased IPv4 identities with particular MAC addresses and ports.
Question 518
A switch change for the media studio consists of this step: use the DHCP-snooping binding table. Which behavior reflects the purpose of that change?
- Snooping records lease-derived bindings that other protections can reference
- Protocol-based classification maps matching frame protocol to the configured VLAN policy
- A DHCP-snooping trusted port may convey legitimate server replies while host-facing ports remain untrusted
- A manually configured source binding can permit a fixed IP/MAC identity without relying on a DHCP lease
- DAI consults valid binding information to reject spoofed ARP traffic before it can poison neighbors
Explanation
Correct Answer
A:For the stated requirement, the configured operation is meant to associate leased IPv4 identities with particular MAC addresses and ports. The most relevant validation is to compare a client's address and MAC with the active binding database for the equipment at the media studio.
Incorrect Answers
B:That behavior applies when engineers “Use protocol-based VLAN classification”; the different operation “Use the DHCP-snooping binding table” is intended to associate leased IPv4 identities with particular MAC addresses and ports. That different feature is verified by capture a packet's EtherType and compare it with protocol-VLAN policy entries; for “Use the DHCP-snooping binding table” on a newly racked distribution unit, the relevant evidence is to compare a client's address and MAC with the active binding database.
C:That behavior applies when engineers “Trust only the uplink toward a legitimate DHCP server”; the different operation “Use the DHCP-snooping binding table” is intended to associate leased IPv4 identities with particular MAC addresses and ports. That different feature is verified by check configured trusted interfaces and the source port of DHCP offers; for “Use the DHCP-snooping binding table” on a newly racked distribution unit, the relevant evidence is to compare a client's address and MAC with the active binding database.
D:That behavior applies when engineers “Provision a static IPv4 source guard entry”; the different operation “Use the DHCP-snooping binding table” is intended to associate leased IPv4 identities with particular MAC addresses and ports. That different feature is verified by inspect the static entry and compare its interface, IPv4 address and MAC; for “Use the DHCP-snooping binding table” on a newly racked distribution unit, the relevant evidence is to compare a client's address and MAC with the active binding database.
E:This outcome would be relevant to “Enable dynamic ARP inspection on a VLAN” at the media studio, not the task “Use the DHCP-snooping binding table”; the other task is to block ARP packets with invalid IP-to-MAC assertions on untrusted access ports. The action “Use the DHCP-snooping binding table” targets a different result: snooping records lease-derived bindings that other protections can reference; the proposed alternative would instead be checked by inspect per-VLAN ARP inspection drops after sending an invalid ARP advertisement.
Question 519
An auditor wants operational evidence for the switch action “Use the DHCP-snooping binding table” at the retail site. Which check is relevant?
- Read storm-control counters during the observed high-rate event
- Check both the VLAN's DHCP snooping setting and DAI enablement
- Compare received source IP with configured IP-based VLAN mapping
- Compare a client's address and MAC with the active binding database
Explanation
Correct Answer
D:The deciding detail is that snooping records lease-derived bindings that other protections can reference. Directly measuring that result demonstrates whether the step to associate leased IPv4 identities with particular MAC addresses and ports succeeded on two distribution switches.
Incorrect Answers
A:The proposed check concerns “Use storm control on a broadcast-heavy access port” rather than “Use the DHCP-snooping binding table”: storm control rate-limits selected Layer 2 traffic categories at a switch port. For “Use the DHCP-snooping binding table” on two distribution switches, a better test would be to compare a client's address and MAC with the active binding database, which targets associate leased IPv4 identities with particular MAC addresses and ports rather than the alternative diagnostic “Use storm control on a broadcast-heavy access port”.
B:This check is suited to “Enable DHCP snooping before dynamic ARP inspection” when trying to provide the binding information DAI needs for validating ARP on client networks, not to verify “Use the DHCP-snooping binding table” at the retail site. Checking “Use the DHCP-snooping binding table” at the retail site requires evidence of its own mechanism: snooping records lease-derived bindings that other protections can reference; that is not the outcome measured by “Enable DHCP snooping before dynamic ARP inspection”.
C:This check is suited to “Use IP-subnet-based VLAN assignment” when trying to assign traffic from recognized source IPv4 subnets to specific VLANs where supported, not to verify “Use the DHCP-snooping binding table” at the retail site. Checking “Use the DHCP-snooping binding table” at the retail site requires evidence of its own mechanism: snooping records lease-derived bindings that other protections can reference; that is not the outcome measured by “Use IP-subnet-based VLAN assignment”.
Question 520
The accepted design for the airport office requires the ability to limit DHCP server acceptance to specified legitimate server addresses. Which switch feature is the closest fit?
- Enable IPv4 source guard on an access port
- Configure an authorized DHCP server list
- Create a static DHCP-snooping binding for a fixed-IP host
- Apply IPv6 RA guard where supported
Explanation
Correct Answer
B:The relevant mechanism is: server whitelisting can narrow acceptable DHCP sources beyond the physical trust-port arrangement. The operator can test this claim by the specific check: inspect the configured allowlist and observe whether an unlisted server offer is accepted.
Incorrect Answers
A:Compared with the requested “Configure an authorized DHCP server list” at the airport office, 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 airport office, the operational proof would instead be to inspect the configured allowlist and observe whether an unlisted server offer is accepted, 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.
C:Compared with the requested “Configure an authorized DHCP server list” at the airport office, 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 airport office, the operational proof would instead be to inspect the configured allowlist and observe whether an unlisted server offer is accepted, 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:For the airport office, “Apply IPv6 RA guard where supported” is a different type of control from “Configure an authorized DHCP server list”: 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 limit DHCP server acceptance to specified legitimate server addresses.