JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
Before changing configuration at Bridgeway Cloud, an engineer investigates: An operator changes local preference on its own router expecting a remote AS to honor it, but the remote side never receives that attribute. Which first diagnostic most directly tests the suspected cause?
That evidence could be normal while the reported defect persists. It is aimed at: A backbone operator needs to prefer a primary egress for all internal routers without changing the external partner's AS path length. Instead inspect: Check outbound advertised path attributes and the remote neighbor's policy and MED comparison rules rather than assuming remote local preference.
The check diagnoses a different layer of service. Its source issue is: A received iBGP route is visible in inet.0 but inactive because its BGP next hop cannot be resolved through the IGP. The relevant initial check is: Check outbound advertised path attributes and the remote neighbor's policy and MED comparison rules rather than assuming remote local preference.
This check may help with another root cause, for example: A planned customer route appears in the partner's advertisements but Junos rejects it at an early inbound policy term. It does not test the first failed condition; start with: Check outbound advertised path attributes and the remote neighbor's policy and MED comparison rules rather than assuming remote local preference.
Check outbound advertised path attributes and the remote neighbor's policy and MED comparison rules rather than assuming remote local preference. BGP MED is a hint under neighbor policy, not a guaranteed cross-AS command to select one path.
At Seawood Media, a service provider router shows this failure: A BGP speaker learns a route from one iBGP peer but does not pass it to another internal peer, causing partial prefix visibility. What is the best targeted configuration or operations action?
That would address a separate configuration fault: Two equal eligible BGP paths to a destination exist, but forwarding uses only the best path while the service design needs shared capacity. This stem identifies a different cause, corrected by: Implement a supported iBGP full mesh or route-reflector topology and verify correct client/peer advertisements and next-hop reachability.
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: An iBGP session being Established does not guarantee iBGP routes can transit through that speaker to a second iBGP peer.
The other action is relevant when A provider advertises two links to a neighboring AS and wishes to express a preferred ingress while keeping the links as separate BGP paths. The current case instead requires: Implement a supported iBGP full mesh or route-reflector topology and verify correct client/peer advertisements and next-hop reachability. The distinction is: An iBGP session being Established does not guarantee iBGP routes can transit through that speaker to a second iBGP peer.
Implement a supported iBGP full mesh or route-reflector topology and verify correct client/peer advertisements and next-hop reachability. The case-specific reason is: An iBGP session being Established does not guarantee iBGP routes can transit through that speaker to a second iBGP peer. A direct acceptance test is: The required internal BGP speakers receive routes across the topology without iBGP re-advertisement violations or looped next hops.
A change auditor at Seawood Media must validate remediation of this finding: A BGP speaker learns a route from one iBGP peer but does not pass it to another internal peer, causing partial prefix visibility. Which test outcome is the strongest acceptance evidence?
This would be valid for another situation: A provider changed a partner's ASN, leaving the old `peer-as` on its Junos BGP group while TCP connection attempts continue. It does not establish that the failing boundary in this scenario works; verify: The required internal BGP speakers receive routes across the topology without iBGP re-advertisement violations or looped next hops.
This would be valid for another situation: A router has eBGP paths with equal relevant attributes and the operations team assumes both will automatically enter the forwarding table. It does not establish that the failing boundary in this scenario works; verify: The required internal BGP speakers receive routes across the topology without iBGP re-advertisement violations or looped next hops.
The required internal BGP speakers receive routes across the topology without iBGP re-advertisement violations or looped next hops. An iBGP session being Established does not guarantee iBGP routes can transit through that speaker to a second iBGP peer.
That check proves something else, such as: An edge advertises unapproved internal prefixes after an operator broadens a BGP export term beyond the intended customer route set. It could pass while the stated problem remains. The targeted evidence here is: The required internal BGP speakers receive routes across the topology without iBGP re-advertisement violations or looped next hops.
The operations training team at Seawood Media discusses this issue: A BGP speaker learns a route from one iBGP peer but does not pass it to another internal peer, causing partial prefix visibility. Which technical explanation matches the intended correction?
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: An iBGP session being Established does not guarantee iBGP routes can transit through that speaker to a second iBGP peer.
Standard iBGP split-horizon prevents an iBGP-learned route from being advertised to other iBGP peers unless a permitted reflector/confederation mechanism is used. The key distinction is: An iBGP session being Established does not guarantee iBGP routes can transit through that speaker to a second iBGP peer. Accordingly the remedy is: Implement a supported iBGP full mesh or route-reflector topology and verify correct client/peer advertisements and next-hop reachability.
This explains a separate protocol behavior: A carrier tags customer routes with a standard BGP community to drive downstream policy, but the tag never appears beyond the ingress edge. In the current facts, the controlling mechanism is: Standard iBGP split-horizon prevents an iBGP-learned route from being advertised to other iBGP peers unless a permitted reflector/confederation mechanism is used.
The statement can be true when A provider changed a partner's ASN, leaving the old `peer-as` on its Junos BGP group while TCP connection attempts continue. But it does not explain the reported failure. Here: An iBGP session being Established does not guarantee iBGP routes can transit through that speaker to a second iBGP peer.
At Seawood Media, a service acceptance review considers the unresolved issue: A BGP speaker learns a route from one iBGP peer but does not pass it to another internal peer, causing partial prefix visibility. Which operational exposure follows most directly?
Parts of the AS can lack routes despite each router having some established iBGP neighbors. The direct mitigation is: Implement a supported iBGP full mesh or route-reflector topology and verify correct client/peer advertisements and next-hop reachability.
That consequence is more closely associated with another deficiency, such as: A router has eBGP paths with equal relevant attributes and the operations team assumes both will automatically enter the forwarding table. The described fault instead exposes: Parts of the AS can lack routes despite each router having some established iBGP neighbors.
It is a risk in another topology or protocol state: A team assumes periodic UPDATE messages keep a quiet BGP session alive, but the route table is stable and no updates are due. Here the most direct failure path is: Parts of the AS can lack routes despite each router having some established iBGP neighbors.
The concern could occur elsewhere when 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. For the stated scenario, the immediate risk is: Parts of the AS can lack routes despite each router having some established iBGP neighbors.
Before changing configuration at Seawood Media, an engineer investigates: A BGP speaker learns a route from one iBGP peer but does not pass it to another internal peer, causing partial prefix visibility. Which first diagnostic most directly tests the suspected cause?
This check may help with another root cause, for example: A received iBGP route is visible in inet.0 but inactive because its BGP next hop cannot be resolved through the IGP. It does not test the first failed condition; start with: Check peer topology and route advertisement path for a specific iBGP-learned prefix, identifying a missing full mesh or reflector role.
Check peer topology and route advertisement path for a specific iBGP-learned prefix, identifying a missing full mesh or reflector role. An iBGP session being Established does not guarantee iBGP routes can transit through that speaker to a second iBGP peer.
The check diagnoses a different layer of service. Its source issue is: A provider advertises two links to a neighboring AS and wishes to express a preferred ingress while keeping the links as separate BGP paths. The relevant initial check is: Check peer topology and route advertisement path for a specific iBGP-learned prefix, identifying a missing full mesh or reflector role.
This check may help with another root cause, for example: A provider changed a partner's ASN, leaving the old `peer-as` on its Junos BGP group while TCP connection attempts continue. It does not test the first failed condition; start with: Check peer topology and route advertisement path for a specific iBGP-learned prefix, identifying a missing full mesh or reflector role.
During a Junos network change at Orion Transit Exchange, the engineer observes: A provider adds more iBGP speakers without a route-reflector or full-mesh design and assumes iBGP will transitively flood routes. Which remediation most directly fixes the described problem?
The other action is relevant when 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 current case instead requires: Implement a supported iBGP full mesh or route-reflector topology and verify correct client/peer advertisements and next-hop reachability. The distinction is: An iBGP session being Established does not guarantee iBGP routes can transit through that speaker to a second iBGP peer.
Implement a supported iBGP full mesh or route-reflector topology and verify correct client/peer advertisements and next-hop reachability. The case-specific reason is: An iBGP session being Established does not guarantee iBGP routes can transit through that speaker to a second iBGP peer. A direct acceptance test is: The required internal BGP speakers receive routes across the topology without iBGP re-advertisement violations or looped next hops.
This action may apply to a different problem, for example: 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 repair the stated failure boundary. The case-specific reason is: An iBGP session being Established does not guarantee iBGP routes can transit through that speaker to a second iBGP peer.
The other action is relevant when A team assumes periodic UPDATE messages keep a quiet BGP session alive, but the route table is stable and no updates are due. The current case instead requires: Implement a supported iBGP full mesh or route-reflector topology and verify correct client/peer advertisements and next-hop reachability. The distinction is: An iBGP session being Established does not guarantee iBGP routes can transit through that speaker to a second iBGP peer.
The Junos team at Orion Transit Exchange needs a success criterion for this defect: A provider adds more iBGP speakers without a route-reflector or full-mesh design and assumes iBGP will transitively flood routes. Which observed result most precisely confirms the intended repair?
The observation confirms a different component's behavior. Its source context is: An edge advertises unapproved internal prefixes after an operator broadens a BGP export term beyond the intended customer route set. In this case the success criterion is: The required internal BGP speakers receive routes across the topology without iBGP re-advertisement violations or looped next hops.
That check proves something else, such as: Two neighboring providers configured for eBGP have IP reachability but the BGP session remains Active because one side uses the wrong peer AS number. It could pass while the stated problem remains. The targeted evidence here is: The required internal BGP speakers receive routes across the topology without iBGP re-advertisement violations or looped next hops.
This would be valid for another situation: An intermittent control-plane firewall blocks one BGP packet class, and operators need to separate OPEN, KEEPALIVE, UPDATE and NOTIFICATION behavior. It does not establish that the failing boundary in this scenario works; verify: The required internal BGP speakers receive routes across the topology without iBGP re-advertisement violations or looped next hops.
The required internal BGP speakers receive routes across the topology without iBGP re-advertisement violations or looped next hops. An iBGP session being Established does not guarantee iBGP routes can transit through that speaker to a second iBGP peer.
While analyzing a service failure at Orion Transit Exchange, the following is observed: A provider adds more iBGP speakers without a route-reflector or full-mesh design and assumes iBGP will transitively flood routes. Which mechanism best explains the underlying control-plane or forwarding behavior?
Standard iBGP split-horizon prevents an iBGP-learned route from being advertised to other iBGP peers unless a permitted reflector/confederation mechanism is used. The key distinction is: An iBGP session being Established does not guarantee iBGP routes can transit through that speaker to a second iBGP peer. Accordingly the remedy is: Implement a supported iBGP full mesh or route-reflector topology and verify correct client/peer advertisements and next-hop reachability.
The statement can be true when Two neighboring providers configured for eBGP have IP reachability but the BGP session remains Active because one side uses the wrong peer AS number. But it does not explain the reported failure. Here: An iBGP session being Established does not guarantee iBGP routes can transit through that speaker to a second iBGP peer.
That principle belongs to a different service stage: A backbone operator needs to prefer a primary egress for all internal routers without changing the external partner's AS path length. The directly relevant mechanism is: Standard iBGP split-horizon prevents an iBGP-learned route from being advertised to other iBGP peers unless a permitted reflector/confederation mechanism is used.
This explains a separate protocol behavior: The provider expects a shorter AS path to win, but another path has a deliberately higher local preference and is selected instead. In the current facts, the controlling mechanism is: Standard iBGP split-horizon prevents an iBGP-learned route from being advertised to other iBGP peers unless a permitted reflector/confederation mechanism is used.
The following provider defect remains uncorrected at Orion Transit Exchange: A provider adds more iBGP speakers without a route-reflector or full-mesh design and assumes iBGP will transitively flood routes. What is the most direct service or security risk of leaving it unresolved?
It is a risk in another topology or protocol state: An edge advertises unapproved internal prefixes after an operator broadens a BGP export term beyond the intended customer route set. Here the most direct failure path is: Parts of the AS can lack routes despite each router having some established iBGP neighbors.
Parts of the AS can lack routes despite each router having some established iBGP neighbors. The direct mitigation is: Implement a supported iBGP full mesh or route-reflector topology and verify correct client/peer advertisements and next-hop reachability.
That consequence is more closely associated with another deficiency, 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. The described fault instead exposes: Parts of the AS can lack routes despite each router having some established iBGP neighbors.
It is a risk in another topology or protocol state: Two neighboring providers configured for eBGP have IP reachability but the BGP session remains Active because one side uses the wrong peer AS number. Here the most direct failure path is: Parts of the AS can lack routes despite each router having some established iBGP neighbors.
A support escalation at Orion Transit Exchange describes: A provider adds more iBGP speakers without a route-reflector or full-mesh design and assumes iBGP will transitively flood routes. Where should the Junos operator look first for decisive evidence?
The check diagnoses a different layer of service. Its source issue is: A provider changed a partner's ASN, leaving the old `peer-as` on its Junos BGP group while TCP connection attempts continue. The relevant initial check is: Check peer topology and route advertisement path for a specific iBGP-learned prefix, identifying a missing full mesh or reflector role.
Check peer topology and route advertisement path for a specific iBGP-learned prefix, identifying a missing full mesh or reflector role. An iBGP session being Established does not guarantee iBGP routes can transit through that speaker to a second iBGP peer.
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: Check peer topology and route advertisement path for a specific iBGP-learned prefix, identifying a missing full mesh or reflector role.
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: Check peer topology and route advertisement path for a specific iBGP-learned prefix, identifying a missing full mesh or reflector role.
Please check your mailbox for a message from support@examlabs.com and follow the directions.