JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
The on-call engineer at Bridgeway Cloud receives this fault report: A provider migrates a service into a separate virtual routing instance but tests only inet.0 and falsely concludes that the tenant route is absent. What initial check best isolates the actual failing protocol stage?
Identify the ingress logical interface's routing-instance membership and inspect the corresponding instance RIB and forwarding table, not just inet.0. The defect is routing-table context; changing the prefix length or changing an unrelated OSPF cost would not enforce the needed tenant separation.
The check diagnoses a different layer of service. Its source issue is: Traffic to one equal-cost destination uses only a single next hop despite two active parallel paths and an approved traffic-sharing requirement. The relevant initial check is: Identify the ingress logical interface's routing-instance membership and inspect the corresponding instance RIB and forwarding table, not just inet.0.
This check may help with another root cause, for example: A services router has a valid connected path in the primary instance yet a policy-dependent secondary RIB never receives it after a routing-instance refactor. It does not test the first failed condition; start with: Identify the ingress logical interface's routing-instance membership and inspect the corresponding instance RIB and forwarding table, not just inet.0.
That evidence could be normal while the reported defect persists. It is aimed at: An edge should install a conditional default only while a qualifying backbone route is reachable, but an unconditional static default currently hides an upstream outage. Instead inspect: Identify the ingress logical interface's routing-instance membership and inspect the corresponding instance RIB and forwarding table, not just inet.0.
The provider operations team at Seawood Media reports: A provider expects selected interface routes from an underlay RIB to be available in a second table, but the secondary table has no copied routes. Which implementation decision best corrects the cause?
That would address a separate configuration fault: Traffic to one equal-cost destination uses only a single next hop despite two active parallel paths and an approved traffic-sharing requirement. This stem identifies a different cause, corrected by: Apply the correct RIB group and route import policy at the route source to import only the intended routes into the secondary RIB.
Apply the correct RIB group and route import policy at the route source to import only the intended routes into the secondary RIB. The case-specific reason is: RIB groups redistribute route entries between tables, whereas a BGP community labels routes but does not itself copy an interface route to another RIB. A direct acceptance test is: Approved routes appear in both the source and destination RIBs with appropriate next-hop resolution, while unrelated tenant routes remain excluded.
The other action is relevant when An edge should install a conditional default only while a qualifying backbone route is reachable, but an unconditional static default currently hides an upstream outage. The current case instead requires: Apply the correct RIB group and route import policy at the route source to import only the intended routes into the secondary RIB. The distinction is: RIB groups redistribute route entries between tables, whereas a BGP community labels routes but does not itself copy an interface route to another RIB.
That would address a separate configuration fault: A provider aggregate continues to be advertised when an operator assumes that any configured aggregate is independent of contributing routes, and wants to validate how the summary activates. This stem identifies a different cause, corrected by: Apply the correct RIB group and route import policy at the route source to import only the intended routes into the secondary RIB.
During a post-change check at Seawood Media, the original condition was: A provider expects selected interface routes from an underlay RIB to be available in a second table, but the secondary table has no copied routes. What evidence would validate the corrected behavior?
This would be valid for another situation: A service edge was renumbered and its manually configured static next hop still points to the former address, blackholing one customer subnet despite healthy dynamic adjacencies. It does not establish that the failing boundary in this scenario works; verify: Approved routes appear in both the source and destination RIBs with appropriate next-hop resolution, while unrelated tenant routes remain excluded.
This would be valid for another situation: An enterprise receives a transit path that should trigger a conditional route of last resort; when that contributor disappears the default must be removed to avoid a blackhole. It does not establish that the failing boundary in this scenario works; verify: Approved routes appear in both the source and destination RIBs with appropriate next-hop resolution, while unrelated tenant routes remain excluded.
Approved routes appear in both the source and destination RIBs with appropriate next-hop resolution, while unrelated tenant routes remain excluded. RIB groups redistribute route entries between tables, whereas a BGP community labels routes but does not itself copy an interface route to another RIB.
That check proves something else, such as: A provider migrates a service into a separate virtual routing instance but tests only inet.0 and falsely concludes that the tenant route is absent. It could pass while the stated problem remains. The targeted evidence here is: Approved routes appear in both the source and destination RIBs with appropriate next-hop resolution, while unrelated tenant routes remain excluded.
At Seawood Media, an engineer is asked to explain this case: A provider expects selected interface routes from an underlay RIB to be available in a second table, but the secondary table has no copied routes. Which underlying routing or switching principle accounts for the appropriate solution?
A Junos RIB group imports routes into a defined primary and additional routing table when attached to the correct configuration context. The key distinction is: RIB groups redistribute route entries between tables, whereas a BGP community labels routes but does not itself copy an interface route to another RIB. Accordingly the remedy is: Apply the correct RIB group and route import policy at the route source to import only the intended routes into the secondary RIB.
That principle belongs to a different service stage: A provider migrates a service into a separate virtual routing instance but tests only inet.0 and falsely concludes that the tenant route is absent. The directly relevant mechanism is: A Junos RIB group imports routes into a defined primary and additional routing table when attached to the correct configuration context.
This explains a separate protocol behavior: A packet class identified by source address needs to use a dedicated service routing table, but packets still follow the global destination-based path. In the current facts, the controlling mechanism is: A Junos RIB group imports routes into a defined primary and additional routing table when attached to the correct configuration context.
The statement can be true when An enterprise receives a transit path that should trigger a conditional route of last resort; when that contributor disappears the default must be removed to avoid a blackhole. But it does not explain the reported failure. Here: RIB groups redistribute route entries between tables, whereas a BGP community labels routes but does not itself copy an interface route to another RIB.
A risk assessment at Seawood Media identifies: A provider expects selected interface routes from an underlay RIB to be available in a second table, but the secondary table has no copied routes. Which practical consequence is most specifically tied to this failure?
The concern could occur elsewhere when A packet class identified by source address needs to use a dedicated service routing table, but packets still follow the global destination-based path. For the stated scenario, the immediate risk is: The secondary routing process lacks required reachability or inadvertently imports unrelated routes if the RIB group is attached too broadly.
The secondary routing process lacks required reachability or inadvertently imports unrelated routes if the RIB group is attached too broadly. The direct mitigation is: Apply the correct RIB group and route import policy at the route source to import only the intended routes into the secondary RIB.
It is a risk in another topology or protocol state: Two wholesale customers use overlapping IPv4 ranges and route lookups occur in the default table, causing one tenant's prefix to shadow the other's. Here the most direct failure path is: The secondary routing process lacks required reachability or inadvertently imports unrelated routes if the RIB group is attached too broadly.
The concern could occur elsewhere when A provider turns on ECMP routing but the forwarding table still resolves customer flows to just one path and operators mistake RIB entries for per-flow distribution. For the stated scenario, the immediate risk is: The secondary routing process lacks required reachability or inadvertently imports unrelated routes if the RIB group is attached too broadly.
The on-call engineer at Seawood Media receives this fault report: A provider expects selected interface routes from an underlay RIB to be available in a second table, but the secondary table has no copied routes. What initial check best isolates the actual failing protocol stage?
This check may help with another root cause, for example: Two wholesale customers use overlapping IPv4 ranges and route lookups occur in the default table, causing one tenant's prefix to shadow the other's. It does not test the first failed condition; start with: Inspect the RIB group table list and attached protocols/interfaces, then verify the affected route in both RIBs and check its resolution.
That evidence could be normal while the reported defect persists. It is aimed at: A provider aggregate continues to be advertised when an operator assumes that any configured aggregate is independent of contributing routes, and wants to validate how the summary activates. Instead inspect: Inspect the RIB group table list and attached protocols/interfaces, then verify the affected route in both RIBs and check its resolution.
The check diagnoses a different layer of service. Its source issue is: A packet class identified by source address needs to use a dedicated service routing table, but packets still follow the global destination-based path. The relevant initial check is: Inspect the RIB group table list and attached protocols/interfaces, then verify the affected route in both RIBs and check its resolution.
Inspect the RIB group table list and attached protocols/interfaces, then verify the affected route in both RIBs and check its resolution. RIB groups redistribute route entries between tables, whereas a BGP community labels routes but does not itself copy an interface route to another RIB.
A production change request at Orion Transit Exchange includes this finding: A services router has a valid connected path in the primary instance yet a policy-dependent secondary RIB never receives it after a routing-instance refactor. What should the engineer change to address it?
The other action is relevant when A provider aggregate continues to be advertised when an operator assumes that any configured aggregate is independent of contributing routes, and wants to validate how the summary activates. The current case instead requires: Apply the correct RIB group and route import policy at the route source to import only the intended routes into the secondary RIB. The distinction is: RIB groups redistribute route entries between tables, whereas a BGP community labels routes but does not itself copy an interface route to another RIB.
That would address a separate configuration fault: A static route and OSPF route cover the identical prefix; the active path is the static one even though the team expected OSPF to win. This stem identifies a different cause, corrected by: Apply the correct RIB group and route import policy at the route source to import only the intended routes into the secondary RIB.
Apply the correct RIB group and route import policy at the route source to import only the intended routes into the secondary RIB. The case-specific reason is: RIB groups redistribute route entries between tables, whereas a BGP community labels routes but does not itself copy an interface route to another RIB. A direct acceptance test is: Approved routes appear in both the source and destination RIBs with appropriate next-hop resolution, while unrelated tenant routes remain excluded.
The other action is relevant when A packet class identified by source address needs to use a dedicated service routing table, but packets still follow the global destination-based path. The current case instead requires: Apply the correct RIB group and route import policy at the route source to import only the intended routes into the secondary RIB. The distinction is: RIB groups redistribute route entries between tables, whereas a BGP community labels routes but does not itself copy an interface route to another RIB.
After Orion Transit Exchange applies its proposed fix to this problem — A services router has a valid connected path in the primary instance yet a policy-dependent secondary RIB never receives it after a routing-instance refactor. — which observation best proves the specific failure has been resolved?
Approved routes appear in both the source and destination RIBs with appropriate next-hop resolution, while unrelated tenant routes remain excluded. RIB groups redistribute route entries between tables, whereas a BGP community labels routes but does not itself copy an interface route to another RIB.
That check proves something else, such as: Two wholesale customers use overlapping IPv4 ranges and route lookups occur in the default table, causing one tenant's prefix to shadow the other's. It could pass while the stated problem remains. The targeted evidence here is: Approved routes appear in both the source and destination RIBs with appropriate next-hop resolution, while unrelated tenant routes remain excluded.
This would be valid for another situation: A provider aggregate continues to be advertised when an operator assumes that any configured aggregate is independent of contributing routes, and wants to validate how the summary activates. It does not establish that the failing boundary in this scenario works; verify: Approved routes appear in both the source and destination RIBs with appropriate next-hop resolution, while unrelated tenant routes remain excluded.
The observation confirms a different component's behavior. Its source context is: Traffic to one equal-cost destination uses only a single next hop despite two active parallel paths and an approved traffic-sharing requirement. In this case the success criterion is: Approved routes appear in both the source and destination RIBs with appropriate next-hop resolution, while unrelated tenant routes remain excluded.
An architecture review at Orion Transit Exchange examines the following symptom: A services router has a valid connected path in the primary instance yet a policy-dependent secondary RIB never receives it after a routing-instance refactor. What Junos or protocol mechanism is most directly responsible?
The statement can be true when A service edge was renumbered and its manually configured static next hop still points to the former address, blackholing one customer subnet despite healthy dynamic adjacencies. But it does not explain the reported failure. Here: RIB groups redistribute route entries between tables, whereas a BGP community labels routes but does not itself copy an interface route to another RIB.
A Junos RIB group imports routes into a defined primary and additional routing table when attached to the correct configuration context. The key distinction is: RIB groups redistribute route entries between tables, whereas a BGP community labels routes but does not itself copy an interface route to another RIB. Accordingly the remedy is: Apply the correct RIB group and route import policy at the route source to import only the intended routes into the secondary RIB.
That principle belongs to a different service stage: A peer presents a route for an address block treated as martian by the platform; engineers mistakenly troubleshoot export communities rather than the fundamental invalid-prefix classification. The directly relevant mechanism is: A Junos RIB group imports routes into a defined primary and additional routing table when attached to the correct configuration context.
This explains a separate protocol behavior: Traffic to one equal-cost destination uses only a single next hop despite two active parallel paths and an approved traffic-sharing requirement. In the current facts, the controlling mechanism is: A Junos RIB group imports routes into a defined primary and additional routing table when attached to the correct configuration context.
The team at Orion Transit Exchange defers a fix for this condition: A services router has a valid connected path in the primary instance yet a policy-dependent secondary RIB never receives it after a routing-instance refactor. What failure is most likely if no targeted control is applied?
It is a risk in another topology or protocol state: A provider turns on ECMP routing but the forwarding table still resolves customer flows to just one path and operators mistake RIB entries for per-flow distribution. Here the most direct failure path is: The secondary routing process lacks required reachability or inadvertently imports unrelated routes if the RIB group is attached too broadly.
The concern could occur elsewhere when An edge should install a conditional default only while a qualifying backbone route is reachable, but an unconditional static default currently hides an upstream outage. For the stated scenario, the immediate risk is: The secondary routing process lacks required reachability or inadvertently imports unrelated routes if the RIB group is attached too broadly.
That consequence is more closely associated with another deficiency, such as: A peer presents a route for an address block treated as martian by the platform; engineers mistakenly troubleshoot export communities rather than the fundamental invalid-prefix classification. The described fault instead exposes: The secondary routing process lacks required reachability or inadvertently imports unrelated routes if the RIB group is attached too broadly.
The secondary routing process lacks required reachability or inadvertently imports unrelated routes if the RIB group is attached too broadly. The direct mitigation is: Apply the correct RIB group and route import policy at the route source to import only the intended routes into the secondary RIB.
During provider troubleshooting at Orion Transit Exchange, this symptom is observed: A services router has a valid connected path in the primary instance yet a policy-dependent secondary RIB never receives it after a routing-instance refactor. Which targeted inspection should precede remediation?
The check diagnoses a different layer of service. Its source issue is: A provider aggregate continues to be advertised when an operator assumes that any configured aggregate is independent of contributing routes, and wants to validate how the summary activates. The relevant initial check is: Inspect the RIB group table list and attached protocols/interfaces, then verify the affected route in both RIBs and check its resolution.
This check may help with another root cause, for example: A maintenance circuit has been retired but an old static route still directs a private customer prefix toward its unresponsive next hop, even while a learned backup route exists. It does not test the first failed condition; start with: Inspect the RIB group table list and attached protocols/interfaces, then verify the affected route in both RIBs and check its resolution.
That evidence could be normal while the reported defect persists. It is aimed at: A provider's firewall filter counts customer steering matches yet tagged traffic goes to the ordinary next hop because the `then routing-instance` forwarding path was not verified. Instead inspect: Inspect the RIB group table list and attached protocols/interfaces, then verify the affected route in both RIBs and check its resolution.
Inspect the RIB group table list and attached protocols/interfaces, then verify the affected route in both RIBs and check its resolution. RIB groups redistribute route entries between tables, whereas a BGP community labels routes but does not itself copy an interface route to another RIB.
Please check your mailbox for a message from support@examlabs.com and follow the directions.