In Junos OS routing policy evaluation, when a route-filter match condition includes a specific action (e.g., accept, reject), that action is executed as soon as a route matches the filter entry. This immediate execution takes precedence over any action defined in the then clause of the same policy term. Consequently, the then clause is bypassed for that specific matching route, and the policy evaluation for that route concludes based on the route-filter's action. This behavior allows for more granular control within a single policy term.

A. The then clause is ignored, not deferred to. The route-filter action has precedence.

B. Actions are not combined; the route-filter action overrides the then clause action for the matching route.

C. The route-filter action is applied even if a then action is defined, and it takes precedence.

1. Juniper Networks. (2023). Routing Policies, Firewall Filters, and Traffic Policers Feature Guide. "Route Filter Match Condition for Routing Policies". The documentation states: "If you specify an action with a route in the route-filter match condition, and the route matches, the action specified in the route-filter is performed. The action specified in the then statement is ignored."

2. Juniper Networks. (n.d.). Junos OS Routing Protocols Library for Routing Devices. "Example: Configuring a BGP Route Filter". This section provides configuration examples that illustrate the precedence of actions within a route-filter over the term's then action, demonstrating that the route-filter action is final for a matching prefix.