The fundamental sampling method used in supervised learning is a labeled dataset. As described in Juniper Mist AI and machine learning application guides, supervised learning algorithms are trained using datasets in which each sample is paired with a known output (label). The model is fed examples comprising input data and the correct answer, learning patterns to map new inputs to their target outputs. While regression, decision tree, and random forest are techniques within supervised learning, the process fundamentally relies on having a labeled dataset for both training and validation phases. “Supervised machine learning models are built on labeled data, with each input paired to a target value or classification.” This allows for accurate model training and evaluation.

The session policy settings in the Juniper Mist Cloud define how long a user session remains active and how the system manages session expirations due to inactivity. These configurations help ensure both security and efficient resource management across the Mist Cloud portal and API sessions.

According to the Juniper Mist Cloud Administration and Security Configuration Guide :

“Session policy defines session timeout and inactivity timeout parameters, controlling how long users can remain logged into the Mist Cloud portal or API before re-authentication is required.”

Session Timeout: Specifies the maximum duration a session can remain active, regardless of activity.

Inactivity Timeout: Defines how long a session can remain idle before automatic logout.

These policies help maintain strong access security by reducing the risk of unauthorized access through stale sessions.

Other options such as password complexity (A, C) and two-factor authentication (D) are configured under authentication and access policies , not session policies.

Therefore, the correct answer is B. The duration for session timeout and inactivity timeout.

The appropriate solution is Juniper Mist Asset Visibility (option C). Asset Visibility is a cloud service that leverages Juniper Mist Access Points and virtual Bluetooth Low Energy (vBLE) technology to track, locate, and display all network devices—including both Juniper and non-Juniper hardware—within the Mist GUI. According to the official Juniper documentation: “Juniper Mist Asset Visibility unites Wi-Fi connectivity, indoor location services for asset tracking, and IoT visibility in a single cloud platform. By combining vBLE with the Mist Cloud, organizations can use the same infrastructure—even when wired switches are from different vendors—for locating, tracking, and analyzing their most valuable assets and network devices.”

This capability is independent of switch manufacturer and provides comprehensive visualization of wireless APs and connected wired devices, ensuring a true single-pane-of-glass management experience. Wired Assurance, Marvis Actions, and LLDP-enabled Wi-Fi Management may provide visibility and proactive troubleshooting, but only Asset Visibility guarantees display and tracking of all assets—Juniper and non-Juniper—in the Mist GUI.

The Marvis Virtual Network Assistant (VNA) in Juniper Mist AI uses real-time telemetry and AI-driven correlation to identify hardware and connectivity issues, including bad cable conditions. When a “Bad Cable” alert is raised, Marvis analyzes physical link metrics from the switch and AP—such as CRC errors, FCS drops, and link flaps—to isolate the root cause.

According to the Juniper Mist AI Operations Guide, the Marvis Actions dashboard provides contextual insights into the issue, showing whether the fault lies in the physical cable itself or the switch port it is connected to. Specifically, the dashboard highlights:

The affected device and port.

Whether the degradation originates from the port hardware or the cabling .

Suggested corrective action (e.g., replace the cable or check switch hardware).

Marvis uses its AI-driven root cause analysis engine to distinguish between cable integrity problems and port failures by examining electrical signature anomalies and historical telemetry.

Options B, C, and D are incorrect because Marvis does not display cable category ratings or identify individual broken Ethernet pairs—it focuses on identifying and isolating the fault domain.

Therefore, the correct answer is A. If the port or cable is at fault.

The Juniper Mist Cloud platform is built on a microservices-based architecture , where individual software components perform specific functions and communicate using well-defined Application Programming Interfaces (APIs) .

According to the Juniper Mist Cloud Architecture and Operations Guide :

“Microservices communicate through secure APIs, allowing independent services to interact seamlessly while maintaining modularity and isolation.”

This architectural design provides major operational benefits, including:

Independent scalability – each service can scale based on workload demand.

Fault isolation – failures in one service do not affect others.

Continuous deployment – updates can be made to one service without impacting the rest of the platform.

Incorrect options:

B: Juniper Mist microservices are independently updated, not deployed as one suite.

C: They are independent, not dependent on one another.

D: Each microservice maintains its own data model; they do not rely on a single shared database.

Thus, the correct answer is A. Microservices communicate with each other using APIs.

Marvis Minis continuously validates the health of network services by performing synthetic tests at predefined intervals without requiring user intervention. These tests simulate real client interactions — such as authentication, DHCP, DNS, and application reachability — to detect network issues proactively.

According to the Juniper Mist Marvis Minis Technical Overview , the feature performs:

“Automated validations every hour to ensure wireless, wired, and WAN network services are operating as expected.”

Each validation cycle allows the Minis agent (running on Mist Access Points) to verify connectivity and performance parameters across key stages of the client experience. If any issues are detected, they are automatically surfaced in the Marvis Actions dashboard for further analysis.

While administrators can trigger additional manual tests, automatic validations occur every hour by default across all enabled sites.

Therefore, the correct answer is B. Every hour.

In Juniper Mist’s Location-Based Services , the Asset Visibility service utilizes the built-in Bluetooth Low Energy (BLE) antenna array within Mist Access Points to track BLE tags and devices in listen-only mode . This allows the APs to receive BLE signals emitted by assets and compute their real-time location using angle-of-arrival (AoA) and RSSI-based triangulation .

According to the Juniper Mist Asset Visibility and Location Services Guide :

“When operating in Asset Visibility mode, the vBLE antenna array in Mist Access Points functions in listen-only mode, collecting BLE chirps from asset tags and relaying this data to the Mist Cloud for location determination.”

This configuration differs from vBLE Engagement , where APs transmit BLE beacons to interact with mobile apps. In Asset Visibility , the BLE array passively listens to track tagged assets (e.g., equipment, IoT devices) across a defined floor map.

Therefore, the correct answer is D. Asset Visibility.

According to the official Juniper Mist documentation on the configuration hierarchy, the platform uses a three-tier model: Organization → Site → Device. At the organization level, you manage administrator accounts, subscriptions, and organization-wide settings. Then:

“An organization can include one or more sites. A site can represent a physical location or a logical subdivision of your enterprise or campus.”

Also, in the simpler case explanation:

“Each customer is created as a separate organization. Within that organization multiple sites can be created.”

Mist

These statements make clear that the correct relationship is: one organization may have multiple sites under it. The inverse — that a site might contain multiple organizations — is not supported in the documented hierarchy. Therefore option B is correct.

Marvis Minis is an advanced feature within the Juniper Mist AI ecosystem designed to perform autonomous, synthetic network testing . It uses Mist Access Points (APs) to simulate client behavior—such as association, authentication, DHCP, DNS, and application reachability—to proactively detect service issues before real users are affected .

According to the Juniper Mist Marvis Minis Deployment Guide and Marvis AI documentation , the key requirement for enabling Marvis Minis is that all participating access points must be running a minimum supported firmware version that includes the Minis agent functionality.

The documentation specifies:

“Marvis Minis requires APs running the minimum firmware version that supports synthetic testing. APs on earlier versions will not be capable of running Minis tests or reporting results to the Mist Cloud.”

Additional subscriptions such as WAN Assurance , Premium Analytics , or WLAN templates are not prerequisites for operation. While Marvis licensing must be active, the feature itself relies primarily on compatible firmware within the Mist-managed APs.

Therefore, the correct answer is C. Minimum AP firmware — ensuring the APs are on a supported firmware release is essential for Marvis Minis functionality.

To create a real-time visualization dashboard that displays clients on a map, use Live View and WebSocket APIs. The "Live View" feature in Juniper Mist provides a graphical, interactive map view of clients (devices) and assets as they move through a site, with location data updated in real time. The Juniper Mist WebSocket API enables developers and integrators to subscribe to client location topics and stream position data directly to custom dashboards. According to the documentation: "WebSockets open a bidirectional communication session for sending and receiving real-time event-driven responses... Useful in circumstances where you want to avoid browser refreshes and display real-time location data." Combining these allows you to build a dashboard showing live client positioning, as seen in sample dashboards and integration guides for Mist.