Pass JN0-460 Exam Guide

Juniper Mist Cloud uses anopen RESTful API frameworkfor integration, automation, and programmability across all Mist services, includingWired Assurance,Marvis, andAI-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 inJSONformat, but the API type itself isREST, 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 thedata format, not the API type.

Option D (RPC):Incorrect — not used in the Mist Cloud architecture.

When deployingJuniper Mist Wired AssuranceinManaged mode, switches are fully integrated with Mist Cloud for configuration, monitoring, and AI-driven operations. Managed mode providescomplete cloud-based management, meaning Mist AI handles configuration, templates, telemetry, and SLE tracking.

“In Managed mode, the switch configuration is fully managed by Mist Cloud. Administrators configure switches, templates, and policies directly through the Mist dashboard. A valid Wired Assurance subscription is required for Managed mode operation.”

Option A:Incorrect — the “Monitor Only” mode is read-only, not Managed.

Option B:Correct— Managed mode requires aWired Assurance subscription.

Option C:Incorrect — subscriptions are mandatory for Mist-managed devices.

Option D:Correct— in Managed mode,all supported EX switches are fully managed by Mist AI, including configuration and telemetry.

Aport negotiation mismatchoccurs when the local and remote interfaces fail to agree on common speed or duplex settings.

Marvis Wired Assurance automatically detects this by analyzing telemetry from the switch’s physical interfaces.

You can resolve this by ensuringauto-negotiationis enabled on both ends (A) and verifying the peer device supports the802.3 autonegotiation standard(D).

Manually forcing half-duplex or replacing hardware is unnecessary unless the hardware is faulty.

“Marvis Wired Actions correlate interface negotiation errors with LLDP neighbor data to pinpoint mismatched configurations, helping administrators quickly verify speed/duplex compatibility and 802.3 autonegotiation support.”

In Juniper’scampus fabric architectures, the location of theLayer 3 gateway(IRB) differentiates between CRB and ERB models:

Centrally-Routed Bridging (CRB):L3 gateways are placed at thecore layer.

Edge-Routed Bridging (ERB):L3 gateways are placed at thedistribution layer, closer to the edge.

“In the ERB model, Layer 2 gateways are deployed at the access layer, andLayer 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 thedistribution layerin the ERB architecture.