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.

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.

According to the Juniper Mist dashboard's firmware management interface shown in the exhibit, several key details of the switch upgrade process are visible. The "Upgrade switch firmware" dialog box is a standard component of Juniper Mist Wired Assurance used to manage Junos OS updates across the fabric.

The correct statement is that the switch will reboot after the upgrade. This is explicitly confirmed by the checkbox labeled "Reboot switch after image copy," which is currently selected in the exhibit. In Juniper's cloud-managed workflow, once the new software image is successfully transferred from the Mist cloud to the switch's local storage, the system requires a reboot to initialize the new Junos OS kernel and complete the installation process5. While some platforms support non-disruptive upgrades, the standard procedure for EX-series switches in a standalone or Virtual Chassis configuration typically involves a scheduled reboot to ensure the new version is correctly applied.

The other options are incorrect based on the visual evidence provided in the exhibit.

Option A: The exhibit clearly identifies the "Switch Model" as an EX2300-C-12P (the 'P' designating PoE support), not an EX2300-C-12T88.

Option C: The dialog box explicitly states "Total Switches selected to upgrade: 1," confirming this is a single-device operation rather than a bulk upgrade.

Option D: The "Upgrade to Version" field is set to 19.3R1.8, which indicates the target version, not the previous version10101010.

By providing these granular controls, Juniper Mist allows administrators to maintain strict version compliance across the site while choosing whether to immediately reboot or stage the image for a later maintenance window.

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.

In Juniper Mist Cloud, there are multiple configuration scopes:

Organization-level templatesapply globally.

Site-level configurationapplies across all devices in a site.

Individual switch configurationis used to define unique, device-specific attributes such ashostname, management IP, or local overrides.

“Templates and site-level configuration ensure consistency across devices, whileindividual 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 configurationis the correct place to assign hostnames uniquely per device.

TheSwitch Insightssection in the Mist dashboard provides detailed switch telemetry, including interface statistics, port utilization, client count, and traffic analysis. It allows administrators to view real-time and historicaltraffic per port, identify top talkers, and detect anomalies.

“The Switch Insights page displays real-time and historical data such as traffic per port, PoE usage, connected clients, and interface errors for every switch managed by Mist.”

Option A:Correct— port-level traffic and utilization metrics are visible in Switch Insights.

Option B:Incorrect — available for all Mist-managed switches (EX and supported QFX).

Option C:Incorrect — displays complete event history, not limited to five events.

Option D:Incorrect — configuration rollback is done via the configuration history section, not Switch Insights.

Group-Based Policy (GBP)is a Juniper EVPN-VXLAN feature that enablesmicrosegmentationwithout requiring multiple VRFs or VLANs. It is implemented within Juniper Mist’sWired Assurance and Campus Fabricframeworks.

“GBP provides scalable, identity-based segmentation for campus fabrics and is supported on EX4100 and EX4400 Series switches operating in EVPN-VXLAN mode under Mist management.”

The feature requires hardware and software support forEVPN-VXLAN and GBP tagging, which is currently available on specific EX models managed by Mist Cloud.

Option A:Correct— GBP requires compatible access switches, specifically EX4100 and EX4400 models.

Option B:Incorrect — GBP is centrally managed through Mist Cloud, not configured per switch.

Option C:Incorrect — GBP is provisioned via Mist Cloud, not the CLI.

Option D:Incorrect — GBP is not supported onallEVPN-capable switches; only on defined platforms (EX4100/EX4400).