Dynamic Frequency Selection (DFS) regulations require wireless devices to prevent interference with incumbent radar systems operating in the 5 GHz band. Before an access point (AP) can transmit on a designated DFS channel, it must perform a mandatory Channel Availability Check (CAC). This process involves passively listening on the channel for a specific duration, typically 60 seconds, to detect any radar signals. If no radar is detected during this period, the AP can then begin broadcasting its SSIDs and servicing clients on that channel.

A. Client device support is a consideration for network performance and design, but it is not a regulatory requirement the AP must perform before transmitting on a DFS channel.

C. The AP must listen passively. Transmitting anything, especially radar-like pulses, before the channel is cleared would cause interference and is a direct violation of DFS regulations.

D. Validating non-DFS channels is part of the AP's broader channel selection algorithm or a fallback action if radar is detected, not the required initial step for an assigned DFS channel.

1. Juniper Mist Documentation, Radio Resource Management (RRM): In the "Dynamic Frequency Selection (DFS)" section, it states, "Before an AP can use a DFS channel, it must scan the channel for 60 seconds to make sure that no radar is present. This is known as the Channel Availability Check (CAC)."

Source: Juniper Networks, "Radio Resource Management (RRM)," Mist Wireless Assurance Documentation, Section: Dynamic Frequency Selection (DFS).

2. Juniper Mist™ Wi-Fi Assurance Feature Guide: This guide explains the operational principles of Mist APs. The section on RRM details the DFS compliance mechanism, emphasizing the listening period. "If RRM assigns a DFS channel to an AP, the AP must first listen on that channel for radar signals for one minute (or 10 minutes for weather radar channels) before it can begin transmitting."

Source: Juniper Networks, "Juniper Mist™ Wi-Fi Assurance Feature Guide," Page 12, Section: Radio Resource Management (RRM).

By default, Juniper Mist Access Points are designed for zero-touch provisioning (ZTP). When a Mist AP is powered on and connected to a network via its primary uplink port (eth0), it immediately acts as a DHCP client. It sends a DHCP request to obtain an IP address, a default gateway, and DNS server information from the local network's DHCP server. This automated process is fundamental to its ability to connect to the Juniper Mist cloud for configuration download and management without requiring manual pre-staging or console access.

A. VLAN tagging is a specific configuration applied post-adoption. By default, the AP's management interface expects to operate on the untagged or native VLAN.

B. The AP does not have a default static IP of 192.168.0.1. While it has a fallback IP (192.168.1.1) for local access if it fails to connect to the cloud, its primary method is DHCP.

D. Requiring a manual static IP configuration is contrary to the ZTP model. The AP is designed to acquire its IP automatically to simplify large-scale deployments.

1. Juniper Mist Documentation, "AP and Switch Onboarding": This guide explicitly states the prerequisites for APs to connect to the Mist cloud. It specifies, "DHCP on the native VLAN to assign the AP an IP address, default gateway, and DNS server." This confirms that DHCP is the default and required method for initial IP acquisition. (Source: Juniper Mist Official Documentation).

2. Juniper Mist AP43 Quick Start Guide: In the "Step 2: Connect the AP to the Network" section, the guide instructs to "Connect the ETH0 port on the AP to an Ethernet switch port. The AP will get an IP address via DHCP." This is standard across all Mist AP hardware guides and confirms DHCP is the default behavior. (Source: Juniper Mist Official Hardware Documentation).

3. Juniper Mist Documentation, "What to do if my AP is not showing up as connected in the dashboard?": This troubleshooting document lists "Check if the AP has a valid IP address" as a primary step and details that the AP should receive this via DHCP. It also mentions the fallback IP of 192.168.1.1 if cloud connectivity fails, distinguishing it from the primary DHCP mechanism. (Source: Juniper Mist Official Documentation, Troubleshooting Section).

Assuming "Mixtape" is a typo for "Mist AP," the default configuration for the upstream Ethernet port (eth0) on a Juniper Mist Access Point is a trunk port. This configuration allows the AP to handle traffic for multiple VLANs simultaneously. While the port does accept untagged management traffic on its native VLAN (VLAN 1) by default, its fundamental mode is "trunk" to support WLANs that are mapped to different tagged VLANs. Among the given choices, this option is the most accurate description of the default port mode.

A. This describes an access port. The default configuration is a trunk port, which is designed to carry traffic for multiple VLANs, not just untagged traffic.

C. The interface is not configured to use a specific user-defined VLAN like 10 by default. The default native (untagged) VLAN is 1.

D. The interface is not configured to use a specific user-defined VLAN like 11 by default. The default native (untagged) VLAN is 1.

---

1. Juniper Mist Documentation, "Ports on the AP": This document explicitly states the default configuration. "By default, the Eth0/PoE port on the AP is configured as a trunk port, with VLAN 1 as the native VLAN. This allows the AP to get an IP address on the untagged VLAN, while still being able to bridge tagged traffic for specified WLANs."

2. Juniper Day One+ Book, "Mist AI for the Wireless LAN, First Edition": In Chapter 3, "Mist APs," the section on "AP Network Settings" explains that the AP requests a DHCP address on the untagged (native) VLAN by default but can be configured with a tagged VLAN for management. This behavior is characteristic of a trunk port with a native VLAN. (Page 31, "AP Network Settings").

The Juniper Mist cloud UI provides extensive remote troubleshooting capabilities. It allows network administrators to initiate live packet captures directly on managed devices without needing physical access. This includes capturing 802.11 wireless frames on a specific radio or for a particular client connected to a Mist Access Point. Additionally, for Juniper EX Series switches managed by the Mist cloud, the UI enables the initiation of wired packet captures on any specific switch port to analyze traffic and diagnose connectivity issues.

C. It can initiate a BLE packet capture.

The Mist UI provides extensive BLE analytics and location data but does not offer a user-facing tool to initiate a raw BLE protocol packet capture.

D. It can initiate a packet capture on cloud uplink.

While you can capture packets on a physical uplink port (as a wired capture), there is no distinct feature specifically to capture the "cloud uplink" control traffic.

1. Juniper Mist Documentation, "Live Packet Captures": This document details the wireless packet capture feature. It states, "You can use the packet capture tool to capture wireless frames on the AP. You can run the capture for a specific client or on a specific radio (2.4 GHz or 5 GHz)." This directly supports option A.

Source: Juniper Networks, Mist Cloud Documentation, Access Points > Troubleshoot with Live Tools > Live Packet Captures.

2. Juniper Mist Documentation, "Packet Capture (Switches)": This section explains the process for capturing wired packets on managed switches. It states, "You can use the packet capture tool to capture packets on a specific port of a switch... The packet capture tool is useful for troubleshooting network issues." This directly supports option B.

Source: Juniper Networks, Mist Cloud Documentation, Switches > Troubleshoot a Switch > Packet Capture.

The Juniper Mist BT11 is an enterprise-grade, BLE-only access point. It is specifically designed to augment existing Wi-Fi deployments with location services in a cost-effective manner. In scenarios where Wi-Fi coverage and capacity are already met by existing access points, but BLE coverage for location services is insufficient, the BT11 is the ideal low-cost device to deploy to fill those gaps without adding unnecessary and more expensive Wi-Fi hardware.

A. AP41: This is a full-featured Wi-Fi 6 access point with integrated vBLE. It is not a "BLE-only" device and is not the most cost-effective solution for this specific requirement.

C. AP32: This is a Wi-Fi 6 access point with integrated vBLE. It is designed for Wi-Fi access, not solely for augmenting BLE coverage.

D. AP43: This is a high-performance Wi-Fi 6 access point with integrated vBLE. It is an incorrect choice as it is not a low-cost, BLE-only device.

1. Juniper Mist BT11 Access Point Datasheet: "The Juniper BT11 is an enterprise-grade Access Point that is exclusively for Bluetooth® Low Energy (BLE). The BT11 is a key component of the Juniper Mist platform for indoor location services... The BT11 is designed to work in conjunction with Juniper Mist Wi-Fi Access Points to provide enterprise-grade BLE services..." (Juniper Networks, "BT11 Access Point Datasheet", Page 1, Overview section).

2. Juniper Mist AP41 Access Point Datasheet: "The Juniper Networks AP41 is a high-performance 802.11ax (Wi-Fi 6) access point that supports 4x4:4SS in 5GHz and 2.4GHz bands. The AP41 also has a dedicated 4th radio for band scanning and a dynamic vBLE 16-element antenna array..." (Juniper Networks, "AP41 Access Point Datasheet", Page 1, Product Description section).

3. Juniper Mist AP32 Access Point Datasheet: "The Juniper AP32 is a Wi-Fi 6 (802.11ax) access point (AP) that supports 2x2:2SS and dual 5GHz operation. The AP32 has a patented virtual Bluetooth® LE (vBLE) antenna array..." (Juniper Networks, "AP32 Access Point Datasheet", Page 1, Product Description section).

4. Juniper Mist AP43 Access Point Datasheet: "The Juniper AP43 is a high-performance Wi-Fi 6 (802.11ax) access point (AP) that supports 4x4:4SS and a 4th radio for spectrum monitoring. The AP43 has a patented virtual Bluetooth® LE (vBLE) antenna array..." (Juniper Networks, "AP43 Access Point Datasheet", Page 1, Product Description section).