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

Answer : B, D

During campus fabric deployment in Mist AI, switches are onboarded using claim codes and must be assigned to the correct site and online so 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 be online to receive configurations from Mist.

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

Option D: Correct --- switches must be assigned to the correct site for topology creation.

Juniper Mist AI for Wired -- Campus Fabric IP Clos Deployment Guide

Juniper Mist AI for Wired -- Campus Fabric Onboarding Requirements

Juniper Validated Design -- Campus Fabric Claiming and Site Assignment

===========

Answer : C

Juniper Mist supports a hierarchical 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 apply common system-level settings (e.g., NTP, SNMP, DNS, syslog) across multiple sites, the correct method is to use an organization-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 Mist AI for Wired -- Configuration Hierarchy and Templates

Juniper Mist AI for Wired -- Multi-Site Configuration Guide

Juniper Mist AI Cloud -- Organization and Site Management

===========

Answer : C

Juniper's official Campus Fabric IP Clos design for Mist Wired Assurance defines that the 3-stage IP Clos topology eliminates the traditional distribution layer entirely. 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 the core 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 configured between layers, and in the case of the 3-stage design (with no distribution), this means between the core and access devices:

''The point-to-point links between each layer utilize /31 addressing to conserve addresses.''

Therefore, the correct statement is C: The core layer is connected to the access layer.

Options A and B incorrectly mention a distribution layer that does not exist in this topology.

Option D is incorrect because core (spine) devices in a Clos fabric are not interconnected with each other.

Juniper Mist AI for Wired -- Campus Fabric IP Clos Architecture Guide

Juniper Mist AI for Wired -- Campus Fabric IP Clos Workflow

Juniper Mist AI for Wired -- Configure Campus Fabric IP Clos

Juniper Validated Design -- Campus Fabric IP Clos Deployment Types

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

Answer : A, B

Dynamic Packet Capture (DPC) requires no manual setup.

It is automatically linked to relevant client events on the Insights page, enabling fast root-cause analysis without extra configuration.

Mist AI for Wired -- Dynamic Packet Capture Overview

Mist Insights and Troubleshooting Guide

Answer : C, D

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

''BUM traffic in EVPN-VXLAN fabrics is replicated using either ingress replication or underlay 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 the control plane, not a data-plane forwarding method.

Option C: Correct --- Ingress replication replicates 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.

Juniper Mist AI for Wired -- EVPN-VXLAN Forwarding Architecture

Junos OS EVPN-VXLAN Deployment and Operations Guide

Juniper Validated Design -- EVPN-VXLAN Control and Data Plane Behavior

Answer : D

When Marvis Actions display ''AI Validated,'' it indicates the issue was detected earlier but is now resolved.

Marvis automatically validates remediation and marks the action closed once the anomaly clears.

Mist AI Marvis Virtual Network Assistant Documentation -- Marvis Actions and Status Definitions

===========