City architects want to know which protocol carries EVPN routes for the municipal VXLAN fabric. Which answer is correct?
Select an answer to reveal the explanation.
Short Explanation
EVPN rides on MP-BGP—the same BGP family toolkit, just the EVPN address family carrying MAC/IP and related routes. IS-IS, nightly FTP MAC dumps, and LLDP are not that control plane. When the city asks what “carries EVPN,” answer Multiprotocol BGP EVPN AFI/SAFI.
Full Explanation
The protocol that carries EVPN routes for the municipal VXLAN fabric is Multiprotocol BGP using the EVPN address family (AFI/SAFI), whether VTEPs peer directly or—more commonly at city scale—through route reflectors. MP-BGP EVPN is how Type-2 MAC/IP routes and other EVPN route types are exchanged on Juniper data-center switches serving civic tenants.
IS-IS alone flooding MAC tables inside TLV 22 without BGP is not the EVPN control plane for VXLAN overlays. FTP pulling static MAC files from a TFTP server every night is not an EVPN control plane and does not scale or converge like BGP. LLDP extended community attributes do not replace BGP for host route exchange between VTEPs, even though LLDP remains useful for physical topology discovery on leaf-spine links.
Exam caveat: EVPN signaling rides MP-BGP EVPN AFI/SAFI; underlay IGP, LLDP, and file-transfer options are incorrect distractors on professional exams.
Operational check: verify EVPN AFI/SAFI negotiation on leaf BGP sessions to RRs or peers, display received EVPN routes, and confirm route-target import installs MAC/IP entries into the intended MAC-VRF for a city test VNI with bidirectional learning.
In civic fabric operations, retain the correct idea—Multiprotocol BGP using the EVPN address family (AFI/SAFI) carries EVPN routes between VXLAN VTEPs or route reflectors—and reject distractors that confuse layers or tools. Specifically, do not treat “IS-IS alone floods MAC tables inside TLV 22 without BGP.” as valid, do not accept “FTP pulls static MAC files from a TFTP server every night as the EVPN control plane.” as a substitute design, and do not operationalize “LLDP extended community attributes replace BGP for host route exchange between VTEPs.” in production runbooks. Re-validate after changes with show commands for sessions, routes, VTEP reachability, and a simple tenant traffic test appropriate to the VNI under review.