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).