Juniper JN0-253 Mist AI - Associate (JNCIA-MistAI) Exam Practice Test

TheAI-driven Radio Resource Management (RRM)system inJuniper Mist Wireless Assuranceemploysreinforcement learningto continuously optimize wireless radio parameters such as channel selection, transmit power, and channel width.

According to theJuniper Mist Wireless Assurance and AI-Driven RRM Guide:

“The RRM system leverages reinforcement learning techniques to dynamically adjust radio configurations based on environmental conditions, user density, and interference patterns.”

Reinforcement learning enables the Mist AI system to make decisions by continuously evaluating the outcome of past configurations and improving future adjustments. This ensures that Mist RRM can autonomously optimize RF conditions for coverage and capacity without manual intervention.

Therefore, the correct answer isC. Reinforcement learning.

Thesession policy settingsin theJuniper Mist Clouddefine how long a user session remains active and how the system manages session expirations due to inactivity. These configurations help ensure bothsecurityandefficient resource managementacross the Mist Cloud portal and API sessions.

According to theJuniper Mist Cloud Administration and Security Configuration Guide:

“Session policy defines session timeout and inactivity timeout parameters, controlling how long users can remain logged into the Mist Cloud portal or API before re-authentication is required.”

Session Timeout:Specifies the maximum duration a session can remain active, regardless of activity.

Inactivity Timeout:Defines how long a session can remain idle before automatic logout.

These policies help maintain strong access security by reducing the risk of unauthorized access through stale sessions.

Other options such as password complexity (A, C) and two-factor authentication (D) are configured underauthentication and access policies, not session policies.

Therefore, the correct answer isB. The duration for session timeout and inactivity timeout.

You must configure the site within your organization—this is the correct process according to Juniper Mist’s official configuration guides. When setting up a deployment, first an organization is created in the Mist cloud. Within this organization, sites are added for each physical location. The Mist documentation says: "You can create Sites in the Juniper Mist portal from the Organization > Site Configuration menu. Add or update sites as needed." The configuration requires the site name, country, and location to be set at the site level—not the organization level. Claiming APs via QR codes and organization definition are separate steps in device onboarding and initial setup.

TheJuniper Mist Cloud APIfollowsRESTful API design principles, enabling programmatic access to all Mist Cloud functions such as device management, configuration, analytics, and monitoring. REST APIs in Mist use a lightweight and standardized data exchange format to facilitate seamless integration with third-party applications and automation frameworks.

According to theJuniper Mist API Developer Guide:

“All Juniper Mist Cloud API requests and responses are transmitted in JavaScript Object Notation (JSON) format. JSON is used because it is lightweight, easy to parse, and compatible with all modern programming environments.”

JSON is the preferred format because it is both human-readable and machine-efficient, allowing for fast serialization and deserialization of data structures.

Other formats such asCSV,XML, andYAMLare not used for API communication within the Mist Cloud architecture.

Therefore, the correct answer isD. JSON.

The correct statement is that Juniper APs have a dedicated radio to scan for rogue and honeypot APs. The official Juniper Mist documentation specifies: "Juniper APs include a dedicated scanning radio to detect rogue, neighbor, and honeypot APs and their clients... The dedicated scanning radios operate on 2.4, 5, and 6 GHz Wi-Fi bands." This third radio operates independently from the client-serving radios and enables continuous threat detection on all Wi-Fi bands, enhancing security and allowing real-time performance adjustments. BLE radios are used for location-based services and asset tracking, not for rogue AP detection. Client-serving radios can also scan, but detection is always enabled and optimized by the dedicated radio.

Audit Logs in Juniper Mist are used to view a complete record of logins. The documentation states: "On the Audit Logs page, you can see who logged in to the Juniper Mist portal, when they logged in, and what they did." Audit Logs also record configuration and administrative actions by users on all sites within the organization, enabling administrators to track activity for compliance, troubleshooting, and security. This comprehensive record assists with accountability and change tracking, but they do not manage subscriptions, organization setup, or error logs for all devices. Filtering options allow for activity analysis over selectable time periods, by users, and by site to provide detailed insights into administrative behavior and user access history.​

In Juniper Mist, allhardware device onboarding and claiming operations—including access points (APs), switches, and gateways—are performed under theInventorysection of the Mist Cloud Portal.

According to the Juniper Mist Cloud documentation, theInventorypage serves as the centralized location for device lifecycle management. It allows administrators to:

Claim new devicesusing their serial numbers or activation codes.

Batch import multiple APsvia manual entry or CSV upload.

Assign claimed devicesto specific sites for configuration and management.

Monitor device claim status, model type, firmware version, and cloud connectivity state.

The documentation specifies:

“To onboard or claim multiple access points in the Mist Cloud, navigate toOrganization → Inventory, then clickClaim Devices. Enter or paste serial numbers of the APs you want to add, and assign them to the appropriate site.”

Other options are incorrect because:

Subscriptionsmanages licensing and service entitlements.

Devicesshows active device status per site but does not handle claiming.

Client Onboardingis used for guest access or authentication workflows, not hardware management.

Therefore, the correct answer isInventory (C).

Radio Resource Management (RRM)is a key feature ofJuniper Mist Wireless Assurancethat uses AI-driven automation to dynamically adjust radio settings across access points (APs) for optimal wireless performance. The RRM engine ensures proper channel assignment, transmit power control, and interference management across the network.

According to theJuniper Mist Wireless Assurance and AI-Driven RRM Guide, RRM operates intwo modes:

Event-Driven RRM:This mode reacts immediately to real-time changes in the RF environment, such as new access points, interference spikes, or client density changes.

Global Optimization RRM:This process runs as ascheduled, system-wide optimization once per dayto evaluate the overall RF environment and redistribute channels and power settings network-wide for the best balance of coverage and capacity.

The documentation states:

“The RRM global optimization algorithm automatically executes once daily to ensure optimal channel and power planning across all APs.”

Thus, the correct answer isD – The RRM global optimization system automatically runs once a day.

TheMarvis Virtual Network Assistant (VNA)in Juniper Mist AI uses real-time telemetry and AI-driven correlation to identify hardware and connectivity issues, including bad cable conditions. When a“Bad Cable”alert is raised, Marvis analyzes physical link metrics from the switch and AP—such as CRC errors, FCS drops, and link flaps—to isolate the root cause.

According to the Juniper Mist AI Operations Guide, theMarvis Actions dashboardprovides contextual insights into the issue, showing whether the fault lies in thephysical cableitself or theswitch portit is connected to. Specifically, the dashboard highlights:

The affected device and port.

Whether the degradation originates from theport hardwareor thecabling.

Suggested corrective action (e.g., replace the cable or check switch hardware).

Marvis uses its AI-driven root cause analysis engine to distinguish between cable integrity problems and port failures by examining electrical signature anomalies and historical telemetry.

Options B, C, and D are incorrect because Marvis does not display cable category ratings or identify individual broken Ethernet pairs—it focuses on identifying and isolating the fault domain.

Therefore, the correct answer isA. If the port or cable is at fault.

ThePredictive Analytics and Correlation Engine (PACE)is the core AI engine that powers theJuniper Mist Cloud. It is designed to continuously learn from real-time telemetry and user interactions across wireless, wired, and WAN networks to proactively identify anomalies and predict performance issues.

According to theJuniper Mist AI Cloud and PACE Architecture Documentation, PACE:

“Leverages machine learning and advanced analytics to correlate data across millions of network sessions, automatically identifying patterns that affect user experience.”

The engine continuously evaluates key Service Level Expectations (SLEs), such asTime to Connect,Throughput, andRoaming, to establish performance baselines and detect deviations before users notice them.

PACE doesnot rely on manual analysisoruser feedback, and it integrates telemetry rather than external monitoring tools to maintain a closed-loop feedback system for self-correction and optimization.

Therefore, PACE usesmachine learning (A)to understand, predict, and improve end-user experience across Juniper Mist-managed networks.

To view an organization’s Audit Logs in the Juniper Mist UI, the required roles are Network Admin and Super User. According to Juniper Mist documentation: “Network Admin (with All Sites access) and Super User roles grant permission to view and interact with organization-level features, including Audit Logs and Inventory.” The Audit Logs page provides a chronological record of user logins and configuration changes, and access is restricted to authorized users for security and compliance reasons. The "Super User" role has full read/write access for the entire organization—no restrictions—allowing these users to view Audit Logs without limitation. The "Network Admin" role, when granted access to All Sites (not just specific sites), can also view Audit Logs as part of their permitted organization-level operations. Other roles, such as Helpdesk and Installer, have limited or specific access and cannot access Audit Logs. These permissions ensure that only trusted network administrators and super users have the necessary authority for sensitive audit and compliance functions.

To supportmobile device engagementwithin theJuniper Mist Cloud UI, you mustenable virtual Bluetooth Low Energy (vBLE). The vBLE functionality allows Mist Access Points (APs) to transmitBluetooth beaconsthat interact with mobile devices running location-aware applications. This capability is essential foruser engagement servicessuch as indoor navigation, proximity notifications, and personalized customer interactions.

According to theJuniper Mist Location-Based Services Configuration Guide, the process is defined as follows:

“To enable mobile engagement and location-based experiences, the vBLE feature must be activated on supported Mist Access Points. Once enabled, APs transmit programmable BLE signals that communicate with mobile devices through the Mist SDK.”

Enabling vBLE allows administrators to:

Providewayfindingandpush notification serviceswithin indoor environments.

Supportmobile app integrationthrough theMist Location SDK.

Customize engagement campaigns viavirtual beaconswithout requiring physical beacon hardware.

Other options are incorrect because:

Wi-Fi 6improves wireless efficiency but is unrelated to BLE-based engagement.

Local Status Pageis used for AP health monitoring, not engagement.

ESL (Electronic Shelf Labels)applies to retail price display systems, not user interaction.

Therefore, the correct answer isA. Enable vBLE.

In theJuniper Mist Cloud architecture, data is collected and streamed from variousedge devicesto the Mist Cloud platform, whereAI-driven analytics,automation, andtelemetry correlationoccur. OnlyMist-managed devicesthat are cloud-connected contribute operational telemetry data to Mist AI for analysis.

According to theJuniper Mist Cloud Architecture and Operations Guide:

“Access Points, Juniper Mist Edge devices, and Session Smart Routers (SSR) communicate directly with the Mist Cloud, sending telemetry, configuration, and analytics data in real time.”

Access Points (B):Provide wireless client telemetry, RF statistics, and user SLE (Service Level Expectation) data.

Session Smart Routers (C):Supply WAN Assurance and routing analytics, including path and session health data.

Juniper Mist Edge (D):Acts as an on-premises gateway that forwards data and enables local breakout for Mist Cloud services.

Syslog ServersandRADIUS Serversare external systems and do not send native telemetry to the Mist Cloud—they only interact through authentication or logging integrations.

TheJuniper Mist Wired Assuranceplatform uses ahierarchical configuration modelto manage switch settings efficiently across organizations and sites. This hierarchy provides flexibility by allowing administrators to applyglobal configurationsthrough templates at theorganization level, while also permitting site-specific customizations.

According to theJuniper Mist Wired Assurance Configuration and Template Management Guide, the configuration hierarchy functions as follows:

“Switch templates can be created at both the organization and site levels. Organization-level templates define global configurations, while site-level templates provide location-specific customization that overrides the organization-level settings where applicable.”

This structure enables consistent policy deployment while preserving site autonomy for unique configurations. For example, global VLAN or QoS configurations can be managed at the organization level, and local templates can adjust settings for switch ports or device groups at specific sites.

Switch-specific overrides are allowed within the hierarchy, ensuring flexibility in cases where unique port or feature configurations are required.

Therefore:

Bis correct because switch templates exist at theorganization levelfor global use.

Cis correct because switch templates also exist at thesite levelfor localized adjustments.

A DHCP lease must be obtained by the switchbefore the ZTP process proceeds. Juniper documentation clarifies: "Ensure that a DHCP server is reachable. In addition to providing an IP address to the switch, your DHCP server must provide the following information: a default gateway, an NTP server, and a DNS server address..." The initial event in the ZTP workflow is the switch receiving a valid IP address via DHCP. Only after obtaining an address can the switch connect to the Mist cloud and proceed with zero-touch provisioning. Other requirements, such as user account, NETCONF, or NTP sync, occur later or are handled automatically via cloud policy after onboarding.

InJuniper Mist’s Location-Based Services, theAsset Visibilityservice utilizes the built-inBluetooth Low Energy (BLE)antenna array within Mist Access Points to track BLE tags and devices inlisten-only mode. This allows the APs to receive BLE signals emitted by assets and compute their real-time location usingangle-of-arrival (AoA)andRSSI-based triangulation.

According to theJuniper Mist Asset Visibility and Location Services Guide:

“When operating in Asset Visibility mode, the vBLE antenna array in Mist Access Points functions in listen-only mode, collecting BLE chirps from asset tags and relaying this data to the Mist Cloud for location determination.”

This configuration differs fromvBLE Engagement, where APs transmit BLE beacons to interact with mobile apps. InAsset Visibility, the BLE array passively listens to track tagged assets (e.g., equipment, IoT devices) across a defined floor map.

Therefore, the correct answer isD. Asset Visibility.

To enable Juniper Mist Access Assurance for 802.1X (RADIUS) authentication with Cisco APs, the correct approach is to configure a new 802.1X SSID on the Cisco AP referencing your Juniper Mist Edge as the RADIUS server (option C). According to Juniper Mist’s official documentation and architecture guides: “Mist Access Assurance supports end-client authentication on third-party infrastructure by leveraging the Mist Auth Proxy application running on a Mist Edge platform. Third-party devices, such as Cisco APs, are added as RADIUS clients at Mist Edge. The Mist Edge proxy handles all RADIUS authentication traffic from the APs, wraps these authentication requests into a secure RadSec tunnel, and relays them to the Mist Access Assurance cloud for validation against configured authentication rules.”

This deployment does not require direct RADSEC tunneling from Cisco APs to Mist Access Assurance (since Cisco APs are not natively RADSEC capable) but uses Mist Edge as an intermediary RADIUS server and authentication proxy. "Add an authentication rule in Access Assurance to permit user access," enabling centralized management and policy enforcement in the Mist Cloud.

Marvis Minisis a component of theMarvis Virtual Network Assistant (VNA)within theJuniper Mist AI ecosystem. It is designed to proactively ensure optimal network performance and user experience by runningsynthetic network testsusing Mist-managed access points.

According to theJuniper Mist Marvis Minis Technical Overview, this feature allows APs to act asvirtual clientsthat automatically simulate user connection flows, including authentication, DHCP, DNS, and application reachability. These tests validate that thenetwork configuration and servicesare functioning as expected, even before real users experience issues.

The documentation states:

“Marvis Minis operates in conjunction with Mist AI to continuously validate network configurations and optimize user experience by identifying potential problems proactively.”

“Using Mist APs, Marvis Minis performs synthetic transactions to verify the performance of wireless, wired, and WAN segments without requiring external devices.”

Hence,Marvis Minis is not a support team (A),not a design AI model (B), andMarvis Actions (C)is a different feature for identifying and resolving live issues. The accurate description is thatMarvis Minis collaborates with Mist AI to validate configurations and optimize user experiences.

In theJuniper Mist Cloud architecture, bothwebhooksandAPIsare key interfaces for automation, integration, and data exchange with third-party systems. While they both facilitate communication between Mist and external applications, they operate inopposite directionsand serve distinct purposes.

According to theJuniper Mist API and Webhook Developer Guide:

Webhooksarepush-based notificationsinitiated by the Juniper Mist Cloud. When specific events occur (such as device disconnection, client onboarding, or alert generation), Mist sends structured JSON payloads to a preconfigured external URL endpoint.

APIs(Application Programming Interfaces) arepull-based querieswhere an external client polls the Mist Cloud to retrieve or update data (e.g., inventory, configuration, or metrics).

Additionally, the Mist Cloud enforcesrate limitson API calls to ensure platform stability and fair usage:

“API rate limits are applied on a per-organization basis to prevent excessive polling and to maintain consistent performance.”

In contrast, webhooks do not have a strict hourly quota because they are event-triggered rather than continuous requests.

Therefore:

Ais correct — Webhooks push, APIs pull.

Bis correct — There is an hourly API rate limit per organization.

OptionsCandDare incorrect because webhooks are event-based (not rate-limited hourly) and do not configure Mist objects directly—they only send notifications.

Marvis Minisis an advanced feature within the Juniper Mist AI ecosystem designed to performautonomous, synthetic network testing. It uses Mist Access Points (APs) to simulate client behavior—such as association, authentication, DHCP, DNS, and application reachability—to proactively detect service issuesbefore real users are affected.

According to theJuniper Mist Marvis Minis Deployment GuideandMarvis AI documentation, the key requirement for enabling Marvis Minis is that all participating access points must be running aminimum supported firmware versionthat includes the Minis agent functionality.

The documentation specifies:

“Marvis Minis requires APs running the minimum firmware version that supports synthetic testing. APs on earlier versions will not be capable of running Minis tests or reporting results to the Mist Cloud.”

Additional subscriptions such asWAN Assurance,Premium Analytics, orWLAN templatesare not prerequisites for operation. WhileMarvis licensingmust be active, the feature itself relies primarily on compatible firmware within the Mist-managed APs.

Therefore, the correct answer isC. Minimum AP firmware— ensuring the APs are on a supported firmware release is essential for Marvis Minis functionality.

Juniper Mist Access Assuranceprovidescloud-based network access control (NAC)by integratingRADIUS,identity-based policy enforcement, andWxLAN role-based segmentation. It allows administrators to assign users and devices to specific VLANs or network segments dynamically based on authentication attributes, thereby improving bothsecurityandpolicy granularity.

According to theJuniper Mist Access Assurance Configuration Guide, to enhance network security in a multi-VLAN environment, you should:

“Use EAP-TLS (certificate-based authentication) for secure user identification, and dynamically assign WxLAN roles or VLANs based on Active Directory (AD) group membership.”

Here’s whyDis correct:

EAP-TLSensuresmutual authenticationbetween client and RADIUS server using digital certificates — preventing credential theft or spoofing.

Integrating withActive Directoryallowsrole-based access control (RBAC), enabling dynamic VLAN or WxLAN assignment. This ensures users from different groups (e.g., staff, contractors, guests) are automatically segmented into appropriate network zones.

Option breakdown:

A (MAB): Used for non-802.1X devices (e.g., printers), less secure for user authentication.

B (EAP-TTLS): Username/password-based and less secure than certificate-based EAP-TLS.

C (Host authentication): Verifies devices only, not user identity—insufficient for user-level control.

Therefore, the most secure and scalable configuration is:

✅D. Configure user authentication using EAP-TLS and assign WxLAN roles based on AD user group.

TheInstallerrole in theJuniper Mist Cloudis atemporary, limited-access account typeused for onboarding network devices—typicallyAccess Points (APs)—during initial deployment. It provides restricted visibility and configuration rights necessary for installation tasks but expires automatically after a definedgrace periodto maintain network security and access control.

According to theJuniper Mist Cloud Administration and User Management Guide:

“The Installer role provides temporary access to add, claim, and verify devices at a site. This access expires automatically after the predefined installation grace period.”

This role is ideal for field engineers or contractors performing device installations without granting them long-term administrative privileges. The grace period is typicallyseven days, after which the Installer account loses access to the organization automatically.

Other roles differ as follows:

Super Observer:Read-only access across the entire organization.

Observer:Read-only access limited to assigned sites.

Helpdesk:Focused on monitoring and basic troubleshooting tasks, not installation.

Therefore, the correct answer isB. Installer.

Juniper Mist WAN Assuranceis a cloud-based service that extends Mist AI capabilities to the WAN edge, providing visibility, automation, and AI-driven analytics for WAN devices. It focuses on ensuringend-to-end service assurancefor users and applications across distributed networks.

According to theJuniper Mist WAN Assurance and SD-WAN Deployment Guide, the supported devices include:

“Juniper SRX Series Firewalls and Session Smart Routers (SSR) are integrated with Mist WAN Assurance for telemetry collection, service-level monitoring, and AI-driven troubleshooting.”

SRX Series Firewalls (A):Provide secure WAN connectivity and send real-time telemetry (including throughput, latency, and packet loss metrics) to Mist Cloud.

Session Smart Routers (C):Power the AI-driven SD-WAN solution with application-aware routing and session intelligence, fully integrated into Mist Cloud for advanced visibility and analytics.

EXandQFXswitches are used withWired Assurance, not WAN Assurance.

Therefore, the correct answers areA. SRX Series FirewallsandC. Session Smart Routers.

The duplex mismatch parameter is beyond the scope of Marvis Actions’ Connectivity category. According to the official Juniper Mist documentation, Marvis Actions within the Connectivity category are designed to troubleshoot common network connectivity issues for wireless clients, including DHCP failure, DNS failure, authentication failure, and ARP failure. These actions automatically detect and provide detailed insights about failures most likely to impact client onboarding, IP addressing, and network services. Duplex mismatch, on the other hand, is a wired networking issue where there is a disagreement between network devices (such as switches and end hosts) regarding duplex settings (half-duplex or full-duplex), and it typically causes performance problems like collisions and slow speeds. Marvis's focus for the Connectivity troubleshooting category is wireless protocol-level connectivity and service reachability, so duplex mismatch falls outside its direct scope of detection and automatic remediation.

ThePredictive Analytics and Correlation Engine (PACE)is thecore AI and data analytics componentof the Juniper Mist Cloud architecture. It collects, processes, and correlates telemetry data across all managed domains —Wireless, Wired, and WAN Assurance— to deliver proactive insights and predictive network intelligence.

According to theJuniper Mist AI Operations and Architecture Guide:

“The Predictive Analytics and Correlation Engine (PACE) serves as the foundation of Mist AI, using continuous telemetry ingestion and machine learning algorithms to understand, correlate, and predict network behaviors across the wireless, wired, and WAN environments.”

PACE enables Mist AI to:

Detect anomalies in user experience and device performance.

Predict failures before they affect users.

Correlate events across network domains for root-cause analysis.

Therefore, the correct answer isA. Predictive Analytics and Correlation Engine (PACE).

In the Juniper Mist dashboard,Service Level Expectations (SLEs)are metrics that measure user experience in key areas such as connection, throughput, and roaming. Each SLE is composed ofclassifiers, which help identify the underlying cause of degraded performance or sub-threshold scores.

According to the Juniper Mist AI documentation, theRoaming SLEtracks client transitions between access points and evaluates the quality of those roaming events. The contributing classifiers typically includeSignal Quality,Wi-Fi Interference,Ethernet, andCapacity.

In this exhibit, the bar forCapacityis the longest under the “Roaming Classifiers” section, indicating that it has the most significant impact on theSub-ThresholdSLE value (10.6%). This means roaming performance is primarily being limited by insufficient capacity — often due to AP radio congestion or a high number of concurrent clients impacting handoff efficiency.

Hence, theCapacityclassifier is responsible for the sub-threshold SLEs.

TheJuniper Mist Cloudoperates as aregionally distributed cloud infrastructure, where each geographic region (for example, US, EU, APAC) hosts its own isolated Mist Cloud instance. This design ensures compliance with regional data privacy regulations, improves network performance, and enhances scalability and reliability.

According to theJuniper Mist Cloud Administration and Operations Guide, user accounts and organizations are region-specific, meaning:

“Users and organizations exist within specific regional Mist Clouds. A user account created in one regional cloud is valid only within that region and cannot be used to access organizations hosted in another cloud.”

This structure ensures data sovereignty and security while maintaining logical separation between regions. When administrators create a new user, that user’s credentials and access privileges applyonly to the Mist Cloud region in which the user was created.

Therefore:

Bis correct because users created in a regional cloud can only manage organizations within that same cloud.

Cis correct because a newly created user is enabled only for the regional cloud where it was registered.

OptionsAandDare incorrect because Mist Clouds are isolated — cross-region user or organization access is not supported.

To create a real-time visualization dashboard that displays clients on a map, use Live View and WebSocket APIs. The "Live View" feature in Juniper Mist provides a graphical, interactive map view of clients (devices) and assets as they move through a site, with location data updated in real time. The Juniper Mist WebSocket API enables developers and integrators to subscribe to client location topics and stream position data directly to custom dashboards. According to the documentation: "WebSockets open a bidirectional communication session for sending and receiving real-time event-driven responses... Useful in circumstances where you want to avoid browser refreshes and display real-time location data." Combining these allows you to build a dashboard showing live client positioning, as seen in sample dashboards and integration guides for Mist.

Port profilesinJuniper Mist Wired Assuranceare reusable configuration templates that define how switch ports behave. They streamline switch provisioning and ensure consistent configurations across multiple ports and devices within a site or organization.

According to theJuniper Mist Wired Assurance Configuration Guide, port profiles are defined as:

“A collection of interface-level settings that can be applied to one or more switch ports to simplify configuration and ensure uniform policy enforcement.”

Key characteristics include:

Reusable templates:Port profiles can beassigned to multiple portson one or more switches, allowing rapid deployment and consistent port behavior (e.g., access, trunk, voice VLAN).

Interface-level parameters:They include settings such as VLAN assignments, PoE configuration, speed, duplex, and LLDP options.

Port profilesdo not include routing configurations(those are defined at the Layer 3 interface or VLAN interface level) and arenot limited to a single port.

Therefore, the correct answers are:

A. They can be assigned to multiple ports.

B. They include a set of interface configurations.

Two wired elements configured using an organization-level template in Juniper Mist are VLAN and DNS settings. Organization-level templates are designed to standardize and propagate common settings across all switches within an organization. As per official guides: "These templates can include VLANs and well-known services such as DNS (Domain Name System) that can be used across all devices within a site." VLAN and DNS settings are defined once at the organization (or switch group) template and automatically inherited by all devices, ensuring consistency. Host name and role are set at an individual switch level, not globally via templates.