Which of the following cannot be used as a matching criterion in route policy statements?
Which of the following cannot be used as a matching criterion in route policy statements?
Route policy statements are typically used to control routing behavior based on specific criteria such as source IP address, prefix lists, and protocol type. However, TCP source port is related to transport layer operations and does not directly influence routing decisions. Hence, TCP source port cannot be used as a matching criterion in route policy statements.
The correct answer I believe is C. Route policies allow you to configure routing according to specifically defined policies. You can create policies and entries to allow or deny paths based on parameters such as source address, destination address, protocol, and community list. The following are the available options to match under the 'from' and 'to' match entry config>router>policy-options begin policy-statement name entry entry-id from area area-id as-path {add | replace} name community comm-name community expression expression external family [ipv4] [vpn-ipv4] group-address prefix-list-name interface interface-name level {1 | 2} neighbor {ip-address | prefix-list name} origin {igp | egp | incomplete | any} prefix-list name [name...(up to 5 max)] protocol protocol [all | instance instance] source-address ip-address tag tag type type to level {1 | 2} neighbor {ip-address | prefix-list name} prefix-list name [name...(up to 5 max)] protocol protocol [all | instance instance]
You Have the option prefix-list name [name...(up to 5 max)] I think the right one is B
The right answer is B. we can filter with all the rest