A mis-tagged application server is placed in the wrong GBP group and suddenly reaches systems it should not. What does this incident highlight?
Select an answer to reveal the explanation.
Short Explanation
Wrong badge, wrong doors. If the server wears the finance club tag by mistake, policy treats it like finance. Classification accuracy is the load-bearing beam under GBP.
Full Explanation
GBP enforcement keys off group membership. A misclassified endpoint inherits the privileges of the wrong group and can bypass the intended least-privilege posture. EVPN reachability does not neutralize bad tags, and underlay filters are not a guaranteed override of incorrect GBP assignment. Mis-tags are a data-plane policy problem, not merely a dashboard cosmetic issue.