what does it mean for the routing system to be “redundant”? is redundancy a good or bad thing?

A “redundant” routing system is one that has multiple possible paths for data to travel instead of relying on just a single path. In almost all modern networking contexts, that redundancy is a good thing.

What “redundant” means in routing

Think of routing like a road map for your data:

• A non‑redundant system: There’s only one road from City A to City B. If that road is closed, nobody gets through.
• A redundant system: There are several roads from A to B. If one is closed, traffic detours over another.

So, in networking:

• Redundancy means:
  • Multiple routers, links, or paths between key points.
  • Backup routes that can take over automatically if one route fails.
  • No single point whose failure brings the network down.

In short, a redundant routing system is designed so that if something breaks, traffic can still be delivered via alternate paths.

Is redundancy good or bad?

Overall, redundancy in routing is considered good , but it comes with trade‑offs.

Why redundancy is good

• Higher reliability and uptime
  Multiple paths mean the network can keep working even when a link, router, or ISP fails, which is critical for businesses and online services.

• Fault tolerance and resilience
  The system can “tolerate” failures because traffic is rerouted automatically, reducing outages and user impact.

• Better performance in many designs
  Some setups use redundant links for load‑balancing, spreading traffic across paths to reduce congestion and improve response times.

• Protection for critical operations
  For services like banking, e‑commerce, logistics, and healthcare, even short outages can be very costly, so redundancy is part of risk management.

Downsides and trade‑offs

Redundancy is not “bad,” but it isn’t free:

• Higher cost
  Extra routers, switches, links, and often extra ISP connections all cost money to buy, host, and maintain.

• More complexity
  Designing and managing a redundant network requires careful planning (routing protocols, failover behavior, loops, priority routes). More moving parts means more things to configure correctly.

• Potential for misconfiguration
  Poorly designed redundancy can cause routing loops, unstable failover behavior, or unexpected traffic paths. In those cases, the problem isn’t redundancy itself but how it’s implemented.

So, engineers usually ask: “How much redundancy is enough?” rather than “Should we have redundancy at all?”

How to think about it in an exam or homework context

If this is from a textbook or a quiz, the expected idea is usually:

A redundant routing system has multiple paths for data, so if one path fails, another can be used. This redundancy is generally a good thing because it increases reliability and availability, even though it may add cost and complexity.

You can phrase it simply like this:

• Redundant routing: multiple routes between devices.
• Good because: improves reliability, fault tolerance, and uptime.
• Possible downside: higher cost and complexity, but still considered beneficial overall.

TL;DR:
A redundant routing system has backup paths so data can keep flowing when something fails. That redundancy is almost always viewed as a good thing, because the reliability and uptime gains outweigh the extra cost and complexity in most real‑world networks.