Channel bonding combines two adjacent channels to create a wider channel, effectively doubling the available bandwidth. However, this also doubles the required device resources such as power and processing.

According to the Lecture 3 - Radio Frequency and Antenna Fundamentals - Part 2 document2, channel bonding is a technique that combines two adjacent channels into one wider channel to increase throughput. This doubles the available bandwidth but also doubles the required device resources such as power and processing.

In the IEEE 802.1X authentication process, the AP acts as an authenticator.

According to the Lecture 5 - Security - Part 1 document, the AP's role in the IEEE 802.1X authentication process is to act as an authenticator. This means that the AP acts as a gatekeeper between the client device (supplicant) and the RADIUS server (authentication server). The AP forwards authentication messages between the supplicant and the server and grants or denies network access based on the server's response.

According to the JNCIS-MistAI Certification page3, a Marvis Actions Missing VLAN notification indicates that an access point is missing a VLAN that is configured on other access points in the same site.

According to the Mist documentation1, a Mist AP will pull a management IP address from the Native VLAN by default. However, if the Local Status Page is configured for the Site, all the site APs will pull their own IP address from the Management VLAN, but also addresses for each of the VLANs configured on the AP. This is because each AP creates a Switch Virtual Interface (SVI) for each VLAN on its eth0 interface.

The Local Status Page is a feature that allows you to access information about an AP's status and configuration through a web browser by connecting to its IP address2. This feature can be enabled or disabled at the site level under Site Settings > Access Points > Advanced Settings.

According to the Juniper Mist Wireless Deployment Service Datasheet1, a configuration template at the organization level can be applied to a site group, not to an individual site. Therefore, there is no option to mention the site in the config template at the organization level.