JN0-460 Exam Dumps - JNCIS-MistAI-Wired

InJuniper Mist Cloud, configuration hierarchy includesorganization-level templates,site-level configurations, andindividual switch configuration. Site and organization levels provide shared settings, while per-device details such as hostname or role are set individually.

“Device-specific attributes such as hostname, role, or management IP are configured under the individual switch configuration menu. Templates and site configurations apply globally, while individual configurations override device-level parameters.”

Option A:Incorrect — site configuration applies to all switches at a site, not unique details.

Option B:Incorrect — CLI configuration is not used when switches are managed by Mist Cloud.

Option C:Correct— each switch’s name and role are configured individually underSwitches → Switch Configuration.

Option D:Incorrect — organization templates define global settings, not per-switch names.

Group-Based Policy (GBP)is a Juniper EVPN-VXLAN feature that enablesmicrosegmentationwithout requiring multiple VRFs or VLANs. It is implemented within Juniper Mist’sWired Assurance and Campus Fabricframeworks.

“GBP provides scalable, identity-based segmentation for campus fabrics and is supported on EX4100 and EX4400 Series switches operating in EVPN-VXLAN mode under Mist management.”

The feature requires hardware and software support forEVPN-VXLAN and GBP tagging, which is currently available on specific EX models managed by Mist Cloud.

Option A:Correct— GBP requires compatible access switches, specifically EX4100 and EX4400 models.

Option B:Incorrect — GBP is centrally managed through Mist Cloud, not configured per switch.

Option C:Incorrect — GBP is provisioned via Mist Cloud, not the CLI.

Option D:Incorrect — GBP is not supported onallEVPN-capable switches; only on defined platforms (EX4100/EX4400).

In Juniper Mist Cloud, administrative roles define what actions a user can perform within an organization. The ability to claim and onboard switches is granted to roles that have configuration or deployment privileges.

“Only users with Super User, Network Admin, or Installer roles can claim, onboard, or delete devices such as access points, switches, or gateways within a Mist organization.”

Option A (Network Admin):Correct— can claim and manage network devices.

Option B (Installer):Correct— role specifically intended for device onboarding and site setup.

Option C (Super User):Correct— full administrative privileges including device claiming.

Option D (Observer):Incorrect — view-only access.

Option E (Helpdesk):Incorrect — limited to troubleshooting functions, not device management.

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, 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.

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.

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.

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.