Site A is configured with a WLAN and a policy. The administrator creates a configuration template at the organization level with additional policies for the same WLAN and mentions Site A in this template.
In this scenario, which statement is correct?
Answer : D
An organization-level configuration template can only be applied to site groups, not to individual sites.
Therefore, a single site such as Site A cannot be directly specified inside an org-level template.
Juniper Mist Wireless and Wired Deployment Guide -- Configuration Templates and Hierarchy
Mist Cloud Configuration Hierarchy Overview
===========
Which description accurately defines a Mist AI 5-stage IP Clos network?
Answer : D
Juniper Mist defines both 3-stage and 5-stage IP Clos architectures for campus and data-center fabrics. The 5-stage IP Clos design adds scalability by introducing spine and super-spine layers above the leaf layer, enabling large campus or aggregation environments.
''The 5-stage IP Clos topology extends the 3-stage design by introducing spine and super-spine tiers. It is ideal for large campus environments requiring additional capacity and hierarchical scaling.''
Option A: Incorrect --- Clos is a topology, not a routing protocol.
Option B: Incorrect --- VXLAN/EVPN encapsulation operates over Clos but does not define it.
Option C: Incorrect --- that describes a traditional three-tier campus (core/distribution/access), not a Clos.
Option D: Correct --- the 5-stage IP Clos is a hierarchical, scalable Clos topology with spine and super-spine layers used in large campus or data-center networks.
Juniper Mist AI for Wired -- Campus Fabric IP Clos Architecture Guide
Juniper Validated Design -- 3-Stage and 5-Stage IP Clos Campus Fabrics
Juniper Mist AI Cloud -- EVPN-VXLAN Fabric Deployment
===========
Which statement is correct about the Switch Insights section?
Answer : A
The Switch Insights section 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 historical traffic 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.
Juniper Mist AI for Wired -- Switch Insights Overview
Juniper Mist Wired Assurance -- Switch Analytics and Port Utilization Guide
Juniper Mist AI Cloud -- Switch Telemetry and Event Monitoring
===========
Which three administrator roles allow you to claim switches? (Choose three.)
Answer : A, B, C
In Juniper Mist Cloud, administrative roles define what actions a user can perform within an organization. The ability to claim and onboard switches is granted to roles that have configuration or deployment privileges.
''Only users with Super User, Network Admin, or Installer roles can claim, onboard, or delete devices such as access points, switches, or gateways within a Mist organization.''
Option A (Network Admin): Correct --- can claim and manage network devices.
Option B (Installer): Correct --- role specifically intended for device onboarding and site setup.
Option C (Super User): Correct --- full administrative privileges including device claiming.
Option D (Observer): Incorrect --- view-only access.
Option E (Helpdesk): Incorrect --- limited to troubleshooting functions, not device management.
Juniper Mist AI for Wired -- User Roles and Permissions Guide
Juniper Mist Organization Administration Documentation
Juniper Mist AI Cloud -- Device Onboarding and Claiming Workflow
===========
What are two unique advantages about configuration automation in Wired Assurance? (Choose two.)
Answer : A, C
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.
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
Which two Marvis Wired Assurance actions require a Juniper switch? (Choose two.)
Answer : B, C
Marvis, the AI-driven virtual network assistant in Mist, provides real-time troubleshooting insights for both wired and wireless devices.
When used with Wired Assurance, certain actions require Juniper EX or QFX switches for telemetry collection.
Two of these wired-specific actions are:
Bad Cable Detection -- triggered when electrical faults or poor cable quality are observed through LLDP or physical diagnostics.
Negotiation Mismatch -- triggered when duplex, speed, or link-mode settings are mismatched between peers.
These insights help reduce manual troubleshooting by automating root-cause analysis.
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?
Answer : C
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.
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
===========