Hi flamego,
I quickly did a test as well as to confirm the answer.
Answer is D.
Explanation:
as per policy it will accept the route 192.168.0.0/16 or longer. So the below routes are applicable to accept
192.168.0.0/16, 192.168.0.0/17, 192.168.50.0/24 and 192.168.51.0/24
So we have 192.168.0.0/17, 192.168.50.0/24 and 192.168.51.0/24 in option D. So this is the answer.
Lab output
:
# run show route 192.168.0.0/16
inet.0: 17 destinations, 17 routes (17 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
192.168.0.0/16 *[Aggregate/130] 00:00:23
Reject
192.168.0.0/17 *[Static/5] 00:03:39
Receive
192.168.50.0/24 *[Static/5] 00:03:16
Receive
192.168.51.0/24 *[Static/5] 00:03:16
Receive
[edit]
labroot@jtac-mx480-r2020#
labroot@jtac-mx480-r2020# show policy-options policy-statement demo
term 1 {
from {
protocol static;
route-filter 192.168.0.0/16 orlonger accept;
}
then accept;
}
[edit]
labroot@jtac-mx480-r2020#
remote end:
# run show route 192.168.0.0/16
inet.0: 26 destinations, 31 routes (25 active, 1 holddown, 2 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both
192.168.0.0/16 [OSPF/150] 00:00:07, metric 0, tag 0
> to 10.0.0.3 via xe-2/0/0.0
192.168.0.0/17 *[OSPF/150] 00:02:21, metric 0, tag 0
> to 10.0.0.3 via xe-2/0/0.0
192.168.50.0/24 *[OSPF/150] 00:02:21, metric 0, tag 0
> to 10.0.0.3 via xe-2/0/0.0
192.168.51.0/24 *[OSPF/150] 00:02:21, metric 0, tag 0
> to 10.0.0.3 via xe-2/0/0.0
[edit]
labroot@piekna11-gw-01#
Hope this helps
--------------------------------------------------------------------------------------------------------
If this post was helpful, please mark this post as an "Accepted Solution".
Kudos are always appreciated!
--------------------------------------------------------------------------------------------------------