350-401 Question 144
Single answerA network engineer is designing a network that must support fast convergence, hierarchical segmentation, and scalability. The network will connect multiple branch locations and use the shortest path as a routing criterion. Which routing protocol should the engineer choose, and why?
- A
Enhanced Interior Gateway Routing Protocol (EIGRP) because it uses advanced distance vector algorithms for fast convergence.
- B
Open Shortest Path First (OSPF) because it uses a link-state algorithm and supports hierarchical area design.
- C
Enhanced Interior Gateway Routing Protocol (EIGRP) because it supports unequal-cost load balancing for traffic distribution.
- D
Open Shortest Path First (OSPF) because it uses a link-state algorithm and supports unequal-cost load balancing.
Show answer and explanation
Correct answer: B
Explanation
Open Shortest Path First (OSPF) is a link-state protocol that supports hierarchical segmentation through the use of areas, making it highly scalable and suitable for large networks. It also uses the Dijkstra algorithm to compute the shortest path, which meets the engineer's requirement for path selection. EIGRP, while an advanced distance vector protocol with fast convergence and unequal-cost load balancing, does not offer the hierarchical segmentation that OSPF provides, making OSPF the better choice for this scenario.
- A. Incorrect.
While EIGRP does use advanced distance vector algorithms and provides fast convergence, it lacks the hierarchical area design needed for scalability in larger networks.
- B. Correct.
OSPF is a link-state protocol that supports hierarchical area designs, making it scalable for larger networks. It also selects the shortest path based on its Dijkstra algorithm, which aligns with the network engineer's requirements.
- C. Incorrect.
Although EIGRP supports unequal-cost load balancing, this feature does not address the hierarchical segmentation and scalability requirements stated in the scenario.
- D. Incorrect.
OSPF does not support unequal-cost load balancing; it only supports equal-cost load balancing. This makes this option incorrect.