Question 40
For a carrier automation platform team, the change record describes: Two eBGP routes reach the same prefix with equal local preference, but operations assumes a shorter AS_PATH cannot affect selection and blames a metric change. What preventive validation should be standard?
Explanation
Correct Answer
Keep best-path attribute snapshots alongside policy change tickets. This helps prevent recurrence of the issue: Two eBGP routes reach the same prefix with equal local preference, but operations assumes a shorter AS_PATH cannot affect selection and blames a metric change. Acceptance evidence should be: A controlled pair of paths selects the expected shorter AS path when higher-priority attributes are equal.
Incorrect Answers
Document nondefault origin modifications to avoid opaque path changes. That is a sensible control for ANOTHER scenario: A BGP router holds multiple valid paths yet chooses an unanticipated route because one path has a smaller origin code, not because of a mistaken community. It is less targeted to this issue than: Keep best-path attribute snapshots alongside policy change tickets.
Require ordered attribute comparison in BGP troubleshooting notes. That is a sensible control for ANOTHER scenario: A provider expects an iBGP-learned path to beat an otherwise equal eBGP path simply because the iBGP router has a lower IGP cost to the next hop. It is less targeted to this issue than: Keep best-path attribute snapshots alongside policy change tickets.
Distinguish translation versus encapsulation requirements in IPv4-as-a-service profiles. That is a sensible control for ANOTHER scenario: A provider tries to deliver MAP-T using an IPv4-in-IPv6 encapsulation template and loses packets because the customer expects stateless translation. It is less targeted to this issue than: Keep best-path attribute snapshots alongside policy change tickets.