Free Juniper JN0-683 Actual Exam Questions - Question 4 Discussion
multiple unique VRF instances. You want to determine the routing information that belongs in each
routing instance's routing table.
In this scenario, which property is used for this purpose?
A The VRF target community controls route import/export between VRFs, so it directly determines what routing info ends up in each instance’s table. That’s the key property for separating tenant routes.
I’m thinking B might be worth considering since the routing instance type defines how the routing table behaves and what kind of routes it accepts. Could that be the key to determining which routes belong where, rather than just tagging or distinguishing them?
I think it's A here. The VRF target community is what controls which routes get imported into a VRF's routing table by tagging them for that specific VRF, so it’s about route assignment rather than just uniqueness or labeling. The route distinguisher just makes routes unique but doesn’t decide which VRF they belong to.
D imo. The route distinguisher value is what makes each route unique across VRFs by adding that extra identifier. It’s not just about sharing or importing routes, but really about keeping the routes distinct in the routing table. Without it, you’d have route conflicts when different tenants use overlapping IPs. That’s why it’s key in determining which routing table a route belongs to in an EVPN-VXLAN setup with multiple VRFs.
C imo. The VRF table label is what effectively tags routes so the system knows which routing table they belong to. Without it, the router can't properly separate the routes for each VRF. While VRF target communities (A) control import/export policies, the actual placement of routes in the correct VRF table depends on the label. The route distinguisher (D) just makes routes unique but doesn’t decide where they go. So for identifying which routes belong in which routing instance, the label is key here.
Maybe C is the right pick here. The VRF table label is what actually tags routes so the system knows which VRF's routing table they belong to. Without that label, the router can't separate routes correctly, even if the route distinguisher or target community are used for uniqueness or import/export policies. So I think the property directly telling the router which routing instance gets which routes would be the VRF table label.
It’s A, VRF target controls route import/export between VRFs.
A, because VRF target controls which routes get imported into each VRF.
It’s D, the route distinguisher makes routes unique per VRF.
It’s A, the VRF target community controls routing info distribution.