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.
Question 481
A colleague asks about the effect of “Use EAP-TTLS for compatible tunnel-based access authentication” on a central switching stack. Which behavior best characterizes that feature?
- TTLS wraps inner authentication within a protected tunnel and requires matching endpoint/server settings
- 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 port policy binds appropriate authentication and security settings to an interface
Explanation
Correct Answer
A:In this deployment, the configured operation is meant to provide a tunneled credential exchange supported by the configured RADIUS server. The most relevant validation is to inspect the negotiated EAP type in the access attempt for the equipment at the lab.
Incorrect Answers
B:That behavior applies when engineers “Use MAC-based 802.1X access sessions”; the different operation “Use EAP-TTLS for compatible tunnel-based access authentication” is intended to provide a tunneled credential exchange supported by the configured RADIUS server. That different feature is verified by inspect individual authenticated MAC session entries on the interface; for “Use EAP-TTLS for compatible tunnel-based access authentication” on a central switching stack, the relevant evidence is to inspect the negotiated EAP type in the access attempt.
C:This outcome would be relevant to “Permit RADIUS traffic from managed FortiSwitch via FortiGate” at the lab, not the task “Use EAP-TTLS for compatible tunnel-based access authentication”; the other task is to restore network authentication when the switch cannot reach a remote RADIUS server. The action “Use EAP-TTLS for compatible tunnel-based access authentication” targets a different result: TTLS wraps inner authentication within a protected tunnel and requires matching endpoint/server settings; the proposed alternative would instead be checked by trace the RADIUS path and examine the matching FortiGate policy hit counters.
D:That behavior applies when engineers “Apply a port security profile to a FortiSwitch interface”; the different operation “Use EAP-TTLS for compatible tunnel-based access authentication” is intended to provide a tunneled credential exchange supported by the configured RADIUS server. That different feature is verified by inspect applied port policy identity and active session state; for “Use EAP-TTLS for compatible tunnel-based access authentication” on a central switching stack, the relevant evidence is to inspect the negotiated EAP type in the access attempt.
Question 482
On a switch used by multiple office teams at the staging rack, the team reports that it has configured “Use EAP-TTLS for compatible tunnel-based access authentication.” Which verification provides the strongest direct evidence that the intended function is working?
- Inspect the negotiated EAP type in the access attempt
- 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
- Inspect the 802.1X session state and RADIUS accept or reject result
Explanation
Correct Answer
A:For the stated requirement, TTLS wraps inner authentication within a protected tunnel and requires matching endpoint/server settings. Directly measuring that result demonstrates whether the step to provide a tunneled credential exchange supported by the configured RADIUS server succeeded on a switch used by multiple office teams.
Incorrect Answers
B:The proposed check concerns “Provision device MAC identities in RADIUS for MAB” rather than “Use EAP-TTLS for compatible tunnel-based access authentication”: MAB needs a server-side record or lookup logic that accepts the enrolled MAC identities. For “Use EAP-TTLS for compatible tunnel-based access authentication” on a switch used by multiple office teams, a better test would be to inspect the negotiated EAP type in the access attempt, which targets provide a tunneled credential exchange supported by the configured RADIUS server rather than the alternative diagnostic “Provision device MAC identities in RADIUS for MAB”.
C:The proposed check concerns “Permit RADIUS traffic from managed FortiSwitch via FortiGate” rather than “Use EAP-TTLS for compatible tunnel-based access authentication”: a managed FortiSwitch often needs an explicit FortiGate firewall policy permitting RADIUS flow from FortiLink. For “Use EAP-TTLS for compatible tunnel-based access authentication” on a switch used by multiple office teams, a better test would be to inspect the negotiated EAP type in the access attempt, which targets provide a tunneled credential exchange supported by the configured RADIUS server rather than the alternative diagnostic “Permit RADIUS traffic from managed FortiSwitch via FortiGate”.
D: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-TTLS for compatible tunnel-based access authentication” at the staging rack. Checking “Use EAP-TTLS for compatible tunnel-based access authentication” at the staging rack requires evidence of its own mechanism: TTLS wraps inner authentication within a protected tunnel and requires matching endpoint/server settings; that is not the outcome measured by “Apply a port security profile to a FortiSwitch interface”.
E: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-TTLS for compatible tunnel-based access authentication” at the staging rack. Checking “Use EAP-TTLS for compatible tunnel-based access authentication” at the staging rack requires evidence of its own mechanism: TTLS wraps inner authentication within a protected tunnel and requires matching endpoint/server settings; that is not the outcome measured by “Configure 802.1X for a user-facing port”.
Question 483
On a production FortiSwitch fabric in the research building, the next task is to change an existing session's access decision without waiting for ordinary reconnection. What is the appropriate configuration decision?
- Use RADIUS change of authorization where supported
- Use EAP-PEAP where the RADIUS design requires a protected inner method
- Use static MAC security for a fixed appliance
- Use port-based 802.1X authorization
Explanation
Correct Answer
A:The deciding detail is that a RADIUS CoA message can alter an established authorization in a supported policy workflow. This distinction is material to the research building, where the stated goal is to change an existing session's access decision without waiting for ordinary reconnection.
Incorrect Answers
B:Compared with the requested “Use RADIUS change of authorization where supported” at the research building, 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 research building, the operational proof would instead be to inspect the CoA transaction and subsequent session policy or VLAN state, 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.
C:For the research building, “Use static MAC security for a fixed appliance” is a different type of control from “Use RADIUS change of authorization where supported”: a configured MAC identity restricts layer-2 admission or learning to designated devices. Unlike the requested feature, that setting addresses the need to allow a particular known device address on a controlled interface, not the objective to change an existing session's access decision without waiting for ordinary reconnection.
D:Compared with the requested “Use RADIUS change of authorization where supported” at the research building, 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 research building, the operational proof would instead be to inspect the CoA transaction and subsequent session policy or VLAN state, 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.
Question 484
When engineers use RADIUS change of authorization where supported at the clinic, which forwarding, security, management or diagnostic outcome follows from that action?
- Port-based access control gates the entire port, which matters if multiple devices share the same physical connection
- Accounting sends session records to a collector distinct from the basic allow-or-deny authentication result
- An 802.1X-capable client must participate in EAPOL before the server can approve its credentials
- A RADIUS CoA message can alter an established authorization in a supported policy workflow
Explanation
Correct Answer
D:The relevant mechanism is: the configured operation is meant to change an existing session's access decision without waiting for ordinary reconnection. The most relevant validation is to inspect the CoA transaction and subsequent session policy or VLAN state for the equipment at the clinic.
Incorrect Answers
A:That behavior applies when engineers “Use port-based 802.1X authorization”; the different operation “Use RADIUS change of authorization where supported” is intended to change an existing session's access decision without waiting for ordinary reconnection. That different feature is verified by inspect authorized port state and evaluate behavior of hosts behind that port; for “Use RADIUS change of authorization where supported” on a newly racked distribution unit, the relevant evidence is to inspect the CoA transaction and subsequent session policy or VLAN state.
B:That behavior applies when engineers “Enable RADIUS accounting for access sessions”; the different operation “Use RADIUS change of authorization where supported” is intended to change an existing session's access decision without waiting for ordinary reconnection. That different feature is verified by compare RADIUS accounting entries with the switch's active sessions; for “Use RADIUS change of authorization where supported” on a newly racked distribution unit, the relevant evidence is to inspect the CoA transaction and subsequent session policy or VLAN state.
C:This outcome would be relevant to “Troubleshoot an 802.1X supplicant that never starts” at the clinic, not the task “Use RADIUS change of authorization where supported”; the other task is to determine why a locked port sees no usable EAP exchange from the attached device. The action “Use RADIUS change of authorization where supported” targets a different result: a RADIUS CoA message can alter an established authorization in a supported policy workflow; the proposed alternative would instead be checked by capture EAPOL frames on the access port and inspect endpoint supplicant state.
Question 485
The work order to change an existing session's access decision without waiting for ordinary reconnection is marked complete on two distribution switches. Which observation most directly tests the completed configuration?
- Check the MAC-based RADIUS transaction and device session authorization
- Compare RADIUS accounting entries with the switch's active sessions
- Inspect the session table before and after clearing and review the new authentication exchange
- Inspect the CoA transaction and subsequent session policy or VLAN state
- Capture EAPOL frames on the access port and inspect endpoint supplicant state
Explanation
Correct Answer
D:This approach fits because a RADIUS CoA message can alter an established authorization in a supported policy workflow. Directly measuring that result demonstrates whether the step to change an existing session's access decision without waiting for ordinary reconnection succeeded on two distribution switches.
Incorrect Answers
A:The proposed check concerns “Enable MAC authentication bypass for a legacy camera” rather than “Use RADIUS change of authorization where supported”: MAB can submit a device MAC address as authentication credentials when no EAP supplicant is available. For “Use RADIUS change of authorization where supported” on two distribution switches, a better test would be to inspect the CoA transaction and subsequent session policy or VLAN state, which targets change an existing session's access decision without waiting for ordinary reconnection rather than the alternative diagnostic “Enable MAC authentication bypass for a legacy camera”.
B:This check is suited to “Enable RADIUS accounting for access sessions” when trying to record network access session starts and stops outside the switch, not to verify “Use RADIUS change of authorization where supported” at the data hall. Checking “Use RADIUS change of authorization where supported” at the data hall requires evidence of its own mechanism: a RADIUS CoA message can alter an established authorization in a supported policy workflow; that is not the outcome measured by “Enable RADIUS accounting for access sessions”.
C:This check is suited to “Clear a stale 802.1X authorized session during diagnostics” when trying to force reauthentication after the endpoint or authorization rule has changed, not to verify “Use RADIUS change of authorization where supported” at the data hall. Checking “Use RADIUS change of authorization where supported” at the data hall requires evidence of its own mechanism: a RADIUS CoA message can alter an established authorization in a supported policy workflow; that is not the outcome measured by “Clear a stale 802.1X authorized session during diagnostics”.
E:The proposed check concerns “Troubleshoot an 802.1X supplicant that never starts” rather than “Use RADIUS change of authorization where supported”: an 802.1X-capable client must participate in EAPOL before the server can approve its credentials. For “Use RADIUS change of authorization where supported” on two distribution switches, a better test would be to inspect the CoA transaction and subsequent session policy or VLAN state, which targets change an existing session's access decision without waiting for ordinary reconnection rather than the alternative diagnostic “Troubleshoot an 802.1X supplicant that never starts”.
Question 486
At the warehouse, a technician is choosing between several switching features to record network access session starts and stops outside the switch. Which one belongs in the implementation plan?
- Enable RADIUS accounting for access sessions
- Use static MAC security for a fixed appliance
- Configure 802.1X for a user-facing port
- Use EAP-PEAP where the RADIUS design requires a protected inner method
Explanation
Correct Answer
A:The critical distinction is that accounting sends session records to a collector distinct from the basic allow-or-deny authentication result. The operator can test this claim by the specific check: compare RADIUS accounting entries with the switch's active sessions.
Incorrect Answers
B:Compared with the requested “Enable RADIUS accounting for access sessions” at the warehouse, this would allow a particular known device address on a controlled interface instead: a configured MAC identity restricts layer-2 admission or learning to designated devices. At the warehouse, the operational proof would instead be to compare RADIUS accounting entries with the switch's active sessions, whereas “Use static MAC security for a fixed appliance” is validated by a different test: check the secure MAC table and the source address of blocked frames.
C:For the warehouse, “Configure 802.1X for a user-facing port” is a different type of control from “Enable RADIUS accounting for access sessions”: 802.1X uses EAP between the endpoint and the switch authenticator, with RADIUS decision-making upstream. Unlike the requested feature, that setting addresses the need to authenticate a standards-compliant supplicant before admitting it to the access network, not the objective to record network access session starts and stops outside the switch.
D:Compared with the requested “Enable RADIUS accounting for access sessions” at the warehouse, 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 warehouse, the operational proof would instead be to compare RADIUS accounting entries with the switch's active sessions, 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.
Question 487
A colleague asks about the effect of “Enable RADIUS accounting for access sessions” on a carefully segmented Layer 2 network. Which behavior best characterizes that feature?
- An 802.1X-capable client must participate in EAPOL before the server can approve its credentials
- Port-based access control gates the entire port, which matters if multiple devices share the same physical connection
- Accounting sends session records to a collector distinct from the basic allow-or-deny authentication result
- PEAP establishes a protected authentication exchange; it remains distinct from MAB and switch MAC limits
Explanation
Correct Answer
C:That setting is appropriate here because the configured operation is meant to record network access session starts and stops outside the switch. The most relevant validation is to compare RADIUS accounting entries with the switch's active sessions for the equipment at the headquarters.
Incorrect Answers
A:That behavior applies when engineers “Troubleshoot an 802.1X supplicant that never starts”; the different operation “Enable RADIUS accounting for access sessions” is intended to record network access session starts and stops outside the switch. That different feature is verified by capture EAPOL frames on the access port and inspect endpoint supplicant state; for “Enable RADIUS accounting for access sessions” on a carefully segmented Layer 2 network, the relevant evidence is to compare RADIUS accounting entries with the switch's active sessions.
B:This outcome would be relevant to “Use port-based 802.1X authorization” at the headquarters, not the task “Enable RADIUS accounting for access sessions”; the other task is to treat the interface as authorized after a permitted port-level authentication succeeds. The action “Enable RADIUS accounting for access sessions” targets a different result: accounting sends session records to a collector distinct from the basic allow-or-deny authentication result; the proposed alternative would instead be checked by inspect authorized port state and evaluate behavior of hosts behind that port.
D:That behavior applies when engineers “Use EAP-PEAP where the RADIUS design requires a protected inner method”; the different operation “Enable RADIUS accounting for access sessions” is intended to record network access session starts and stops outside the switch. That different feature is verified by inspect client EAP type and server-side PEAP negotiation events; for “Enable RADIUS accounting for access sessions” on a carefully segmented Layer 2 network, the relevant evidence is to compare RADIUS accounting entries with the switch's active sessions.
Question 488
An auditor wants operational evidence for the switch action “Enable RADIUS accounting for access sessions” at the hospital wing. Which check is relevant?
- Inspect the CoA transaction and subsequent session policy or VLAN state
- Check the MAC-based RADIUS transaction and device session authorization
- Capture EAPOL frames on the access port and inspect endpoint supplicant state
- Compare RADIUS accounting entries with the switch's active sessions
Explanation
Correct Answer
D:This is the precise control because accounting sends session records to a collector distinct from the basic allow-or-deny authentication result. Directly measuring that result demonstrates whether the step to record network access session starts and stops outside the switch succeeded on a central switching stack.
Incorrect Answers
A:The proposed check concerns “Use RADIUS change of authorization where supported” rather than “Enable RADIUS accounting for access sessions”: a RADIUS CoA message can alter an established authorization in a supported policy workflow. For “Enable RADIUS accounting for access sessions” on a central switching stack, a better test would be to compare RADIUS accounting entries with the switch's active sessions, which targets record network access session starts and stops outside the switch rather than the alternative diagnostic “Use RADIUS change of authorization where supported”.
B:This check is suited to “Enable MAC authentication bypass for a legacy camera” when trying to admit a non-802.1X device through a controlled RADIUS identity check, not to verify “Enable RADIUS accounting for access sessions” at the hospital wing. Checking “Enable RADIUS accounting for access sessions” at the hospital wing requires evidence of its own mechanism: accounting sends session records to a collector distinct from the basic allow-or-deny authentication result; that is not the outcome measured by “Enable MAC authentication bypass for a legacy camera”.
C: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 RADIUS accounting for access sessions” at the hospital wing. Checking “Enable RADIUS accounting for access sessions” at the hospital wing requires evidence of its own mechanism: accounting sends session records to a collector distinct from the basic allow-or-deny authentication result; that is not the outcome measured by “Troubleshoot an 802.1X supplicant that never starts”.
Question 489
The accepted design for the training center requires the ability to maintain a reusable set of network admission controls on selected access ports. Which switch feature is the closest fit?
- Configure a reachable RADIUS authentication server
- Use EAP-TLS where device certificates are deployed
- Configure MAC address learning limits
- Apply a port security profile to a FortiSwitch interface
- Use a guest or unauthorized VLAN policy where supported
Explanation
Correct Answer
D:The implementation works because a port policy binds appropriate authentication and security settings to an interface. This distinction is material to the training center, where the stated goal is to maintain a reusable set of network admission controls on selected access ports.
Incorrect Answers
A:Compared with the requested “Apply a port security profile to a FortiSwitch interface” at the training center, 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 training center, the operational proof would instead be to inspect applied port policy identity and active session state, whereas “Configure a reachable RADIUS authentication server” is validated by a different test: test RADIUS reachability, shared-secret agreement and server response time.
B:For the training center, “Use EAP-TLS where device certificates are deployed” is a different type of control from “Apply a port security profile to a FortiSwitch interface”: EAP-TLS uses certificate validation in the authentication flow rather than a simple MAC-only identity. Unlike the requested feature, that setting addresses the need to authenticate compliant devices with a certificate-based EAP exchange, not the objective to maintain a reusable set of network admission controls on selected access ports.
C:Compared with the requested “Apply a port security profile to a FortiSwitch interface” at the training center, this would restrict how many endpoint MAC addresses an access interface can learn instead: MAC learning limits cap layer-2 learned identities rather than validating EAP or DHCP leases. At the training center, the operational proof would instead be to inspect applied port policy identity and active session state, whereas “Configure MAC address learning limits” is validated by a different test: check learned-MAC counts and violations against the configured limit.
E:Compared with the requested “Apply a port security profile to a FortiSwitch interface” at the training center, 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 training center, the operational proof would instead be to inspect applied port policy identity and active session state, 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.
Question 490
When engineers apply a port security profile to a FortiSwitch interface at the lab, which forwarding, security, management or diagnostic outcome follows from that action?
- MAC-based mode maintains per-device authorization decisions instead of granting the entire port one common state
- A port policy binds appropriate authentication and security settings to an interface
- TTLS wraps inner authentication within a protected tunnel and requires matching endpoint/server settings
- An unauthorized or guest network can provide limited connectivity instead of normal production access
Explanation
Correct Answer
B:Given the described goal, the configured operation is meant to maintain a reusable set of network admission controls on selected access ports. The most relevant validation is to inspect applied port policy identity and active session state for the equipment at the lab.
Incorrect Answers
A:That behavior applies when engineers “Use MAC-based 802.1X access sessions”; the different operation “Apply a port security profile to a FortiSwitch interface” is intended to maintain a reusable set of network admission controls on selected access ports. That different feature is verified by inspect individual authenticated MAC session entries on the interface; for “Apply a port security profile to a FortiSwitch interface” on an access switch in routine maintenance, the relevant evidence is to inspect applied port policy identity and active session state.
C:This outcome would be relevant to “Use EAP-TTLS for compatible tunnel-based access authentication” at the lab, not the task “Apply a port security profile to a FortiSwitch interface”; the other task is to provide a tunneled credential exchange supported by the configured RADIUS server. The action “Apply a port security profile to a FortiSwitch interface” targets a different result: a port policy binds appropriate authentication and security settings to an interface; the proposed alternative would instead be checked by inspect the negotiated EAP type in the access attempt.
D:That behavior applies when engineers “Use a guest or unauthorized VLAN policy where supported”; the different operation “Apply a port security profile to a FortiSwitch interface” is intended to maintain a reusable set of network admission controls on selected access ports. That different feature is verified by inspect the failed authentication state and assigned VLAN on the endpoint session; for “Apply a port security profile to a FortiSwitch interface” on an access switch in routine maintenance, the relevant evidence is to inspect applied port policy identity and active session state.