An animal-control HQ PE should not import every extranet VPNv4 route advertised in the autonomous system. What control limits which VPN routes that PE accepts?
Select an answer to reveal the explanation.
Short Explanation
RT filtering is the bouncer at the PE door: if the route’s RT isn’t on the guest list, it does not get into the VRF. Animal-control HQ should not collect every extranet just because the RR has them. IGP metrics and PHP are the wrong tools for VPN membership.
Full Explanation
VPNv4 route acceptance at a PE is governed by whether the route’s extended community RTs match the VRF’s import policy. RT filtering prevents a PE from installing extranets it should not serve, conserving memory and enforcing topology. IGP metrics, PHP, and RD collapsing do not replace import-RT policy. Apply explicit RT filters so animal-control HQ imports only the extranets it is entitled to.