JN0-460 Exam Dumps : JNCIS-MistAI-Wired

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.

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

Juniper Mist AI collectstelemetry 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 toone monthin 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 for30 days (1 month).