Which two statements are correct about switch adoption? (Choose two.)

Juniper Mist supports two primary methods for switch adoption: Greenfield and Brownfield.

Greenfield adoption is designed for new deployments and utilizes a Zero-Touch Provisioning (ZTP) model. This process requires a cloud-enabled Juniper EX switch and its associated claim code (or activation code) which is entered into the Mist portal. When the switch powers on and connects to the network, it automatically contacts the Mist cloud, authenticates using its identity, and downloads its configuration.

Brownfield adoption is for existing switches already deployed or those that do not have a claim code. This method requires manual intervention. An administrator generates a set of CLI commands from the Mist portal and applies them to the switch, which then establishes a management connection to the Mist cloud for adoption.

B. Switch adoption uses SSH over TCP port 443.

This is incorrect. Switches connect to the Mist cloud using a secure WebSocket over TLS on TCP port 443 for management, not SSH over 443.

C. Switch adoption requires Mist AP.

This is incorrect. While a Mist AP can act as a proxy for a switch without direct Internet access, it is not a general requirement for switch adoption.

1. Juniper Mist Documentation, "Adopt a Switch": This document explicitly outlines the two methods. It states, "Enter the claim code or activation code that you received when you purchased the switch. This is the easiest way to add a switch, and is the method we recommend for new (greenfield) deployments." It also describes the alternative: "Adopt a switch that is already connected to your network. This method is useful for existing (brownfield) deployments." This directly supports answers A and D.

2. Juniper Mist Documentation, "Juniper Mist Ports and IP Addresses for Firewall Configuration": This official guide details the required network connectivity. For switch management, it specifies TCP port 443 for outbound connections to ep-terminator.mistsys.net and redirect.mist.com. The protocol is listed as a secure WebSocket, not SSH, which invalidates option B.

3. Juniper Mist Documentation, "Configure a Mist AP as a Wired Assurance Proxy": This document describes the AP proxy feature as an optional configuration for specific network scenarios (e.g., when a switch lacks direct cloud connectivity), confirming that a Mist AP is not a mandatory requirement for switch adoption, thus invalidating option C.