What is the difference between RPL and route map actions?

Question

Options

• ARPL uses match, set, drop, and stop actions, and route maps use match, set, and drop actions
• BRPL uses match, pass, set, and drop actions, and route maps use match, set, and drop actions.
• CRPL uses pass, set, and drop actions only, and route maps use match, set, and drop actions.
• DRPL uses pass, set, drop, and done actions, and route maps use match and set actions only.

• A
  4% (2)
• B
  6% (3)
• C
  2% (1)
• D
  89% (47)

Explanation

Option D correctly identifies that RPL (Route Policy Language, used in IOS XR) has four distinct action types - pass, set, drop, and done - where pass accepts and continues processing while done accepts and immediately terminates processing. Route maps (used in IOS/IOS-XE) operate with only match conditions and set modifications, with permit/deny determined at the clause level rather than as standalone action keywords.

Why the distractors fail:

• A is wrong because RPL does not use match or stop as action keywords - those terms belong to route map and IOS syntax respectively.
• B incorrectly adds match to RPL's action set and omits done, which is a critical RPL action distinct from pass.
• C gets three RPL actions right but drops done, which is essential - without it, you can't distinguish between "accept and keep processing" (pass) and "accept and stop" (done).

Memory tip: For RPL, remember "PSD+D" - Pass, Set, Drop, then Done - the first three feel intuitive, and done is the IOS XR "hard stop" that separates RPL from route maps, which only care about matching and modifying attributes.

No community discussion yet for this question.