Question 580
A core network change board wants to avoid: A route reflector exports every VRF route to a public transit peer after route targets are reused carelessly in an import policy. Which ongoing safeguard fits best?
Explanation
Correct Answer
Enforce explicit domain boundaries in route-target and global export policy checks. This helps prevent recurrence of the issue: A route reflector exports every VRF route to a public transit peer after route targets are reused carelessly in an import policy. Acceptance evidence should be: A transit peer receives only global internet prefixes while VPN routes remain in authorized VRFs.
Incorrect Answers
Archive policy diffs and route-acceptance fixtures with change approvals. That is a sensible control for ANOTHER scenario: A policy deployer overwrites an existing RPL route policy in production without a prechange candidate diff, causing accidental withdrawal of one customer aggregate. It is less targeted to this issue than: Enforce explicit domain boundaries in route-target and global export policy checks.
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: Enforce explicit domain boundaries in route-target and global export policy checks.
Teach neighbor-state expectations per OSPF network type in runbooks. That is a sensible control for ANOTHER scenario: A multiaccess OSPF network forms neighbor relationships but routes stay stuck at 2-Way between two DROTHER peers, and the operator repeatedly resets them. It is less targeted to this issue than: Enforce explicit domain boundaries in route-target and global export policy checks.