Juniper JN0-460 JNCIS-MistAI-Wired Exam Practice Test

Dynamic Port Configuration (DPC)in Juniper Mist enablesautomatic switch port configurationbased on connected device type (e.g., phones, access points, printers). When setting up DPC, administrators define thematching criteria(such as MAC OUI or LLDP system name) and associate aConfiguration Profilethat determines which settings are applied.

“To configure Dynamic Port Configuration, you must assign the ports where DPC will run and select the configuration profile that defines how the port will be automatically configured when a matching device is detected.”

Option A:Correct— you must select the configuration profile to apply once the device type matches.

Option B:Incorrect — DPC does not use polling; it reacts to real-time LLDP/device discovery.

Option C:Correct— you must assign the ports on which DPC operates.

Option D:Incorrect — DPC is supported across EX models running compatible firmware but does not require manually setting a Junos version in configuration.

Anorganization-level configuration templatecan only be applied tosite groups, not to individual sites.

Therefore, a single site such as Site A cannot be directly specified inside an org-level template.

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

Marvis is Juniper’s Virtual Network Assistant (VNA) that leverages AI to provide natural language queries, anomaly detection, and proactive troubleshooting across wireless, wired, and WAN networks.

“Marvis, the AI-driven Virtual Network Assistant, requires a Virtual Network Assistant subscription. The subscription enables Marvis to provide insights, recommendations, and natural language queries for Mist-managed networks.”

Option A (Access Assurance) is related to NAC/802.1X enforcement.

Option B (IoT Assurance) applies to profiling and securing IoT devices.

Option D (Wired Assurance) enables switch telemetry, onboarding, and assurance, but does not unlock Marvis.

Option C (Virtual Network Assistant) is correct — this subscription is required to enable Marvis AI.

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.

In Mist,sitesrepresent the physical or logical grouping of devices within an organization.

You create and manage a site configuration under theLocationhierarchy in the Mist UI.

Each site inherits organization-level settings but can override or customize specific configurations such as VLANs, templates, or switch settings.

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.

Link Layer Discovery Protocol (LLDP)is a Layer 2 discovery protocol that allows network devices to advertise identity and capabilities to directly connected neighbors. While LLDP is useful for basic topology discovery, it has two key limitations inWired Assurance client identification:

“LLDP operates at Layer 2 between directly connected devices and must be explicitly enabled on all participating network elements to provide neighbor information. It cannot discover devices beyond the first physical hop.”

Option A:Correct— LLDP must beconfigured and enabledon each network device to function.

Option B:Incorrect — LLDP itself is scalable but limited to direct adjacency.

Option C:Correct— LLDP only worksbetween directly connected devices.

Option D:Incorrect — not all clients support LLDP; however, the question asks forlimitations of using LLDP, not lack of support.

Dynamic Packet Capture (DPC)requires no manual setup.

It is automatically linked to relevantclient eventson theInsights page, enabling fast root-cause analysis without extra configuration.

Abrownfield adoptionin Mist AI refers to onboarding existing Juniper switches (with existing configurations) into the Mist Cloud for management and monitoring. For the switch to connect successfully, it must be able to reach Mist Cloud services usingDNSandInternet connectivity.

“To onboard existing (brownfield) switches into Mist Cloud, the device must have outbound Internet connectivity and DNS resolution to discover Mist Cloud service endpoints.”

Option A:Correct— DNS is required for the switch to resolve Mist Cloud URLs.

Option B:Correct— Internet access is required for registration and telemetry exchange.

Option C:Incorrect — templates can be applied later but are not required for adoption.

Option D:Incorrect — Mist uses TCP ports 2200 or 443, not UDP 1280.

RadSec(RADIUS over TLS) enhances traditional RADIUS authentication security by encapsulating RADIUS messages withinTCP and TLSinstead of UDP.

This ensures encrypted, reliable, and authenticated transmission between network devices (such as Juniper EX switches) and RADIUS servers.

It is often used in modernMist-managed wired networksto securely integrate withAccess Assuranceor external authentication systems.

According to Juniper Mist documentation regarding campus fabric design, the campus fabric IP Clos (also known as a 5-stage Clos) is the architecture that extends the EVPN-VXLAN protocol stack from the core tier down through the distribution tier and finally to the access tier. In this model, every switch in the hierarchy—from the high-capacity core switches to the wiring closet access switches—participates in the EVPN control plane and VXLAN data plane.

By extending EVPN-VXLAN to the access tier, the IP Clos architecture provides a standards-based, scalable framework that allows for seamless Layer 2 connectivity over a Layer 3 underlay across the entire campus333333333. This enables advanced features like Microsegmentation using Group-Based Policies (GBP) and Macrosegmentation via Virtual Routing and Forwarding (VRF) instances directly at the edge of the network.

In contrast, other architectures like "core-distribution" (either CRB or ERB) typically limit the EVPN-VXLAN fabric to the core and distribution layers, leaving the access tier to connect via traditional methods like LAG, Virtual Chassis, or standard Layer 2 trunks5555. The IP Clos architecture is specifically designed for large-scale deployments where high density, vendor interoperability, and end-to-end policy enforcement are critical6. By utilizing a 5-stage IP Clos, organizations can eliminate the complexities of Spanning Tree Protocol (STP) while maintaining a flexible, "any-to-any" communication path throughout the physical infrastructure.

InMist Cloud,site variablesare used to store and reference common configuration values (such as VLAN IDs, subnet addresses, or gateway IPs) that are reused across multiple devices and templates within a site.

“Site variables allow administrators to define reusable configuration parameters that can be referenced in multiple templates or device configurations, ensuring consistency and reducing manual errors.”

Option A:Incorrect — applies configuration directly, not reusable references.

Option B:Correct— site variables enable you to reference the same VLAN or value in multiple configurations (switches, WLANs, etc.).

Option C:Incorrect — WLAN templates are for wireless SSID configuration.

Option D:Incorrect — switch templates define static configuration but don’t store shared variables.

In theJuniper 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 — theSave buttonmust 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 Ais incorrect: saving does not create a backup. Backups and snapshots are handled through Mist’s configuration archive, not via the Save button.

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

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

Option Dis correct: the Save button is explicitly forapplying configuration changesto the selected switch or port(s).

According to Juniper’s Validated Designs (JVD) for campus fabrics, the Campus Fabric IP Clos (often referred to as a 5-stage Clos) is the architecture specifically engineered for high-scale environments supporting 10,000+ users. This design is characterized by extending the EVPN control plane and VXLAN data plane all the way to the access layer. By terminating VXLAN tunnels at the access switch—functioning as a Virtual Tunnel Endpoint (VTEP)—the network can seamlessly support both Layer 2 and Layer 3 devices directly at the edge of the fabric.

The primary driver for choosing IP Clos in large-scale deployments is its superior scalability. In this model, the core switches are shielded from the massive table sizes required to learn thousands of individual endpoint MAC and IP addresses. Instead, core devices only need to maintain reachability to the loopback addresses of the access layer switches. This reduction in the "flood and learn" pressure on the core is critical as the number of endpoints grows, ensuring that the core can scale far into the future with predictable growth.

Additionally, the IP Clos architecture provides the most flexible environment for microsegmentation using Group-Based Policies (GBP) and macrosegmentation using Virtual Routing and Forwarding (VRF) instances. Since routing occurs at the access device, "east-west" traffic between local endpoints remains efficient and does not need to traverse the distribution or core tiers. While EVPN Multihoming and Core-Distribution (CRB/ERB) models are effective for smaller sites or brownfield environments where access switches are legacy Layer 2-only devices, only the IP Clos architecture provides the end-to-end VXLAN capability required for high-density, future-proof campus fabrics.

Juniper Mist Wired AssuranceprovidesAI-driven operational visibilityfor EX and QFX switches. It defines and tracksService Level Expectations (SLEs)across multiple performance areas including connectivity, throughput, and switch health.

“Wired Assurance uses AI and telemetry to deliver operational visibility, track service level expectations (SLEs), and monitor throughput, successful connects, and switch health through pre- and post-connection metrics.”

Option A:Correct— accurately describes the full scope of Wired Assurance.

Option B:Incorrect — Wired Assurance provides SLEs specifically for EX and QFX switches.

Option C:Incorrect — both pre- and post-connection SLEs are monitored.

Option D:Incorrect — Wired Assurance monitors both connectivity and device health.

During campus fabric deploymentin Mist AI, switches are onboarded usingclaim codesand must beassigned to the correct siteandonlineso 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 beonlineto receive configurations from Mist.

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

Option D:Correct— switches must beassigned to the correct sitefor topology creation.

Mistwebhooksprovide real-time integration with external systems by streamingalertsandSLE (client) metrics.

They allow automation tools to react immediately to network health or performance changes.

Juniper Mist supports ahierarchical 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 applycommon system-level settings(e.g., NTP, SNMP, DNS, syslog) across multiple sites, the correct method is to use anorganization-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.

According to Juniper Networks' documentation on campus fabric and EVPN-VXLAN architectures, a Virtual Routing and Forwarding (VRF) instance—conceptually referred to within the Junos OS as a routing instance—is typically used to provide macro-segmentation by logically separating a single physical network into multiple, isolated virtual networks.2 In the context of a modern campus fabric managed by Juniper Mist, VRFs allow network administrators to create distinct routing domains that maintain their own independent routing and forwarding tables.3

This separation is essential for multitenancy and security.4 For example, an organization might use one VRF for "Corporate_IT" and another for "Guest_WiFi" or "IoT_Devices". Because each VRF operates with its own routing table, traffic belonging to one instance is completely isolated from traffic in another by default; packets cannot travel between VRFs unless an administrator explicitly configures "route leaking" or directs the traffic through a stateful firewall for security inspection. This architectural approach also permits the use of overlapping IP address spaces, as the routing decisions for one tenant do not interfere with the address entries of another.5

In a Juniper Mist-driven campus fabric (such as Core-Distribution or IP Clos), the Mist portal streamlines the creation of these VRF instances as part of the fabric workflow.6 Once a VRF is created, specific VLANs (and their corresponding IRB interfaces) are assigned to it, ensuring that Layer 3 gateways are placed in the correct logical domain. While the underlay network (Option D) is responsible for providing the physical reachability (loopback to loopback) between switches using a protocol like eBGP, the overlay network leverages VRFs to deliver the actual isolated user services.

Juniper Mist automatically classifies ports to simplify visibility and automation withinWired Assurance. The Mist cloud analyzesport telemetryandlink behaviorto determine port roles, including uplinks.

“Mist uses machine learning and switch telemetry to automatically detect uplinks by analyzing traffic behavior and topology information. Uplink ports typically exhibit higher TX/RX utilization and are identified as spanning-tree root or forwarding ports connecting upstream devices.”

Option A:Correct — Mist examines traffic statistics. Ports with significantly higher TX/RX utilization relative to others are likely uplinks.

Option B:Incorrect — MTU size is not a classification criterion.

Option C:Correct — Mist usesSTP information(root or designated port status) to identify uplinks.

Option D:Incorrect — port description fields are for administrative purposes only and are not used by Mist analytics.

The exhibit shows:

L2 gateways (blue dots)positioned at the distribution layer.

L3 gateways (red dots)positioned at thecore layer.

EVPN/VXLAN providing fabric connectivity between layers.

Access switches forwarding traffic into the fabric without acting as gateways.

This directly maps to thecentrally-routed bridging (CRB)model, where:

Bridging occurs at the access/distribution layer.

Routing (L3 gateway) occurs centrally at the core layer.

“In the core-distribution CRB model, Layer 2 gateways are deployed at the distribution switches, and Layer 3 gateways are deployed centrally at the core switches.”

Option A (ERB)is incorrect because ERB places the L3 gateway at the edge/access.

Option B (5-stage IP Clos)is incorrect — that topology has a leaf/spine architecture, not core/distribution.

Option C (3-stage IP Clos)is incorrect — that eliminates the distribution layer.

Option D (CRB)is correct, matching the diagram exactly.

WhenMarvis Actionsdisplay “AI Validated,” it indicates the issue was detected earlier but is nowresolved.

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

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.