The Juniper Mist platform operates on a hierarchical configuration model. Settings configured at a more specific level (Site) take precedence over settings from a more general level (Organization Template). In this scenario, because the WLAN and its policy are explicitly configured at the Site A level, this configuration will override the settings for the same WLAN within the organization-level template applied to Site A. Therefore, the policy created at the site level is the one that will be enforced.

A. The policy from the organization-level template is overridden by the more specific site-level configuration and will not be the one that is executed.

B. Organization-level configuration templates can be applied to individual sites, multiple selected sites, or site groups, not exclusively to site groups.

D. The core function of an organization-level template is to be applied to specific sites or groups of sites, which are explicitly selected during template configuration.

1. Juniper Mist Documentation, "Use Configuration Templates": In the section detailing configuration hierarchy, it states, "Mist has a configuration hierarchy. You can configure settings at the Organization level and at the Site level. Site-level settings override Organization-level settings. For example, if you enable a specific band in a template and disable it at the site level, the site-level setting (disabled) takes precedence." This directly supports the principle that site-level configurations are executed over template-level ones.

2. Juniper Learning Portal, JNCIA-MistAI Courseware, "Module 3: Mist Configuration Basics": This module explains the object hierarchy (Organization > Site). It details that templates are created at the organization level to provide a baseline configuration for multiple sites, but any configuration made directly on a site object will override the template settings for that specific site. This confirms that the site-level policy is the effective one.

3. Juniper TechLibrary, "Mist Cloud—An Introduction to the Cloud-Native Platform": This document outlines the architectural design, which includes the hierarchical management structure. It explains that this structure allows for both broad, consistent policy application via organization-level templates and granular, site-specific exceptions and configurations, with the latter taking precedence.