JN0-460 Juniper JNCIS-MistAI-Wired Free Practice Exam Questions (2026 Updated)

InEVPN-VXLAN,BUM (Broadcast, Unknown unicast, and Multicast)traffic is handled differently than unicast traffic. EVPN provides two main forwarding mechanisms to distribute BUM traffic betweenVTEPs(VXLAN Tunnel Endpoints):

“BUM traffic in EVPN-VXLAN fabrics is replicated using eitheringress replicationorunderlay multicast(PIM-based). Both methods ensure that broadcast and unknown unicast frames reach all remote VTEPs within the same VXLAN segment.”

Option A:Incorrect — static routes are unrelated to BUM forwarding.

Option B:Incorrect — BGP is thecontrol plane, not a data-plane forwarding method.

Option C:Correct—Ingress replicationreplicates BUM packets to all remote VTEPs in the same VNI using unicast tunnels.

Option D:Correct—Underlay replication (multicast)uses multicast groups in the IP underlay to distribute BUM frames efficiently.

ForJuniper cloud-ready EX Series switches(EX2300, EX3400, EX4100, EX4400, etc.) to successfully onboard to theJuniper Mist Cloud, specific connectivity requirements must be met:

“Cloud-managed EX switches require outbound connectivity to the Mist Cloud on TCP ports 2200 or 443. Switches must also have access to DNS services to resolve cloud service URLs during onboarding.”

Option A:Incorrect — minimum version depends on switch model; older models may onboard with earlier releases (e.g., 20.x, 21.x).

Option B:Correct— outbound TCP 2200 or 443 connectivity is required for cloud registration.

Option C:Incorrect — switches connect directly to Mist Cloud, not the Agile Licensing Portal.

Option D:Correct— DNS resolution is mandatory for discovering Mist Cloud endpoints.

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.

Juniper Mist Wired AssuranceprovidesAI-driven operational visibilityfor EX and QFX switches. It defines and tracksService Level Expectations (SLEs)across multiple performance areas including connectivity, throughput, and switch health.

“Wired Assurance uses AI and telemetry to deliver operational visibility, track service level expectations (SLEs), and monitor throughput, successful connects, and switch health through pre- and post-connection metrics.”

Option A:Correct— accurately describes the full scope of Wired Assurance.

Option B:Incorrect — Wired Assurance provides SLEs specifically for EX and QFX switches.

Option C:Incorrect — both pre- and post-connection SLEs are monitored.

Option D:Incorrect — Wired Assurance monitors both connectivity and device health.

Juniper Wired Assurance licensingis based on switch port count and supports a range of hardware platforms. Subscriptions are available for12-port,24-port, and48-portmodels across the EX Series portfolio.

“Wired Assurance subscriptions are available for all supported EX Series switches in 12-port, 24-port, and 48-port license options, aligning to switch hardware configurations.”

Option A:Incorrect — 24-port only does not cover all options.

Option B:Incorrect — 12- and 24-port licenses exist, but 48-port is also supported.

Option C:Correct— Mist supports12-, 24-, and 48-portsubscription tiers.

Option D:Incorrect — 12-port alone is incomplete.

Route targets (RTs)are extended BGP communities used inMultiprotocol BGP (MP-BGP)forEVPN-VXLANto control route import/export between VRFs.

“A route target identifies the VRF instances that should import or export specific MP-BGP routes. It enables the association of EVPN routes with particular VRFs in multi-tenant environments.”

Option A:Incorrect — EVPN family support is identified through BGP capabilities, not RTs.

Option B:Incorrect — that’s handled by BGP EVPN negotiation, not route targets.

Option C:Correct— route targets definewhich VRFs import/export BGP routes.

Option D:Incorrect — RTs can be manually configured and reused where necessary.

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.

According to Juniper Mist documentation, the brownfield adoption process is utilized when bringing existing Juniper switches—which already have a local configuration—under the management of the Mist cloud. This process differs significantly from the greenfield "claiming" method, as it requires manual interaction with the device's management interface to establish the initial connection2.

A critical requirement for this process is that CLI access to the Juniper cloud-ready switch is required3. To initiate adoption, the administrator must log in to the switch via console or SSH and enter a specific set of Junos OS configuration commands provided by the Mist portal. These commands include the necessary parameters for the switch to establish an outbound SSH connection to the Mist cloud, typically using either TCP port 2200 or 443. Without direct CLI access to paste and execute these adoption strings, the switch cannot register itself with the organization's inventory in the dashboard.

Furthermore, because this process involves modifying the switch's local configuration file to add the Mist management parameters, you must perform a commit on the switch after adding the switch adoption commands7. In the Junos operating system, configuration changes reside in a candidate configuration buffer and do not take effect until a commit operation is successfully executed8. Once committed, the switch initiates the connection to Mist9. If the connection is successful, the switch status in the Mist dashboard will transition from "Unassigned" to "Connected," enabling AI-driven telemetry collection and Wired Assurance monitoring. This adoption method allows for a seamless transition of legacy infrastructure into a modern, cloud-managed environment without requiring a factory reset or the presence of a physical QR claim code.

According toJuniper Mist Wired Assurance documentation, three built-in diagnostic tools available for testing switch functionality areBounce Port,Ping, andCable Test.

Bounce Portallows you to disable and re-enable a port to reset connectivity.

Pingverifies Layer 3 reachability between the switch and target IPs.

Cable Testperforms diagnostics to detect wiring faults, impedance mismatches, or cable lengths.

These tools are accessed directly from theSwitch Testing Toolssection in the Mist dashboard and are available for EX Series and QFX Series switches onboarded to the Mist cloud.

According to Juniper Networks' EVPN-VXLAN documentation, devices that perform the encapsulation and de-encapsulation of Ethernet frames into VXLAN UDP packets at the edge of the network are known as Virtual Tunnel Endpoints (VTEPs)1111. In the context of a campus fabric overlay, these devices often function as L2 gateways when they bridge traditional Layer 2 traffic from end-user devices across a Layer 3 IP fabric.

The exhibit demonstrates a 3-stage IP Clos architecture where access1 and access3 are explicitly identified as VTEP endpoints. A VXLAN tunnel is shown originating at access1 and terminating at access3, allowing "User1" and "Server1"—both located on the same 10.1.1.0/24 subnet—to communicate as if they were on the same physical Layer 2 segment despite being separated by a Layer 3 IP Fabric (172.16.0.0/24). In this scenario, access1 and access3 fulfill the L2 gateway role by mapping the local VLAN traffic to a specific VXLAN Network Identifier (VNI) for transport across the underlay3.

As L2 gateways, these switches maintain the bridge table for the overlay network, learning MAC addresses from local ports and via the EVPN control plane from remote VTEPs4. This architecture allows for seamless Layer 2 mobility and connectivity across complex routed infrastructures while eliminating the need for Spanning Tree Protocol (STP) in the core5555. In contrast, options like "VNI" refer to the segment ID itself rather than a device role, and "root bridge" refers to an STP-specific role that EVPN-VXLAN is designed to move away from in a modern fabric.

Juniper Mist automatically classifies ports to simplify visibility and automation withinWired Assurance. The Mist cloud analyzesport telemetryandlink behaviorto determine port roles, including uplinks.

“Mist uses machine learning and switch telemetry to automatically detect uplinks by analyzing traffic behavior and topology information. Uplink ports typically exhibit higher TX/RX utilization and are identified as spanning-tree root or forwarding ports connecting upstream devices.”

Option A:Correct — Mist examines traffic statistics. Ports with significantly higher TX/RX utilization relative to others are likely uplinks.

Option B:Incorrect — MTU size is not a classification criterion.

Option C:Correct — Mist usesSTP information(root or designated port status) to identify uplinks.

Option D:Incorrect — port description fields are for administrative purposes only and are not used by Mist analytics.

When deployingJuniper Mist Wired AssuranceinManaged mode, switches are fully integrated with Mist Cloud for configuration, monitoring, and AI-driven operations. Managed mode providescomplete cloud-based management, meaning Mist AI handles configuration, templates, telemetry, and SLE tracking.

“In Managed mode, the switch configuration is fully managed by Mist Cloud. Administrators configure switches, templates, and policies directly through the Mist dashboard. A valid Wired Assurance subscription is required for Managed mode operation.”

Option A:Incorrect — the “Monitor Only” mode is read-only, not Managed.

Option B:Correct— Managed mode requires aWired Assurance subscription.

Option C:Incorrect — subscriptions are mandatory for Mist-managed devices.

Option D:Correct— in Managed mode,all supported EX switches are fully managed by Mist AI, including configuration and telemetry.

Juniper’s official Campus 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.

In Juniper’scampus fabric architectures, the location of theLayer 3 gateway(IRB) differentiates between CRB and ERB models:

Centrally-Routed Bridging (CRB):L3 gateways are placed at thecore layer.

Edge-Routed Bridging (ERB):L3 gateways are placed at thedistribution layer, closer to the edge.

“In the ERB model, Layer 2 gateways are deployed at the access layer, andLayer 3 gateways are deployed at the distribution layer.”

Option A (CRB):Incorrect — L3 is at the core, not distribution.

Option B (IP Clos):Incorrect — in 3-stage Clos, L3 is pushed to the access layer.

Option D (EVPN multihoming):Incorrect — this is about redundancy, not gateway placement.

Option C (ERB):Correct — L3 gateways sit at thedistribution layerin the ERB architecture.

Wired Assurance in Mist Cloud provides automated configuration for Juniper EX Series switches. The automation is built on open APIs and supports programmable workflows, which allow seamless integration with external systems and reduce manual configuration errors.

“Wired Assurance leverages 100% open APIs, enabling integration with third-party automation and orchestration tools. Combined with programmable workflows, this provides a consistent and scalable automation framework for switch deployment and management.”

Option A (100% open APIs): Correct — APIs enable automation and external integration.

Option C (programmable workflows): Correct — workflows automate repetitive tasks and provisioning.

Option B (client SLEs): Incorrect — this is part of user experience monitoring, not automation.

Option D (switch insights): Incorrect — this relates to telemetry and visibility, not automation.

According to Juniper Mist documentation, the term "Adopting a Switch" specifically refers to the process of bringing an existing, already-configured switch—often termed a brownfield device—under the management of the Juniper Mist cloud. This is distinct from the "claiming" process, which is reserved for greenfield environments where new, factory-default switches are added using a QR code or activation code.

In a brownfield scenario, the switch is typically already in production or has a pre-existing local configuration that must be preserved or integrated into the Mist AI-driven dashboard. To adopt such a switch, the administrator must manually interact with the switch's Command Line Interface (CLI). The Mist portal provides a unique adoption command—a string of Junos OS configuration—that includes the specific URL for the Mist cloud and the organization’s unique registration token. Once this command is pasted into the switch's CLI and committed, the switch initiates an outbound connection to the Mist cloud via TCP port 2200 or 443.

Upon successful connection, the switch's status changes from "Unassigned" to "Connected" in the Mist dashboard. This transition allows the Mist AI engine to begin collecting telemetry, monitoring Service Level Expectations (SLEs), and performing automated troubleshooting. While the adoption process allows for "monitoring only" mode to avoid disrupting existing services, it is the fundamental first step for transitioning legacy Juniper infrastructure into a modern, cloud-managed Wired Assurance environment. This workflow is essential for organizations looking to leverage Marvis AI and automated operations without having to factory-reset their entire existing network.

According to Juniper Mist documentation, the EX2300, EX4650, and QFX5120 switches require a specific additional workflow within the Mist portal to form a Virtual Chassis because these models do not have dedicated Virtual Chassis ports (VCPs). Unlike other EX-series models (such as the EX4100 or EX4400) that possess factory-defined, dedicated VCPs and can form a Virtual Chassis automatically upon physical connection, these three platforms require an administrator to explicitly initiate the "Form Virtual Chassis" action from the Mist UI.

This workflow is necessary because the system must logically convert standard network uplink ports into Virtual Chassis ports to enable stack communication. To execute this, the switches must first be onboarded to the Juniper Mist cloud as standalone devices and assigned to the same site. Once they are online and their configuration is managed by Mist, the administrator selects the desired members from the switch inventory and clicks More > Form Virtual Chassis.

During this additional workflow, the Mist portal prompts the user to specify which front-panel ports will be repurposed as VCPs and allows for the manual assignment of member IDs and Routing Engine roles. This "pre-provisioned" method ensures a deterministic setup where roles are not left to chance. Once the command is pushed, the switches reboot to reconfigure their internal hardware logic to treat the selected ports as fabric links. Juniper emphasizes that for these specific models, the "Form Virtual Chassis" option is the only supported way to establish the stack within Wired Assurance, as it ensures that the cloud-native management plane correctly recognizes the multiple physical chassis as a single logical entity.

Juniper Mist uses open, cloud-native APIs to providereal-time telemetry and integration.

Data is collected and streamed from the backend using:

RESTful APIs– for configuration, automation, and reporting.

Webhooks– to push events, alerts, or SLE changes to third-party systems.

When a switch is successfully onboarded into Mist Cloud but shows“Unassigned,”it means the device has been claimed into the organization but hasnot yet been assigned to a specific site.

“After claiming switches into an organization, you must assign each switch to a site for it to transition from Unassigned to Connected state and begin receiving configuration and telemetry updates.”

Option A:Incorrect — rescanning is not needed once the device is claimed.

Option B:Incorrect — reboots are unnecessary for assignment recognition.

Option C:Incorrect — these commands are for connectivity troubleshooting, not site assignment.

Option D:Correct— assigning each switch to itsintended siteenables full Mist management and connectivity state.