A policy term at a cooperative's border router does not match the current route, but the policy has additional terms below it that might. Which flow-control action would Junos apply by default in this situation?
Select an answer to reveal the explanation.
Short Explanation
When a route doesn't match a term, nothing dramatic happens, Junos just quietly moves on to check the next term in that same policy, which is the built-in next term behavior. It's not a reject, not an accept, and it doesn't skip ahead to a whole different policy. Non-matches simply fall through to whatever comes next in line.
Full Explanation
When a route fails to match the from or to conditions of a given term, Junos does not apply that term's then action at all, since the action only fires on a match, and instead evaluation automatically falls through to the next term within the same policy, which is functionally equivalent to an implicit next term. This is what allows a policy to be built as a sequence of increasingly specific exceptions followed by a catch-all term, since a route simply keeps moving down the list until something actually matches it. The first distractor is wrong because reject is a terminating action that only applies when a term's conditions are met and its then clause specifies it; a non-match does not trigger any then action. The second distractor is wrong for the same reason in the opposite direction: a non-match does not implicitly accept the route, it simply defers the decision to whatever term comes next. The last distractor confuses this fall-through behavior with the explicit then next policy action, which is a different, deliberately configured action that jumps to an entirely separate policy rather than the next term in the current one. A useful caveat is that if a route falls through every term in every policy in the chain without a match, the protocol's own default routing policy ultimately decides its fate. A concrete check is show policy <name> detail alongside a trace of which term actually matched, using the policy's own then trace or count actions during testing.