In acore-distribution campus fabricmodel, the EVPN-VXLAN overlay is establishedonly between the core and distribution tiers. Theaccess switches are not part of the EVPN fabric; they connect upstream to distribution but do not run VXLAN tunnels.
"In the core-distribution campus fabric, only the core and distribution layers participate in the EVPN-VXLAN topology. The access layer connects to the distribution switches and forwards traffic but does not take part in the EVPN-VXLAN fabric." Option A:Correct - EVPN-VXLAN is built between core and distribution tiers.
Option B:Incorrect - both coreand distributionparticipate, not just core.
Option C:Incorrect - access switches are excluded from EVPN-VXLAN participation.
Option D:Correct - the access layer does not participate in EVPN-VXLAN.
References:
Juniper Mist AI for Wired - Campus Fabric Core-Distribution Architecture Juniper Validated Design - EVPN-VXLAN Campus Deployment Models Junos OS EVPN Campus Fabric Design Guide

According to the Juniper Mist Wired Assurance Configuration Guide, the foundational step for implementing Layer 2 segmentation within the Mist UI is the creation of a "Network". In the context of Mist Wired Assurance, a Network is logically synonymous with a Virtual Local Area Network (VLAN). To define a network, a user must navigate to the Networks section-located within an organization-level template, a site- level configuration, or an individual switch configuration-and click to add a new entry.
The two mandatory parameters for this step are naming the VLAN and providing the corresponding VLAN ID. The name serves as a human-readable alias (such as "Corporate_Data" or "IoT_Devices") that allows administrators to easily reference the segment across different parts of the configuration without constantly tracking numeric IDs. The VLAN ID is the specific numeric value (ranging from 1 to 4094) that will be used by the switch for 802.1Q tagging on the physical wire.
This step is a prerequisite for more advanced configurations. Once a network is created with its name and ID, it can then be selected within a Port Profile. While creating a port profile (Option C) or an access policy (Option D) are common tasks in the deployment workflow, they are dependent on the prior existence of a defined Network. For instance, a Port Profile defines how a port behaves (e.g., access vs. trunk), but it must point to a specific Network name to know which VLAN to assign to that interface. Similarly, site variables can be used to override these VLAN IDs at specific locations, but the base definition requires the initial pairing of a name and a default ID in the portal.

Within Mist Insights,Client Eventsshow state transitions such asreassociationand IP-level issues likeDHCP Denied.
These help correlate connectivity issues across wired or wireless edge connections.
References:
Mist AI Insights Dashboard Guide
Mist AI for Wired - Client Event Monitoring