Inter-VRF Route Leaking with PBR
Short answer
B Policy-based routing with the global set statement in a route map enables inter-VRF route leaking without BGP, VRF-Lite, or static routes.
Question
Key Takeaways
The trap is assuming only BGP or VRF-Lite can leak routes; PBR offers a simpler alternative for specific traffic flows.
Learn how to enable inter-VRF routing between the global table and a VRF using Policy-Based Routing (PBR) with the set global statement, avoiding BGP or static routing.
Common mistake: Choosing Option D (VRF receive) because it sounds similar, but VRF receive is often a supporting feature rather than the primary steering mechanism for this scenario.
Expert Analysis
The question requires inter-VRF routing between the global routing table (GRT) and VRF-A, specifically at the core network layer. The customer explicitly excludes BGP, VRF-Lite, and static routing as solutions.
Option B is correct because Policy-Based Routing (PBR) with a set ip next-hop or set interface pointing to the GRT (or vice versa via route leaking mechanisms) allows traffic to be steered between VRFs without requiring dynamic routing protocols like BGP. Specifically, using a route-map with PBR on the VRF interface can match traffic destined for the GRT and set the next-hop in the GRT, effectively 'leaking' the route. As noted in community comments, this leverages the 'set global' statement in a route-map to achieve route leaking from a VRF to the GRT.
Option A is incorrect because inter-VRF routing can be performed on internal devices (like routers) using features like PBR or route leaking, not just external firewalls.
Option C is incorrect because while route-maps are part of the solution, the 'import' feature alone does not define the mechanism; it's the PBR action that matters.
Option D is incorrect because 'VRF receive' is typically used to allow a VRF to receive traffic destined for an IP address configured in another VRF or the GRT on the same device, but it often works in conjunction with other mechanisms. However, the primary mechanism described for active steering/leaking without BGP/static is PBR. Comments suggest VRF Receive works with PBR, but PBR is the active mechanism enabling the flow.
Official Reference
This link opens the official vendor documentation in a new tab.
Exam Strategy
When asked about route leaking or inter-VRF communication without dynamic routing protocols, consider Policy-Based Routing (PBR). Look for keywords like 'set global', 'set next-hop', or 'route-map' applied to interfaces. PBR is the go-to mechanism for non-standard routing paths between VRFs when BGP is excluded.
Frequently Asked Questions
Can PBR be used for inter-VRF routing?
What is the difference between VRF-Lite and PBR for route leaking?
Community Votes
87% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 3 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 3
-
12504a3 👍 3 Answered BIt's B - and I learn something today, I hope you too : "PBR can be used to leak routes between GRT and VRF" As the answer said, the key is the "set global" statement in the route-map. https://www.cisco.com/c/en/us/support/docs/ip/ip-routing/200158-Configure-Route-Leaking-between-Global-a.html#toc-hId--485856924
-
12504a3 👍 1Oh and why not VRF Receive (option D) : it works in conjunction with PBR, so we can consider it more as a feature and not as an entire "mechanism" like PBR.
-
G_Singh12 👍 1 Answered BB is correct
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All 300-420 Questions
Access 150 questions with complete answers and detailed explanations.
View Full 300-420 Practice Test →