Juniper jn0-460 practice test
Mist AI Wired, Specialist (JNCIS-MistAI-Wired)
Question 1
Which statement is correct about a 3-stage campus fabric IP Clos?
- A. The distribution layer is connected to the access layer.
- B. The distribution layer is connected to the core layer.
- C. The core layer is connected to the access layer.
- D. The core layer devices are connected to each other.
Answer:
C
Explanation:
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.
Reference:
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
Question 2
Which three steps should be part of the campus fabric deployment? (Choose three.)
- A. Define the physical connections.
- B. Define the networks of interest.
- C. Configure the DNS server.
- D. Choose the topology.
- E. Configure the group-based policy (GBP) tag.
Answer:
A, B, D
Explanation:
According to the Juniper 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 as configuring DNS servers or defining GBP tags are not part of the campus fabric
deployment workflow in Mist Wired; they are optional or separate configurations outside the main
deployment flow.
Reference:
Juniper Mist AI for Wired – Campus Fabric IP Clos Deployment Workflow
Juniper Mist AI for Wired – Configure Campus Fabric IP Clos
Juniper Validated Design – Campus Fabric Overview
===========
Question 3
What is the primary benefit of using switch configuration templates?
- A. They improve the performance of switches.
- B. They reduce Junos OS upgrade times.
- C. They make it easier to make switch-specific configuration changes.
- D. They provide a consistent configuration for all switches in an organization.
Answer:
D
Explanation:
In Juniper Mist AI for Wired, configuration templates are a foundational part of switch 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 A is incorrect — templates do not directly impact hardware performance.
Option B is incorrect — templates are not related to upgrade times.
Option C is incorrect — templates are used for uniformity, not for switch-specific changes.
Option D correctly describes their main benefit — ensuring consistent configuration across all
switches.
Reference:
Juniper Mist AI for Wired – Switch Configuration Templates Guide
Juniper Mist AI for Wired – Wired Assurance Administration Guide
Juniper Validated Design – Mist Wired Configuration Best Practices
Question 4
Referring to the exhibit, what is the purpose of the Save button in the upper-right corner of the Mist
dashboard?
- A. It generates a backup of the current port configuration.
- B. It resets the port configuration to its default settings.
- C. It previews the impact of the port configuration changes before applying them.
- D. It applies the port configuration changes to the switch.
Answer:
D
Explanation:
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).
Reference:
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
You have two sites connected to an EVPN network. Each site is using the 172.16.1.0/24 network for
its own respective site.
How does EVPN prevent overlap in this scenario?
- A. It elects a designated forwarder.
- B. It uses a Layer 2 gateway.
- C. It uses a route distinguisher.
- D. It uses an Ethernet segment identifier (ESI).
Answer:
C
Explanation:
EVPN, when used with VXLAN, leverages BGP MPLS/VXLAN control plane mechanisms. To prevent
overlapping IP prefixes between different tenants or sites, EVPN uses a Route 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.
Reference:
Juniper Mist AI for Wired – EVPN-VXLAN Overview
Juniper Validated Design – EVPN-VXLAN Fundamentals
Junos OS EVPN Configuration Guide
===========
Question 6
Click the Exhibit button.
Which campus fabric architecture is shown in the exhibit?
- A. core-distribution – edge-routed bridging (ERB)
- B. 5-stage IP Clos
- C. 3-stage IP Clos
- D. core-distribution – centrally-routed bridging (CRB)
Answer:
D
Explanation:
The exhibit shows:
L2 gateways (blue dots) positioned at the distribution layer.
L3 gateways (red dots) positioned at the core layer.
EVPN/VXLAN providing fabric connectivity between layers.
Access switches forwarding traffic into the fabric without acting as gateways.
This directly maps to the centrally-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.
Reference:
Juniper Mist AI for Wired – Campus Fabric Architecture Guide
Juniper Validated Design – Campus Fabric EVPN-VXLAN Deployment Models
Junos OS EVPN Campus Deployment Examples
Question 7
A company has a Mist campus fabric with a single VRF and must configure group-based policy (GBP)
tags to isolate different types of endpoints.
What would be an appropriate solution for this scenario?
- A. Assign a separate GBP tag to each endpoint.
- B. Assign GBP tags based on endpoint type.
- C. Assign GBP tags based on endpoint location.
- D. Assign a single GBP tag to all endpoints.
Answer:
B
Explanation:
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.
Reference:
Juniper Mist AI for Wired – Group-Based Policy (GBP) Configuration Guide
Juniper Validated Design – GBP with EVPN-VXLAN in Campus Fabrics
===========
Question 8
Which subscription is required to use Marvis?
- A. Access Assurance
- B. IoT Assurance
- C. Virtual Network Assistant
- D. Wired Assurance
Answer:
C
Explanation:
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.
Reference:
Juniper Mist Subscriptions Guide
Juniper Mist AI for Wired – Marvis Virtual Network Assistant Overview
Juniper Licensing and Subscription Matrix
Question 9
Which statement is correct about the VXLAN data plane?
- A. The data plane learns the IP addresses of end-user devices.
- B. The data plane advertises the MAC addresses of end-user devices.
- C. The data plane encapsulates the traffic.
- D. The data plane learns the MAC addresses of end-user devices.
Answer:
C
Explanation:
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.
Reference:
Juniper Mist AI for Wired – EVPN-VXLAN Overview
Juniper Validated Design – EVPN-VXLAN Control and Data Plane Separation
Junos OS EVPN-VXLAN Deployment Guide
===========
Question 10
What are two unique advantages about configuration automation in Wired Assurance? (Choose two.)
- A. 100% open APIs
- B. client SLEs
- C. programmable workflows
- D. switch insights
Answer:
A, C
Explanation:
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.
Reference:
Juniper Mist AI for Wired – Wired Assurance Overview
Juniper Mist AI for Wired – Switch Automation and APIs Guide
Juniper Validated Design – Mist Wired Automation Best Practices
Question 11
In Juniper Mist cloud services, service level expectation (SLE) telemetry is collected from every
device and stored for up to how long?
- A. 1 month
- B. 2 months
- C. 7 days
- D. 24 hours
Answer:
A
Explanation:
Juniper Mist AI collects telemetry 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 to one month
in 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 for 30 days (1 month).
Reference:
Juniper Mist AI for Wired – Service Level Expectations Overview
Juniper Mist AI for Wired – Telemetry and Data Retention Guide
===========
Question 12
Which campus fabric architecture supports Layer 3 gateways at the distribution layer?
- A. campus fabric core/distribution – centrally-routed bridging (CRB)
- B. campus fabric IP Clos
- C. campus fabric core/distribution – edge-routed bridging (ERB)
- D. EVPN multihoming
Answer:
C
Explanation:
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.
Reference:
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 13
You have deployed your switches and need to provide a unique hostname on each switch.
Which Mist dashboard option allows you to accomplish this task?
- A. Organization switch template
- B. Site switch configuration
- C. Individual switch configuration
- D. Device profiles
Answer:
C
Explanation:
In Juniper Mist Cloud, there are multiple configuration scopes:
Organization-level templates apply globally.
Site-level configuration applies across all devices in a site.
Individual switch configuration is used to define unique, device-specific attributes such as hostname,
management IP, or local overrides.
“Templates and site-level configuration ensure consistency across devices, while individual switch
configuration is used to assign unique values such as hostnames.”
Option A: Incorrect — org templates define common config, not hostnames.
Option B: Incorrect — site configs are shared across all switches in the site.
Option D: Incorrect — device profiles apply settings like port policies or authentication, not
hostnames.
Option C: Correct — individual switch configuration is the correct place to assign hostnames uniquely
per device.
Reference:
Juniper Mist AI for Wired – Switch Configuration Hierarchy
Juniper Mist Documentation – Device-Level Configuration in Wired Assurance
===========
Question 14
Which two statements are correct about the campus fabric core-distribution architecture? (Choose
two.)
- A. Only the core and distribution tiers are part of the EVPN-VXLAN topology.
- B. Only the core tier participates in the EVPN-VXLAN topology.
- C. The access tier is included in the EVPN-VXLAN topology.
- D. The access tier does not participate in the EVPN-VXLAN topology.
Answer:
A, D
Explanation:
In a core-distribution campus fabric model, the EVPN-VXLAN overlay is established only between the
core and distribution tiers. The access 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 core and distribution participate, 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.
Reference:
Juniper Mist AI for Wired – Campus Fabric Core-Distribution Architecture
Juniper Validated Design – EVPN-VXLAN Campus Deployment Models
Junos OS EVPN Campus Fabric Design Guide
Question 15
What information does Mist use to determine if the port is classified as an uplink? (Choose two.)
- A. if TX and RX are higher than the rest of the ports
- B. if the port has an MTU greater than 1500 configured
- C. if the port is an STP root port
- D. if the port has a description configured
Answer:
A, C
Explanation:
Juniper Mist automatically classifies ports to simplify visibility and automation within Wired
Assurance. The Mist cloud analyzes port telemetry and link behavior to 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 uses STP 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.
Reference:
Juniper Mist AI for Wired – Port Role Classification and Telemetry
Juniper Mist AI for Wired – Automated Uplink Detection and Insights
Juniper Wired Assurance Analytics Guide
===========