JN0-460 JNCIS-MistAI-Wired Questions and Answers

In Juniper Mist Cloud, there are multiple configuration scopes:

Organization-level templatesapply globally.

Site-level configurationapplies across all devices in a site.

Individual switch configurationis used to define unique, device-specific attributes such ashostname, management IP, or local overrides.

“Templates and site-level configuration ensure consistency across devices, whileindividual switch configuration is used to assign unique values such as hostnames.”

Option A:Incorrect — org templates define common config, not hostnames.

Option B:Incorrect — site configs are shared across all switches in the site.

Option D:Incorrect — device profiles apply settings like port policies or authentication, not hostnames.

Option C:Correct —individual switch configurationis the correct place to assign hostnames uniquely per device.

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.

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.

InJuniper Mist Wired Assurance, SLEs (Service Level Expectations) measure key performance indicators for wired network quality.Throughput SLEmonitorsdata transfer quality, includinglatency, jitter, and packet loss, which directly impact real-time applications such as voice or video.

“The Throughput SLE provides visibility into end-to-end network performance by tracking latency, jitter, and packet loss, helping identify congestion or quality issues across wired connections.”

Option A (Throughput):Correct— this SLE includes jitter measurement.

Option B (Successful Connect):Tracks client connection success rate, not jitter.

Option C (Capacity):Monitors link utilization and load, not jitter.

Option D (Switch Health):Monitors device hardware and software health, not traffic performance.

Aport negotiation mismatchoccurs when the local and remote interfaces fail to agree on common speed or duplex settings.

Marvis Wired Assurance automatically detects this by analyzing telemetry from the switch’s physical interfaces.

You can resolve this by ensuringauto-negotiationis enabled on both ends (A) and verifying the peer device supports the802.3 autonegotiation standard(D).

Manually forcing half-duplex or replacing hardware is unnecessary unless the hardware is faulty.

“Marvis Wired Actions correlate interface negotiation errors with LLDP neighbor data to pinpoint mismatched configurations, helping administrators quickly verify speed/duplex compatibility and 802.3 autonegotiation support.”

Juniper Mist defines both3-stageand5-stage IP Closarchitectures for campus and data-center fabrics. The5-stage IP Closdesign adds scalability by introducingspineandsuper-spinelayers above the leaf layer, enabling large campus or aggregation environments.

“The 5-stage IP Clos topology extends the 3-stage design by introducing spine and super-spine tiers. It is ideal for large campus environments requiring additional capacity and hierarchical scaling.”

Option A:Incorrect — Clos is a topology, not a routing protocol.

Option B:Incorrect — VXLAN/EVPN encapsulation operates over Clos but does not define it.

Option C:Incorrect — that describes a traditional three-tier campus (core/distribution/access), not a Clos.

Option D:Correct— the5-stage IP Closis a hierarchical, scalable Clos topology withspine and super-spinelayers used in large campus or data-center networks.

In Juniper Mist campus fabric architectures, thelocation of the Layer 3 gateway (IRB interface)differentiatescentrally-routed bridging (CRB)fromedge-routed bridging (ERB):

InCRB, thegateway resides at the core layer— routing occurs centrally, and access/distribution layers perform Layer 2 bridging.

InERB, thegateway moves to the edge (distribution layer), enabling routing to occur closer to endpoints, improving performance and scalability.

“In a centrally-routed bridging (CRB) topology, Layer 3 gateways reside at the core. When transitioning to an edge-routed bridging (ERB) design, the Layer 3 gateways are moved to the distribution layer, closer to the access switches and clients.”

Therefore, when moving from acore-distribution CRBto anERBmodel, thegateway moves from the distribution to the access layerin campus terms (edge = access).

Option A:Incorrect — ERB gateways are not at the distribution layer only.

Option B:Incorrect — opposite direction.

Option C:Correct— the gateway movesfrom distribution to access (edge).

Option D:Incorrect — this describes CRB, not ERB.

Juniper Mist supports ahierarchical configuration model:

Organization level:global configuration templates applied across sites.

Site level:shared configuration for all devices in a site.

Individual device level:unique overrides.

To applycommon system-level settings(e.g., NTP, SNMP, DNS, syslog) across multiple sites, the correct method is to use anorganization-level template.

“Organization-level templates provide a consistent configuration framework that can be applied across multiple sites, ensuring uniform system settings for all switches.”

Option A:Incorrect — manual CLI configuration defeats automation.

Option B:Incorrect — applies only to one site, not multiple.

Option C:Correct— organization-level templates provide centralized configuration for all sites.

Option D:Incorrect — individual configuration is for unique settings only.

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.

According to the Juniper Mist dashboard's firmware management interface shown in the exhibit, several key details of the switch upgrade process are visible. The "Upgrade switch firmware" dialog box is a standard component of Juniper Mist Wired Assurance used to manage Junos OS updates across the fabric.

The correct statement is that the switch will reboot after the upgrade. This is explicitly confirmed by the checkbox labeled "Reboot switch after image copy," which is currently selected in the exhibit. In Juniper's cloud-managed workflow, once the new software image is successfully transferred from the Mist cloud to the switch's local storage, the system requires a reboot to initialize the new Junos OS kernel and complete the installation process5. While some platforms support non-disruptive upgrades, the standard procedure for EX-series switches in a standalone or Virtual Chassis configuration typically involves a scheduled reboot to ensure the new version is correctly applied.

The other options are incorrect based on the visual evidence provided in the exhibit.

Option A: The exhibit clearly identifies the "Switch Model" as an EX2300-C-12P (the 'P' designating PoE support), not an EX2300-C-12T88.

Option C: The dialog box explicitly states "Total Switches selected to upgrade: 1," confirming this is a single-device operation rather than a bulk upgrade.

Option D: The "Upgrade to Version" field is set to 19.3R1.8, which indicates the target version, not the previous version10101010.

By providing these granular controls, Juniper Mist allows administrators to maintain strict version compliance across the site while choosing whether to immediately reboot or stage the image for a later maintenance window.

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.

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.

According to Juniper Networks' validated designs for campus fabrics, the campus fabric core-distribution with edge-routed bridging (ERB) is the optimal architecture when high volumes of east-west traffic are present and access switches are restricted to Layer 2 operations. In an ERB design, the EVPN-VXLAN fabric extends from the core switches to the distribution switches.1 The critical differentiator is the placement of the default gateways (Integrated Routing and Bridging or IRB interfaces). In the ERB model, these gateways are moved from the core to the distribution layer, which effectively acts as the "edge" of the EVPN fabric.

By placing the Layer 3 gateways at the distribution layer, inter-VLAN (east-west) traffic is routed closer to the endpoints.2 This prevents the "hairpinning" effect found in Centrally-Routed Bridging (CRB) architectures, where traffic must travel all the way to the core layer to be routed between subnets before returning down to the distribution and access layers. This reduction in latency and core-link utilization is essential for modern campus environments with high server-to-server or client-to-client traffic patterns.

Furthermore, this architecture specifically accommodates Layer 2 access switches. In the ERB core-distribution model, the access switches are not part of the EVPN-VXLAN overlay; instead, they connect to the distribution tier using standard Link Aggregation Control Protocol (LACP) or ESI-LAG. This allows organizations to leverage existing legacy or lower-tier access switches that do not support advanced VXLAN capabilities while still benefiting from a robust, scalable EVPN-VXLAN fabric at the distribution and core layers.5 In contrast, while the campus fabric IP Clos also excels at handling east-west traffic, it requires the access switches themselves to perform VXLAN encapsulation/decapsulation (acting as VTEPs), which contradicts the requirement for access switches to operate only at Layer 2.

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.

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.

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.

During campus fabric deploymentin Mist AI, switches are onboarded usingclaim codesand must beassigned to the correct siteandonlineso that Mist can push configurations and validate connectivity.

“All switches to be included in a campus fabric must be claimed, online, and assigned to the target site before launching the Campus Fabric wizard. Mist Cloud automatically discovers their roles and builds the topology.”

Option A:Incorrect — switches must be site-assigned before fabric creation.

Option B:Correct— switches must beonlineto receive configurations from Mist.

Option C:Incorrect — offline devices cannot be configured or validated in the fabric wizard.

Option D:Correct— switches must beassigned to the correct sitefor topology creation.

Juniper Mist is built on a fully open andRESTful API architecture, allowing programmatic access to all functions.

Administrators and developers can automate switch provisioning, monitoring, and troubleshooting directly via the REST API.

This open design supports JSON data formatting and HTTPS authentication, ensuring secure integration with external systems.

The exhibit shows:

L2 gateways (blue dots)positioned at the distribution layer.

L3 gateways (red dots)positioned at thecore layer.

EVPN/VXLAN providing fabric connectivity between layers.

Access switches forwarding traffic into the fabric without acting as gateways.

This directly maps to thecentrally-routed bridging (CRB)model, where:

Bridging occurs at the access/distribution layer.

Routing (L3 gateway) occurs centrally at the core layer.

“In the core-distribution CRB model, Layer 2 gateways are deployed at the distribution switches, and Layer 3 gateways are deployed centrally at the core switches.”

Option A (ERB)is incorrect because ERB places the L3 gateway at the edge/access.

Option B (5-stage IP Clos)is incorrect — that topology has a leaf/spine architecture, not core/distribution.

Option C (3-stage IP Clos)is incorrect — that eliminates the distribution layer.

Option D (CRB)is correct, matching the diagram exactly.

InJuniper Mist AI for Wired, configuration templates are a foundational part ofswitch onboarding and management. The primary purpose of these templates is to ensure configuration consistency across all switches that belong to a specific site or organization.

“Switch configuration templates allow administrators to define a standard configuration that is automatically applied to all switches within a site or organization, ensuring consistency and reducing configuration errors.”

Templates can contain base configuration parameters such as NTP, syslog, VLANs, port profiles, and authentication settings. When new switches are onboarded to the Mist Cloud, they automatically inherit the template’s configuration, ensuring uniform behavior across the network fabric.

Option Ais incorrect — templates do not directly impact hardware performance.

Option Bis incorrect — templates are not related to upgrade times.

Option Cis incorrect — templates are used for uniformity, not for switch-specific changes.

Option Dcorrectly describes their main benefit —ensuring consistent configuration across all switches.

In Mist,sitesrepresent the physical or logical grouping of devices within an organization.

You create and manage a site configuration under theLocationhierarchy in the Mist UI.

Each site inherits organization-level settings but can override or customize specific configurations such as VLANs, templates, or switch settings.

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.