Build fluency in the vocabulary of autonomous networks exchanging reachability information to route internet traffic.
0 / 5 completed
1 / 5
At standup, a dev mentions the protocol that autonomous networks on the internet use to exchange information about which IP address ranges they can reach, so each network can pick a best path toward any destination across the wider internet. What is this protocol called?
BGP, the Border Gateway Protocol, is exactly this: it is the protocol autonomous networks on the internet use to exchange information about which IP address ranges, or prefixes, they can reach, so each network can pick a best path toward any destination across the wider internet based on the routes its neighbors advertise. A hash collision is an unrelated hash-table concept about two keys sharing a bucket. This exchange-reachability-between-networks approach is exactly why the global internet can route traffic between tens of thousands of independently operated networks without any single central authority computing every path.
2 / 5
During a design review, a network team relies on BGP to advertise its IP address ranges to upstream providers, specifically because exchanging reachability information lets every other network on the internet learn a path to reach it without any centrally computed global routing table. Which capability does this provide?
BGP here provides decentralized, scalable internet-wide routing, since each network only needs to exchange reachability information with its direct neighbors, letting best paths propagate across the internet without any single entity computing every route. A single centrally computed global routing table would need constant, instant coordination across every independently operated network on the internet, which doesn't scale. This exchange-with-neighbors-only behavior is exactly why BGP is the routing protocol that holds the internet together across so many independent networks.
3 / 5
In a code review of a network-automation tool, an engineer notices it hardcodes a fixed routing path to a set of external destinations with no mechanism to react to a BGP-advertised route withdrawal, instead of dynamically following BGP's live reachability updates. What does this represent?
This is a missed BGP opportunity, since dynamically following BGP's live reachability updates would reroute traffic automatically around a withdrawn or failed path instead of continuing to use a hardcoded route that may no longer be reachable. A cache eviction policy is an unrelated concept about discarded cache entries. This hardcoded-routing-path pattern is exactly the kind of fragility a reviewer flags once a network path can fail or change.
4 / 5
An incident report shows traffic to an external service silently blackholed for hours, because a network-automation tool used a hardcoded routing path and never reacted to a BGP-advertised withdrawal of that path after an upstream failure. What practice would prevent this?
Dynamically following BGP's live reachability updates automatically reroutes traffic around a withdrawn or failed path instead of continuing to use a stale, hardcoded route. Continuing to use a hardcoded routing path with no reaction to BGP route withdrawals regardless of how long traffic silently blackholes after an upstream failure is exactly what caused the outage described in this incident. This dynamic-BGP-following approach is the standard fix once a hardcoded path is confirmed to blackhole traffic after a failure.
5 / 5
During a PR review, a teammate asks why a network team relies on BGP's dynamic route advertisements instead of statically configuring every possible route by hand across the network's edge routers. What is the reasoning?
BGP lets networks automatically learn and propagate reachability changes, such as a failed link or a new provider, across the internet in near real time, while statically configuring every route by hand cannot react to a change until an engineer manually updates every affected router. This is exactly why BGP is the standard routing protocol at internet scale, while static routes remain useful only for small, stable, and simple network topologies.