BGP Interview Questions & Answers (2026)
These interviews test your grasp of BGP fundamentals, route selection, policy control, scalability, and troubleshooting. To succeed, demonstrate clear knowledge of path attributes, convergence behavior, and real‑world design trade‑offs, while articulating why each configuration choice matters for reliability and performance.
23 questions · updated Aug 29, 2026
Quick facts
| Typical rounds | Phone screen, technical deep‑dive, system design, and final manager interview |
| Core topics | Path attributes, route reflectors, confederations, BGP timers, and security |
| Key metrics | Convergence time, route flap damping, and prefix count per peer |
| Common tools | Wireshark, BGPmon, Quagga/FRR, and vendor‑specific CLI |
| Typical employers | ISPs, cloud providers, large enterprises, and networking equipment vendors |
Questions
Beginner
What is the primary purpose of BGP and how does it differ from interior routing protocols?
BGP (Border Gateway Protocol) is the de‑facto inter‑domain routing protocol that exchanges reachability information between autonomous systems. Unlike interior protocols such as OSPF or EIGRP, which focus on shortest‑path metrics within a single AS, BGP makes routing decisions based on policy, path attributes, and business relationships. Interviewers expect you to stress that BGP’s flexibility lets operators enforce traffic engineering, avoid certain ASes, and control inbound/outbound paths, while interior protocols prioritize fast convergence and link‑state or distance‑vector calculations.
Explain the BGP path selection process in order of preference.
BGP evaluates routes using a deterministic sequence: highest weight (Cisco‑only), highest local preference, shortest AS‑PATH length, lowest origin type (IGP < EGP < Incomplete), lowest MED (if comparable), eBGP over iBGP, lowest IGP cost to BGP next‑hop, and finally oldest route. The candidate should walk through each step, noting that weight and local‑preference are locally set, while AS‑PATH and MED are propagated. Emphasize that understanding this order lets you predict routing outcomes and design policies that steer traffic as intended.
What is a BGP route reflector and why is it used?
A route reflector (RR) centralizes iBGP updates, allowing client routers to receive routes without a full mesh. Without an RR, every iBGP speaker must peer with every other, leading to O(n²) sessions. The RR eliminates this scaling issue by reflecting routes from one client to others, while still preserving loop‑free behavior via the cluster ID. Interviewers look for you to explain the reduction in session count, the impact on convergence, and the need for careful design to avoid suboptimal paths.
What is the role of BGP ‘origin’ attribute and how does it affect path selection?
The origin attribute indicates how a route was learned: IGP (0), EGP (1), or INCOMPLETE (2). Lower values are preferred, so routes originated via IGP are chosen over EGP, which are preferred over incomplete. This attribute is the fourth step in the BGP best‑path algorithm. Interviewers expect you to state that origin reflects the source of the prefix and that it is rarely manipulated directly, but understanding it helps explain why certain paths are selected.
Why is BGP considered a path‑vector protocol and not a distance‑vector protocol?
BGP is a path‑vector protocol because it carries the full AS‑PATH vector, enabling each router to make loop‑free decisions based on the entire path history. Distance‑vector protocols like RIP only advertise a metric (hop count) without path details, leading to potential loops. Interviewers want you to emphasize that the AS‑PATH attribute provides policy control and loop prevention, distinguishing BGP’s scalability and flexibility from simple distance‑vector mechanisms.
Intermediate
How does BGP MED influence route selection and when should it be used?
MED (Multi‑Exit Discriminator) is a non‑transitive attribute that suggests a preferred entry point into an AS when multiple links exist. Lower MED values are preferred. It is typically used between neighboring ASes that have a bilateral agreement, allowing one side to influence inbound traffic without affecting other ASes. Interviewers expect you to note that MED is only compared when routes share the same neighboring AS unless the ‘compare‑med‑different‑as’ option is enabled, and that overusing MED can create routing loops if not coordinated.
Describe BGP route dampening and its impact on network stability.
Route dampening suppresses flapping prefixes by assigning a penalty each time a route changes state. When the cumulative penalty exceeds a suppress threshold, the prefix is withheld for a configurable reuse time. This reduces unnecessary updates, stabilizing the control plane, but can also increase convergence latency for legitimate changes. Interviewers look for awareness of the trade‑off: dampening helps large ISPs manage instability, yet many modern networks disable it because fast convergence and route‑reflector designs mitigate flaps more effectively.
What are BGP confederations and when would you deploy them?
Confederations partition a large AS into smaller sub‑ASes that appear as a single AS to external peers. Internally, iBGP sessions treat each sub‑AS as eBGP, reducing the full‑mesh requirement while preserving a unified AS number externally. They are useful for very large service provider networks where scaling iBGP becomes impractical. Interviewers expect you to discuss the benefits (reduced session count, easier policy segmentation) and drawbacks (additional complexity, potential suboptimal paths) and to cite real‑world scenarios such as multi‑regional ISP deployments.
How does BGP handle loop prevention?
BGP prevents loops primarily through the AS‑PATH attribute. Each time a route is advertised, the originating AS number is prepended. When a router receives a route, it checks the AS‑PATH for its own AS number; if present, the route is discarded. This simple mechanism works across autonomous systems. Interviewers also appreciate mention of additional safeguards like route‑reflector cluster IDs and the originator ID attribute, which prevent loops in iBGP topologies that involve route reflectors.
Explain the difference between eBGP and iBGP in terms of hop count and attribute propagation.
eBGP peers are in different autonomous systems and exchange the full set of path attributes, including MED and local preference (which is set locally). eBGP updates are sent only to directly connected peers, and the AS‑PATH length increments by one per hop. iBGP peers reside within the same AS; they do not modify the AS‑PATH and do not carry MED across the AS. Because iBGP does not alter the AS‑PATH, routers must maintain a full‑mesh or use route reflectors to avoid loops. Interviewers want you to stress that eBGP influences inter‑AS policy while iBGP ensures internal consistency.
What is the effect of the ‘no client‑to‑client reflection’ command on a route reflector?
Disabling client‑to‑client reflection prevents a route reflector from advertising routes learned from one client to another client, limiting the propagation to only non‑client peers. This reduces unnecessary traffic between clients but can increase path length if clients need to reach each other via the RR. Interviewers expect you to discuss the trade‑off between reduced update traffic and potential suboptimal routing, and when this setting is appropriate in large hierarchies.
How does BGP handle route flaps and what mechanisms can mitigate their impact?
Route flaps cause frequent updates, increasing CPU and bandwidth usage. BGP mitigates this with route dampening, which assigns penalties to flapping prefixes and suppresses them after a threshold. Additionally, using route reflectors, confederations, and proper timer tuning (hold‑time, keepalive) can reduce flap propagation. Interviewers look for you to explain the penalty calculation, the suppress and reuse thresholds, and why many modern networks prefer to disable dampening in favor of faster convergence and better monitoring.
Advanced
What is the purpose of the BGP 'next‑hop' attribute and how is it used in route selection?
The next‑hop attribute indicates the IP address of the router that should be used to reach the advertised prefix. It is critical for forwarding decisions and for IGP cost calculations during BGP best‑path selection. When multiple routes have identical attributes, the router with the lowest IGP metric to the next‑hop is preferred. Interviewers look for you to explain that next‑hop is often rewritten by eBGP peers to point to the receiving router, and that misconfigured next‑hop values can cause black‑hole routing or suboptimal paths.
How does BGP handle multiple exit points from an AS, and what attributes influence inbound traffic engineering?
Multiple exit points are managed through attributes like LOCAL_PREF, MED, and AS‑PATH prepending. To influence inbound traffic, an AS can advertise higher LOCAL_PREF to its own routers, prepend its own AS number to make a path appear longer, or set a lower MED on the preferred exit. Communities (e.g., NO_EXPORT) can also restrict propagation. Interviewers expect you to describe how each attribute works, the order of preference, and the practical impact on traffic flow, demonstrating an ability to design policies that meet business objectives.
What are BGP communities and how are they used to simplify policy management?
BGP communities are 32‑bit tags attached to routes that convey optional, non‑transitive information to downstream peers. Standard communities like NO_EXPORT prevent further propagation, while custom communities can encode routing policies (e.g., prepend‑2, high‑local‑pref). By applying a community to a set of prefixes, operators can centrally control behavior across many peers without per‑prefix ACLs. Interviewers look for examples such as using a ‘customer‑type’ community to apply a uniform local‑preference, demonstrating how communities reduce configuration complexity and improve scalability.
Describe how BGP Graceful Restart works and why it matters for high‑availability networks.
Graceful Restart (GR) allows a BGP speaker to restart its process without flushing learned routes. During restart, the router advertises a ‘restart flag’ and retains forwarding state for a configurable timer, while peers continue to use the stale routes. Once the restarted router re‑establishes sessions, it validates the retained routes. This minimizes traffic disruption and convergence delay. Interviewers expect you to discuss the required support on both ends, the role of the ‘restart timer’, and how GR complements other HA mechanisms like BFD and redundant routers.
What is BGP multipath and when would you enable it?
BGP multipath allows a router to install multiple equal‑cost paths into the forwarding table, enabling load balancing across parallel links. It is enabled when routes have identical attributes up to the point where the decision diverges (e.g., same weight, local‑pref, AS‑PATH length, MED, and IGP cost). Use cases include data‑center fabrics with multiple uplinks or ISP edge routers with redundant peering. Interviewers want you to note that enabling multipath can improve bandwidth utilization but may complicate troubleshooting and require consistent hashing on downstream devices.
How does BGP handle route aggregation, and what is the difference between manual and automatic summarization?
Route aggregation combines multiple specific prefixes into a broader summary route, reducing the size of the BGP table. Manual aggregation is configured with a specific prefix and mask, optionally using the ‘aggregate‑address’ command, which can preserve or discard more specific routes. Automatic summarization (or ‘summary‑only’) allows the router to generate a summary without advertising the constituent prefixes. Interviewers expect you to explain the impact on path attributes, the need to set the ‘summary‑only’ flag to avoid leaking more specific routes, and the trade‑off between table size and granularity.
What is the impact of BGP TTL security (GTSM) on peer relationships?
GTSM (Generalized TTL Security Mechanism) protects BGP sessions by requiring received packets to have a TTL of 255 or a value within a configurable range, effectively limiting acceptance to directly connected peers. This mitigates spoofed BGP attacks from distant sources. The impact is that peers must be directly adjacent or configure a higher TTL threshold, and any intermediate devices that decrement TTL must be accounted for. Interviewers look for you to discuss the security benefit, the configuration command (bgp ttl-security), and potential operational considerations.
Explain the purpose of the BGP ‘soft reset’ and how it differs from a hard reset.
A soft reset (clear ip bgp * soft‑in) forces a router to re‑process inbound updates without tearing down the TCP session, preserving existing routes while applying new policy. A hard reset (clear ip bgp *) drops the session, causing a full re‑advertisement and temporary loss of routes. Soft resets are used for policy changes that should not disrupt traffic, whereas hard resets are needed for session recovery or major configuration changes. Interviewers expect you to illustrate the operational impact on convergence and route stability.
How does BGP route reflectors handle the ‘cluster‑id’ attribute to prevent loops?
When a route reflector forwards a route to a client, it adds its own cluster‑ID to the route. Clients discard any route that contains their own cluster‑ID, preventing loops that could arise from reflected updates. This mechanism works in addition to the AS‑PATH check. Interviewers want you to explain that the cluster‑ID is a 32‑bit identifier unique per RR cluster, and that proper configuration ensures loop‑free operation even in complex hierarchies of reflectors.
What are the consequences of disabling BGP ‘next‑hop self’ on eBGP sessions?
Disabling ‘next‑hop self’ causes the eBGP speaker to advertise the original next‑hop address of the route, which may be unreachable from the receiving router if the path traverses multiple hops. This can lead to black‑hole routing, increased IGP load, and failed reachability. Interviewers expect you to discuss scenarios where keeping the original next‑hop is desirable (e.g., when the peer has a direct link) and the importance of ensuring that the advertised next‑hop is reachable via the IGP.
How does BGP handle route redistribution from an IGP, and what pitfalls should be avoided?
Redistributing IGP routes into BGP involves injecting prefixes with appropriate attributes (e.g., local‑pref, MED). Common pitfalls include unintentionally advertising internal routes, creating routing loops, and overwhelming peers with excessive prefixes. To avoid these, filter redistributed routes, set appropriate route‑maps, and ensure that the IGP metric to the next‑hop aligns with BGP decisions. Interviewers look for awareness of the need for careful filtering and the impact on the global routing table.
Common mistakes
- Misconfiguring local‑preference on eBGP peers, causing unintended outbound traffic shifts
- Forgetting to set ‘next‑hop self’, leading to unreachable routes
- Overusing AS‑PATH prepending without considering MED, resulting in longer convergence
- Disabling route‑reflector client‑to‑client reflection unintentionally increasing path length
- Applying route dampening globally and causing unnecessary route suppression
Study plan
- Review BGP fundamentals: attributes, path selection order, and differences from IGPs
- Practice configuration scenarios: route reflectors, confederations, and community usage
- Simulate troubleshooting: flap handling, soft reset, and graceful restart cases
- Master policy design: MED, local‑pref, AS‑PATH prepending, and security features
- Run mock interviews focusing on explanation depth and real‑world trade‑offs
FAQ
How many BGP sessions can a single router realistically handle?
A modern router can manage thousands of sessions, but practical limits depend on CPU, memory, and IOS version. For large ISPs, 10‑20 k sessions are common, while enterprise edge devices typically handle a few hundred. Interviewers expect you to mention scaling techniques like route reflectors and confederations.
What is the default BGP hold timer and why might you change it?
The default hold timer is 180 seconds, with a keepalive interval of 60 seconds. Adjusting it can improve detection of failed peers in high‑availability environments or reduce unnecessary traffic in stable links. Shorter timers speed up failure detection but increase control‑plane load.
Can BGP advertise IPv6 routes the same way it advertises IPv4?
Yes, BGP supports Multiprotocol BGP (MP‑BGP) to carry both IPv4 and IPv6 NLRI in separate address families. The configuration differs only in the address‑family command, but the path‑selection process and attributes remain consistent.
Why is BGP considered a “policy‑driven” protocol?
Because routing decisions are based on configurable attributes (local‑pref, MED, communities) rather than purely on metrics. This allows operators to enforce business relationships, traffic engineering, and security policies, which is a core interview discussion point.
What tools can I use to debug BGP issues during an interview exercise?
Common tools include ‘show ip bgp’, ‘show ip bgp neighbors’, Wireshark for packet capture, and route‑monitoring platforms like BGPmon. Knowing how to interpret BGP tables and neighbor states demonstrates practical competence.
Related
Ready for your next interview?
Download MiPrep AI. Load your resume and the job description. Show up ready.
Free tier · No credit card · macOS 14+ · Windows 10+
Free tier · No credit card · Runs on your Mac or Windows machine