Question 470
After implementing “Enable MAC authentication bypass for a legacy camera,” the site engineer needs to assess its actual effect on a remote FortiSwitch installation. Which test is the best match?
- Inspect the negotiated EAP type in the access attempt
- Capture EAPOL frames on the access port and inspect endpoint supplicant state
- Check the MAC-based RADIUS transaction and device session authorization
- Inspect authorized port state and evaluate behavior of hosts behind that port
Explanation
Correct Answer
C:For the stated requirement, MAB can submit a device MAC address as authentication credentials when no EAP supplicant is available. Directly measuring that result demonstrates whether the step to admit a non-802.1X device through a controlled RADIUS identity check succeeded on a remote FortiSwitch installation.
Incorrect Answers
A: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 “Enable MAC authentication bypass for a legacy camera” at the campus. Checking “Enable MAC authentication bypass for a legacy camera” at the campus requires evidence of its own mechanism: MAB can submit a device MAC address as authentication credentials when no EAP supplicant is available; that is not the outcome measured by “Use EAP-TTLS for compatible tunnel-based access authentication”.
B:This check is suited to “Troubleshoot an 802.1X supplicant that never starts” when trying to determine why a locked port sees no usable EAP exchange from the attached device, not to verify “Enable MAC authentication bypass for a legacy camera” at the campus. Checking “Enable MAC authentication bypass for a legacy camera” at the campus requires evidence of its own mechanism: MAB can submit a device MAC address as authentication credentials when no EAP supplicant is available; that is not the outcome measured by “Troubleshoot an 802.1X supplicant that never starts”.
D:The proposed check concerns “Use port-based 802.1X authorization” rather than “Enable MAC authentication bypass for a legacy camera”: port-based access control gates the entire port, which matters if multiple devices share the same physical connection. For “Enable MAC authentication bypass for a legacy camera” on a remote FortiSwitch installation, a better test would be to check the MAC-based RADIUS transaction and device session authorization, which targets admit a non-802.1X device through a controlled RADIUS identity check rather than the alternative diagnostic “Use port-based 802.1X authorization”.
Question 471
A network architect documents a single goal for an endpoint-facing FortiSwitch port: make network devices without certificates recognizable to the access policy. Which listed procedure provides that capability?
- Configure a reachable RADIUS authentication server
- Use EAP-PEAP where the RADIUS design requires a protected inner method
- Provision device MAC identities in RADIUS for MAB
- Use a guest or unauthorized VLAN policy where supported
- Use RADIUS change of authorization where supported
Explanation
Correct Answer
C:The deciding detail is that MAB needs a server-side record or lookup logic that accepts the enrolled MAC identities. This distinction is material to the remote depot, where the stated goal is to make network devices without certificates recognizable to the access policy.
Incorrect Answers
A:For the remote depot, “Configure a reachable RADIUS authentication server” is a different type of control from “Provision device MAC identities in RADIUS for MAB”: the switch forwards authentication exchanges to a configured RADIUS service rather than validating enterprise credentials by itself. Unlike the requested feature, that setting addresses the need to provide external identity validation for network access control, not the objective to make network devices without certificates recognizable to the access policy.
B:Compared with the requested “Provision device MAC identities in RADIUS for MAB” at the remote depot, this would support a tunneled EAP authentication approach for compatible endpoints instead: PEAP establishes a protected authentication exchange; it remains distinct from MAB and switch MAC limits. At the remote depot, the operational proof would instead be to search RADIUS logs for the submitted hardware address and expected accept decision, whereas “Use EAP-PEAP where the RADIUS design requires a protected inner method” is validated by a different test: inspect client EAP type and server-side PEAP negotiation events.
D:Compared with the requested “Provision device MAC identities in RADIUS for MAB” at the remote depot, this would separate endpoints that have not completed approved network authentication instead: an unauthorized or guest network can provide limited connectivity instead of normal production access. At the remote depot, the operational proof would instead be to search RADIUS logs for the submitted hardware address and expected accept decision, whereas “Use a guest or unauthorized VLAN policy where supported” is validated by a different test: inspect the failed authentication state and assigned VLAN on the endpoint session.
E:Compared with the requested “Provision device MAC identities in RADIUS for MAB” at the remote depot, 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 remote depot, the operational proof would instead be to search RADIUS logs for the submitted hardware address and expected accept decision, 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.
Question 472
A change record for a standalone FortiSwitch appliance states “Provision device MAC identities in RADIUS for MAB.” Which description correctly explains what this will accomplish?
- MAB needs a server-side record or lookup logic that accepts the enrolled MAC identities
- MAC-based mode maintains per-device authorization decisions instead of granting the entire port one common state
- A managed FortiSwitch often needs an explicit FortiGate firewall policy permitting RADIUS flow from FortiLink
- A RADIUS CoA message can alter an established authorization in a supported policy workflow
Explanation
Correct Answer
A:The relevant mechanism is: the configured operation is meant to make network devices without certificates recognizable to the access policy. The most relevant validation is to search RADIUS logs for the submitted hardware address and expected accept decision for the equipment at the lab.
Incorrect Answers
B:This outcome would be relevant to “Use MAC-based 802.1X access sessions” at the lab, not the task “Provision device MAC identities in RADIUS for MAB”; the other task is to control separate endpoint identities on one shared physical port. The action “Provision device MAC identities in RADIUS for MAB” targets a different result: MAB needs a server-side record or lookup logic that accepts the enrolled MAC identities; the proposed alternative would instead be checked by inspect individual authenticated MAC session entries on the interface.
C:That behavior applies when engineers “Permit RADIUS traffic from managed FortiSwitch via FortiGate”; the different operation “Provision device MAC identities in RADIUS for MAB” is intended to make network devices without certificates recognizable to the access policy. That different feature is verified by trace the RADIUS path and examine the matching FortiGate policy hit counters; for “Provision device MAC identities in RADIUS for MAB” on a standalone FortiSwitch appliance, the relevant evidence is to search RADIUS logs for the submitted hardware address and expected accept decision.
D:That behavior applies when engineers “Use RADIUS change of authorization where supported”; the different operation “Provision device MAC identities in RADIUS for MAB” is intended to make network devices without certificates recognizable to the access policy. That different feature is verified by inspect the CoA transaction and subsequent session policy or VLAN state; for “Provision device MAC identities in RADIUS for MAB” on a standalone FortiSwitch appliance, the relevant evidence is to search RADIUS logs for the submitted hardware address and expected accept decision.
Question 473
At the staging rack, a dashboard shows ordinary link-up state, but the team also needs proof for “Provision device MAC identities in RADIUS for MAB.” Which targeted check should be used?
- Examine EAP-TLS negotiation and server certificate trust results
- Search RADIUS logs for the submitted hardware address and expected accept decision
- Trace the RADIUS path and examine the matching FortiGate policy hit counters
- Inspect applied port policy identity and active session state
Explanation
Correct Answer
B:This approach fits because MAB needs a server-side record or lookup logic that accepts the enrolled MAC identities. Directly measuring that result demonstrates whether the step to make network devices without certificates recognizable to the access policy succeeded on a newly commissioned floor switch.
Incorrect Answers
A:This check is suited to “Use EAP-TLS where device certificates are deployed” when trying to authenticate compliant devices with a certificate-based EAP exchange, not to verify “Provision device MAC identities in RADIUS for MAB” at the staging rack. Checking “Provision device MAC identities in RADIUS for MAB” at the staging rack requires evidence of its own mechanism: MAB needs a server-side record or lookup logic that accepts the enrolled MAC identities; that is not the outcome measured by “Use EAP-TLS where device certificates are deployed”.
C: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 “Provision device MAC identities in RADIUS for MAB” at the staging rack. Checking “Provision device MAC identities in RADIUS for MAB” at the staging rack requires evidence of its own mechanism: MAB needs a server-side record or lookup logic that accepts the enrolled MAC identities; that is not the outcome measured by “Permit RADIUS traffic from managed FortiSwitch via FortiGate”.
D:The proposed check concerns “Apply a port security profile to a FortiSwitch interface” rather than “Provision device MAC identities in RADIUS for MAB”: a port policy binds appropriate authentication and security settings to an interface. For “Provision device MAC identities in RADIUS for MAB” on a newly commissioned floor switch, a better test would be to search RADIUS logs for the submitted hardware address and expected accept decision, which targets make network devices without certificates recognizable to the access policy rather than the alternative diagnostic “Apply a port security profile to a FortiSwitch interface”.
Question 474
The operational requirement for a local switch administering branch clients at the research building is to authenticate compliant devices with a certificate-based EAP exchange. Which FortiSwitch choice directly targets it?
- Configure a reachable RADIUS authentication server
- Use EAP-TLS where device certificates are deployed
- Use MAC-based 802.1X access sessions
- Use a guest or unauthorized VLAN policy where supported
- Use RADIUS change of authorization where supported
Explanation
Correct Answer
B:The critical distinction is that EAP-TLS uses certificate validation in the authentication flow rather than a simple MAC-only identity. The operator can test this claim by the specific check: examine EAP-TLS negotiation and server certificate trust results.
Incorrect Answers
A:Compared with the requested “Use EAP-TLS where device certificates are deployed” at the research building, 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 research building, the operational proof would instead be to examine EAP-TLS negotiation and server certificate trust results, whereas “Configure a reachable RADIUS authentication server” is validated by a different test: test RADIUS reachability, shared-secret agreement and server response time.
C:Compared with the requested “Use EAP-TLS where device certificates are deployed” at the research building, this would control separate endpoint identities on one shared physical port instead: MAC-based mode maintains per-device authorization decisions instead of granting the entire port one common state. At the research building, the operational proof would instead be to examine EAP-TLS negotiation and server certificate trust results, whereas “Use MAC-based 802.1X access sessions” is validated by a different test: inspect individual authenticated MAC session entries on the interface.
D:For the research building, “Use a guest or unauthorized VLAN policy where supported” is a different type of control from “Use EAP-TLS where device certificates are deployed”: 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 authenticate compliant devices with a certificate-based EAP exchange.
E:Compared with the requested “Use EAP-TLS where device certificates are deployed” at the research building, 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 research building, the operational proof would instead be to examine EAP-TLS negotiation and server certificate trust results, 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.
Question 475
An operations log records this activity at the clinic: use EAP-TLS where device certificates are deployed. Which result is specifically attributable to that action?
- A managed FortiSwitch often needs an explicit FortiGate firewall policy permitting RADIUS flow from FortiLink
- A port policy binds appropriate authentication and security settings to an interface
- EAP-TLS uses certificate validation in the authentication flow rather than a simple MAC-only identity
- MAC-based mode maintains per-device authorization decisions instead of granting the entire port one common state
Explanation
Correct Answer
C:That setting is appropriate here because the configured operation is meant to authenticate compliant devices with a certificate-based EAP exchange. The most relevant validation is to examine EAP-TLS negotiation and server certificate trust results for the equipment at the clinic.
Incorrect Answers
A:This outcome would be relevant to “Permit RADIUS traffic from managed FortiSwitch via FortiGate” at the clinic, not the task “Use EAP-TLS where device certificates are deployed”; the other task is to restore network authentication when the switch cannot reach a remote RADIUS server. The action “Use EAP-TLS where device certificates are deployed” targets a different result: EAP-TLS uses certificate validation in the authentication flow rather than a simple MAC-only identity; the proposed alternative would instead be checked by trace the RADIUS path and examine the matching FortiGate policy hit counters.
B:That behavior applies when engineers “Apply a port security profile to a FortiSwitch interface”; the different operation “Use EAP-TLS where device certificates are deployed” is intended to authenticate compliant devices with a certificate-based EAP exchange. That different feature is verified by inspect applied port policy identity and active session state; for “Use EAP-TLS where device certificates are deployed” on a switch used by multiple office teams, the relevant evidence is to examine EAP-TLS negotiation and server certificate trust results.
D:That behavior applies when engineers “Use MAC-based 802.1X access sessions”; the different operation “Use EAP-TLS where device certificates are deployed” is intended to authenticate compliant devices with a certificate-based EAP exchange. That different feature is verified by inspect individual authenticated MAC session entries on the interface; for “Use EAP-TLS where device certificates are deployed” on a switch used by multiple office teams, the relevant evidence is to examine EAP-TLS negotiation and server certificate trust results.
Question 476
A FortiSwitch engineer in the data hall is documenting successful operation of “Use EAP-TLS where device certificates are deployed.” Which measurement or inspection confirms it?
- Examine EAP-TLS negotiation and server certificate trust results
- Inspect applied port policy identity and active session state
- Inspect the 802.1X session state and RADIUS accept or reject result
- Search RADIUS logs for the submitted hardware address and expected accept decision
Explanation
Correct Answer
A:This is the precise control because EAP-TLS uses certificate validation in the authentication flow rather than a simple MAC-only identity. Directly measuring that result demonstrates whether the step to authenticate compliant devices with a certificate-based EAP exchange succeeded on a production FortiSwitch fabric.
Incorrect Answers
B:This check is suited to “Apply a port security profile to a FortiSwitch interface” when trying to maintain a reusable set of network admission controls on selected access ports, not to verify “Use EAP-TLS where device certificates are deployed” at the data hall. Checking “Use EAP-TLS where device certificates are deployed” at the data hall requires evidence of its own mechanism: EAP-TLS uses certificate validation in the authentication flow rather than a simple MAC-only identity; that is not the outcome measured by “Apply a port security profile to a FortiSwitch interface”.
C:This check is suited to “Configure 802.1X for a user-facing port” when trying to authenticate a standards-compliant supplicant before admitting it to the access network, not to verify “Use EAP-TLS where device certificates are deployed” at the data hall. Checking “Use EAP-TLS where device certificates are deployed” at the data hall requires evidence of its own mechanism: EAP-TLS uses certificate validation in the authentication flow rather than a simple MAC-only identity; that is not the outcome measured by “Configure 802.1X for a user-facing port”.
D:The proposed check concerns “Provision device MAC identities in RADIUS for MAB” rather than “Use EAP-TLS where device certificates are deployed”: MAB needs a server-side record or lookup logic that accepts the enrolled MAC identities. For “Use EAP-TLS where device certificates are deployed” on a production FortiSwitch fabric, a better test would be to examine EAP-TLS negotiation and server certificate trust results, which targets authenticate compliant devices with a certificate-based EAP exchange rather than the alternative diagnostic “Provision device MAC identities in RADIUS for MAB”.
Question 477
During a change window in the development floor, engineers are asked to support a tunneled EAP authentication approach for compatible endpoints. What should they configure rather than using a feature for an adjacent purpose?
- Apply a port security profile to a FortiSwitch interface
- Provision device MAC identities in RADIUS for MAB
- Use EAP-PEAP where the RADIUS design requires a protected inner method
- Configure 802.1X for a user-facing port
Explanation
Correct Answer
C:The implementation works because PEAP establishes a protected authentication exchange; it remains distinct from MAB and switch MAC limits. This distinction is material to the development floor, where the stated goal is to support a tunneled EAP authentication approach for compatible endpoints.
Incorrect Answers
A:For the development floor, “Apply a port security profile to a FortiSwitch interface” is a different type of control from “Use EAP-PEAP where the RADIUS design requires a protected inner method”: 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 support a tunneled EAP authentication approach for compatible endpoints.
B:Compared with the requested “Use EAP-PEAP where the RADIUS design requires a protected inner method” at the development floor, this would make network devices without certificates recognizable to the access policy instead: MAB needs a server-side record or lookup logic that accepts the enrolled MAC identities. At the development floor, the operational proof would instead be to inspect client EAP type and server-side PEAP negotiation events, whereas “Provision device MAC identities in RADIUS for MAB” is validated by a different test: search RADIUS logs for the submitted hardware address and expected accept decision.
D:Compared with the requested “Use EAP-PEAP where the RADIUS design requires a protected inner method” at the development floor, this would authenticate a standards-compliant supplicant before admitting it to the access network instead: 802.1X uses EAP between the endpoint and the switch authenticator, with RADIUS decision-making upstream. At the development floor, the operational proof would instead be to inspect client EAP type and server-side PEAP negotiation events, whereas “Configure 802.1X for a user-facing port” is validated by a different test: inspect the 802.1X session state and RADIUS accept or reject result.
Question 478
When engineers use EAP-PEAP where the RADIUS design requires a protected inner method at the conference venue, which forwarding, security, management or diagnostic outcome follows from that action?
- A configured MAC identity restricts layer-2 admission or learning to designated devices
- MAB needs a server-side record or lookup logic that accepts the enrolled MAC identities
- TTLS wraps inner authentication within a protected tunnel and requires matching endpoint/server settings
- 802.1X uses EAP between the endpoint and the switch authenticator, with RADIUS decision-making upstream
- PEAP establishes a protected authentication exchange; it remains distinct from MAB and switch MAC limits
Explanation
Correct Answer
E:Given the described goal, the configured operation is meant to support a tunneled EAP authentication approach for compatible endpoints. The most relevant validation is to inspect client EAP type and server-side PEAP negotiation events for the equipment at the conference venue.
Incorrect Answers
A:This outcome would be relevant to “Use static MAC security for a fixed appliance” at the conference venue, not the task “Use EAP-PEAP where the RADIUS design requires a protected inner method”; the other task is to allow a particular known device address on a controlled interface. The action “Use EAP-PEAP where the RADIUS design requires a protected inner method” targets a different result: PEAP establishes a protected authentication exchange; it remains distinct from MAB and switch MAC limits; the proposed alternative would instead be checked by check the secure MAC table and the source address of blocked frames.
B:That behavior applies when engineers “Provision device MAC identities in RADIUS for MAB”; the different operation “Use EAP-PEAP where the RADIUS design requires a protected inner method” is intended to support a tunneled EAP authentication approach for compatible endpoints. That different feature is verified by search RADIUS logs for the submitted hardware address and expected accept decision; for “Use EAP-PEAP where the RADIUS design requires a protected inner method” on two distribution switches, the relevant evidence is to inspect client EAP type and server-side PEAP negotiation events.
C:That behavior applies when engineers “Use EAP-TTLS for compatible tunnel-based access authentication”; the different operation “Use EAP-PEAP where the RADIUS design requires a protected inner method” is intended to support a tunneled EAP authentication approach for compatible endpoints. That different feature is verified by inspect the negotiated EAP type in the access attempt; for “Use EAP-PEAP where the RADIUS design requires a protected inner method” on two distribution switches, the relevant evidence is to inspect client EAP type and server-side PEAP negotiation events.
D:That behavior applies when engineers “Configure 802.1X for a user-facing port”; the different operation “Use EAP-PEAP where the RADIUS design requires a protected inner method” is intended to support a tunneled EAP authentication approach for compatible endpoints. That different feature is verified by inspect the 802.1X session state and RADIUS accept or reject result; for “Use EAP-PEAP where the RADIUS design requires a protected inner method” on two distribution switches, the relevant evidence is to inspect client EAP type and server-side PEAP negotiation events.
Question 479
A feature acceptance test on a staging FortiSwitch concerns “Use EAP-PEAP where the RADIUS design requires a protected inner method.” What should be checked to establish its expected operation?
- Inspect client EAP type and server-side PEAP negotiation events
- Capture EAPOL frames on the access port and inspect endpoint supplicant state
- Inspect the negotiated EAP type in the access attempt
- Inspect authorized port state and evaluate behavior of hosts behind that port
Explanation
Correct Answer
A:The switch behavior that matters is: PEAP establishes a protected authentication exchange; it remains distinct from MAB and switch MAC limits. Directly measuring that result demonstrates whether the step to support a tunneled EAP authentication approach for compatible endpoints succeeded on a staging FortiSwitch.
Incorrect Answers
B:This check is suited to “Troubleshoot an 802.1X supplicant that never starts” when trying to determine why a locked port sees no usable EAP exchange from the attached device, not to verify “Use EAP-PEAP where the RADIUS design requires a protected inner method” at the hospital wing. Checking “Use EAP-PEAP where the RADIUS design requires a protected inner method” at the hospital wing requires evidence of its own mechanism: PEAP establishes a protected authentication exchange; it remains distinct from MAB and switch MAC limits; that is not the outcome measured by “Troubleshoot an 802.1X supplicant that never starts”.
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 EAP-PEAP where the RADIUS design requires a protected inner method” at the hospital wing. Checking “Use EAP-PEAP where the RADIUS design requires a protected inner method” at the hospital wing requires evidence of its own mechanism: PEAP establishes a protected authentication exchange; it remains distinct from MAB and switch MAC limits; that is not the outcome measured by “Use EAP-TTLS for compatible tunnel-based access authentication”.
D:The proposed check concerns “Use port-based 802.1X authorization” rather than “Use EAP-PEAP where the RADIUS design requires a protected inner method”: port-based access control gates the entire port, which matters if multiple devices share the same physical connection. For “Use EAP-PEAP where the RADIUS design requires a protected inner method” on a staging FortiSwitch, a better test would be to inspect client EAP type and server-side PEAP negotiation events, which targets support a tunneled EAP authentication approach for compatible endpoints rather than the alternative diagnostic “Use port-based 802.1X authorization”.
Question 480
For the training center, the network team needs to provide a tunneled credential exchange supported by the configured RADIUS server. Which change is the most direct way to implement that requirement on a carefully segmented Layer 2 network?
- Use MAC-based 802.1X access sessions
- Use RADIUS change of authorization where supported
- Use a guest or unauthorized VLAN policy where supported
- Use EAP-TTLS for compatible tunnel-based access authentication
Explanation
Correct Answer
D:At this network boundary, TTLS wraps inner authentication within a protected tunnel and requires matching endpoint/server settings. The operator can test this claim by the specific check: inspect the negotiated EAP type in the access attempt.
Incorrect Answers
A:Compared with the requested “Use EAP-TTLS for compatible tunnel-based access authentication” at the training center, this would control separate endpoint identities on one shared physical port instead: MAC-based mode maintains per-device authorization decisions instead of granting the entire port one common state. At the training center, the operational proof would instead be to inspect the negotiated EAP type in the access attempt, whereas “Use MAC-based 802.1X access sessions” is validated by a different test: inspect individual authenticated MAC session entries on the interface.
B:Compared with the requested “Use EAP-TTLS for compatible tunnel-based access authentication” at the training center, 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 training center, the operational proof would instead be to inspect the negotiated EAP type in the access attempt, 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.
C:For the training center, “Use a guest or unauthorized VLAN policy where supported” is a different type of control from “Use EAP-TTLS for compatible tunnel-based access authentication”: 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 provide a tunneled credential exchange supported by the configured RADIUS server.