Analysis of Exhibits:

RF Analysis:

Channel 1 (2.4 GHz) shows very high utilization (91%) and significant overlap/interference from other APs (8 overlap-AP, 7 interfere-AP).

Channel utilization on 2.4 GHz is very high, indicating congestion and contention.

AP Diagnostic Summary:

Radio 1 (2.4 GHz):

Channel Utilization: 78%

Interfering SSIDs: 18

A long list of clients and many SSIDs being broadcast on Channel 1.

Radio 2 (5 GHz):

Channel Utilization: 0% (much lower usage; likely not all clients or SSIDs are using it).

SSID List:

Multiple SSIDs are being broadcast by the AP, which increases management overhead (beacon/probe traffic) and reduces airtime for actual data.

Problem Symptoms:

Guest users in the reception area (on 2.4 GHz, channel 1) are experiencing slow performance .

Option Analysis:

A. Reduce the number of SSIDs being broadcast by the reception AP

Correct.

Each SSID adds additional management overhead (beacons, probes) that consume airtime on already congested 2.4 GHz channels.

Reducing the number of SSIDs frees up airtime for actual client data, which can improve throughput and reduce latency, especially in high-density environments with high channel utilization.

This is a recommended best practice for optimizing Wi-Fi performance in congested environments.

B. Enable frequency handoff on the AP to band steer clients

Helpful if clients support 5 GHz, but not all client devices (especially IoT/guests) do; with such high channel utilization, this is a secondary optimization.

C. Increase the transmission power of the AP radios

This can make interference worse and does not solve airtime congestion; it may also increase contention with neighboring APs.

D. Install another AP in the reception area to improve available bandwidth

Adding more APs on congested channels can actually increase interference and may not help unless channel planning and SSID management are also addressed.

Summary:

Reducing the number of SSIDs is the most direct, configuration-based action that will improve available airtime and performance for clients in a congested, high-utilization environment like the one shown in the exhibits.

FortiPresence analytics is a platform for presence analytics—monitoring WiFi user presence, dwell time, and visitor trends in physical spaces.

A: It collects and reports details about on-site guest users, such as visit duration and repeat visits.

C: It enables comparison of current user presence and activity data with historical trends, supporting operational and marketing analysis.

B (reporting potential threats) is not a function of presence analytics.

D (predicting future guest counts) is not a core function; FortiPresence reports on actual and historical data, not predictive analytics.

WPA3 improves security over WPA2 by, among other things:

Using robust key establishment (SAE/Dragonfly), which is not vulnerable to KRACK (Key Reinstallation Attack).

WPA3 does not enforce only enterprise mode, nor does it universally prevent all legacy protocols, nor is 128-bit key size unique to WPA3.

Analysis of the Exhibits and Scenario:

The DHCP server configuration is correct for dynamic assignment within a specified IP range for the interface “WLAN01”.

The RADIUS configuration for user1 includes:

Tunnel-Type (should be set to VLAN, but value is missing)

Tunnel-Medium-Type (set to IEEE-802, which is correct for Ethernet/WiFi)

Tunnel-Private-Group-Id (set to “infrastructure” as a string)

The problem described: Dynamic VLAN assignment is not working for user1.

How Dynamic VLAN Assignment Works in 802.1X/EAP (with FortiGate/FortiAP):

When a user authenticates, the RADIUS server returns attributes specifying the VLAN that should be assigned.

The critical attributes are:

Tunnel-Type (must be set to value “VLAN”, which is integer 13)

Tunnel-Medium-Type (must be “IEEE-802”, integer 6)

Tunnel-Private-Group-Id (can be the VLAN name or VLAN ID, depending on your configuration)

Problem in the Exhibit:

The Tunnel-Type value is missing!

It must be set to 13 (for VLAN).

The Tunnel-Medium-Type and Tunnel-Private-Group-Id are correctly set.

Corrective Action:

Update user1’s RADIUS attributes so that Tunnel-Type is set to the correct value for VLAN (integer 13).

Without this, FortiGate/FortiAP will not know to interpret the returned VLAN name or ID for dynamic assignment.

Review of Options:

Disable the DHCP server on ONBOARD to allow VLAN assignment.

Irrelevant; DHCP server presence does not affect dynamic VLAN assignment.

Add user1 in one of the VLAN names

This is not how dynamic VLAN assignment works. The RADIUS response must include the correct VLAN assignment.

Update user1 RADIUS attributes to include a VLAN ID attribute ID

Correct. You must set Tunnel-Type (13) and possibly provide the VLAN ID in Tunnel-Private-Group-Id.

Create a new VLAN name infrastructure ' with a VLAN ID associated with it

Not the root cause; you must first ensure the correct attributes are present in the RADIUS response.

Summary:

The missing “Tunnel-Type” attribute value is the reason dynamic VLAN assignment is not working. The correct configuration requires setting Tunnel-Type = 13 (VLAN) for user1 in the RADIUS server.

When a client moves out of range, the connection drops.

The normal behavior is for the client to disconnect and then seek out and connect to another AP with a stronger signal.

The AP does not force disconnection or send alerts; the client handles roaming.

Clients do not increase their own radio power substantially in response to poor signals due to hardware limits.

For remote sites with no on-site IT , you should:

A: Use APs that support Fortinet UTM (i.e., FortiAPs that can tunnel traffic back to a FortiGate for UTM enforcement).

D: Use cloud-based management ( FortiLAN Cloud ) and configure tunnel SSIDs so all traffic from the AP is sent back for security inspection at a central FortiGate.

B refers to PoE power but isn’t essential if APs can be powered in another way.

C (bridge mode to local subnet) would not allow centralized UTM enforcement unless local FortiGate is present.

FortiPresence is Fortinet’s Wi-Fi analytics/cloud presence platform.

FortiAPs can be managed directly by FortiGate or FortiLAN Cloud and connect their analytics/events to the FortiPresence cloud for presence analytics.

FortiSASE and FortiSwitch Manager do not provide FortiPresence integration for APs.

Exhibit Review:

The diagnostics panel for FortiAP FP231FTF2001 shows:

Tx bandwidth label: 150.54 Mbps (likely the negotiated or theoretical maximum).

Bandwidth graph (actual traffic) : Transmit (Tx) bandwidth peaked at only ~3 Mbps over the last 5 minutes—far below the maximum.

Radio 1 (2.4 GHz) shows 10 interfering SSIDs and 40% channel utilization .

Radio 2 (5 GHz) is not the focus in the current graph.

Interpretation:

The significant difference between the potential (label) and actual (graph) throughput indicates that something is preventing the AP from delivering full speed.

This could be resource overload (e.g., too many clients, too much interference, CPU/memory constraints), leading to overall reduced throughput for all users .

The graph represents real-time/actual usage, not just the theoretical capability.

Option Breakdown:

A. Resources on FortiAP are overloaded which limits speed rates for all users

Correct. Overload (either due to too many clients, high interference, or hardware resources) is a logical reason why actual throughput is far below the possible maximum.

B. Label values are historical and provide average bandwidth

Incorrect. The label reflects the maximum link rate or negotiated data rate, not an average or historical usage value.

C. FortiAP is dual band and is transmitting data faster with a higher frequency band

Not supported by the evidence. The current data is for Radio 1 (2.4 GHz) and does not show high usage on either band.

D. Bandwidth is shared with other SSID signals broadcasting for nearby AP devices

While interference does share airtime, the drastic drop in throughput strongly suggests an overload or other limiting factor on this AP.

Summary:

The large gap between the expected maximum (label) and the actual throughput observed suggests that resource overload is the root cause of poor wireless speeds for all users.

When you need different access levels for various users and device types but want to keep the SSID structure simple, dynamic VLAN assignment is the best practice.

With dynamic VLANs, all clients connect to the same SSID . The RADIUS server (via 802.1X authentication or MAC authentication) assigns each user or device to a specific VLAN based on attributes (like user group, device type, etc.).

This design:

Reduces SSID sprawl.

Allows flexible, scalable, and policy-driven access.

Simplifies management and enhances security.

The other options are either less scalable (multiple SSIDs) or do not provide the required dynamic access control (user groups or NAC alone without VLAN assignment).