Which two methods can you use to prevent redistribution loops between two routing protocols? Choose two.

Redistribution loops occur when routes learned from one protocol are redistributed into another, and then those same routes (or summaries of them) are redistributed back into the original protocol. Tagging routes is an effective method. When routes are redistributed from Protocol A to Protocol B, they can be assigned a specific tag. When redistributing from Protocol B back to Protocol A, a route-map can be configured to deny any routes with that specific tag, preventing them from being re-injected. Using prefix-lists or distribute-lists (often within a route-map) allows for granular control over which routes are redistributed. You can explicitly permit or deny specific prefixes, preventing routes that originated in one protocol from being redistributed back into it. Relying solely on administrative distance is insufficient; while AD influences route selection, it doesn't prevent a route from being redistributed and potentially looping if the ADs are favorable at different points in the network. Applying an interface access-list to drop routing protocol packets would disrupt the routing protocol's operation entirely, not just prevent redistribution loops.