An assessor’s office needs redistributed transit routes that match a prefix-list to receive both a new metric and a route tag in one policy pass. How should the route-map be built?
Select an answer to reveal the explanation.
Short Explanation
One sticky note can carry two scribbles. Match the transit prefixes once, then set metric and tag in the same permit clause so the assessor’s policy lands in one shot.
Full Explanation
One route-map permit clause can match a set of prefixes and apply multiple set actions in one pass. For an assessor’s office that needs redistributed transit routes matching a prefix-list to receive both a new metric and a route tag, configure match ip address prefix-list <name> (or the appropriate match) and then both set metric … and set tag … under the same permit sequence. When redistribution evaluates that clause, matched transit prefixes receive both attributes together without requiring a second protocol hop or a second redistribute statement.
The approach using two redistribute statements with empty route-maps does not merge attributes automatically and often creates duplicate or uncontrolled injection. The approach that matches the prefix-list in one clause but sets only metric is false: tags do not require a second protocol; set tag works in the same clause as set metric. The approach that applies an inbound ACL on the interface instead of a redistribute route-map filters data-plane packets or, at best, is the wrong tool for controlling redistribution attributes on matched prefixes.
Exam caveat: clause order matters. If an earlier permit matches the same transit prefixes with only one set action, later clauses will not reprocess those prefixes. Put all required set actions in the clause that first permits the match. Also ensure the metric syntax matches the destination protocol (EIGRP composite vs OSPF cost). Implicit deny at the end still drops non-matching assessor prefixes, which is usually desired for selective redistribution.
Operational check: redistribute with the route-map attached, then inspect the target protocol’s table for a transit prefix and verify both the expected metric and tag. show route-map should list match prefix-list plus both set lines under one sequence number. Adjust the prefix-list and confirm only listed transit routes carry the new metric/tag while others remain unredistributed.