Engineers need every leaf to enforce the same GBP decisions for a mobile municipal workload. At a describe-level understanding, how does group information typically stay consistent across the fabric?
Select an answer to reveal the explanation.
Short Explanation
If only one leaf knows the badge color, the next leaf treats the endpoint like a stranger. EVPN carries the group story around the fabric so enforcement matches everywhere the workload lands.
Full Explanation
When engineers need every leaf to enforce the same GBP decisions for a mobile municipal workload, at a describe-level understanding group information typically stays consistent across the fabric because group information is distributed with EVPN signaling so leaves can enforce policy consistently. As the workload moves or attaches on different VTEPs, EVPN-distributed group context lets each leaf apply the same allow and deny outcomes without relying on per-box tribal knowledge. Each leaf learning groups only from local SPAN mirrors with no control-plane distribution cannot scale consistent policy for mobile civic endpoints. GBP tags are not flooded only in underlay OSPF opaque LSAs as the described distribution model for EVPN-VXLAN GBP. Operators must not paste identical static MAC ACLs on every VTEP with no EVPN involvement if the goal is scalable, signaling-driven group consistency. Exam caveat: associate fabric-wide GBP consistency with EVPN control-plane distribution rather than underlay flooding or manual ACL cloning. Operational check: attach a tagged endpoint on leaf A, move or dual-home it toward leaf B in the lab, confirm both leaves show the same GBP group context via EVPN-learned information, and verify identical inter-group deny behavior before and after the move.