JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
A support escalation at Oakbend Education describes: A service route remains hidden after an eBGP-to-iBGP handoff; the internal router knows the prefix but not a path to its advertised next hop. Where should the Junos operator look first for decisive evidence?
That evidence could be normal while the reported defect persists. It is aimed at: An edge advertises unapproved internal prefixes after an operator broadens a BGP export term beyond the intended customer route set. Instead inspect: Inspect the received route's next-hop field and `show route <next-hop>` resolution path, then check the IGP transport route.
The check diagnoses a different layer of service. Its source issue is: A provider receives a malformed or unauthorized customer prefix yet it enters route selection after a loose import policy. The relevant initial check is: Inspect the received route's next-hop field and `show route <next-hop>` resolution path, then check the IGP transport route.
Inspect the received route's next-hop field and `show route <next-hop>` resolution path, then check the IGP transport route. Changing local preference does not make a BGP route usable if its next-hop address is unresolved.
That evidence could be normal while the reported defect persists. It is aimed at: A BGP speaker learns a route from one iBGP peer but does not pass it to another internal peer, causing partial prefix visibility. Instead inspect: Inspect the received route's next-hop field and `show route <next-hop>` resolution path, then check the IGP transport route.
During a Junos network change at Stonebridge Hospitality, the engineer observes: Two paths learned inside one AS reach the same destination; the selected exit conflicts with policy despite the chosen link having fewer AS hops. Which remediation most directly fixes the described problem?
This action may apply to a different problem, for example: An intermittent control-plane firewall blocks one BGP packet class, and operators need to separate OPEN, KEEPALIVE, UPDATE and NOTIFICATION behavior. It does not repair the stated failure boundary. The case-specific reason is: Local preference controls the AS-wide preferred exit before AS-path length, unlike MED which is commonly compared for neighbor ingress selection.
This action may apply to a different problem, for example: A router has eBGP paths with equal relevant attributes and the operations team assumes both will automatically enter the forwarding table. It does not repair the stated failure boundary. The case-specific reason is: Local preference controls the AS-wide preferred exit before AS-path length, unlike MED which is commonly compared for neighbor ingress selection.
The other action is relevant when A carrier tags customer routes with a standard BGP community to drive downstream policy, but the tag never appears beyond the ingress edge. The current case instead requires: Set a suitable higher BGP local preference on the desired imported egress route and propagate it consistently inside the AS. The distinction is: Local preference controls the AS-wide preferred exit before AS-path length, unlike MED which is commonly compared for neighbor ingress selection.
Set a suitable higher BGP local preference on the desired imported egress route and propagate it consistently inside the AS. The case-specific reason is: Local preference controls the AS-wide preferred exit before AS-path length, unlike MED which is commonly compared for neighbor ingress selection. A direct acceptance test is: Internal routers choose the policy-preferred egress based on higher local preference before comparing later path-selection attributes.
The Junos team at Stonebridge Hospitality needs a success criterion for this defect: Two paths learned inside one AS reach the same destination; the selected exit conflicts with policy despite the chosen link having fewer AS hops. Which observed result most precisely confirms the intended repair?
Internal routers choose the policy-preferred egress based on higher local preference before comparing later path-selection attributes. Local preference controls the AS-wide preferred exit before AS-path length, unlike MED which is commonly compared for neighbor ingress selection.
This would be valid for another situation: Two eBGP routes have equal earlier BGP decision attributes and the operator needs to explain why a path with fewer AS numbers is preferred. It does not establish that the failing boundary in this scenario works; verify: Internal routers choose the policy-preferred egress based on higher local preference before comparing later path-selection attributes.
The observation confirms a different component's behavior. Its source context is: A transit customer prefix is locally active but never advertised to an approved eBGP neighbor because the export policy's final term rejects it. In this case the success criterion is: Internal routers choose the policy-preferred egress based on higher local preference before comparing later path-selection attributes.
That check proves something else, such as: An operator changes local preference on its own router expecting a remote AS to honor it, but the remote side never receives that attribute. It could pass while the stated problem remains. The targeted evidence here is: Internal routers choose the policy-preferred egress based on higher local preference before comparing later path-selection attributes.
While analyzing a service failure at Stonebridge Hospitality, the following is observed: Two paths learned inside one AS reach the same destination; the selected exit conflicts with policy despite the chosen link having fewer AS hops. Which mechanism best explains the underlying control-plane or forwarding behavior?
The statement can be true when A transit customer prefix is locally active but never advertised to an approved eBGP neighbor because the export policy's final term rejects it. But it does not explain the reported failure. Here: Local preference controls the AS-wide preferred exit before AS-path length, unlike MED which is commonly compared for neighbor ingress selection.
That principle belongs to a different service stage: An operator changes local preference on its own router expecting a remote AS to honor it, but the remote side never receives that attribute. The directly relevant mechanism is: BGP local preference is carried within an autonomous system and favors larger values for route selection; it is not advertised to external eBGP peers.
This explains a separate protocol behavior: A provider receives a malformed or unauthorized customer prefix yet it enters route selection after a loose import policy. In the current facts, the controlling mechanism is: BGP local preference is carried within an autonomous system and favors larger values for route selection; it is not advertised to external eBGP peers.
BGP local preference is carried within an autonomous system and favors larger values for route selection; it is not advertised to external eBGP peers. The key distinction is: Local preference controls the AS-wide preferred exit before AS-path length, unlike MED which is commonly compared for neighbor ingress selection. Accordingly the remedy is: Set a suitable higher BGP local preference on the desired imported egress route and propagate it consistently inside the AS.
The following provider defect remains uncorrected at Stonebridge Hospitality: Two paths learned inside one AS reach the same destination; the selected exit conflicts with policy despite the chosen link having fewer AS hops. What is the most direct service or security risk of leaving it unresolved?
The concern could occur elsewhere when A transit customer prefix is locally active but never advertised to an approved eBGP neighbor because the export policy's final term rejects it. For the stated scenario, the immediate risk is: Traffic may exit through the wrong carrier, producing inconsistent routing or unwanted transit cost across the AS.
Traffic may exit through the wrong carrier, producing inconsistent routing or unwanted transit cost across the AS. The direct mitigation is: Set a suitable higher BGP local preference on the desired imported egress route and propagate it consistently inside the AS.
It is a risk in another topology or protocol state: A received iBGP route is visible in inet.0 but inactive because its BGP next hop cannot be resolved through the IGP. Here the most direct failure path is: Traffic may exit through the wrong carrier, producing inconsistent routing or unwanted transit cost across the AS.
The concern could occur elsewhere when A planned customer route appears in the partner's advertisements but Junos rejects it at an early inbound policy term. For the stated scenario, the immediate risk is: Traffic may exit through the wrong carrier, producing inconsistent routing or unwanted transit cost across the AS.
A support escalation at Stonebridge Hospitality describes: Two paths learned inside one AS reach the same destination; the selected exit conflicts with policy despite the chosen link having fewer AS hops. Where should the Junos operator look first for decisive evidence?
This check may help with another root cause, for example: A provider receives a malformed or unauthorized customer prefix yet it enters route selection after a loose import policy. It does not test the first failed condition; start with: Compare best paths and local-preference values for the exact prefix on internal speakers and identify the import policy setting it.
That evidence could be normal while the reported defect persists. It is aimed at: An operator changes local preference on its own router expecting a remote AS to honor it, but the remote side never receives that attribute. Instead inspect: Compare best paths and local-preference values for the exact prefix on internal speakers and identify the import policy setting it.
The check diagnoses a different layer of service. Its source issue is: A carrier tags customer routes with a standard BGP community to drive downstream policy, but the tag never appears beyond the ingress edge. The relevant initial check is: Compare best paths and local-preference values for the exact prefix on internal speakers and identify the import policy setting it.
Compare best paths and local-preference values for the exact prefix on internal speakers and identify the import policy setting it. Local preference controls the AS-wide preferred exit before AS-path length, unlike MED which is commonly compared for neighbor ingress selection.
The provider operations team at Canal City University reports: A backbone operator needs to prefer a primary egress for all internal routers without changing the external partner's AS path length. Which implementation decision best corrects the cause?
The other action is relevant when A neighbor's agreed selective-routing behavior fails because a community is added after the rejecting export term rather than before policy selection. The current case instead requires: Set a suitable higher BGP local preference on the desired imported egress route and propagate it consistently inside the AS. The distinction is: Local preference controls the AS-wide preferred exit before AS-path length, unlike MED which is commonly compared for neighbor ingress selection.
Set a suitable higher BGP local preference on the desired imported egress route and propagate it consistently inside the AS. The case-specific reason is: Local preference controls the AS-wide preferred exit before AS-path length, unlike MED which is commonly compared for neighbor ingress selection. A direct acceptance test is: Internal routers choose the policy-preferred egress based on higher local preference before comparing later path-selection attributes.
This action may apply to a different problem, for example: A service route remains hidden after an eBGP-to-iBGP handoff; the internal router knows the prefix but not a path to its advertised next hop. It does not repair the stated failure boundary. The case-specific reason is: Local preference controls the AS-wide preferred exit before AS-path length, unlike MED which is commonly compared for neighbor ingress selection.
The other action is relevant when A provider receives a malformed or unauthorized customer prefix yet it enters route selection after a loose import policy. The current case instead requires: Set a suitable higher BGP local preference on the desired imported egress route and propagate it consistently inside the AS. The distinction is: Local preference controls the AS-wide preferred exit before AS-path length, unlike MED which is commonly compared for neighbor ingress selection.
During a post-change check at Canal City University, the original condition was: A backbone operator needs to prefer a primary egress for all internal routers without changing the external partner's AS path length. What evidence would validate the corrected behavior?
The observation confirms a different component's behavior. Its source context is: An operator changes local preference on its own router expecting a remote AS to honor it, but the remote side never receives that attribute. In this case the success criterion is: Internal routers choose the policy-preferred egress based on higher local preference before comparing later path-selection attributes.
Internal routers choose the policy-preferred egress based on higher local preference before comparing later path-selection attributes. Local preference controls the AS-wide preferred exit before AS-path length, unlike MED which is commonly compared for neighbor ingress selection.
This would be valid for another situation: A planned customer route appears in the partner's advertisements but Junos rejects it at an early inbound policy term. It does not establish that the failing boundary in this scenario works; verify: Internal routers choose the policy-preferred egress based on higher local preference before comparing later path-selection attributes.
The observation confirms a different component's behavior. Its source context is: A carrier tags customer routes with a standard BGP community to drive downstream policy, but the tag never appears beyond the ingress edge. In this case the success criterion is: Internal routers choose the policy-preferred egress based on higher local preference before comparing later path-selection attributes.
At Canal City University, an engineer is asked to explain this case: A backbone operator needs to prefer a primary egress for all internal routers without changing the external partner's AS path length. Which underlying routing or switching principle accounts for the appropriate solution?
This explains a separate protocol behavior: A planned customer route appears in the partner's advertisements but Junos rejects it at an early inbound policy term. In the current facts, the controlling mechanism is: BGP local preference is carried within an autonomous system and favors larger values for route selection; it is not advertised to external eBGP peers.
The statement can be true when The provider expects a shorter AS path to win, but another path has a deliberately higher local preference and is selected instead. But it does not explain the reported failure. Here: Local preference controls the AS-wide preferred exit before AS-path length, unlike MED which is commonly compared for neighbor ingress selection.
That principle belongs to a different service stage: A service route remains hidden after an eBGP-to-iBGP handoff; the internal router knows the prefix but not a path to its advertised next hop. The directly relevant mechanism is: BGP local preference is carried within an autonomous system and favors larger values for route selection; it is not advertised to external eBGP peers.
BGP local preference is carried within an autonomous system and favors larger values for route selection; it is not advertised to external eBGP peers. The key distinction is: Local preference controls the AS-wide preferred exit before AS-path length, unlike MED which is commonly compared for neighbor ingress selection. Accordingly the remedy is: Set a suitable higher BGP local preference on the desired imported egress route and propagate it consistently inside the AS.
A risk assessment at Canal City University identifies: A backbone operator needs to prefer a primary egress for all internal routers without changing the external partner's AS path length. Which practical consequence is most specifically tied to this failure?
Traffic may exit through the wrong carrier, producing inconsistent routing or unwanted transit cost across the AS. The direct mitigation is: Set a suitable higher BGP local preference on the desired imported egress route and propagate it consistently inside the AS.
The concern could occur elsewhere when A provider receives a malformed or unauthorized customer prefix yet it enters route selection after a loose import policy. For the stated scenario, the immediate risk is: Traffic may exit through the wrong carrier, producing inconsistent routing or unwanted transit cost across the AS.
That consequence is more closely associated with another deficiency, such as: A provider changed a partner's ASN, leaving the old `peer-as` on its Junos BGP group while TCP connection attempts continue. The described fault instead exposes: Traffic may exit through the wrong carrier, producing inconsistent routing or unwanted transit cost across the AS.
It is a risk in another topology or protocol state: A carrier tags customer routes with a standard BGP community to drive downstream policy, but the tag never appears beyond the ingress edge. Here the most direct failure path is: Traffic may exit through the wrong carrier, producing inconsistent routing or unwanted transit cost across the AS.
The on-call engineer at Canal City University receives this fault report: A backbone operator needs to prefer a primary egress for all internal routers without changing the external partner's AS path length. What initial check best isolates the actual failing protocol stage?
Compare best paths and local-preference values for the exact prefix on internal speakers and identify the import policy setting it. Local preference controls the AS-wide preferred exit before AS-path length, unlike MED which is commonly compared for neighbor ingress selection.
This check may help with another root cause, for example: A provider advertises two links to a neighboring AS and wishes to express a preferred ingress while keeping the links as separate BGP paths. It does not test the first failed condition; start with: Compare best paths and local-preference values for the exact prefix on internal speakers and identify the import policy setting it.
That evidence could be normal while the reported defect persists. It is aimed at: A provider changed a partner's ASN, leaving the old `peer-as` on its Junos BGP group while TCP connection attempts continue. Instead inspect: Compare best paths and local-preference values for the exact prefix on internal speakers and identify the import policy setting it.
The check diagnoses a different layer of service. Its source issue is: Two equal eligible BGP paths to a destination exist, but forwarding uses only the best path while the service design needs shared capacity. The relevant initial check is: Compare best paths and local-preference values for the exact prefix on internal speakers and identify the import policy setting it.
Please check your mailbox for a message from support@examlabs.com and follow the directions.