An ISP is designing an MPLS core network and needs to choose an IGP that supports fast convergence. Which IGP meets this requirement and is most commonly used in MPLS core networks?
IS-IS provides fast convergence and is the predominant IGP in service provider MPLS cores.
Why this answer
IS-IS is the correct choice because it is a link-state IGP that inherently supports fast convergence through mechanisms like incremental SPF (iSPF) and prefix-independent convergence (PIC). It is widely deployed in MPLS core networks due to its scalability, extensibility via TLVs, and native support for MPLS Traffic Engineering (MPLS-TE) without requiring additional protocol extensions like OSPF's opaque LSA.
Exam trap
Cisco often tests the misconception that OSPF is the default IGP for all networks, but in MPLS core environments, IS-IS is the preferred choice due to its native TE support and hierarchical scalability, making OSPF a distractor despite its fast convergence capabilities.
How to eliminate wrong answers
Option B (OSPFv3) is wrong because while OSPFv3 supports IPv6 and fast convergence, it is less commonly used in MPLS core networks compared to IS-IS due to its reliance on opaque LSAs for MPLS-TE, which adds complexity; IS-IS is the dominant IGP in service provider cores. Option C (EIGRP) is wrong because EIGRP is a Cisco-proprietary distance-vector protocol that does not natively support MPLS-TE and is not designed for the hierarchical, scalable architecture required in MPLS core networks. Option D (RIPng) is wrong because RIPng is a distance-vector protocol with slow convergence (based on hop count) and is unsuitable for any modern MPLS core network due to its lack of fast convergence, scalability, and MPLS-TE support.