A county enables VXLAN between leaves but deploys no EVPN or other MAC/IP control plane. What is the primary remote-learning implication?
Select an answer to reveal the explanation.
Short Explanation
No control plane means the county is back to learning the hard way—flood until someone answers. That flood-and-learn habit can work in a lab, but it gets chatty and brittle as civic pods grow. You do not magically get EVPN Type-2 routes or Type-5-only behavior just by turning VXLAN on.
Full Explanation
Without an EVPN-like control plane, VXLAN deployments historically relied on flood-and-learn: unknown unicasts and other BUM frames are flooded so remote VTEPs can learn source MACs from data-plane traffic. That approach functions but scales poorly and increases underlay/overlay BUM load compared with BGP EVPN MAC/IP advertisement. Enabling VXLAN encapsulation alone does not create EVPN routes or force Type-5-only forwarding. Designers choosing no control plane must accept flooding-based discovery and plan multicast or ingress-replication BUM accordingly.