-- Exhibit --
[edit policy-options policy-statement my-policy]
user@router# show
term 1 {
from {
route-filter 192.168.0.0/16 prefix-length-range /20-/24;
}
then accept;
}
-- Exhibit --
Referring to the exhibit, which three networks match the policy? (Choose three.)
Click on the arrows to vote for the correct answer
A. B. C. D. E.ADE
The policy statement shown in the exhibit is defining a term named "1" that matches a specific route filter and then applies an accept action.
The route filter specified in the "from" section of the term is "192.168.0.0/16 prefix-length-range /20-/24". This filter matches all routes that fall within the 192.168.0.0/16 address block and have a prefix length between 20 and 24 bits. This means that the policy will match any route in the 192.168.0.0/16 address block that has a subnet mask between /20 (255.255.240.0) and /24 (255.255.255.0).
Based on this information, the three networks that match the policy are:
A. 192.168.0.0/20 - This network falls within the 192.168.0.0/16 address block and has a prefix length of 20 bits, which falls within the specified prefix-length-range of /20-/24.
C. 192.168.128.0/18 - This network also falls within the 192.168.0.0/16 address block and has a prefix length of 18 bits, which falls outside the specified prefix-length-range of /20-/24. Therefore, this network does not match the policy.
D. 192.168.128.0/21 - This network also falls within the 192.168.0.0/16 address block and has a prefix length of 21 bits, which falls within the specified prefix-length-range of /20-/24.
E. 192.168.64.0/24 - This network also falls within the 192.168.0.0/16 address block but has a prefix length of 24 bits, which falls within the specified prefix-length-range of /20-/24.
Therefore, the three networks that match the policy are 192.168.0.0/20, 192.168.128.0/21, and 192.168.64.0/24.