Juniper JN0-460 - JNCIS-MistAI-Wired

TheAlerts Configurationsection in the Mist dashboard allows administrators to definenotification rules and recipientsfor various network events, including switch issues, site-level incidents, and SLE threshold violations. Notifications can be sent viaemail, webhook, or third-party integrations.

“Use the Alerts Configuration page to enable alerts for specific device events, assign severity levels, and define e-mail or webhook recipients for switch and site notifications.”

Option A (Marvis conversational interface):Used for querying issues via AI, not for email alerts.

Option B (Wired SLEs):Provides analytics and thresholds but does not manage notifications.

Option D (Marvis Actions):Offers suggested remediation steps, not alert setup.

Option C (Alerts Configuration):Correct— this is where email notifications are configured.

In theCampus Fabric Deployment Wizard, the first step is defining thetopology type(3-stage or 5-stage IP Clos) and mapping thephysical connectionsbetween devices (core, distribution, and access).

“The first step in the campus fabric deployment process is to define the topology and identify physical connections between devices. This ensures correct port mapping between core, distribution, and access tiers.”

Option A:Correct— topology definition and physical connectivity mapping occur in the initial step.

Option B:Incorrect — the underlay network configuration happens after topology definition.

Option C:Incorrect — overlay configuration handles EVPN/VXLAN and routing setup, not physical cabling.

Option D:Incorrect — applying intent finalizes the deployment but does not define connectivity.

According to Juniper Mist documentation, Dynamic Port Configuration (DPC)—also referred to as Dynamic Port Profiles—is the feature specifically designed to automate the assignment of VLANs and port settings based on the type of device connected to a switch. This technology enables the concept of "colorless ports," where any device (such as a Juniper Mist Access Point, an IP camera, or a VoIP phone) can be plugged into any available switch port without prior manual configuration.

The system functions by using "port assignment rules" that leverage various device properties to identify the connected hardware. These properties include LLDP attributes (System Name, Chassis ID, or Description), MAC addresses (including specific OUI ranges), and RADIUS attributes. For example, a rule can be configured to detect an LLDP System Description starting with "Mist Systems" and automatically apply a "Wireless AP" port profile. This profile typically includes the management VLAN, PoE settings, and Spanning Tree Protocol (STP) parameters required for an access point to function.

The primary benefit of DPC is the reduction of manual labor and the elimination of configuration errors in large-scale deployments. In traditional environments, an administrator would have to manually assign a VLAN to a specific physical port; with DPC, the Juniper Mist cloud detects the device and pushes the relevant configuration to the switch in real-time. If the device is disconnected, the port can be configured to revert to a "restricted" or "guest" VLAN, ensuring that the network remains secure against unauthorized access. This AI-driven approach drives consistency across multiple sites while significantly streamlining the onboarding of new hardware.

TheMist UI(User Interface) is Juniper’s cloud-based management platform used tomanage both wired and wireless devices, including EX, QFX, and SRX platforms.

It provides centralized visibility, configuration, analytics, and AI-driven insights for the entire enterprise network infrastructure.

WithinWired Assurance, the Mist UI enables device claiming, switch templates, configuration management, and SLE monitoring.

According to Juniper Mist documentation, Switch Insights is the dedicated diagnostic and auditing feature within the Mist AI dashboard that provides a granular, chronological record of all events pertaining to a specific switch1. While Site Events or Site Alerts provide a broad overview of health and anomalies across an entire location, Switch Insights is specifically designed for device-level deep dives. When a user navigates to the Insights page for a particular switch, they are presented with a comprehensive timeline that correlates telemetry data with specific system occurrences.

This feature displays a detailed list of Switch Events, including but not limited to interface state transitions (Up/Down), Spanning Tree Protocol (STP) role changes, LLDP neighbor updates, and PoE controller status. Importantly, Switch Insights also tracks administrative actions, such as configuration commits and software upgrades, allowing an administrator to see exactly when a change was made and if that change coincided with a performance degradation in the Wired Service Level Expectations (SLEs).

Beyond simple logging, Switch Insights allows for retroactive troubleshooting. By adjusting the time slider, an administrator can go back in time to review the exact state of the switch during a reported issue2. For example, if a user reports a video conferencing issue that occurred three hours ago, the administrator can use Switch Insights to see if any port flaps, storm control events, or configuration changes took place during that specific window. This AI-driven visibility eliminates the need for manual syslog analysis or persistent CLI monitoring, providing a transparent and easily accessible audit trail for all switch-specific activity within the managed organization.

In Juniper Mist,Greenfield adoptionapplies to new, cloud-ready switches (such as EX4100, EX4400, and QFX series) using aclaim or activation codeto securely connect to the Mist cloud.

Brownfield adoption, however, supports switches already deployed or not factory-fresh. These are manually onboarded by configuring outbound management connectivity and adopting them through the Mist portal.

This distinction enables both new and legacy EX/QFX environments to be cloud-managed under Wired Assurance.

When a switch is claimed into a Mist organization, it appears in one of several states depending on connectivity and site assignment.

“After claiming, switches initially appear asUnassignedif they are not yet linked to a site. Once online and connected to Mist Cloud, they transition toConnectedstatus and begin receiving configurations and telemetry.”

Option A (Connected):Correct— indicates the switch is online and communicating with Mist Cloud.

Option B (Inactive):Incorrect — not a valid device state in Mist.

Option C (Active):Incorrect — “Active” is not a device state label in Mist.

Option D (Unassigned):Correct— indicates the switch has been claimed but not yet assigned to a site.

Forgreenfield onboarding, switches are newly deployed and must be claimed into Mist Cloud. Juniper Mist offers multiple claim options to simplify large-scale onboarding.

“You can claim switches using the device’s QR claim code, by bulk importing from a sales order, or through API-based automation for large deployments. Each of these methods securely associates the devices to your organization in Mist Cloud.”

Option A:Incorrect — serial number alone is not sufficient for claiming.

Option B:Correct— claim codes (QR) uniquely identify switches.

Option C:Correct— bulk claim from a sale order streamlines large deployments.

Option D:Correct— APIs support automated claiming and provisioning workflows.

Option E:Incorrect — MAC address alone cannot be used to claim devices.

According to Juniper Mist documentation, the Throughput Service Level Expectation (SLE) is the primary metric used to measure the ability of wired clients to pass traffic across the physical network without impedance. This SLE is critical for diagnosing issues with real-time, high-bandwidth applications such as video streams, which are highly sensitive to packet loss and latency. Within the Throughput SLE, the Storm Control classifier is specifically designed to identify "bad user minutes" caused by the suppression of Broadcast, Unknown Unicast, and Multicast (BUM) traffic.

Storm control is a mechanism that enables the switch to monitor traffic levels and drop BUM packets when a specified traffic level—known as the storm control level—is exceeded. This prevents a "traffic storm" from proliferating and degrading the overall performance of the LAN. While this is a vital security feature to prevent network meltdowns, it can inadvertently impact legitimate traffic. For instance, if multicast-based video streams or other heavy BUM traffic exceed the configured bandwidth percentage on a port, the switch will drop those packets to protect the rest of the network.

When troubleshooting video stream issues, network administrators should inspect the Storm Control classifier to see if it is triggering "bad user minutes". If the Mist dashboard indicates failures under this classifier, it signifies that the switch hardware is actively dropping packets because the BUM traffic limit has been reached. This provides immediate root-cause evidence, allowing the administrator to determine if they need to adjust the storm control thresholds within the Port Profile or investigate the source of the excessive broadcast traffic. By correlating these hardware-level events with the end-user experience, Mist AI simplifies the resolution of complex performance problems that traditional "up/down" monitoring would miss.