Which Path-Vector Routing Protocol Connects Branch Offices with Redundancy?
Short answer
C Use BGP between the branch offices to gain path-vector AS-path routing with redundant paths and multipath load balancing.
Question
Key Takeaways
The item tests protocol-category recognition under a functional requirement; the trap is selecting OSPF because it offers equal-cost load balancing and redundancy despite being link-state rather than path vector.
This N10-009 question tests path-vector routing protocol selection for branch-office WAN connectivity; BGP is the correct choice because it is the only path-vector option and can support redundant, load-balanced paths.
Common mistake: The most plausible wrong answer is B (OSPF): it supports redundancy and equal-cost multipath inside an enterprise, but it is a link-state interior gateway protocol and does not satisfy the path-vector constraint.
Expert Analysis
Path vector is the deciding constraint The question asks for a routing protocol that connects multiple branch offices, provides automatic load balancing and redundancy, and uses path-vector routing. BGP is the only option that satisfies the path-vector requirement: it advertises reachability with an AS-path and uses path attributes to select and propagate routes. A community explanation summarized this accurately, noting that BGP maintains AS-path information for routing decisions, redundancy, and load balancing across multiple connections or branch offices. BGP can be deployed as eBGP between branch sites or between branches and a provider, and multipath support lets eligible paths be installed for load sharing. Its default behavior is best-path selection, so the load-balancing claim should be read as BGP's capability with appropriate multipath configuration—not as automatic equal-cost behavior on every router.
Why the other options fail A (RIP) is a distance-vector protocol and uses hop count, not an AS-path. B (OSPF) is a link-state interior gateway protocol; it does provide redundancy and equal-cost multipath inside an area, which makes it an attractive trap, but it is not path vector. D (MPLS) is a label-switching forwarding technology, not a path-vector routing protocol. The exam explicitly narrows the answer by protocol category, so feature overlap in OSPF cannot override that constraint. If the scenario dropped “path vector” and described a single enterprise autonomous system with equal-cost links, OSPF would become a viable answer; if it described service-provider label forwarding, MPLS would be relevant. That adjacent decision—category first, features second—is exactly what this question tests.
Operational consequence Choosing OSPF solely because it supports redundancy and load balancing misses the design requirement and can produce an interior-only routing design that does not scale across separate administrative domains. BGP gives policy control through AS-path, local preference, and multi-exit discriminator, but those knobs must be planned; otherwise traffic may not balance as intended. The safe exam takeaway is to identify the named routing family before comparing capabilities, making C the clear answer.
Official Reference
- https://www.rfc-editor.org/rfc/rfc4271
- https://www.rfc-editor.org/rfc/rfc2328
- https://www.rfc-editor.org/rfc/rfc2453
These links open the official vendor documentation in a new tab.
Exam Strategy
When a question names a routing-protocol category, eliminate options by category before weighing features: RIP is distance-vector, OSPF is link-state, and MPLS is a forwarding technology, leaving BGP as the only path-vector choice. Then check the stated requirement—here, redundancy and load balancing—against how that protocol handles multiple paths. This two-pass method prevents choosing a familiar IGP merely because it supports equal-cost multipath.
Frequently Asked Questions
Why is BGP the correct answer instead of OSPF for branch-office connectivity?
Does BGP automatically load balance across multiple branch-office links?
Why not MPLS when connecting multiple branch offices?
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
ERB14 👍 1 Answered CBGP (Border Gateway Protocol): BGP is classified as a path vector routing protocol. It maintains the path information (specifically the autonomous system path or AS-path) which allows it to make routing decisions, provide redundancy, and support load balancing across multiple connections or branch offices.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All N10-009 Questions
Access 100 questions with complete answers and detailed explanations.
View Full N10-009 Practice Test →