Hub-and-Spoke Resilience Misconception
A junior engineer proposes replacing a company’s partial-mesh WAN topology with a strict hub-and-spoke topology to simplify routing.
The engineer argues, “By routing all branch-to-branch traffic through the central headquarters hub, we eliminate the need for redundant links between branches. This guarantees that if any single link fails, the affected branch can simply use an alternate path through the hub, improving overall network resilience.”
What is the primary misconception in the engineer’s argument regarding failure consequences?
A partial-mesh topology relies on a single central controller, meaning a failure at headquarters disconnects all branches simultaneously.
A strict hub-and-spoke topology lacks alternate paths for a branch if its single link to the hub fails, reducing resilience compared to a partial mesh.
Hub-and-spoke topologies require complex dynamic routing protocols that increase the likelihood of routing loops during a link failure.
Branch-to-branch traffic in a hub-and-spoke topology bypasses the central hub, making the central hub a single point of failure for internet access only.
Question Leaderboard
Not enough data yet to show leaderboard.
