Question 180
A core network change board wants to avoid: A route map denies a tagged customer route but includes a later permit clause matching all prefixes, and operations misinterprets the first match behavior. Which ongoing safeguard fits best?
Explanation
Correct Answer
Include tagged and untagged candidate routes in route-map test suites. This helps prevent recurrence of the issue: A route map denies a tagged customer route but includes a later permit clause matching all prefixes, and operations misinterprets the first match behavior. Acceptance evidence should be: Test prefixes show the tagged route rejected and only approved routes advertised.
Incorrect Answers
Require boundary-prefix tests whenever prefix sets are edited. That is a sensible control for ANOTHER scenario: A route-policy template attempts to match a more-specific /25 by using an exact /24 prefix without a length range, mistakenly accepting only the aggregate. It is less targeted to this issue than: Include tagged and untagged candidate routes in route-map test suites.
Maintain positive and negative RPL policy unit tests for each provider peer. That is a sensible control for ANOTHER scenario: An IOS XR route policy applies `pass` before a prefix filter and an engineer expects later reject logic to stop evaluation automatically. It is less targeted to this issue than: Include tagged and untagged candidate routes in route-map test suites.
Rotate peer keys through a coordinated overlap and verification plan. That is a sensible control for ANOTHER scenario: A service-provider IS-IS adjacency drops intermittently when one side uses authentication while the other still sends unauthenticated LSPs. It is less targeted to this issue than: Include tagged and untagged candidate routes in route-map test suites.