Question 500
A FortiSwitch engineer in the media studio is documenting successful operation of “Use a guest or unauthorized VLAN policy where supported.” Which measurement or inspection confirms it?
- Examine EAP-TLS negotiation and server certificate trust results
- Inspect the failed authentication state and assigned VLAN on the endpoint session
- Inspect the negotiated EAP type in the access attempt
- Test RADIUS reachability, shared-secret agreement and server response time
- Check the secure MAC table and the source address of blocked frames
Explanation
Correct Answer
B:This is the precise control because an unauthorized or guest network can provide limited connectivity instead of normal production access. Directly measuring that result demonstrates whether the step to separate endpoints that have not completed approved network authentication succeeded on a FortiLink-managed access switch.
Incorrect Answers
A:The proposed check concerns “Use EAP-TLS where device certificates are deployed” rather than “Use a guest or unauthorized VLAN policy where supported”: EAP-TLS uses certificate validation in the authentication flow rather than a simple MAC-only identity. For “Use a guest or unauthorized VLAN policy where supported” on a FortiLink-managed access switch, a better test would be to inspect the failed authentication state and assigned VLAN on the endpoint session, which targets separate endpoints that have not completed approved network authentication rather than the alternative diagnostic “Use EAP-TLS where device certificates are deployed”.
C:This check is suited to “Use EAP-TTLS for compatible tunnel-based access authentication” when trying to provide a tunneled credential exchange supported by the configured RADIUS server, not to verify “Use a guest or unauthorized VLAN policy where supported” at the media studio. Checking “Use a guest or unauthorized VLAN policy where supported” at the media studio requires evidence of its own mechanism: an unauthorized or guest network can provide limited connectivity instead of normal production access; that is not the outcome measured by “Use EAP-TTLS for compatible tunnel-based access authentication”.
D:This check is suited to “Configure a reachable RADIUS authentication server” when trying to provide external identity validation for network access control, not to verify “Use a guest or unauthorized VLAN policy where supported” at the media studio. Checking “Use a guest or unauthorized VLAN policy where supported” at the media studio requires evidence of its own mechanism: an unauthorized or guest network can provide limited connectivity instead of normal production access; that is not the outcome measured by “Configure a reachable RADIUS authentication server”.
E:The proposed check concerns “Use static MAC security for a fixed appliance” rather than “Use a guest or unauthorized VLAN policy where supported”: a configured MAC identity restricts layer-2 admission or learning to designated devices. For “Use a guest or unauthorized VLAN policy where supported” on a FortiLink-managed access switch, a better test would be to inspect the failed authentication state and assigned VLAN on the endpoint session, which targets separate endpoints that have not completed approved network authentication rather than the alternative diagnostic “Use static MAC security for a fixed appliance”.
Question 501
A switch rollout in the retail site will be approved only if it can determine why a locked port sees no usable EAP exchange from the attached device. Which administrative action meets this acceptance criterion?
- Troubleshoot an 802.1X supplicant that never starts
- Apply a port security profile to a FortiSwitch interface
- Use EAP-TLS where device certificates are deployed
- Configure a reachable RADIUS authentication server
Explanation
Correct Answer
A:The implementation works because an 802.1X-capable client must participate in EAPOL before the server can approve its credentials. This distinction is material to the retail site, where the stated goal is to determine why a locked port sees no usable EAP exchange from the attached device.
Incorrect Answers
B:For the retail site, “Apply a port security profile to a FortiSwitch interface” is a different type of control from “Troubleshoot an 802.1X supplicant that never starts”: a port policy binds appropriate authentication and security settings to an interface. Unlike the requested feature, that setting addresses the need to maintain a reusable set of network admission controls on selected access ports, not the objective to determine why a locked port sees no usable EAP exchange from the attached device.
C:Compared with the requested “Troubleshoot an 802.1X supplicant that never starts” at the retail site, this would authenticate compliant devices with a certificate-based EAP exchange instead: EAP-TLS uses certificate validation in the authentication flow rather than a simple MAC-only identity. At the retail site, the operational proof would instead be to capture EAPOL frames on the access port and inspect endpoint supplicant state, whereas “Use EAP-TLS where device certificates are deployed” is validated by a different test: examine EAP-TLS negotiation and server certificate trust results.
D:Compared with the requested “Troubleshoot an 802.1X supplicant that never starts” at the retail site, this would provide external identity validation for network access control instead: the switch forwards authentication exchanges to a configured RADIUS service rather than validating enterprise credentials by itself. At the retail site, the operational proof would instead be to capture EAPOL frames on the access port and inspect endpoint supplicant state, whereas “Configure a reachable RADIUS authentication server” is validated by a different test: test RADIUS reachability, shared-secret agreement and server response time.
Question 502
During validation of a switch serving a high-density endpoint area at the airport office, the team asks what the change “Troubleshoot an 802.1X supplicant that never starts” actually does. Which outcome is correct?
- The switch forwards authentication exchanges to a configured RADIUS service rather than validating enterprise credentials by itself
- A configured MAC identity restricts layer-2 admission or learning to designated devices
- An 802.1X-capable client must participate in EAPOL before the server can approve its credentials
- TTLS wraps inner authentication within a protected tunnel and requires matching endpoint/server settings
Explanation
Correct Answer
C:Given the described goal, the configured operation is meant to determine why a locked port sees no usable EAP exchange from the attached device. The most relevant validation is to capture EAPOL frames on the access port and inspect endpoint supplicant state for the equipment at the airport office.
Incorrect Answers
A:That behavior applies when engineers “Configure a reachable RADIUS authentication server”; the different operation “Troubleshoot an 802.1X supplicant that never starts” is intended to determine why a locked port sees no usable EAP exchange from the attached device. That different feature is verified by test RADIUS reachability, shared-secret agreement and server response time; for “Troubleshoot an 802.1X supplicant that never starts” on a switch serving a high-density endpoint area, the relevant evidence is to capture EAPOL frames on the access port and inspect endpoint supplicant state.
B:This outcome would be relevant to “Use static MAC security for a fixed appliance” at the airport office, not the task “Troubleshoot an 802.1X supplicant that never starts”; the other task is to allow a particular known device address on a controlled interface. The action “Troubleshoot an 802.1X supplicant that never starts” targets a different result: an 802.1X-capable client must participate in EAPOL before the server can approve its credentials; the proposed alternative would instead be checked by check the secure MAC table and the source address of blocked frames.
D:That behavior applies when engineers “Use EAP-TTLS for compatible tunnel-based access authentication”; the different operation “Troubleshoot an 802.1X supplicant that never starts” is intended to determine why a locked port sees no usable EAP exchange from the attached device. That different feature is verified by inspect the negotiated EAP type in the access attempt; for “Troubleshoot an 802.1X supplicant that never starts” on a switch serving a high-density endpoint area, the relevant evidence is to capture EAPOL frames on the access port and inspect endpoint supplicant state.
Question 503
A feature acceptance test on a managed switch running FortiSwitchOS 7.6 concerns “Troubleshoot an 802.1X supplicant that never starts.” What should be checked to establish its expected operation?
- Inspect individual authenticated MAC session entries on the interface
- Trace the RADIUS path and examine the matching FortiGate policy hit counters
- Capture EAPOL frames on the access port and inspect endpoint supplicant state
- Inspect the negotiated EAP type in the access attempt
Explanation
Correct Answer
C:The switch behavior that matters is: an 802.1X-capable client must participate in EAPOL before the server can approve its credentials. Directly measuring that result demonstrates whether the step to determine why a locked port sees no usable EAP exchange from the attached device succeeded on a managed switch running FortiSwitchOS 7.6.
Incorrect Answers
A:The proposed check concerns “Use MAC-based 802.1X access sessions” rather than “Troubleshoot an 802.1X supplicant that never starts”: MAC-based mode maintains per-device authorization decisions instead of granting the entire port one common state. For “Troubleshoot an 802.1X supplicant that never starts” on a managed switch running FortiSwitchOS 7.6, a better test would be to capture EAPOL frames on the access port and inspect endpoint supplicant state, which targets determine why a locked port sees no usable EAP exchange from the attached device rather than the alternative diagnostic “Use MAC-based 802.1X access sessions”.
B:This check is suited to “Permit RADIUS traffic from managed FortiSwitch via FortiGate” when trying to restore network authentication when the switch cannot reach a remote RADIUS server, not to verify “Troubleshoot an 802.1X supplicant that never starts” at the operations center. Checking “Troubleshoot an 802.1X supplicant that never starts” at the operations center requires evidence of its own mechanism: an 802.1X-capable client must participate in EAPOL before the server can approve its credentials; that is not the outcome measured by “Permit RADIUS traffic from managed FortiSwitch via FortiGate”.
D:This check is suited to “Use EAP-TTLS for compatible tunnel-based access authentication” when trying to provide a tunneled credential exchange supported by the configured RADIUS server, not to verify “Troubleshoot an 802.1X supplicant that never starts” at the operations center. Checking “Troubleshoot an 802.1X supplicant that never starts” at the operations center requires evidence of its own mechanism: an 802.1X-capable client must participate in EAPOL before the server can approve its credentials; that is not the outcome measured by “Use EAP-TTLS for compatible tunnel-based access authentication”.
Question 504
An administrator responsible for a remote FortiSwitch installation in the warehouse must restore network authentication when the switch cannot reach a remote RADIUS server. Which configuration best matches that precise goal?
- Use RADIUS change of authorization where supported
- Use port-based 802.1X authorization
- Permit RADIUS traffic from managed FortiSwitch via FortiGate
- Enable MAC authentication bypass for a legacy camera
- Use a guest or unauthorized VLAN policy where supported
Explanation
Correct Answer
C:At this network boundary, a managed FortiSwitch often needs an explicit FortiGate firewall policy permitting RADIUS flow from FortiLink. The operator can test this claim by the specific check: trace the RADIUS path and examine the matching FortiGate policy hit counters.
Incorrect Answers
A:Compared with the requested “Permit RADIUS traffic from managed FortiSwitch via FortiGate” at the warehouse, this would change an existing session's access decision without waiting for ordinary reconnection instead: a RADIUS CoA message can alter an established authorization in a supported policy workflow. At the warehouse, the operational proof would instead be to trace the RADIUS path and examine the matching FortiGate policy hit counters, whereas “Use RADIUS change of authorization where supported” is validated by a different test: inspect the CoA transaction and subsequent session policy or VLAN state.
B:Compared with the requested “Permit RADIUS traffic from managed FortiSwitch via FortiGate” at the warehouse, this would treat the interface as authorized after a permitted port-level authentication succeeds instead: port-based access control gates the entire port, which matters if multiple devices share the same physical connection. At the warehouse, the operational proof would instead be to trace the RADIUS path and examine the matching FortiGate policy hit counters, whereas “Use port-based 802.1X authorization” is validated by a different test: inspect authorized port state and evaluate behavior of hosts behind that port.
D:Compared with the requested “Permit RADIUS traffic from managed FortiSwitch via FortiGate” at the warehouse, this would admit a non-802.1X device through a controlled RADIUS identity check instead: MAB can submit a device MAC address as authentication credentials when no EAP supplicant is available. At the warehouse, the operational proof would instead be to trace the RADIUS path and examine the matching FortiGate policy hit counters, whereas “Enable MAC authentication bypass for a legacy camera” is validated by a different test: check the MAC-based RADIUS transaction and device session authorization.
E:For the warehouse, “Use a guest or unauthorized VLAN policy where supported” is a different type of control from “Permit RADIUS traffic from managed FortiSwitch via FortiGate”: an unauthorized or guest network can provide limited connectivity instead of normal production access. Unlike the requested feature, that setting addresses the need to separate endpoints that have not completed approved network authentication, not the objective to restore network authentication when the switch cannot reach a remote RADIUS server.
Question 505
Before applying the planned operation “Permit RADIUS traffic from managed FortiSwitch via FortiGate” at the headquarters, the administrator must predict its impact. Which prediction is sound?
- A port policy binds appropriate authentication and security settings to an interface
- Session clearing removes prior authorization state so that a fresh EAP/RADIUS exchange can be assessed
- MAB can submit a device MAC address as authentication credentials when no EAP supplicant is available
- A managed FortiSwitch often needs an explicit FortiGate firewall policy permitting RADIUS flow from FortiLink
Explanation
Correct Answer
D:In this deployment, the configured operation is meant to restore network authentication when the switch cannot reach a remote RADIUS server. The most relevant validation is to trace the RADIUS path and examine the matching FortiGate policy hit counters for the equipment at the headquarters.
Incorrect Answers
A:That behavior applies when engineers “Apply a port security profile to a FortiSwitch interface”; the different operation “Permit RADIUS traffic from managed FortiSwitch via FortiGate” is intended to restore network authentication when the switch cannot reach a remote RADIUS server. That different feature is verified by inspect applied port policy identity and active session state; for “Permit RADIUS traffic from managed FortiSwitch via FortiGate” on an endpoint-facing FortiSwitch port, the relevant evidence is to trace the RADIUS path and examine the matching FortiGate policy hit counters.
B:This outcome would be relevant to “Clear a stale 802.1X authorized session during diagnostics” at the headquarters, not the task “Permit RADIUS traffic from managed FortiSwitch via FortiGate”; the other task is to force reauthentication after the endpoint or authorization rule has changed. The action “Permit RADIUS traffic from managed FortiSwitch via FortiGate” targets a different result: a managed FortiSwitch often needs an explicit FortiGate firewall policy permitting RADIUS flow from FortiLink; the proposed alternative would instead be checked by inspect the session table before and after clearing and review the new authentication exchange.
C:That behavior applies when engineers “Enable MAC authentication bypass for a legacy camera”; the different operation “Permit RADIUS traffic from managed FortiSwitch via FortiGate” is intended to restore network authentication when the switch cannot reach a remote RADIUS server. That different feature is verified by check the MAC-based RADIUS transaction and device session authorization; for “Permit RADIUS traffic from managed FortiSwitch via FortiGate” on an endpoint-facing FortiSwitch port, the relevant evidence is to trace the RADIUS path and examine the matching FortiGate policy hit counters.
Question 506
A network architect documents a single goal for a standalone FortiSwitch appliance: force reauthentication after the endpoint or authorization rule has changed. Which listed procedure provides that capability?
- Apply a port security profile to a FortiSwitch interface
- Clear a stale 802.1X authorized session during diagnostics
- Use EAP-TLS where device certificates are deployed
- Permit RADIUS traffic from managed FortiSwitch via FortiGate
Explanation
Correct Answer
B:For the stated requirement, session clearing removes prior authorization state so that a fresh EAP/RADIUS exchange can be assessed. The operator can test this claim by the specific check: inspect the session table before and after clearing and review the new authentication exchange.
Incorrect Answers
A:Compared with the requested “Clear a stale 802.1X authorized session during diagnostics” at the hospital wing, this would maintain a reusable set of network admission controls on selected access ports instead: a port policy binds appropriate authentication and security settings to an interface. At the hospital wing, the operational proof would instead be to inspect the session table before and after clearing and review the new authentication exchange, whereas “Apply a port security profile to a FortiSwitch interface” is validated by a different test: inspect applied port policy identity and active session state.
C:Compared with the requested “Clear a stale 802.1X authorized session during diagnostics” at the hospital wing, this would authenticate compliant devices with a certificate-based EAP exchange instead: EAP-TLS uses certificate validation in the authentication flow rather than a simple MAC-only identity. At the hospital wing, the operational proof would instead be to inspect the session table before and after clearing and review the new authentication exchange, whereas “Use EAP-TLS where device certificates are deployed” is validated by a different test: examine EAP-TLS negotiation and server certificate trust results.
D:For the hospital wing, “Permit RADIUS traffic from managed FortiSwitch via FortiGate” is a different type of control from “Clear a stale 802.1X authorized session during diagnostics”: a managed FortiSwitch often needs an explicit FortiGate firewall policy permitting RADIUS flow from FortiLink. Unlike the requested feature, that setting addresses the need to restore network authentication when the switch cannot reach a remote RADIUS server, not the objective to force reauthentication after the endpoint or authorization rule has changed.
Question 507
Before applying the planned operation “Clear a stale 802.1X authorized session during diagnostics” at the factory, the administrator must predict its impact. Which prediction is sound?
- The switch forwards authentication exchanges to a configured RADIUS service rather than validating enterprise credentials by itself
- EAP-TLS uses certificate validation in the authentication flow rather than a simple MAC-only identity
- Session clearing removes prior authorization state so that a fresh EAP/RADIUS exchange can be assessed
- A configured MAC identity restricts layer-2 admission or learning to designated devices
- A port policy binds appropriate authentication and security settings to an interface
Explanation
Correct Answer
C:The deciding detail is that the configured operation is meant to force reauthentication after the endpoint or authorization rule has changed. The most relevant validation is to inspect the session table before and after clearing and review the new authentication exchange for the equipment at the factory.
Incorrect Answers
A:This outcome would be relevant to “Configure a reachable RADIUS authentication server” at the factory, not the task “Clear a stale 802.1X authorized session during diagnostics”; the other task is to provide external identity validation for network access control. The action “Clear a stale 802.1X authorized session during diagnostics” targets a different result: session clearing removes prior authorization state so that a fresh EAP/RADIUS exchange can be assessed; the proposed alternative would instead be checked by test RADIUS reachability, shared-secret agreement and server response time.
B:That behavior applies when engineers “Use EAP-TLS where device certificates are deployed”; the different operation “Clear a stale 802.1X authorized session during diagnostics” is intended to force reauthentication after the endpoint or authorization rule has changed. That different feature is verified by examine EAP-TLS negotiation and server certificate trust results; for “Clear a stale 802.1X authorized session during diagnostics” on a newly commissioned floor switch, the relevant evidence is to inspect the session table before and after clearing and review the new authentication exchange.
D:That behavior applies when engineers “Use static MAC security for a fixed appliance”; the different operation “Clear a stale 802.1X authorized session during diagnostics” is intended to force reauthentication after the endpoint or authorization rule has changed. That different feature is verified by check the secure MAC table and the source address of blocked frames; for “Clear a stale 802.1X authorized session during diagnostics” on a newly commissioned floor switch, the relevant evidence is to inspect the session table before and after clearing and review the new authentication exchange.
E:That behavior applies when engineers “Apply a port security profile to a FortiSwitch interface”; the different operation “Clear a stale 802.1X authorized session during diagnostics” is intended to force reauthentication after the endpoint or authorization rule has changed. That different feature is verified by inspect applied port policy identity and active session state; for “Clear a stale 802.1X authorized session during diagnostics” on a newly commissioned floor switch, the relevant evidence is to inspect the session table before and after clearing and review the new authentication exchange.
Question 508
During a change window in the distribution floor, engineers are asked to stop an untrusted access port from supplying rogue DHCP server messages. What should they configure rather than using a feature for an adjacent purpose?
- Provision a static IPv4 source guard entry
- Enable DHCP snooping on an access VLAN
- Enable dynamic ARP inspection on a VLAN
- Keep ordinary client ports DHCP-snooping untrusted
Explanation
Correct Answer
B:The relevant mechanism is: DHCP snooping checks DHCP packets on the VLAN and builds trusted IP-to-MAC lease bindings. The operator can test this claim by the specific check: inspect DHCP snooping status and the learned bindings for that VLAN.
Incorrect Answers
A:For the distribution floor, “Provision a static IPv4 source guard entry” is a different type of control from “Enable DHCP snooping on an access VLAN”: 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 stop an untrusted access port from supplying rogue DHCP server messages.
C:Compared with the requested “Enable DHCP snooping on an access VLAN” at the distribution floor, 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 distribution floor, the operational proof would instead be to inspect DHCP snooping status and the learned bindings for that VLAN, 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.
D:Compared with the requested “Enable DHCP snooping on an access VLAN” at the distribution 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 distribution floor, the operational proof would instead be to inspect DHCP snooping status and the learned bindings for that VLAN, 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 509
Before applying the planned operation “Enable DHCP snooping on an access VLAN” at the media studio, the administrator must predict its impact. Which prediction is sound?
- DHCP snooping checks DHCP packets on the VLAN and builds trusted IP-to-MAC lease bindings
- 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
- Fortinet requires DHCP snooping to be configured before enabling DAI for the VLAN
Explanation
Correct Answer
A:This approach fits because the configured operation is meant to stop an untrusted access port from supplying rogue DHCP server messages. The most relevant validation is to inspect DHCP snooping status and the learned bindings for that VLAN for the equipment at the media studio.
Incorrect Answers
B:This outcome would be relevant to “Use storm control on a broadcast-heavy access port” at the media studio, not the task “Enable DHCP snooping on an access VLAN”; the other task is to limit disruption from excessive broadcast, multicast or unknown-unicast traffic. The action “Enable DHCP snooping on an access VLAN” targets a different result: DHCP snooping checks DHCP packets on the VLAN and builds trusted IP-to-MAC lease bindings; the proposed alternative would instead be checked by read storm-control counters during the observed high-rate event.
C:That behavior applies when engineers “Use IP-subnet-based VLAN assignment”; the different operation “Enable DHCP snooping on an access VLAN” is intended to stop an untrusted access port from supplying rogue DHCP server messages. That different feature is verified by compare received source IP with configured IP-based VLAN mapping; for “Enable DHCP snooping on an access VLAN” on a switch serving a high-density endpoint area, the relevant evidence is to inspect DHCP snooping status and the learned bindings for that VLAN.
D:That behavior applies when engineers “Enable DHCP snooping before dynamic ARP inspection”; the different operation “Enable DHCP snooping on an access VLAN” is intended to stop an untrusted access port from supplying rogue DHCP server messages. That different feature is verified by check both the VLAN's DHCP snooping setting and DAI enablement; for “Enable DHCP snooping on an access VLAN” on a switch serving a high-density endpoint area, the relevant evidence is to inspect DHCP snooping status and the learned bindings for that VLAN.
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”.