Fortinet NSE5_FSW_AD-7.6 (Fortinet NSE 5 - FortiSwitch 7.6 Administrator) Practice Test 47

Question 460

A change record for a switch linked to a FortiGate running FortiOS 7.6 states “Configure a reachable RADIUS authentication server.” Which description correctly explains what this will accomplish?

  1. MAC learning limits cap layer-2 learned identities rather than validating EAP or DHCP leases
  2. MAB needs a server-side record or lookup logic that accepts the enrolled MAC identities
  3. Session clearing removes prior authorization state so that a fresh EAP/RADIUS exchange can be assessed
  4. PEAP establishes a protected authentication exchange; it remains distinct from MAB and switch MAC limits
  5. The switch forwards authentication exchanges to a configured RADIUS service rather than validating enterprise credentials by itself

Explanation

Correct Answer

E:

The relevant mechanism is: the configured operation is meant to provide external identity validation for network access control. The most relevant validation is to test RADIUS reachability, shared-secret agreement and server response time for the equipment at the conference venue.

Incorrect Answers

A:

This outcome would be relevant to “Configure MAC address learning limits” at the conference venue, not the task “Configure a reachable RADIUS authentication server”; the other task is to restrict how many endpoint MAC addresses an access interface can learn. The action “Configure a reachable RADIUS authentication server” targets a different result: the switch forwards authentication exchanges to a configured RADIUS service rather than validating enterprise credentials by itself; the proposed alternative would instead be checked by check learned-MAC counts and violations against the configured limit.

B:

That behavior applies when engineers “Provision device MAC identities in RADIUS for MAB”; the different operation “Configure a reachable RADIUS authentication server” is intended to provide external identity validation for network access control. That different feature is verified by search RADIUS logs for the submitted hardware address and expected accept decision; for “Configure a reachable RADIUS authentication server” on a switch linked to a FortiGate running FortiOS 7.6, the relevant evidence is to test RADIUS reachability, shared-secret agreement and server response time.

C:

That behavior applies when engineers “Clear a stale 802.1X authorized session during diagnostics”; the different operation “Configure a reachable RADIUS authentication server” is intended to provide external identity validation for network access control. That different feature is verified by inspect the session table before and after clearing and review the new authentication exchange; for “Configure a reachable RADIUS authentication server” on a switch linked to a FortiGate running FortiOS 7.6, the relevant evidence is to test RADIUS reachability, shared-secret agreement and server response time.

D:

That behavior applies when engineers “Use EAP-PEAP where the RADIUS design requires a protected inner method”; the different operation “Configure a reachable RADIUS authentication server” is intended to provide external identity validation for network access control. That different feature is verified by inspect client EAP type and server-side PEAP negotiation events; for “Configure a reachable RADIUS authentication server” on a switch linked to a FortiGate running FortiOS 7.6, the relevant evidence is to test RADIUS reachability, shared-secret agreement and server response time.

Question 461

A post-change review at the campus must validate the implementation of “Configure a reachable RADIUS authentication server.” What should the reviewer inspect first?

  1. Test RADIUS reachability, shared-secret agreement and server response time
  2. Inspect the failed authentication state and assigned VLAN on the endpoint session
  3. Inspect client EAP type and server-side PEAP negotiation events
  4. Inspect authorized port state and evaluate behavior of hosts behind that port

Explanation

Correct Answer

A:

This approach fits because the switch forwards authentication exchanges to a configured RADIUS service rather than validating enterprise credentials by itself. Directly measuring that result demonstrates whether the step to provide external identity validation for network access control succeeded on a switch serving a high-density endpoint area.

Incorrect Answers

B:

This check is suited to “Use a guest or unauthorized VLAN policy where supported” when trying to separate endpoints that have not completed approved network authentication, not to verify “Configure a reachable RADIUS authentication server” at the campus. Checking “Configure a reachable RADIUS authentication server” at the campus requires evidence of its own mechanism: the switch forwards authentication exchanges to a configured RADIUS service rather than validating enterprise credentials by itself; that is not the outcome measured by “Use a guest or unauthorized VLAN policy where supported”.

C:

This check is suited to “Use EAP-PEAP where the RADIUS design requires a protected inner method” when trying to support a tunneled EAP authentication approach for compatible endpoints, not to verify “Configure a reachable RADIUS authentication server” at the campus. Checking “Configure a reachable RADIUS authentication server” at the campus requires evidence of its own mechanism: the switch forwards authentication exchanges to a configured RADIUS service rather than validating enterprise credentials by itself; that is not the outcome measured by “Use EAP-PEAP where the RADIUS design requires a protected inner method”.

D:

The proposed check concerns “Use port-based 802.1X authorization” rather than “Configure a reachable RADIUS authentication server”: port-based access control gates the entire port, which matters if multiple devices share the same physical connection. For “Configure a reachable RADIUS authentication server” on a switch serving a high-density endpoint area, a better test would be to test RADIUS reachability, shared-secret agreement and server response time, which targets provide external identity validation for network access control rather than the alternative diagnostic “Use port-based 802.1X authorization”.

Question 462

A switch rollout in the remote depot will be approved only if it can treat the interface as authorized after a permitted port-level authentication succeeds. Which administrative action meets this acceptance criterion?

  1. Use EAP-TLS where device certificates are deployed
  2. Use static MAC security for a fixed appliance
  3. Use port-based 802.1X authorization
  4. Configure 802.1X for a user-facing port

Explanation

Correct Answer

C:

The critical distinction is that port-based access control gates the entire port, which matters if multiple devices share the same physical connection. The operator can test this claim by the specific check: inspect authorized port state and evaluate behavior of hosts behind that port.

Incorrect Answers

A:

For the remote depot, “Use EAP-TLS where device certificates are deployed” is a different type of control from “Use port-based 802.1X authorization”: 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 treat the interface as authorized after a permitted port-level authentication succeeds.

B:

Compared with the requested “Use port-based 802.1X authorization” at the remote depot, 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 remote depot, the operational proof would instead be to inspect authorized port state and evaluate behavior of hosts behind that port, 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.

D:

Compared with the requested “Use port-based 802.1X authorization” at the remote depot, 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 remote depot, the operational proof would instead be to inspect authorized port state and evaluate behavior of hosts behind that port, 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 463

An operations log records this activity at the branch office: use port-based 802.1X authorization. Which result is specifically attributable to that action?

  1. 802.1X uses EAP between the endpoint and the switch authenticator, with RADIUS decision-making upstream
  2. Port-based access control gates the entire port, which matters if multiple devices share the same physical connection
  3. MAC-based mode maintains per-device authorization decisions instead of granting the entire port one common state
  4. TTLS wraps inner authentication within a protected tunnel and requires matching endpoint/server settings
  5. A configured MAC identity restricts layer-2 admission or learning to designated devices

Explanation

Correct Answer

B:

That setting is appropriate here because the configured operation is meant to treat the interface as authorized after a permitted port-level authentication succeeds. The most relevant validation is to inspect authorized port state and evaluate behavior of hosts behind that port for the equipment at the branch office.

Incorrect Answers

A:

That behavior applies when engineers “Configure 802.1X for a user-facing port”; the different operation “Use port-based 802.1X authorization” is intended to treat the interface as authorized after a permitted port-level authentication succeeds. That different feature is verified by inspect the 802.1X session state and RADIUS accept or reject result; for “Use port-based 802.1X authorization” on a remote FortiSwitch installation, the relevant evidence is to inspect authorized port state and evaluate behavior of hosts behind that port.

C:

That behavior applies when engineers “Use MAC-based 802.1X access sessions”; the different operation “Use port-based 802.1X authorization” is intended to treat the interface as authorized after a permitted port-level authentication succeeds. That different feature is verified by inspect individual authenticated MAC session entries on the interface; for “Use port-based 802.1X authorization” on a remote FortiSwitch installation, the relevant evidence is to inspect authorized port state and evaluate behavior of hosts behind that port.

D:

This outcome would be relevant to “Use EAP-TTLS for compatible tunnel-based access authentication” at the branch office, not the task “Use port-based 802.1X authorization”; the other task is to provide a tunneled credential exchange supported by the configured RADIUS server. The action “Use port-based 802.1X authorization” targets a different result: port-based access control gates the entire port, which matters if multiple devices share the same physical connection; the proposed alternative would instead be checked by inspect the negotiated EAP type in the access attempt.

E:

That behavior applies when engineers “Use static MAC security for a fixed appliance”; the different operation “Use port-based 802.1X authorization” is intended to treat the interface as authorized after a permitted port-level authentication succeeds. That different feature is verified by check the secure MAC table and the source address of blocked frames; for “Use port-based 802.1X authorization” on a remote FortiSwitch installation, the relevant evidence is to inspect authorized port state and evaluate behavior of hosts behind that port.

Question 464

An auditor wants operational evidence for the switch action “Use port-based 802.1X authorization” at the factory. Which check is relevant?

  1. Inspect individual authenticated MAC session entries on the interface
  2. Compare RADIUS accounting entries with the switch's active sessions
  3. Inspect authorized port state and evaluate behavior of hosts behind that port
  4. Capture EAPOL frames on the access port and inspect endpoint supplicant state

Explanation

Correct Answer

C:

This is the precise control because port-based access control gates the entire port, which matters if multiple devices share the same physical connection. Directly measuring that result demonstrates whether the step to treat the interface as authorized after a permitted port-level authentication succeeds succeeded on an endpoint-facing FortiSwitch port.

Incorrect Answers

A:

This check is suited to “Use MAC-based 802.1X access sessions” when trying to control separate endpoint identities on one shared physical port, not to verify “Use port-based 802.1X authorization” at the factory. Checking “Use port-based 802.1X authorization” at the factory requires evidence of its own mechanism: port-based access control gates the entire port, which matters if multiple devices share the same physical connection; that is not the outcome measured by “Use MAC-based 802.1X access sessions”.

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 port-based 802.1X authorization” at the factory. Checking “Use port-based 802.1X authorization” at the factory requires evidence of its own mechanism: port-based access control gates the entire port, which matters if multiple devices share the same physical connection; that is not the outcome measured by “Enable RADIUS accounting for access sessions”.

D:

The proposed check concerns “Troubleshoot an 802.1X supplicant that never starts” rather than “Use port-based 802.1X authorization”: an 802.1X-capable client must participate in EAPOL before the server can approve its credentials. For “Use port-based 802.1X authorization” on an endpoint-facing FortiSwitch port, a better test would be to inspect authorized port state and evaluate behavior of hosts behind that port, which targets treat the interface as authorized after a permitted port-level authentication succeeds rather than the alternative diagnostic “Troubleshoot an 802.1X supplicant that never starts”.

Question 465

An administrator responsible for a standalone FortiSwitch appliance in the research building must control separate endpoint identities on one shared physical port. Which configuration best matches that precise goal?

  1. Configure 802.1X for a user-facing port
  2. Use static MAC security for a fixed appliance
  3. Use MAC-based 802.1X access sessions
  4. Use EAP-TTLS for compatible tunnel-based access authentication

Explanation

Correct Answer

C:

The implementation works because MAC-based mode maintains per-device authorization decisions instead of granting the entire port one common state. This distinction is material to the research building, where the stated goal is to control separate endpoint identities on one shared physical port.

Incorrect Answers

A:

For the research building, “Configure 802.1X for a user-facing port” is a different type of control from “Use MAC-based 802.1X 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 control separate endpoint identities on one shared physical port.

B:

Compared with the requested “Use MAC-based 802.1X access sessions” at the research building, 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 research building, the operational proof would instead be to inspect individual authenticated MAC session entries on the interface, 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.

D:

Compared with the requested “Use MAC-based 802.1X access sessions” at the research building, this would provide a tunneled credential exchange supported by the configured RADIUS server instead: TTLS wraps inner authentication within a protected tunnel and requires matching endpoint/server settings. At the research building, the operational proof would instead be to inspect individual authenticated MAC session entries on the interface, whereas “Use EAP-TTLS for compatible tunnel-based access authentication” is validated by a different test: inspect the negotiated EAP type in the access attempt.

Question 466

A change record for a newly commissioned floor switch states “Use MAC-based 802.1X access sessions.” Which description correctly explains what this will accomplish?

  1. An 802.1X-capable client must participate in EAPOL before the server can approve its credentials
  2. TTLS wraps inner authentication within a protected tunnel and requires matching endpoint/server settings
  3. MAC-based mode maintains per-device authorization decisions instead of granting the entire port one common state
  4. Port-based access control gates the entire port, which matters if multiple devices share the same physical connection

Explanation

Correct Answer

C:

Given the described goal, the configured operation is meant to control separate endpoint identities on one shared physical port. The most relevant validation is to inspect individual authenticated MAC session entries on the interface for the equipment at the clinic.

Incorrect Answers

A:

That behavior applies when engineers “Troubleshoot an 802.1X supplicant that never starts”; the different operation “Use MAC-based 802.1X access sessions” is intended to control separate endpoint identities on one shared physical port. That different feature is verified by capture EAPOL frames on the access port and inspect endpoint supplicant state; for “Use MAC-based 802.1X access sessions” on a newly commissioned floor switch, the relevant evidence is to inspect individual authenticated MAC session entries on the interface.

B:

That behavior applies when engineers “Use EAP-TTLS for compatible tunnel-based access authentication”; the different operation “Use MAC-based 802.1X access sessions” is intended to control separate endpoint identities on one shared physical port. That different feature is verified by inspect the negotiated EAP type in the access attempt; for “Use MAC-based 802.1X access sessions” on a newly commissioned floor switch, the relevant evidence is to inspect individual authenticated MAC session entries on the interface.

D:

This outcome would be relevant to “Use port-based 802.1X authorization” at the clinic, not the task “Use MAC-based 802.1X access sessions”; the other task is to treat the interface as authorized after a permitted port-level authentication succeeds. The action “Use MAC-based 802.1X access sessions” targets a different result: MAC-based mode maintains per-device authorization decisions instead of granting the entire port one common state; the proposed alternative would instead be checked by inspect authorized port state and evaluate behavior of hosts behind that port.

Question 467

A technician says “Use MAC-based 802.1X access sessions” has solved the issue at the data hall. Which diagnostic step would substantiate that claim?

  1. Compare RADIUS accounting entries with the switch's active sessions
  2. Inspect authorized port state and evaluate behavior of hosts behind that port
  3. Capture EAPOL frames on the access port and inspect endpoint supplicant state
  4. Inspect individual authenticated MAC session entries on the interface
  5. Search RADIUS logs for the submitted hardware address and expected accept decision

Explanation

Correct Answer

D:

The switch behavior that matters is: MAC-based mode maintains per-device authorization decisions instead of granting the entire port one common state. Directly measuring that result demonstrates whether the step to control separate endpoint identities on one shared physical port succeeded on a local switch administering branch clients.

Incorrect Answers

A:

The proposed check concerns “Enable RADIUS accounting for access sessions” rather than “Use MAC-based 802.1X access sessions”: accounting sends session records to a collector distinct from the basic allow-or-deny authentication result. For “Use MAC-based 802.1X access sessions” on a local switch administering branch clients, a better test would be to inspect individual authenticated MAC session entries on the interface, which targets control separate endpoint identities on one shared physical port rather than the alternative diagnostic “Enable RADIUS accounting for access sessions”.

B:

The proposed check concerns “Use port-based 802.1X authorization” rather than “Use MAC-based 802.1X access sessions”: port-based access control gates the entire port, which matters if multiple devices share the same physical connection. For “Use MAC-based 802.1X access sessions” on a local switch administering branch clients, a better test would be to inspect individual authenticated MAC session entries on the interface, which targets control separate endpoint identities on one shared physical port rather than the alternative diagnostic “Use port-based 802.1X authorization”.

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 “Use MAC-based 802.1X access sessions” at the data hall. Checking “Use MAC-based 802.1X access sessions” at the data hall requires evidence of its own mechanism: MAC-based mode maintains per-device authorization decisions instead of granting the entire port one common state; that is not the outcome measured by “Troubleshoot an 802.1X supplicant that never starts”.

E:

This check is suited to “Provision device MAC identities in RADIUS for MAB” when trying to make network devices without certificates recognizable to the access policy, not to verify “Use MAC-based 802.1X access sessions” at the data hall. Checking “Use MAC-based 802.1X access sessions” at the data hall requires evidence of its own mechanism: MAC-based mode maintains per-device authorization decisions instead of granting the entire port one common state; that is not the outcome measured by “Provision device MAC identities in RADIUS for MAB”.

Question 468

A peer review of the development floor asks how the design will admit a non-802.1X device through a controlled RADIUS identity check. Which FortiSwitch technique is the correct response?

  1. Configure 802.1X for a user-facing port
  2. Apply a port security profile to a FortiSwitch interface
  3. Enable MAC authentication bypass for a legacy camera
  4. Use EAP-TLS where device certificates are deployed

Explanation

Correct Answer

C:

At this network boundary, MAB can submit a device MAC address as authentication credentials when no EAP supplicant is available. The operator can test this claim by the specific check: check the MAC-based RADIUS transaction and device session authorization.

Incorrect Answers

A:

Compared with the requested “Enable MAC authentication bypass for a legacy camera” 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 check the MAC-based RADIUS transaction and device session authorization, 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.

B:

For the development floor, “Apply a port security profile to a FortiSwitch interface” is a different type of control from “Enable MAC authentication bypass for a legacy camera”: 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 admit a non-802.1X device through a controlled RADIUS identity check.

D:

Compared with the requested “Enable MAC authentication bypass for a legacy camera” at the development floor, 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 development floor, the operational proof would instead be to check the MAC-based RADIUS transaction and device session authorization, whereas “Use EAP-TLS where device certificates are deployed” is validated by a different test: examine EAP-TLS negotiation and server certificate trust results.

Question 469

An operations log records this activity at the conference venue: enable MAC authentication bypass for a legacy camera. Which result is specifically attributable to that action?

  1. MAB can submit a device MAC address as authentication credentials when no EAP supplicant is available
  2. TTLS wraps inner authentication within a protected tunnel and requires matching endpoint/server settings
  3. A configured MAC identity restricts layer-2 admission or learning to designated devices
  4. 802.1X uses EAP between the endpoint and the switch authenticator, with RADIUS decision-making upstream

Explanation

Correct Answer

A:

In this deployment, the configured operation is meant to admit a non-802.1X device through a controlled RADIUS identity check. The most relevant validation is to check the MAC-based RADIUS transaction and device session authorization for the equipment at the conference venue.

Incorrect Answers

B:

That behavior applies when engineers “Use EAP-TTLS for compatible tunnel-based access authentication”; the different operation “Enable MAC authentication bypass for a legacy camera” is intended to admit a non-802.1X device through a controlled RADIUS identity check. That different feature is verified by inspect the negotiated EAP type in the access attempt; for “Enable MAC authentication bypass for a legacy camera” on a managed switch running FortiSwitchOS 7.6, the relevant evidence is to check the MAC-based RADIUS transaction and device session authorization.

C:

This outcome would be relevant to “Use static MAC security for a fixed appliance” at the conference venue, not the task “Enable MAC authentication bypass for a legacy camera”; the other task is to allow a particular known device address on a controlled interface. The action “Enable MAC authentication bypass for a legacy camera” targets a different result: MAB can submit a device MAC address as authentication credentials when no EAP supplicant is available; 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 “Configure 802.1X for a user-facing port”; the different operation “Enable MAC authentication bypass for a legacy camera” is intended to admit a non-802.1X device through a controlled RADIUS identity check. That different feature is verified by inspect the 802.1X session state and RADIUS accept or reject result; for “Enable MAC authentication bypass for a legacy camera” on a managed switch running FortiSwitchOS 7.6, the relevant evidence is to check the MAC-based RADIUS transaction and device session authorization.

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?

  1. Inspect the negotiated EAP type in the access attempt
  2. Capture EAPOL frames on the access port and inspect endpoint supplicant state
  3. Check the MAC-based RADIUS transaction and device session authorization
  4. 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”.

Fortinet NSE 5 - FortiSwitch 7.6 Administrator (NSE5_FSW_AD-7.6) Practice Tests