City architects ask how VTEPs can learn remote MAC and IP mappings for municipal workloads without relying on endless unknown-unicast flooding. Which control-plane approach best answers that design goal?
Select an answer to reveal the explanation.
Short Explanation
Picture each leaf as a city branch that used to shout every unknown address into the street until someone answered. EVPN is the shared directory: VTEPs advertise MAC/IP mappings over BGP so you stop living on endless flood-and-learn. Flood-only designs still work in a pinch, but they do not scale like a real municipal fabric directory.
Full Explanation
Classic VXLAN flood-and-learn discovers remote hosts by flooding BUM/unknown traffic across the overlay, which becomes expensive and noisy as VTEP and host counts grow. EVPN provides a control plane—commonly Multiprotocol BGP with the EVPN address family—so VTEPs distribute MAC/IP routes for remote learning without perpetual unknown-unicast flooding. Underlay IGPs such as OSPF carry VTEP reachability, not tenant MAC tables, and stretching raw VLANs across the underlay abandons the VXLAN overlay model. For JNCIP-DC designs, prefer EVPN-based MAC/IP distribution when the goal is scalable remote learning.