JN0-102 · Question #307
user@router> show route inet.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, = Both 10.10.10.91/32 [Direct/0] 00:09:40 >via lo0.0 10.10.10.92/32…
The correct answer is C. 192.168.50.0/24 and 192.168.51.0/24. The policy demo is configured to match static routes that are 192.168.0.0/16 or more specific. Among the available routes, only 192.168.50.0/24 and 192.168.51.0/24 are static and fall within the specified prefix range.
Question
user@router> show route inet.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 10.10.10.91/32 *[Direct/0] 00:09:40 >via lo0.0 10.10.10.92/32 *[OSPF/10] 00:01:50, metric 1 >to 172.16.1.2 via ge-0/0/2.0 100.100.1.0/24 *[Static/5] 00:01:50 Reject 172.16.1.0/24 *[Direct/0] 00:06:09 >via ge-0/0/2.0 172.16.1.1/32 *[Local/0] 00:06:09 Local via ge-0/0/2.0 192.168.0.0/16 *[Aggregate/130] 00:00:06 Reject 192.168.0.0/17 *[Aggregate/130] 00:00:06 >to 172.16.1.2 via ge-0/0/2.0 192.168.50.0/24 *[Static/5] 00:00:06 >to 172.16.1.2 via ge-0/0/2.0 192.168.51.0/24 *[Static/5] 00:00:06 >to 172.16.1.2 via ge-0/0/2.0 user@router> show configuration policy-options policy-statement demo { term 1 { from { protocol static; route-filter 192.168.0.0/16 orlonger accept; } then accept; } } user@router> show configuration protocols ospf export demo; area 0.0.0.0 { interface ge-0/0/2.0; } Given the configuration and routing table shown in the exhibit, which routes will be advertised to OSPF neighbors because of the demo policy?
Options
- A192.168.0.0/16 only
- B192.168.50.0/24 only
- C192.168.50.0/24 and 192.168.51.0/24
- D192.168.0.0/17, 192.168.50.0/24, and 192.168.51.0/24
How the community answered
(31 responses)- A6% (2)
- B6% (2)
- C84% (26)
- D3% (1)
Why each option
The policy `demo` is configured to match static routes that are `192.168.0.0/16` or more specific. Among the available routes, only `192.168.50.0/24` and `192.168.51.0/24` are static and fall within the specified prefix range.
The route `192.168.0.0/16` is an aggregate route, not a static route, so it does not match the `from protocol static` condition.
While `192.168.50.0/24` matches the policy, `192.168.51.0/24` also matches and is omitted from this choice.
The `route-filter 192.168.0.0/16 orlonger` matches routes that are `192.168.0.0/16` itself or any more specific prefix within that range. The `from protocol static` clause further filters this to only include routes learned via the static protocol. Both `192.168.50.0/24` and `192.168.51.0/24` are explicitly marked as static routes and are more specific than `192.168.0.0/16`, making them the only matches.
The `192.168.0.0/17` route is an aggregate route, not a static route, so it does not match the `from protocol static` condition.
Concept tested: Route policy matching (protocol, route-filter)
Source: https://www.juniper.net/documentation/us/en/software/junos/routing-policy/topics/topic-map-routing-policy-match-conditions.html
Topics
Community Discussion
No community discussion yet for this question.