There can be multiple nodes under one Route-Policy, and the device starts matching in order when calling Route-Policy.

Question

Options

• ATRUE
• BFALSE
• C
• D

• A
  72% (36)
• B
  8% (4)
• C
  16% (8)
• D
  4% (2)

Explanation

A Route-Policy (also called a route policy or route-map in some vendor contexts) supports multiple nodes, each identified by a unique node number, and the device evaluates them sequentially in ascending node order - stopping at the first matching node. This ordered, sequential matching is fundamental to how Route-Policy logic works, making A (TRUE) correct.

B (FALSE) is wrong because denying multiple nodes would break the core design: Route-Policies are explicitly built to support chained conditional logic across numbered nodes (e.g., node 10, node 20, node 30), each with its own match and apply clauses.

Memory tip: Think of Route-Policy nodes like numbered paragraphs in a rulebook - the device reads from the lowest number upward and acts on the first paragraph that matches, skipping the rest. If no node matches, the route is denied by default.

No community discussion yet for this question.