Juniper Mist AI Wired, Specialist JN0-460 JNCIS-MistAI-Wired Exam Questions

Page: 1 / 14
Total 72 questions
Question 1

You receive a Marvis Action that reports ''Port negotiation mismatch detected on EX3400-48P.''

In this scenario, which two steps should you take to resolve the issue? (Choose two.)



Answer : A, D

A port negotiation mismatch occurs 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 ensuring auto-negotiation is enabled on both ends (A) and verifying the peer device supports the 802.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 Wired Assurance -- Marvis Actions and Insights Guide

Juniper EX Series Switches -- Interface Negotiation Troubleshooting

Question 2

Which campus fabric architecture supports Layer 3 gateways at the distribution layer?



Answer : C

In Juniper's campus fabric architectures, the location of the Layer 3 gateway (IRB) differentiates between CRB and ERB models:

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

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

''In the ERB model, Layer 2 gateways are deployed at the access layer, and Layer 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 the distribution layer in the ERB architecture.


Juniper Mist AI for Wired -- Campus Fabric Architecture Models

Juniper Validated Design -- Core/Distribution CRB vs ERB Gateways

Junos OS EVPN-VXLAN Campus Fabric Deployment Guide

Question 3

What are three ways that data is collected from the Mist backend? (Choose three.)



Answer : A, B, C

Juniper Mist uses open, cloud-native APIs to provide real-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.

WebSockets -- for real-time updates between Mist cloud and clients (dashboards or automation tools).

These methods support seamless integration and programmability for both Wired and Wireless Assurance.


Question 4

Referring to the exhibit, what is the purpose of the Save button in the upper-right corner of the Mist dashboard?



Answer : D

In the Juniper Mist AI for Wired dashboard, administrators can select one or more switch ports (as shown in the exhibit, e.g., port ge-0/0/25 on an EX4100-48MP). Once configuration changes are made --- such as VLAN assignment, port profiles, PoE settings, or administrative state --- the Save button must be clicked to confirm and apply those changes to the device.

''When making configuration changes in the Mist switch interface, the Save button must be used to confirm the modifications. Clicking Save applies the selected port settings to the switch through Mist Cloud.''

Option A is incorrect: saving does not create a backup. Backups and snapshots are handled through Mist's configuration archive, not via the Save button.

Option B is incorrect: Save does not reset configuration; instead, it commits changes.

Option C is incorrect: there is no preview function tied to Save.

Option D is correct: the Save button is explicitly for applying configuration changes to the selected switch or port(s).


Juniper Mist AI for Wired -- Switch Port Configuration Guide

Juniper Mist AI for Wired -- Wired Assurance Administration Guide

Juniper Mist Documentation -- Managing Switch Interfaces

Question 5

A switch is claimed in a Mist organization using the activation code.

What are two possible device states that the switch will have in this scenario? (Choose two.)



Answer : A, D

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 as Unassigned if they are not yet linked to a site. Once online and connected to Mist Cloud, they transition to Connected status 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.


Juniper Mist AI for Wired -- Device Claiming and State Management Guide

Juniper Mist Cloud -- Switch Onboarding Workflow

Juniper Mist Wired Assurance -- Device Status Descriptions

Question 6

Which statement is correct about the Switch Insights section?



Answer : A

The Switch Insights section 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 historical traffic 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.


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

===========

Question 7

What are the available Wired Assurance subscriptions for Juniper Mist switches in terms of port numbers?



Answer : C

Juniper Wired Assurance licensing is based on switch port count and supports a range of hardware platforms. Subscriptions are available for 12-port, 24-port, and 48-port models 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 supports 12-, 24-, and 48-port subscription tiers.

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


Juniper Mist AI for Wired -- Licensing and Subscription Guide

Juniper Mist AI Cloud -- Wired Assurance Licensing FAQ

Juniper Networks EX Series -- Licensing and Port-Based Subscription Matrix

Page:    1 / 14   
Total 72 questions