Question 640
To prevent recurrence of this provider network issue: A policy deployer overwrites an existing RPL route policy in production without a prechange candidate diff, causing accidental withdrawal of one customer aggregate. Which control should be retained?
Explanation
Correct Answer
Archive policy diffs and route-acceptance fixtures with change approvals. This helps prevent recurrence of the issue: A policy deployer overwrites an existing RPL route policy in production without a prechange candidate diff, causing accidental withdrawal of one customer aggregate. Acceptance evidence should be: A sandbox change shows the aggregate retained and the desired new filter applied before production approval.
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: Archive policy diffs and route-acceptance fixtures with change approvals.
Include tagged and untagged candidate routes in route-map test suites. That is a sensible control for ANOTHER scenario: A route map denies a tagged customer route but includes a later permit clause matching all prefixes, and operations misinterprets the first match behavior. It is less targeted to this issue than: Archive policy diffs and route-acceptance fixtures with change approvals.
Baseline BFD jitter and loss before setting aggressive detection timers. That is a sensible control for ANOTHER scenario: A BFD session on a long-haul link uses submillisecond detection and repeatedly declares faults during normal microbursts despite healthy optics. It is less targeted to this issue than: Archive policy diffs and route-acceptance fixtures with change approvals.