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

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 : B, C, D

For greenfield 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.

Juniper Mist AI for Wired -- Switch Onboarding and Claiming Guide

Juniper Mist AI Cloud -- Greenfield Deployment and Automation Documentation

Juniper Mist Wired Assurance -- API-Based Device Provisioning

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 : B

The Post-Install (Installer) role has minimal access---sufficient only to claim APs or switches, assign or unassign them, and place them on maps.

It cannot unclaim or remove devices and typically expires after installation.

Mist AI Mobile App Documentation -- Installer and Post-Install Roles

Juniper Mist AI Access Control Guide

===========

Answer : B, D

For Juniper cloud-ready EX Series switches (EX2300, EX3400, EX4100, EX4400, etc.) to successfully onboard to the Juniper Mist Cloud, specific connectivity requirements must be met:

''Cloud-managed EX switches require outbound connectivity to the Mist Cloud on TCP ports 2200 or 443. Switches must also have access to DNS services to resolve cloud service URLs during onboarding.''

Option A: Incorrect --- minimum version depends on switch model; older models may onboard with earlier releases (e.g., 20.x, 21.x).

Option B: Correct --- outbound TCP 2200 or 443 connectivity is required for cloud registration.

Option C: Incorrect --- switches connect directly to Mist Cloud, not the Agile Licensing Portal.

Option D: Correct --- DNS resolution is mandatory for discovering Mist Cloud endpoints.

Juniper Mist AI for Wired -- Cloud-Ready Switch Onboarding Requirements

Juniper Mist AI for Wired -- Network Connectivity and Port Usage

Junos OS Documentation -- Mist Cloud Connectivity and Registration

Answer : A

Syslog is the standard method for exporting Mist AI event and telemetry messages to third-party collectors.

It supports both UDP and TCP delivery for centralized log correlation.

Juniper Mist AI for Wired -- Syslog Configuration Guide

Mist AI Operations and Event Forwarding Documentation

Answer : B, C

In an EVPN-VXLAN fabric, the control plane operates over BGP EVPN and is responsible for distributing endpoint reachability information (MAC and IP) among VTEPs. The data plane, by contrast, performs encapsulation and forwarding.

''The EVPN control plane uses BGP to exchange MAC and IP address reachability information between VTEPs, enabling efficient forwarding and loop prevention without relying on flood-and-learn behavior.''

Option A: Incorrect --- encapsulation occurs in the data plane, not the control plane.

Option B: Correct --- the control plane distributes MAC-to-VTEP mappings.

Option C: Correct --- the control plane also distributes IP-to-MAC associations (Type 2 and Type 5 EVPN routes).

Option D: Incorrect --- the control plane does not alter packet headers.

Juniper Mist AI for Wired -- EVPN-VXLAN Overview

Juniper Validated Design -- EVPN Control and Data Plane Operation

Junos OS EVPN-VXLAN Implementation Guide