In a carrier network using VRF-lite for customer isolation, which issue arises if route-target values are not correctly configured?
Mismatched route-targets can cause unintended import/export, leading to route leakage between VRFs.
Why this answer
In VRF-lite, route-target (RT) values control the import and export of routes between VRFs. If RTs are misconfigured, a VRF may import routes intended for another VRF, causing customer routes to leak across VRFs. This violates isolation because the VRF table incorrectly accepts routes based on mismatched RT import statements.
Exam trap
Cisco often tests the misconception that route-target misconfiguration causes BGP session failures or routing protocol issues, when in fact it only affects route import/export logic, leading to route leakage.
How to eliminate wrong answers
Option A is wrong because VRF-lite does not use the global routing table for customer routes; routes are installed in the per-VRF table, and incorrect RTs do not affect the global table. Option B is wrong because BGP sessions between PEs are established independently of RT configuration; RTs only affect route processing within BGP, not session state. Option C is wrong because the PE-CE routing protocol (e.g., OSPF, EIGRP, static) operates on the VRF interface and is unaffected by RT misconfiguration; RTs only influence route redistribution between VRFs or between VRF and BGP.