County courts need all routers in the civic ASN to exit via the ISP that offers the better SLA, without using MED toward customers. Which BGP attribute should they set for outbound preference inside the AS?
Select an answer to reveal the explanation.
Short Explanation
LOCAL_PREF is the sticky note passed around the whole ASN saying ‘prefer this ISP exit.’ Set it high on the better-SLA path and every iBGP speaker gets the memo. Weight is a sticky note that never leaves one router’s desk.
Full Explanation
LOCAL_PREF is evaluated early in BGP best-path selection and is propagated via iBGP, making it the standard tool for consistent outbound exit preference inside an AS. County courts needing all routers in the civic ASN to exit via the ISP with the better SLA, without using MED toward customers, should set LOCAL_PREF so outbound traffic preference is consistent across iBGP speakers. Prefer LOCAL_PREF for ASN-wide SLA-based exit selection.
MED is primarily an inbound preference hint to an upstream and is not the AS-wide outbound tool; it is not always compared before LOCAL_PREF as a mandatory first step for this design. Origin code Incomplete on every ISP prefix does not correctly force a disciplined SLA-based exit policy. Cisco Weight on a single border router does not propagate, so other routers will not inherit the same exit.
Exam caveat: higher LOCAL_PREF wins; apply it via route-maps on inbound ISP advertisements so the entire AS agrees, and remember Weight can still override locally on one box if mis-set. Operational check: set higher LOCAL_PREF for the preferred ISP, show BGP paths on multiple routers, confirm identical exit choice, and traceroute outbound traffic to verify the SLA path.