NSE7_LED-7.0 Fortinet NSE 7 - LAN Edge 7.0 Questions and Answers

Based on LAN Edge 7.0 Study Guide page 217 When FortiGate discovers the first switch, it automatically adds to its configuration some settings that are default, quarantine, rspan, voice, video, onboarding, and nac_segment

According to the FortiGate Administration Guide, “The Group Name is the name of the LDAP group that you want to use for authentication. The name must match exactly the name of the LDAP group on the LDAP server.” Therefore, option A is true because it will set the Group Name to match the LDAP group that contains only the student user. Option B is false because changing the Name will not affect the authentication process, as it is only a local identifier for the user group on FortiGate. Option C is false because setting the Group Name to Domain Users will include all users in the domain, not just the student user. Option D is false because changing the Type to FSSO will require a different configuration method and will not solve the problem.

According to the FortiGate Administration Guide, “To use an external captive portal, you must configure a user group that uses the external captive portal as the authentication method and apply it to a firewall policy.” Therefore, option C is true because it will allow the wireless users to be redirected to the external captive portal URL when they try to access the Internet. Option A is false because disabling the user group from the SSID configuration will prevent the wireless users from being authenticated by the FortiGate device. Option B is false because enabling the captive-portal-exempt option in the firewall policy will bypass the captive portal authentication for the wireless users, which is not the desired outcome. Option D is false because including the wireless client subnet range in the Exempt Source section will also bypass the captive portal authentication for the wireless users, which is not the desired outcome.

Based on the provided exhibit and Fortinet's official documentation for FortiOS and FortiSwitch, particularly the NSE 7 - LAN Edge 7.0 materials and the FortiSwitch Administration Guide, the behavior of the FortiSwitch security policy can be analyzed as follows:

The exhibit shows a FortiSwitch security policy configured with the following key settings:

Security mode:Port-based

User groups:FAC-Lab-User (a wired user group)

Guest VLAN:Set to "onboarding"

Guest authentication delay:30 seconds

Authentication fail VLAN:Set to "quarantine"

MAC authentication bypass:Disabled

EAP pass-through:Enabled

Override RADIUS timeout:Disabled

Analysis of the Scenario:

The question specifies that a device that does not support 802.1X authentication is connected to a port using this Port-Security security policy. Since the device does not support 802.1X, it cannot perform the standard 802.1X authentication process. The FortiSwitch will then evaluate alternative configurations to determine the port's behavior:

Guest VLAN Configuration:The Guest VLAN is set to "onboarding." According to Fortinet documentation, when a device fails to authenticate via 802.1X (e.g., due to lack of support), and a Guest VLAN is configured, the FortiSwitch assigns the port to the specified Guest VLAN after the guest authentication delay period (30 seconds in this case). The "onboarding" VLAN is typically used to place unauthenticated devices in a restricted network segment where they can be redirected to a captive portal or other onboarding process.

Authentication Fail VLAN:The Authentication Fail VLAN is set to "quarantine," which would apply if authentication fails after an attempt. However, since the device does not support 802.1X, no authentication attempt is made, and this setting does not trigger unless an authentication process is initiated and fails.

MAC Authentication Bypass:This option is disabled, so the FortiSwitch will not attempt to authenticate the device using its MAC address as the username and password.

EAP Pass-Through:This is enabled, allowing EAP frames to pass through to an external RADIUS server, but it is irrelevant here since the device does not support 802.1X.

Port Shutdown:There is no indication in the configuration or Fortinet documentation that the port will be shut down for a device that does not support 802.1X when a Guest VLAN is configured.

Conclusion:

When a device does not support 802.1X authentication and the security policy is set to Port-based with a Guest VLAN configured (set to "onboarding"), the FortiSwitch assigns the port to the Guest VLAN (onboarding) after the guest authentication delay (30 seconds). This behavior is consistent with Fortinet's design for handling unauthenticated devices in a secure network environment, as outlined in the FortiSwitch Port Security and VLAN assignment sections of the official documentation.

Why not the other options?

B. FortiSwitch shuts down the port:This action would occur only if the port security policy is configured to shut down the port upon authentication failure or violation (e.g., with a limit on MAC addresses), which is not indicated in this configuration.

C. FortiSwitch assigns the port to the quarantine VLAN:The quarantine VLAN is configured as the Authentication Fail VLAN, which applies only after an unsuccessful authentication attempt. Since no 802.1X authentication is attempted due to the device's lack of support, this does not apply.

D. FortiSwitch authenticates the device using the device MAC address as username and password:This requires MAC authentication bypass to be enabled, which it is not in this configuration.

Source Verification:

The answer is verified through the FortiSwitch Administration Guide (FortiOS 7.0) and NSE 7 - LAN Edge 7.0 training materials, specifically the sections on Port Security, 802.1X, and VLAN assignment for unauthenticated devices.

Fortinet’s official documentation, including the FortiOS Handbook and NSE 7 training materials, provides detailed guidance on troubleshooting RADIUS authentication issues. The three tools listed below are explicitly supported for diagnosing RADIUS-related problems in FortiOS:

B. You can use the diagnose test authserver radius command to verify RADIUS server configuration, user credentials, and user group membership.This command is a well-documented troubleshooting tool in the FortiOS CLI Reference and Technical Documentation. It allows administrators to manually test RADIUS authentication by specifying the RADIUS server, username, and password. The output provides details on whether the authentication succeeds or fails, along with information about group membership and server reachability. For example:

bash

CollapseWrapCopy

diagnose test authserver radius

This is a critical tool for verifying the RADIUS server's configuration and user authentication flow.

D. You can enable debug for the fnbamd process to view RADIUS authentication details.The fnbamd process (FortiNet Authentication Daemon) handles non-local authentication protocols like RADIUS and LDAP in FortiOS. Enabling debug for this process provides real-time logs of the authentication exchange between the FortiGate and the RADIUS server. This is officially recommended in Fortinet’s troubleshooting guides for advanced diagnostics. The command sequence is:

bash

CollapseWrapCopy

diagnose debug application fnbamd -1

diagnose debug enable

After testing, you can disable debugging with diagnose debug disable. This tool is invaluable for identifying issues such as misconfigured shared secrets, timeouts, or attribute mismatches.

E. You can use the diagnose test application radiusd command to verify the RADIUS server configuration, user credentials, and user group membership.The radiusd process relates to the RADIUS daemon on the FortiGate, and this diagnostic command tests the RADIUS server’s operational status and authentication functionality. While less commonly highlighted than diagnose test authserver radius, it is referenced in Fortinet’s CLI documentation for deeper troubleshooting of the RADIUS service itself. It provides detailed output about the server’s response and can help isolate issues specific to the RADIUS protocol implementation.

Why not A and C?

A. You can enable debug for the fssod process to view RADIUS authentication details.The fssod process relates to FortiSSO (Single Sign-On) and is primarily used for FSSO-based authentication, not direct RADIUS troubleshooting. While it may log some authentication-related events in specific SSO scenarios, it is not a standard tool for RADIUS diagnostics according to Fortinet’s official documentation. Thus, it is not a correct choice here.

C. You can check the Firewall Users widget to view the list of active RADIUS users.While the Firewall Users widget (available in the FortiOS GUI underUser & Authentication > Firewall Users) shows a list of authenticated users, it is a monitoring tool, not a troubleshooting tool. It does not provide diagnostic details about RADIUS authentication failures or server issues, making it insufficient for this purpose per Fortinet’s troubleshooting methodology.

Source Verification

The answers are derived from official Fortinet resources, including:

FortiOS 7.0 CLI Reference(diagnose commands section)

FortiOS Handbook: Authentication(RADIUS troubleshooting section)

NSE 7 - LAN Edge 7.0 training materials (authentication diagnostics module)

These tools (B, D, E) align with Fortinet’s recommended practices for diagnosing RADIUS authentication issues effectively.

https://docs.fortinet.com/document/fortimanager/7.6.1/administration-guide/155479/zero-touch-and-low-touch-provisioning

According to the exhibit, the User-Name attribute in the RADIUS Access-Request packet contains the client MAC address of 00:0c:29:6a:2b:3d. This indicates that FortiSwitch is authenticating the client using MAC authentication bypass (MAB), which is a method of authenticating devices that do not support 802.1X by using their MAC address as the username and password. Therefore, option B is true because it explains why the User-Name attribute contains the client MAC address. Option A is false because AD machine authentication uses a computer account name and password, not a MAC address. Option C is false because userauthentication uses a user name and password, not a MAC address. Option D is false because FortiSwitch is sending a RADIUS Access-Request message to FortiAuthenticator, not a RADIUS accounting message.

According to the FortiSwitch Administration Guide, “If a device does not support 802.1X authentication, you can configure the switch to assign the device to an onboarding VLAN. The onboarding VLAN is a separate VLAN that you can use to provide limited network access to non-802.1X devices.” Therefore, option C is true because it describes the behavior of FortiSwitch when the security profile shown in the exhibit is assigned to all ports. Option A is false because FortiSwitch can authenticate multiple devices connected to the same port using MAC-based or MAB-EAP modes. Option B is false because FortiSwitch will not try to authenticate non-802.1X devices using the device MAC address as the username and password, but rather use MAC authentication bypass (MAB) or EAP pass-through modes. Option D is false because all EAP messages will be terminated on FortiGate, not FortiSwitch, when using 802.1X authentication.

According to the FortiSwitch Administration Guide, “MAC-based 802.1X security mode allows you to authenticate each device connected to a port using its MAC address as the username and password.” Therefore, option B is true because it describes the MAC-based 802.1X security mode available on FortiSwitch. Option D is also true because FortiSwitch can grant different access levels to each device connected to the port based on the user group and security policy assigned to them. Option A is false because FortiSwitch does not authenticate a single device and open the port to other devices connected to the port, but rather authenticates each device individually. Option C is false because MAC-based 802.1X security mode can be used in conjunction with MAC authentication bypass (MAB) or EAP pass-through modes, which are fallback options for non-802.1X devices.

According to the exhibits, the administrator has configured an automation stitch to automatically quarantine compromised devices based on FortiAnalyzer’s threat detection services. However, according to the FortiAnalyzer logs, the test device is not detected as compromised by FortiAnalyzer, even though it tried to access a malicious website. Therefore, option B is true because FortiAnalyzer does not have a valid threat detection services license, which is required to enable the threat detection services feature. Option D is also true because FortiAnalyzer does not consider the malicious website an indicator of compromise (IOC), which is a criterion for identifying compromised devices. Option A is false because the web filtering rating service is working, as shown by the log entry that indicates that the test device accessed a URL with a category of “Malicious Websites”. Option C is false because the device does not need to have FortiClient installed to be quarantined by FortiGate, as long as it is connected to a managed FortiSwitch device.