In Juniper Mist cloud services, service level expectation (SLE) telemetry is collected from every
device and stored for up to how long?
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
===========
Which campus fabric architecture supports Layer 3 gateways at the distribution layer?
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
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?
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
===========
Which two statements are correct about the campus fabric core-distribution architecture? (Choose
two.)
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
What information does Mist use to determine if the port is classified as an uplink? (Choose two.)
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
===========
Which two statements are correct about the EVPN-VXLAN control plane? (Choose two.)
B, C
Explanation:
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.
Reference:
Juniper Mist AI for Wired – EVPN-VXLAN Overview
Juniper Validated Design – EVPN Control and Data Plane Operation
Junos OS EVPN-VXLAN Implementation Guide
Which service level expectation (SLE) metric measures congestion on the uplink interface of a
switch?
B
Explanation:
Juniper Mist’s Wired Assurance includes multiple SLE metrics that monitor the health and
performance of wired connections. One of these is Asymmetric Uplink, which measures uplink
congestion or imbalance between the transmit (TX) and receive (RX) rates on the switch uplink
interfaces.
“The Asymmetric Uplink SLE monitors congestion and traffic imbalance on the switch’s uplink ports.
It identifies when the uplink bandwidth utilization or transmit/receive rates are inconsistent with
expected patterns, indicating congestion or flow asymmetry.”
Option A (Successful Connect): Tracks client connection success rate, not uplink congestion.
Option C (Throughput): Relates to end-to-end data transfer rate, not specifically uplink congestion.
Option D (Switch Health): Measures hardware, software, and PoE health, not link congestion.
Option B (Asymmetric Uplink): Correct — this SLE directly reflects uplink interface congestion or
imbalance.
Reference:
Juniper Mist AI for Wired – Wired SLE Metrics Overview
Juniper Mist AI for Wired – Asymmetric Uplink SLE Description
Juniper Mist Documentation – Troubleshooting with SLE Analytics
===========
Which API is used within the Juniper Mist solution?
A
Explanation:
Juniper Mist Cloud uses an open RESTful API framework for integration, automation, and
programmability across all Mist services, including Wired Assurance, Marvis, and AI-driven
automation.
“All Mist Cloud services are built on a 100% open REST API framework, allowing customers to
automate configuration, monitoring, and troubleshooting through standard REST calls.”
The REST API exchanges data in JSON format, but the API type itself is REST, not JSON.
Option A (REST): Correct — Mist services expose 100% REST-based APIs.
Option B (SOAP): Incorrect — SOAP is an older XML-based protocol not used in Mist.
Option C (JSON): Incorrect — JSON is the data format, not the API type.
Option D (RPC): Incorrect — not used in the Mist Cloud architecture.
Reference:
Juniper Mist AI for Wired – API Overview
Juniper Mist API Developer Documentation
Juniper Mist AI Cloud – Automation and Integration Guide
You must move from a campus fabric core-distribution centrally-routed bridging (CRB) network to an
edge-routed bridging (ERB) network.
In this scenario, where does the gateway for the network move?
C
Explanation:
In Juniper Mist campus fabric architectures, the location of the Layer 3 gateway (IRB interface)
differentiates centrally-routed bridging (CRB) from edge-routed bridging (ERB):
In CRB, the gateway resides at the core layer — routing occurs centrally, and access/distribution
layers perform Layer 2 bridging.
In ERB, the gateway moves to the edge (distribution layer), enabling routing to occur closer to
endpoints, improving performance and scalability.
“In a centrally-routed bridging (CRB) topology, Layer 3 gateways reside at the core. When
transitioning to an edge-routed bridging (ERB) design, the Layer 3 gateways are moved to the
distribution layer, closer to the access switches and clients.”
Therefore, when moving from a core-distribution CRB to an ERB model, the gateway moves from the
distribution to the access layer in campus terms (edge = access).
Option A: Incorrect — ERB gateways are not at the distribution layer only.
Option B: Incorrect — opposite direction.
Option C: Correct — the gateway moves from distribution to access (edge).
Option D: Incorrect — this describes CRB, not ERB.
Reference:
Juniper Mist AI for Wired – Campus Fabric Architecture Models (CRB vs ERB)
Juniper Validated Design – Campus Fabric EVPN-VXLAN Gateway Placement
Junos OS EVPN-VXLAN Deployment Guide
===========
What are the two ways to forward BUM traffic when using EVPN? (Choose two.)
C, D
Explanation:
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.
Reference:
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