How does conditional matching operate with RPL?

Question

Options

• AThe matching identifies a set of criteria, and an action is taken based on whether the criteria are
• BThe matching identifies a group of routes that are removed from the routing table when the
• CThe matching identifies tags that are placed on routes from neighboring autonomous systems and
• DThe matching identifies interfaces that run the same routing protocol and manipulates data based

• A
  92% (46)
• B
  2% (1)
• C
  2% (1)
• D
  4% (2)

Explanation

Conditional matching in RPL (Route Policy Language) follows an if-then-else programming paradigm. A routing policy defines match criteria (such as prefix sets, community sets, AS-path sets, or local-preference values), and then specifies actions (such as setting attributes, accepting, or dropping routes) that are applied only when those criteria are satisfied or not satisfied. This is the core mechanism of policy-based routing control. Option B is incorrect because RPL does not remove routes from the routing table based on matching; it manipulates BGP attributes or controls route acceptance/redistribution. Option C is incorrect because tags are a route map concept and RPL conditional matching is not limited to routes from neighboring ASes. Option D is incorrect because RPL operates on route attributes, not on interfaces running routing protocols.

No community discussion yet for this question.