A policy term is written with a then action of reject but includes no from or to condition at all. Which routes will this term match when evaluation reaches it?
Select an answer to reveal the explanation.
Short Explanation
A term with nothing in its from or to clause isn't a term that matches nothing, it's the opposite: it matches everything that reaches it, unconditionally. That's exactly the shape of a catch-all term, often placed last with a reject to clean up anything an earlier, more specific term didn't already handle. No conditions means no restrictions on what qualifies.
Full Explanation
A term without any from or to condition matches every route that is evaluated against it, since match conditions are what narrow down which routes a term applies to, and the absence of any condition places no restriction at all. This makes a bare then reject term with no conditions a classic catch-all, commonly placed as the last term in an export policy to guarantee that anything not already handled by an earlier, more specific accept term is explicitly withheld, reinforcing the export chain's overall intent even though the protocol's own default export policy would ultimately reject it anyway. Reading an empty condition as a match against nothing gets the logic backwards, when in Junos policy the opposite is true. Restricting the term to routes earlier terms missed describes something closer to normal fall-through behavior, but it incorrectly implies this term is somehow restricted to only those previously-unmatched routes, when in fact it would match a route even on the very first term of the policy if it were placed there, since it has no conditions to narrow its scope. The protocol-based distractor invents a restriction tied to the policy's application point, but a term's matching is governed entirely by its own from and to conditions, not by which protocol the policy happens to be attached to. A caveat worth remembering is that placing such a term early in a policy is risky, since its unconditional match combined with a terminating action would immediately end evaluation for every route that reaches it. A concrete check is adding a temporary then count action to the term and reviewing show policy <name> statistics to confirm it is matching every route as expected.