JN0-460 JNCIS-MistAI-Wired Questions and Answers

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.

In Juniper Mist role-based access control (RBAC),site-level administratorshave limited privileges to manage devices within their assigned sites.

They cannot modify organization-level templates or global settings but can performoperational tasks, includingrebooting APs or switchesand monitoring their status.

This ensures proper delegation of duties while maintaining centralized configuration control.

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.

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.

EVPN, when used with VXLAN, leveragesBGP MPLS/VXLAN control plane mechanisms. To prevent overlapping IP prefixes between different tenants or sites, EVPN uses aRoute Distinguisher (RD).

“In EVPN-VXLAN, the route distinguisher (RD) makes routes unique when overlapping IP prefixes or MAC addresses are advertised between multiple tenants or sites.”

Option A(designated forwarder) applies to multi-homing in EVPN, not prefix uniqueness.

Option B(Layer 2 gateway) does not prevent IP overlap; it bridges VLANs.

Option D(ESI) is used for identifying multi-homed Ethernet segments, not to differentiate overlapping subnets.

Option C(Route Distinguisher) is correct, as it uniquely identifies routes even if the IP addresses are the same across sites.

According to Juniper documentation, a route distinguisher (RD) is a critical address qualifier used to ensure that network layer reachability information (NLRI) remains unique within a Multiprotocol BGP (MP-BGP) control plane, especially in multitenant environments. In a service provider network, different tenants may use identical, overlapping private IP address spaces (such as 192.168.1.0/24). If these routes were advertised without a qualifier, BGP—which typically only considers the IP prefix—would treat them as the same route and potentially overwrite one with the other based on standard BGP best-path selection.

The route distinguisher solves this by prepending an 8-byte field to the tenant's IP address, effectively transforming a 32-bit IPv4 prefix into a unique 96-bit VPN-IPv4 address. This 8-byte value is typically configured in formats such as as-number:number or ip-address:number. Because the resulting VPN-IPv4 prefix is unique to that specific routing instance, the service provider's BGP infrastructure can carry and distinguish between overlapping routes from multiple customers simultaneously.

It is important to differentiate the RD from a route target (RT). While the RD's sole purpose is to provide uniqueness so that routes are not discarded or overwritten, the route target is an extended community attribute used to control the import and export of these routes into the correct virtual routing and forwarding (VRF) tables on remote PE routers. In Juniper's Junos OS, each routing instance of type vrf or evpn must have a unique RD associated with it; failing to configure a unique RD or attempting to use the same RD across different instances will result in a configuration commit failure. This fundamental separation of "making routes unique" (RD) and "directing routes to the right place" (RT) allows for the scalable, isolated multitenancy required in modern EVPN-VXLAN campus and data center fabrics.

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.

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.

Juniper Mist AI for Wired uses group-based policy (GBP) to enforce segmentation within a single VRF, without requiring separate VRFs per user group. GBP tags classify endpoints logically (e.g., employees, guests, IoT devices) and enforce security rules across the EVPN-VXLAN fabric.

“Group-Based Policy (GBP) provides scalable segmentation by assigning tags to endpoints based on attributes such as user type, role, or device type. These GBP tags are then used in policies to control communication between groups.”

Option A is inefficient: assigning unique tags per endpoint is not scalable.

Option C is incorrect: GBP is identity-based segmentation, not location-based.

Option D is incorrect: assigning a single tag defeats the purpose of segmentation.

Option B is correct: the best practice is to assign GBP tags based on endpoint type (e.g., servers, staff, IoT, guests), which then drives policy enforcement.

Within Mist Insights,Client Eventsshow state transitions such asreassociationand IP-level issues likeDHCP Denied.

These help correlate connectivity issues across wired or wireless edge connections.

According to theJuniper Mist AI for Wired – Campus Fabric IP Clos Deployment Workflow, deploying a campus fabric involves a defined sequence of planning and configuration steps within the Mist Cloud interface. The key stages include:

“To deploy a campus fabric, you must first define the topology type, identify the physical connections between devices, and define the networks of interest that will be extended across the fabric.”

Breaking this down:

Choose the topology (D):Selecting the correct fabric type (3-Stage or 5-Stage IP Clos) determines how access, distribution, and core switches will interconnect.

Define the physical connections (A):This step involves specifying the uplink and downlink relationships between switches so that Mist can auto-generate EVPN-VXLAN and routing configurations.

Define the networks of interest (B):These are the VLANs and subnets that need to be extended across the fabric for user and device connectivity.

Steps such asconfiguring DNS serversordefining GBP tagsarenot part of the campus fabric deployment workflowin Mist Wired; they are optional or separate configurations outside the main deployment flow.

Juniper Mist Cloud uses anopen RESTful API frameworkfor integration, automation, and programmability across all Mist services, includingWired Assurance,Marvis, andAI-driven automation.

“All Mist Cloud services are built on a 100% open REST API framework, allowing customers to automate configuration, monitoring, and troubleshooting through standard REST calls.”

The REST API exchanges data inJSONformat, but the API type itself isREST, not JSON.

Option A (REST):Correct— Mist services expose 100% REST-based APIs.

Option B (SOAP):Incorrect — SOAP is an older XML-based protocol not used in Mist.

Option C (JSON):Incorrect — JSON is thedata format, not the API type.

Option D (RPC):Incorrect — not used in the Mist Cloud architecture.

In acore-distribution campus fabricmodel, the EVPN-VXLAN overlay is establishedonly between the core and distribution tiers. Theaccess switches are not part of the EVPN fabric; they connect upstream to distribution but do not run VXLAN tunnels.

“In the core-distribution campus fabric, only the core and distribution layers participate in the EVPN-VXLAN topology. The access layer connects to the distribution switches and forwards traffic but does not take part in the EVPN-VXLAN fabric.”

Option A:Correct — EVPN-VXLAN is built between core and distribution tiers.

Option B:Incorrect — both coreand distributionparticipate, not just core.

Option C:Incorrect — access switches are excluded from EVPN-VXLAN participation.

Option D:Correct — the access layer does not participate in EVPN-VXLAN.

VXLAN (Virtual Extensible LAN) uses an overlay encapsulation method to carry Layer-2 frames over an IP underlay. This functionality is part of the data plane, which is responsible for packet forwarding and encapsulation/decapsulation.

“In an EVPN-VXLAN fabric, the control plane (via BGP EVPN) learns and advertises MAC and IP information, while the data plane encapsulates and forwards traffic using VXLAN tunnels between VTEPs.”

Option A is incorrect: IP learning happens in the control plane, not the data plane.

Option B is incorrect: MAC advertisement is done in the control plane through EVPN route types.

Option D is incorrect: MAC learning is handled by EVPN control plane, not the VXLAN data plane.

Option C is correct: the VXLAN data plane encapsulates the traffic in UDP tunnels between VTEPs.

Creating a new site requires asite nameandtime zone.

Other parameters (like templates or location data) are optional but recommended for proper reporting.

According to the provided exhibit, several visual indicators confirm the operational status and compliance of the EX4100-48MP switch within the Juniper Mist dashboard1.

First, the statement that PoE is enabled is verified by multiple sections of the dashboard2. In the Front Panel view, several ports display a green icon representing a wireless access point, and the PoE status indicator in the top right is lit green, indicating the subsystem is active. Furthermore, the Statistics panel shows a "Total Power Draw" of 48.40 W, and the Metrics section displays "100% PoE Compliance," confirming that the switch is successfully delivering Power over Ethernet to connected devices such as the three Mist APs listed in the summary.

Second, the exhibit indicates that the Junos OS version on this switch is not compliant with the other switches in the site5. This is explicitly shown in the Metrics section, where the Version Compliance tile is highlighted in red with a value of 0%6. In the Mist AI-driven interface, a red compliance tile signifies that the current software version running on the device (identified as 23.2R1.13 in the Properties panel) does not match the "Configured Version" or the "Approved Version" set at the Site or Organization level.

The other options are incorrect based on the visual evidence. While Mist APs are connected, the Front Panel shows them connected to 2.5GbE (mGig) ports (ports 0, 2, 8, etc.) and standard 1GbE ports, not specifically just "ge" interfaces in a traditional sense8. Additionally, the 0% Version Compliance score directly contradicts the idea that the switch is compliant with the organization's standards.

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.

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.

Juniper Mist AI collectstelemetry for Service Level Expectations (SLEs)across wired and wireless devices. This telemetry includes metrics such as time-to-connect, throughput, coverage, and switch performance.

“Service Level Expectation (SLE) data is collected from every device and stored for up toone monthin the Mist Cloud. This allows administrators to analyze historical performance trends and troubleshoot issues based on real-time and historical data.”

Option B (2 months):Incorrect — data is not retained this long.

Option C (7 days):Incorrect — telemetry retention is longer.

Option D (24 hours):Incorrect — too short for Mist SLE analytics.

Option A (1 month):Correct — Mist Cloud retains SLE telemetry for30 days (1 month).

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.

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.