JN0-106 ยท Routing policy
Policy structure, terms, match criteria and actions
Policy statements, from and to conditions, then actions (accept, reject, next term, next policy), route filters and match types (exact, orlonger, longer, upto, prefix-length-range).
Key points
- policy-statement: named terms evaluated top to bottom.
- Term: optional from (and to) conditions select routes; then holds actions such as accept, reject, next term, next policy.
- route-filter (in from): compares a prefix using a match type.
- exact: same length; longer: strictly more specific.
- orlonger: same or more specific; upto: configured length up to a limit.
- prefix-length-range: lower and upper bound, inclusive.
Practice questions
Which route-filter match type matches only prefixes that are strictly more specific than the configured one?
- exact
- orlonger
- longer
- upto
Show answer
Answer: C. longer
longer excludes the configured prefix itself. orlonger includes it, exact matches only that length, and upto caps the length from above while still including the configured length.
Which of these are valid route-filter match types?
- exact
- orlonger
- upto
- shorter
- lower-bound
Show answer
Answer: A. exact, B. orlonger, C. upto
exact, orlonger and upto are real match types (along with longer, prefix-length-range, through and address-mask). There is no match type called shorter or lower-bound.
The filter "route-filter 10.0.0.0/8 longer" also matches the route 10.0.0.0/8 itself.
Show answer
Answer: False
False. longer requires a strictly greater prefix length than the configured one, so the /8 itself is excluded. Use orlonger to include it.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
