Question 560
An operations log records this activity at the lab: use protocol-based VLAN classification. Which result is specifically attributable to that action?
- Protocol-based classification maps matching frame protocol to the configured VLAN policy
- DHCP snooping checks DHCP packets on the VLAN and builds trusted IP-to-MAC lease bindings
- The switch can designate trusted ARP interfaces when the network design warrants an exception
- Option 82 carries relay-agent information such as circuit and remote identifiers toward the DHCP infrastructure
Explanation
Correct Answer
A:This is the precise control because the configured operation is meant to assign inbound traffic to a VLAN based on its protocol identifier when required. The most relevant validation is to capture a packet's EtherType and compare it with protocol-VLAN policy entries for the equipment at the lab.
Incorrect Answers
B:That behavior applies when engineers “Enable DHCP snooping on an access VLAN”; the different operation “Use protocol-based VLAN classification” is intended to assign inbound traffic to a VLAN based on its protocol identifier when required. That different feature is verified by inspect DHCP snooping status and the learned bindings for that VLAN; for “Use protocol-based VLAN classification” on an endpoint-facing FortiSwitch port, the relevant evidence is to capture a packet's EtherType and compare it with protocol-VLAN policy entries.
C:That behavior applies when engineers “Trust an infrastructure port for ARP inspection when justified”; the different operation “Use protocol-based VLAN classification” is intended to assign inbound traffic to a VLAN based on its protocol identifier when required. That different feature is verified by review ARP trust state on the uplink and confirm that host ports remain untrusted; for “Use protocol-based VLAN classification” on an endpoint-facing FortiSwitch port, the relevant evidence is to capture a packet's EtherType and compare it with protocol-VLAN policy entries.
D:This outcome would be relevant to “Include DHCP option 82 for relay-agent context” at the lab, not the task “Use protocol-based VLAN classification”; the other task is to identify the access circuit or switch involved in a DHCP client request. The action “Use protocol-based VLAN classification” targets a different result: protocol-based classification maps matching frame protocol to the configured VLAN policy; the proposed alternative would instead be checked by capture a forwarded DHCP discover and inspect its option-82 fields.
Question 561
On a standalone FortiSwitch appliance at the staging rack, the team reports that it has configured “Use protocol-based VLAN classification.” Which verification provides the strongest direct evidence that the intended function is working?
- Inspect the static entry and compare its interface, IPv4 address and MAC
- Inspect the device MAC and the associated VLAN mapping rule
- Inspect per-VLAN ARP inspection drops after sending an invalid ARP advertisement
- Capture a packet's EtherType and compare it with protocol-VLAN policy entries
Explanation
Correct Answer
D:The implementation works because protocol-based classification maps matching frame protocol to the configured VLAN policy. Directly measuring that result demonstrates whether the step to assign inbound traffic to a VLAN based on its protocol identifier when required succeeded on a standalone FortiSwitch appliance.
Incorrect Answers
A:The proposed check concerns “Provision a static IPv4 source guard entry” rather than “Use protocol-based VLAN classification”: a manually configured source binding can permit a fixed IP/MAC identity without relying on a DHCP lease. For “Use protocol-based VLAN classification” on a standalone FortiSwitch appliance, a better test would be to capture a packet's EtherType and compare it with protocol-VLAN policy entries, which targets assign inbound traffic to a VLAN based on its protocol identifier when required rather than the alternative diagnostic “Provision a static IPv4 source guard entry”.
B: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 “Use protocol-based VLAN classification” at the staging rack. Checking “Use protocol-based VLAN classification” at the staging rack requires evidence of its own mechanism: protocol-based classification maps matching frame protocol to the configured VLAN policy; that is not the outcome measured by “Use MAC-based VLAN classification”.
C: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 “Use protocol-based VLAN classification” at the staging rack. Checking “Use protocol-based VLAN classification” at the staging rack requires evidence of its own mechanism: protocol-based classification maps matching frame protocol to the configured VLAN policy; that is not the outcome measured by “Enable dynamic ARP inspection on a VLAN”.
Question 562
A deployment review at the research building identifies this objective: assign a known endpoint to its designated VLAN independent of the access-port default. Which FortiSwitch operation should be selected?
- Apply IPv6 RA guard where supported
- Use MAC-based VLAN classification
- Configure an authorized DHCP server list
- Enable DHCP snooping before dynamic ARP inspection
- Avoid using source guard as an ARP-only inspection replacement
Explanation
Correct Answer
B:Given the described goal, MAC-based VLAN policies identify permitted source MAC addresses and map them to VLANs. The operator can test this claim by the specific check: inspect the device MAC and the associated VLAN mapping rule.
Incorrect Answers
A:Compared with the requested “Use MAC-based VLAN classification” at the research building, 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 research building, the operational proof would instead be to inspect the device MAC and the associated VLAN mapping rule, whereas “Apply IPv6 RA guard where supported” is validated by a different test: capture unauthorized ICMPv6 router advertisements and monitor guard drops.
C:For the research building, “Configure an authorized DHCP server list” is a different type of control from “Use MAC-based VLAN classification”: server whitelisting can narrow acceptable DHCP sources beyond the physical trust-port arrangement. Unlike the requested feature, that setting addresses the need to limit DHCP server acceptance to specified legitimate server addresses, not the objective to assign a known endpoint to its designated VLAN independent of the access-port default.
D:Compared with the requested “Use MAC-based VLAN classification” at the research building, 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 research building, the operational proof would instead be to inspect the device MAC and the associated VLAN mapping rule, 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.
E:Compared with the requested “Use MAC-based VLAN classification” at the research building, 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 research building, the operational proof would instead be to inspect the device MAC and the associated VLAN mapping rule, 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.
Question 563
When engineers use MAC-based VLAN classification at the airport office, which forwarding, security, management or diagnostic outcome follows from that action?
- A DHCP-snooping trusted port may convey legitimate server replies while host-facing ports remain untrusted
- IP source guard matches IPv4 origin against static or DHCP-snooping-learned source bindings
- A static port/IP/MAC binding supplies known information for binding-aware protections
- MAC-based VLAN policies identify permitted source MAC addresses and map them to VLANs
Explanation
Correct Answer
D:The switch behavior that matters is: the configured operation is meant to assign a known endpoint to its designated VLAN independent of the access-port default. The most relevant validation is to inspect the device MAC and the associated VLAN mapping rule for the equipment at the airport office.
Incorrect Answers
A:That behavior applies when engineers “Trust only the uplink toward a legitimate DHCP server”; the different operation “Use MAC-based VLAN classification” is intended to assign a known endpoint to its designated VLAN independent of the access-port default. That different feature is verified by check configured trusted interfaces and the source port of DHCP offers; for “Use MAC-based VLAN classification” on a local switch administering branch clients, the relevant evidence is to inspect the device MAC and the associated VLAN mapping rule.
B:That behavior applies when engineers “Enable IPv4 source guard on an access port”; the different operation “Use MAC-based VLAN classification” is intended to assign a known endpoint to its designated VLAN independent of the access-port default. That different feature is verified by compare the source IP of rejected traffic with the allowed binding set; for “Use MAC-based VLAN classification” on a local switch administering branch clients, the relevant evidence is to inspect the device MAC and the associated VLAN mapping rule.
C:This outcome would be relevant to “Create a static DHCP-snooping binding for a fixed-IP host” at the airport office, not the task “Use MAC-based VLAN classification”; the other task is to protect an endpoint whose address was not learned through a DHCP lease. The action “Use MAC-based VLAN classification” targets a different result: MAC-based VLAN policies identify permitted source MAC addresses and map them to VLANs; the proposed alternative would instead be checked by inspect the configured static binding and verify the endpoint's actual source identity.
Question 564
The work order to assign a known endpoint to its designated VLAN independent of the access-port default is marked complete on a switch used by multiple office teams. Which observation most directly tests the completed configuration?
- Inspect the device MAC and the associated VLAN mapping rule
- Read the active binding after the move and compare it with the client's new port
- Compare received source IP with configured IP-based VLAN mapping
- Compare ARP inspection statistics for the endpoint port and the relevant VLAN
Explanation
Correct Answer
A:At this network boundary, MAC-based VLAN policies identify permitted source MAC addresses and map them to VLANs. Directly measuring that result demonstrates whether the step to assign a known endpoint to its designated VLAN independent of the access-port default succeeded on a switch used by multiple office teams.
Incorrect Answers
B:The proposed check concerns “Check DHCP-derived bindings for IP source guard” rather than “Use MAC-based VLAN classification”: dynamic source-guard entries depend on valid snooping bindings for the interface and source identity. For “Use MAC-based VLAN classification” on a switch used by multiple office teams, a better test would be to inspect the device MAC and the associated VLAN mapping rule, which targets assign a known endpoint to its designated VLAN independent of the access-port default rather than the alternative diagnostic “Check DHCP-derived bindings for IP source guard”.
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 MAC-based VLAN classification” at the operations center. Checking “Use MAC-based VLAN classification” at the operations center requires evidence of its own mechanism: MAC-based VLAN policies identify permitted source MAC addresses and map them to VLANs; that is not the outcome measured by “Use IP-subnet-based VLAN assignment”.
D:This check is suited to “Keep DAI untrusted on endpoint interfaces” when trying to verify ARP statements made by clients rather than exempting them from inspection, not to verify “Use MAC-based VLAN classification” at the operations center. Checking “Use MAC-based VLAN classification” at the operations center requires evidence of its own mechanism: MAC-based VLAN policies identify permitted source MAC addresses and map them to VLANs; that is not the outcome measured by “Keep DAI untrusted on endpoint interfaces”.
Question 565
A peer review of the warehouse asks how the design will assign traffic from recognized source IPv4 subnets to specific VLANs where supported. Which FortiSwitch technique is the correct response?
- Use IP-subnet-based VLAN assignment
- Enable dynamic ARP inspection on a VLAN
- Provision a static IPv4 source guard entry
- Keep ordinary client ports DHCP-snooping untrusted
Explanation
Correct Answer
A:In this deployment, source subnet classification uses IP address information to select a configured VLAN association. This distinction is material to the warehouse, where the stated goal is to assign traffic from recognized source IPv4 subnets to specific VLANs where supported.
Incorrect Answers
B:Compared with the requested “Use IP-subnet-based VLAN assignment” at the warehouse, this would block ARP packets with invalid IP-to-MAC assertions on untrusted access ports instead: DAI consults valid binding information to reject spoofed ARP traffic before it can poison neighbors. At the warehouse, the operational proof would instead be to compare received source IP with configured IP-based VLAN mapping, whereas “Enable dynamic ARP inspection on a VLAN” is validated by a different test: inspect per-VLAN ARP inspection drops after sending an invalid ARP advertisement.
C:For the warehouse, “Provision a static IPv4 source guard entry” is a different type of control from “Use IP-subnet-based VLAN assignment”: 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 assign traffic from recognized source IPv4 subnets to specific VLANs where supported.
D:Compared with the requested “Use IP-subnet-based VLAN assignment” at the warehouse, 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 warehouse, the operational proof would instead be to compare received source IP with configured IP-based VLAN mapping, 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.
Question 566
A colleague asks about the effect of “Use IP-subnet-based VLAN assignment” on a newly racked distribution unit. Which behavior best characterizes that feature?
- Fortinet requires DHCP snooping to be configured before enabling DAI for the VLAN
- Storm control rate-limits selected Layer 2 traffic categories at a switch port
- Source subnet classification uses IP address information to select a configured VLAN association
- Untrusted ports are checked for invalid DHCP server activity and may log rogue-server detection
- DHCP snooping can log the arrival of DHCP server packets on untrusted interfaces
Explanation
Correct Answer
C:For the stated requirement, the configured operation is meant to assign traffic from recognized source IPv4 subnets to specific VLANs where supported. The most relevant validation is to compare received source IP with configured IP-based VLAN mapping for the equipment at the headquarters.
Incorrect Answers
A:That behavior applies when engineers “Enable DHCP snooping before dynamic ARP inspection”; the different operation “Use IP-subnet-based VLAN assignment” is intended to assign traffic from recognized source IPv4 subnets to specific VLANs where supported. That different feature is verified by check both the VLAN's DHCP snooping setting and DAI enablement; for “Use IP-subnet-based VLAN assignment” on a newly racked distribution unit, the relevant evidence is to compare received source IP with configured IP-based VLAN mapping.
B:This outcome would be relevant to “Use storm control on a broadcast-heavy access port” at the headquarters, not the task “Use IP-subnet-based VLAN assignment”; the other task is to limit disruption from excessive broadcast, multicast or unknown-unicast traffic. The action “Use IP-subnet-based VLAN assignment” targets a different result: source subnet classification uses IP address information to select a configured VLAN association; 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 ordinary client ports DHCP-snooping untrusted”; the different operation “Use IP-subnet-based VLAN assignment” is intended to assign traffic from recognized source IPv4 subnets to specific VLANs where supported. That different feature is verified by send a test rogue offer and verify it is rejected on the client-facing port; for “Use IP-subnet-based VLAN assignment” on a newly racked distribution unit, the relevant evidence is to compare received source IP with configured IP-based VLAN mapping.
E:That behavior applies when engineers “Investigate rogue DHCP offer logs”; the different operation “Use IP-subnet-based VLAN assignment” is intended to assign traffic from recognized source IPv4 subnets to specific VLANs where supported. That different feature is verified by correlate the rogue-server event with VLAN, port and packet source MAC; for “Use IP-subnet-based VLAN assignment” on a newly racked distribution unit, the relevant evidence is to compare received source IP with configured IP-based VLAN mapping.
Question 567
An auditor wants operational evidence for the switch action “Use IP-subnet-based VLAN assignment” at the hospital wing. Which check is relevant?
- Capture unauthorized ICMPv6 router advertisements and monitor guard drops
- Capture whether the spoof is ordinary IPv4 payload traffic or ARP control traffic
- Inspect the configured allowlist and observe whether an unlisted server offer is accepted
- Compare received source IP with configured IP-based VLAN mapping
Explanation
Correct Answer
D:The deciding detail is that source subnet classification uses IP address information to select a configured VLAN association. Directly measuring that result demonstrates whether the step to assign traffic from recognized source IPv4 subnets to specific VLANs where supported succeeded on two distribution switches.
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 “Use IP-subnet-based VLAN assignment” at the hospital wing. Checking “Use IP-subnet-based VLAN assignment” at the hospital wing requires evidence of its own mechanism: source subnet classification uses IP address information to select a configured VLAN association; that is not the outcome measured by “Apply IPv6 RA guard where supported”.
B:The proposed check concerns “Avoid using source guard as an ARP-only inspection replacement” rather than “Use IP-subnet-based VLAN assignment”: IPSG filters IPv4 packet sources while DAI validates ARP IP/MAC statements; they address different packet classes. For “Use IP-subnet-based VLAN assignment” on two distribution switches, a better test would be to compare received source IP with configured IP-based VLAN mapping, which targets assign traffic from recognized source IPv4 subnets to specific VLANs where supported rather than the alternative diagnostic “Avoid using source guard as an ARP-only inspection replacement”.
C: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 “Use IP-subnet-based VLAN assignment” at the hospital wing. Checking “Use IP-subnet-based VLAN assignment” at the hospital wing requires evidence of its own mechanism: source subnet classification uses IP address information to select a configured VLAN association; that is not the outcome measured by “Configure an authorized DHCP server list”.
Question 568
A production incident in the training center reveals the need to locate an untrusted server attached to a client-facing port. Which targeted FortiSwitch setting or method should the team use?
- Create a static DHCP-snooping binding for a fixed-IP host
- Enable IPv4 source guard on an access port
- Investigate rogue DHCP offer logs
- Apply IPv6 RA guard where supported
Explanation
Correct Answer
C:The relevant mechanism is: DHCP snooping can log the arrival of DHCP server packets on untrusted interfaces. The operator can test this claim by the specific check: correlate the rogue-server event with VLAN, port and packet source MAC.
Incorrect Answers
A:Compared with the requested “Investigate rogue DHCP offer logs” at the training center, 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 training center, the operational proof would instead be to correlate the rogue-server event with VLAN, port and packet source MAC, 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.
B:Compared with the requested “Investigate rogue DHCP offer logs” at the training center, 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 training center, the operational proof would instead be to correlate the rogue-server event with VLAN, port and packet source 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.
D:For the training center, “Apply IPv6 RA guard where supported” is a different type of control from “Investigate rogue DHCP offer logs”: 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 locate an untrusted server attached to a client-facing port.
Question 569
When engineers investigate rogue DHCP offer logs at the lab, which forwarding, security, management or diagnostic outcome follows from that action?
- A DHCP-snooping trusted port may convey legitimate server replies while host-facing ports remain untrusted
- DHCP snooping can log the arrival of DHCP server packets on untrusted interfaces
- MAC-based VLAN policies identify permitted source MAC addresses and map them to VLANs
- Dynamic source-guard entries depend on valid snooping bindings for the interface and source identity
Explanation
Correct Answer
B:This approach fits because the configured operation is meant to locate an untrusted server attached to a client-facing port. The most relevant validation is to correlate the rogue-server event with VLAN, port and packet source MAC for the equipment at the lab.
Incorrect Answers
A:That behavior applies when engineers “Trust only the uplink toward a legitimate DHCP server”; the different operation “Investigate rogue DHCP offer logs” is intended to locate an untrusted server attached to a client-facing port. That different feature is verified by check configured trusted interfaces and the source port of DHCP offers; for “Investigate rogue DHCP offer logs” on a carefully segmented Layer 2 network, the relevant evidence is to correlate the rogue-server event with VLAN, port and packet source MAC.
C:This outcome would be relevant to “Use MAC-based VLAN classification” at the lab, not the task “Investigate rogue DHCP offer logs”; the other task is to assign a known endpoint to its designated VLAN independent of the access-port default. The action “Investigate rogue DHCP offer logs” targets a different result: DHCP snooping can log the arrival of DHCP server packets on untrusted interfaces; 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 “Investigate rogue DHCP offer logs” is intended to locate an untrusted server attached to a client-facing port. That different feature is verified by read the active binding after the move and compare it with the client's new port; for “Investigate rogue DHCP offer logs” on a carefully segmented Layer 2 network, the relevant evidence is to correlate the rogue-server event with VLAN, port and packet source MAC.
Question 570
A technician says “Investigate rogue DHCP offer logs” has solved the issue at the media studio. Which diagnostic step would substantiate that claim?
- Compare a client's address and MAC with the active binding database
- Compare current port trust, VLAN snooping enablement and the revised cabling diagram
- Compare ARP inspection statistics for the endpoint port and the relevant VLAN
- Correlate the rogue-server event with VLAN, port and packet source MAC
- Read the active binding after the move and compare it with the client's new port
Explanation
Correct Answer
D:The critical distinction is that DHCP snooping can log the arrival of DHCP server packets on untrusted interfaces. Directly measuring that result demonstrates whether the step to locate an untrusted server attached to a client-facing port succeeded on a central switching stack.
Incorrect Answers
A:The proposed check concerns “Use the DHCP-snooping binding table” rather than “Investigate rogue DHCP offer logs”: snooping records lease-derived bindings that other protections can reference. For “Investigate rogue DHCP offer logs” on a central switching stack, a better test would be to correlate the rogue-server event with VLAN, port and packet source MAC, which targets locate an untrusted server attached to a client-facing port rather than the alternative diagnostic “Use the DHCP-snooping binding table”.
B:This check is suited to “Audit DHCP snooping after VLAN redesign” when trying to avoid unintentionally permitting server traffic on newly repurposed host uplinks, not to verify “Investigate rogue DHCP offer logs” at the media studio. Checking “Investigate rogue DHCP offer logs” at the media studio requires evidence of its own mechanism: DHCP snooping can log the arrival of DHCP server packets on untrusted interfaces; that is not the outcome measured by “Audit DHCP snooping after VLAN redesign”.
C:This check is suited to “Keep DAI untrusted on endpoint interfaces” when trying to verify ARP statements made by clients rather than exempting them from inspection, not to verify “Investigate rogue DHCP offer logs” at the media studio. Checking “Investigate rogue DHCP offer logs” at the media studio requires evidence of its own mechanism: DHCP snooping can log the arrival of DHCP server packets on untrusted interfaces; that is not the outcome measured by “Keep DAI untrusted on endpoint interfaces”.
E:The proposed check concerns “Check DHCP-derived bindings for IP source guard” rather than “Investigate rogue DHCP offer logs”: dynamic source-guard entries depend on valid snooping bindings for the interface and source identity. For “Investigate rogue DHCP offer logs” on a central switching stack, a better test would be to correlate the rogue-server event with VLAN, port and packet source MAC, which targets locate an untrusted server attached to a client-facing port rather than the alternative diagnostic “Check DHCP-derived bindings for IP source guard”.