Question 310
At a dual-homed business network peering with two upstream providers, a Junos specialist investigates this scenario: A route filter intended to allow a single aggregate accidentally accepts many more-specific customer prefixes. The routing policy must retain intended primary and backup paths. What protocol behavior accounts for this failure?
Explanation
Correct Answer
For a dual-homed business network peering with two upstream providers, the governing mechanism is: Junos route filters distinguish exact matching from longer or longer-prefix patterns. It explains the reported symptom: A route filter intended to allow a single aggregate accidentally accepts many more-specific customer prefixes. The intended response is: Choose exact or bounded prefix-length matching appropriate to the advertisement contract. Verification: Only intended prefix lengths pass the import or export policy.
Incorrect Answers
In Junos BGP best-path selection an eligible shorter AS path is generally preferred after higher-priority criteria tie. This alternative mechanism does not match the current fault.
BGP export policy controls which eligible active routes the speaker announces to selected neighbors. Fixing that different mechanism would not address the current root cause: junos route filters distinguish exact matching from longer or longer-prefix patterns.
A BGP prefix-limit control detects or constrains excessive received NLRI from a peer. Its verification is distinct from the reported condition: A route filter intended to allow a single aggregate accidentally accepts many more-specific customer prefixes. The routing policy must retain intended primary and backup paths.