TheSwitch Insightssection in the Mist dashboard provides detailed switch telemetry, including interface statistics, port utilization, client count, and traffic analysis. It allows administrators to view real-time and historicaltraffic per port, identify top talkers, and detect anomalies.
"The Switch Insights page displays real-time and historical data such as traffic per port, PoE usage, connected clients, and interface errors for every switch managed by Mist." Option A:Correct- port-level traffic and utilization metrics are visible in Switch Insights.
Option B:Incorrect - available for all Mist-managed switches (EX and supported QFX).
Option C:Incorrect - displays complete event history, not limited to five events.
Option D:Incorrect - configuration rollback is done via the configuration history section, not Switch Insights.
References:
Juniper Mist AI for Wired - Switch Insights Overview
Juniper Mist Wired Assurance - Switch Analytics and Port Utilization Guide Juniper Mist AI Cloud - Switch Telemetry and Event Monitoring

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.
References:
Juniper Mist AI for Wired - Device Claiming and State Management Guide
Juniper Mist Cloud - Switch Onboarding Workflow
Juniper Mist Wired Assurance - Device Status Descriptions

Link Layer Discovery Protocol (LLDP)is a Layer 2 discovery protocol that allows network devices to advertise identity and capabilities to directly connected neighbors. While LLDP is useful for basic topology discovery, it has two key limitations inWired Assurance client identification:
"LLDP operates at Layer 2 between directly connected devices and must be explicitly enabled on all participating network elements to provide neighbor information. It cannot discover devices beyond the first physical hop." Option A:Correct- LLDP must beconfigured and enabledon each network device to function.
Option B:Incorrect - LLDP itself is scalable but limited to direct adjacency.
Option C:Correct- LLDP only worksbetween directly connected devices.
Option D:Incorrect - not all clients support LLDP; however, the question asks forlimitations of using LLDP, not lack of support.
References:
Juniper Mist AI for Wired - LLDP Client Discovery Overview
Junos OS Documentation - LLDP Protocol Operation
Juniper Mist Wired Assurance - Device Identification and Topology Guide

InMist Cloud,site variablesare used to store and reference common configuration values (such as VLAN IDs, subnet addresses, or gateway IPs) that are reused across multiple devices and templates within a site.
"Site variables allow administrators to define reusable configuration parameters that can be referenced in multiple templates or device configurations, ensuring consistency and reducing manual errors." Option A:Incorrect - applies configuration directly, not reusable references.
Option B:Correct- site variables enable you to reference the same VLAN or value in multiple configurations (switches, WLANs, etc.).
Option C:Incorrect - WLAN templates are for wireless SSID configuration.
Option D:Incorrect - switch templates define static configuration but don't store shared variables.
References:
Juniper Mist AI for Wired - Site Variables and Template Management Guide Juniper Mist AI for Wired - Multi-Device Configuration Reuse Best Practices Juniper Mist Cloud - Organization and Site Configuration Reference

Juniper's officialCampus Fabric IP Clos designfor Mist Wired Assurance defines that the3-stage IP Clostopology eliminates the traditionaldistribution layerentirely. This architecture is intended for smaller campus environments that do not need an intermediate distribution layer between the access and core.
"Juniper's Wired Assurance supports 3-Stage and 5-Stage IP Clos deployments. The 3-Stage IP Clos is targeted towards deployments that do not require a Distribution Layer and have smaller scale requirements." Because the distribution layer is not present, the only hierarchical connection in a 3-stage campus fabric is between thecore and access layers. Traffic is routed directly at the access layer, and each access switch acts as a Layer-3 gateway (IRB) for its VLANs.
"In a campus fabric IP Clos architecture, Mist provisions Layer-3 (L3) integrated routing and bridging (IRB) interfaces on the access layer. All the access switches are configured with the same IP address for each L3 subnet." Additionally, the Juniper documentation explains that point-to-point links are configuredbetween layers, and in the case of the 3-stage design (with no distribution), this means between thecore and accessdevices:
"The point-to-point links between each layer utilize /31 addressing to conserve addresses." Therefore, the correct statement isC: The core layer is connected to the access layer.
OptionsAandBincorrectly mention a distribution layer that does not exist in this topology.
OptionDis incorrect because core (spine) devices in a Clos fabric are not interconnected with each other.
References:
Juniper Mist AI for Wired - Campus Fabric IP Clos Architecture Guide
Juniper Mist AI for Wired - Campus Fabric IP Clos Workflow
Juniper Mist AI for Wired - Configure Campus Fabric IP Clos
Juniper Validated Design - Campus Fabric IP Clos Deployment Types