In the Juniper Mist AI ecosystem, Service Level Expectations (SLEs) provide a proactive way to monitor the health of a wireless network from the perspective of the end-user. When investigating potential interference—whether it is from neighboring Wi-Fi networks or non-Wi-Fi sources like microwaves or motion sensors—the Capacity SLE is the primary metric to analyze. While interference certainly impacts the overall Throughput SLE, Mist categorizes the specific environmental factors that limit airtime availability under the "Capacity" umbrella.

The Capacity SLE tracks "user minutes" during which a client experiences a drop in available RF channel capacity. It is specifically designed to identify why a client might be struggling to transmit data despite having a strong signal. Within the Capacity SLE block, Mist provides granular classifiers that pinpoint the root cause of the capacity degradation. These classifiers include:

Wi-Fi Interference: This identifies airtime contention caused by other 802.11 networks (Co-Channel Interference or Adjacent Channel Interference).

Non-Wi-Fi Interference: This identifies energy from non-802.11 sources detected by the AP's dedicated scanning radio.

Client Count: High density leading to contention.

Client Usage: A single "bandwidth hog" consuming the available airtime.

By checking the Capacity SLE in the Mist dashboard before heading to a site, an administrator can see a historical timeline of interference events. If the "Wi-Fi Interference" or "Non-Wi-Fi Interference" classifiers show a high percentage of "Bad User Minutes," the administrator can confirm that the client's complaint is indeed valid. This allows for remote troubleshooting and may even enable the admin to resolve the issue by adjusting Radio Resource Management (RRM) settings or identifying a specific rogue device, potentially saving an unnecessary truck roll.

In the Juniper Mist AI product portfolio, the BT11 is a specialized, enterprise-grade access point designed exclusively for Bluetooth Low Energy (BLE).4 Unlike the other access points in the Juniper Mist family (such as the AP12, AP24, and AP34), the BT11 does not contain Wi-Fi radios.5 Its sole purpose is to provide high-accuracy, enterprise-grade location-based services (LBS) by leveraging Juniper's patented 16-element virtual BLE (vBLE) antenna array.6

The primary use case for the BT11 is to augment BLE coverage in environments where Wi-Fi connectivity is already established by other APs, but the density of those APs is insufficient for precise location services. For applications like turn-by-turn wayfinding or asset tracking, the RF requirements for BLE are often more stringent than those for Wi-Fi. A facility might have enough Wi-Fi APs to provide data coverage, but may have "location holes" where the BLE signals are too sparse for 1–3 meter accuracy. By deploying BT11 units in these gaps, administrators can extend the reach of the location engine without the expense of adding full-featured Wi-Fi radios where additional capacity is not needed.7

The BT11 communicates directly with the Mist Cloud to manage virtual beacons, which eliminate the need for physical, battery-powered beacons and manual calibration.8 Because it runs on Power over Ethernet (PoE) and integrates seamlessly with the Mist AI engine, it provides a scalable and cost-effective way to ensure continuous, high-fidelity BLE coverage across a campus, hospital, or retail floor.

According to the VLANs (Static & Dynamic) - Mist document3, you can define VLANs as untagged, tagged, or using VLAN pooling in the WLAN settings in the Juniper Mist UI. A WLAN is a wireless network that defines parameters such as SSID, security type, and VLAN.

In a Juniper Mist environment, the Radio Resource Management (RRM) system is responsible for the automated allocation of channels and transmit power across all Access Points (APs) at a site. When you modify an RF Template—for example, by excluding specific UNII-2 Extended channels that certain legacy or region-specific clients cannot "see" or support—you are updating the intended policy for the network. However, because Mist RRM is designed for stability, it does not always force an immediate, disruptive channel change across the entire site the moment a template is saved.

To force the Mist AI engine to immediately recalculate the channel plan based on your new constraints and push those settings to the APs, you use the Optimize Now button. This feature is found within the Radio Management section of the site settings or the RF template application page. When "Optimize Now" is triggered, the Mist Cloud analyzes the current RF environment, takes your new channel exclusions into account, and issues a command to the APs to switch to the most efficient channels available within the newly defined subset.

Choosing Restart the APs (C) or Restart the WLANs (B) is unnecessary and causes more downtime than required. A reboot might eventually result in a new channel selection, but it does not guarantee that the RRM algorithm has fully processed the global optimization for the site. Restarting clients (D) does nothing to change the AP's channel behavior. By using Optimize Now (A), you ensure a coordinated, AI-driven transition that minimizes "co-channel interference" while respecting the updated frequency constraints you defined to accommodate your specific client devices. This ensures that clients previously struggling with unsupported UNII-2 channels are immediately moved to compatible frequencies.

In Juniper Networks Mist AI Wireless, the strength and quality of a client’s wireless connection are primarily evaluated using RSSI (Received Signal Strength Indicator) and SNR (Signal-to-Noise Ratio). These two metrics are core inputs into multiple Wireless Assurance SLEs, including Coverage and Throughput, and are reliable indicators when determining which client has the weakest WLAN connection.

From the exhibit, the key metrics for each client are:

Client 1: RSSI –81 dBm, SNR 11 dB

Client 2: RSSI –71 dBm, SNR 21 dB

Client 3: RSSI –67 dBm, SNR 25 dB

Client 4: RSSI –70 dBm, SNR 22 dB

In wireless design, lower (more negative) RSSI values indicate weaker signal strength, and lower SNR values indicate poorer signal quality due to higher relative noise. Among all listed clients, Client 1 clearly has the weakest connection, as it has both:

The lowest RSSI (–81 dBm), indicating it is farthest from the AP or experiencing significant attenuation.

The lowest SNR (11 dB), which suggests the signal is only marginally stronger than the background noise.

Mist best practices typically consider RSSI values below –70 dBm and SNR values below ~20 dB as suboptimal for reliable performance, especially for higher modulation schemes. Client 1 falls well below these thresholds, making it the most likely to experience low data rates, retransmissions, and degraded user experience.

Mist AI would flag this client as having poor coverage and may recommend actions such as:

Improving AP placement or density

Adjusting RF power or channel plans

Enforcing minimum RSSI thresholds

Therefore, based on both RSSI and SNR, Client 1 has the weakest WLAN connection, making Option D the correct answer.

In this scenario, you would begin troubleshooting by checking the WLAN-level Pre-Shared Keys.

According to the Cisco Catalyst 9800 Series Wireless Controller Software Configuration Guide1, you can configure a time-based setting for WLAN-level Pre-Shared Keys (PSKs) that will reset the key after a specified interval. This feature is useful for enhancing security and preventing unauthorized access. If a user reports that the Wi-Fi worked for a week and now it does not work, you should check the WLAN-level PSK settings and see if the key has been changed.

In Juniper Networks Mist AI Wireless, Juniper prescribes a top-down, structured troubleshooting methodology when using Service-Level Expectations (SLEs). This approach ensures that engineers identify systemic issues before drilling into individual client problems, preventing misdiagnosis and wasted effort.

The correct troubleshooting order is:

Organization → Site → SLE → Client

Organization of interestTroubleshooting always begins at the organization level. This provides a global view of overall health, license status, widespread outages, and configuration changes that may impact multiple sites. Organization-level visibility helps determine whether the issue is localized or systemic.

Site of interestAfter confirming the organization is healthy, the next step is narrowing the scope to the affected site. Site-level views expose infrastructure issues such as WAN problems, DHCP outages, AP connectivity issues, or RF-wide anomalies that affect many users simultaneously.

SLE of interestOnce scoped to the site, administrators identify the specific degraded SLE (for example, Time to Connect, Coverage, Capacity, or Throughput). Each SLE includes classifiers that pinpoint the likely root cause, such as DHCP, DNS, authentication, or RF interference.

Client of interestOnly after isolating the failing SLE should troubleshooting move to the individual client level. Client views provide detailed timelines, event history, and packet-level insights to confirm whether the issue is isolated or a symptom of a broader problem.

The other answer choices are incorrect because they start with either the SLE or client, which risks overlooking organization-wide or site-wide conditions. Juniper’s recommended workflow ensures efficient, accurate fault isolation and aligns with how Mist AI correlates telemetry and events.

Therefore, the correct answer is A. Organization of interest, site of interest, SLE of interest, client of interest.