A network administrator is having problems with redistribution routing loops between two EIGRP processes. You've looked at the configurations and determined there is no filtering configured on the rou

Reducing the number of redistribution routers directly contradicts the stated requirement to avoid a single point of failure, making this solution operationally unacceptable.

Prefix-based route filters require explicit listing of every redistributed network and must be updated whenever the network topology changes, resulting in higher long-term management complexity than tag-based filtering.

Replacing one EIGRP process with a different IGP introduces a new protocol to manage and does not inherently prevent redistribution loops - the loop problem is a policy issue, not a protocol choice issue.

Route tags allow each redistributing router to stamp routes with a numeric tag as they enter a process, and all redistribution points can be configured with a matching deny rule to block any route carrying that tag from being redistributed back into the originating process. This prevents feedback loops uniformly across all three redistribution routers with a simple, consistent policy that does not require updates when prefixes change.