JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
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.
During a Junos network change at Redleaf Airports, the engineer observes: A transit customer prefix is locally active but never advertised to an approved eBGP neighbor because the export policy's final term rejects it. Which remediation most directly fixes the described problem?
Constrain Junos BGP export terms to approved active prefixes and attributes, preserving explicit accept/reject behavior for the neighbor. The case-specific reason is: A healthy BGP session does not bypass an export filter, and a local active prefix is not necessarily advertised to every peer. A direct acceptance test is: The neighbor receives only intended active advertised routes with correct attributes; internal and reserved prefixes are not leaked.
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: Constrain Junos BGP export terms to approved active prefixes and attributes, preserving explicit accept/reject behavior for the neighbor. The distinction is: A healthy BGP session does not bypass an export filter, and a local active prefix is not necessarily advertised to every peer.
That would address a separate configuration fault: A provider advertises two links to a neighboring AS and wishes to express a preferred ingress while keeping the links as separate BGP paths. This stem identifies a different cause, corrected by: Constrain Junos BGP export terms to approved active prefixes and attributes, preserving explicit accept/reject behavior for the neighbor.
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: A healthy BGP session does not bypass an export filter, and a local active prefix is not necessarily advertised to every peer.
The Junos team at Redleaf Airports needs a success criterion for this defect: A transit customer prefix is locally active but never advertised to an approved eBGP neighbor because the export policy's final term rejects it. Which observed result most precisely confirms the intended repair?
This would be valid for another situation: A carrier tags customer routes with a standard BGP community to drive downstream policy, but the tag never appears beyond the ingress edge. It does not establish that the failing boundary in this scenario works; verify: The neighbor receives only intended active advertised routes with correct attributes; internal and reserved prefixes are not leaked.
The neighbor receives only intended active advertised routes with correct attributes; internal and reserved prefixes are not leaked. A healthy BGP session does not bypass an export filter, and a local active prefix is not necessarily advertised to every peer.
That check proves something else, such as: Two paths learned inside one AS reach the same destination; the selected exit conflicts with policy despite the chosen link having fewer AS hops. It could pass while the stated problem remains. The targeted evidence here is: The neighbor receives only intended active advertised routes with correct attributes; internal and reserved prefixes are not leaked.
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: The neighbor receives only intended active advertised routes with correct attributes; internal and reserved prefixes are not leaked.
While analyzing a service failure at Redleaf Airports, the following is observed: A transit customer prefix is locally active but never advertised to an approved eBGP neighbor because the export policy's final term rejects it. Which mechanism best explains the underlying control-plane or forwarding behavior?
That principle belongs to a different service stage: Two paths learned inside one AS reach the same destination; the selected exit conflicts with policy despite the chosen link having fewer AS hops. The directly relevant mechanism is: Ordered Junos BGP export policies determine which eligible local routes are advertised to a BGP group or neighbor.
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: A healthy BGP session does not bypass an export filter, and a local active prefix is not necessarily advertised to every peer.
The statement can be true 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. But it does not explain the reported failure. Here: A healthy BGP session does not bypass an export filter, and a local active prefix is not necessarily advertised to every peer.
Ordered Junos BGP export policies determine which eligible local routes are advertised to a BGP group or neighbor. The key distinction is: A healthy BGP session does not bypass an export filter, and a local active prefix is not necessarily advertised to every peer. Accordingly the remedy is: Constrain Junos BGP export terms to approved active prefixes and attributes, preserving explicit accept/reject behavior for the neighbor.
The following provider defect remains uncorrected at Redleaf Airports: A transit customer prefix is locally active but never advertised to an approved eBGP neighbor because the export policy's final term rejects it. What is the most direct service or security risk of leaving it unresolved?
That consequence is more closely associated with another deficiency, such as: Two paths learned inside one AS reach the same destination; the selected exit conflicts with policy despite the chosen link having fewer AS hops. The described fault instead exposes: Overly broad export leaks internal routing information or turns the edge into unwanted transit; overly narrow policy withholds customers.
It is a risk in another topology or protocol state: A planned customer route appears in the partner's advertisements but Junos rejects it at an early inbound policy term. Here the most direct failure path is: Overly broad export leaks internal routing information or turns the edge into unwanted transit; overly narrow policy withholds customers.
Overly broad export leaks internal routing information or turns the edge into unwanted transit; overly narrow policy withholds customers. The direct mitigation is: Constrain Junos BGP export terms to approved active prefixes and attributes, preserving explicit accept/reject behavior for the neighbor.
That consequence is more closely associated with another deficiency, such as: A neighbor's agreed selective-routing behavior fails because a community is added after the rejecting export term rather than before policy selection. The described fault instead exposes: Overly broad export leaks internal routing information or turns the edge into unwanted transit; overly narrow policy withholds customers.
A support escalation at Redleaf Airports describes: A transit customer prefix is locally active but never advertised to an approved eBGP neighbor because the export policy's final term rejects it. Where should the Junos operator look first for decisive evidence?
The check diagnoses a different layer of service. Its source issue is: An intermittent control-plane firewall blocks one BGP packet class, and operators need to separate OPEN, KEEPALIVE, UPDATE and NOTIFICATION behavior. The relevant initial check is: Check source route active state and `show route advertising-protocol bgp` with ordered export terms for the exact prefix.
Check source route active state and `show route advertising-protocol bgp` with ordered export terms for the exact prefix. A healthy BGP session does not bypass an export filter, and a local active prefix is not necessarily advertised to every peer.
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 source route active state and `show route advertising-protocol bgp` with ordered export terms for the exact prefix.
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: Check source route active state and `show route advertising-protocol bgp` with ordered export terms for the exact prefix.
The provider operations team at Silverpeak Data Networks reports: An edge advertises unapproved internal prefixes after an operator broadens a BGP export term beyond the intended customer route set. Which implementation decision best corrects the cause?
That would address a separate configuration fault: Two eBGP routes have equal earlier BGP decision attributes and the operator needs to explain why a path with fewer AS numbers is preferred. This stem identifies a different cause, corrected by: Constrain Junos BGP export terms to approved active prefixes and attributes, preserving explicit accept/reject behavior for the neighbor.
This action may apply to a different problem, for example: 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 does not repair the stated failure boundary. The case-specific reason is: A healthy BGP session does not bypass an export filter, and a local active prefix is not necessarily advertised to every peer.
The other action is relevant when A backbone operator needs to prefer a primary egress for all internal routers without changing the external partner's AS path length. The current case instead requires: Constrain Junos BGP export terms to approved active prefixes and attributes, preserving explicit accept/reject behavior for the neighbor. The distinction is: A healthy BGP session does not bypass an export filter, and a local active prefix is not necessarily advertised to every peer.
Constrain Junos BGP export terms to approved active prefixes and attributes, preserving explicit accept/reject behavior for the neighbor. The case-specific reason is: A healthy BGP session does not bypass an export filter, and a local active prefix is not necessarily advertised to every peer. A direct acceptance test is: The neighbor receives only intended active advertised routes with correct attributes; internal and reserved prefixes are not leaked.
During a post-change check at Silverpeak Data Networks, the original condition was: An edge advertises unapproved internal prefixes after an operator broadens a BGP export term beyond the intended customer route set. What evidence would validate the corrected behavior?
That check proves something else, such as: A planned customer route appears in the partner's advertisements but Junos rejects it at an early inbound policy term. It could pass while the stated problem remains. The targeted evidence here is: The neighbor receives only intended active advertised routes with correct attributes; internal and reserved prefixes are not leaked.
The neighbor receives only intended active advertised routes with correct attributes; internal and reserved prefixes are not leaked. A healthy BGP session does not bypass an export filter, and a local active prefix is not necessarily advertised to every peer.
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: The neighbor receives only intended active advertised routes with correct attributes; internal and reserved prefixes are not leaked.
That check proves something else, such as: The provider expects a shorter AS path to win, but another path has a deliberately higher local preference and is selected instead. It could pass while the stated problem remains. The targeted evidence here is: The neighbor receives only intended active advertised routes with correct attributes; internal and reserved prefixes are not leaked.
At Silverpeak Data Networks, an engineer is asked to explain this case: An edge advertises unapproved internal prefixes after an operator broadens a BGP export term beyond the intended customer route set. Which underlying routing or switching principle accounts for the appropriate solution?
Ordered Junos BGP export policies determine which eligible local routes are advertised to a BGP group or neighbor. The key distinction is: A healthy BGP session does not bypass an export filter, and a local active prefix is not necessarily advertised to every peer. Accordingly the remedy is: Constrain Junos BGP export terms to approved active prefixes and attributes, preserving explicit accept/reject behavior for the neighbor.
That principle belongs to a different service stage: 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 directly relevant mechanism is: Ordered Junos BGP export policies determine which eligible local routes are advertised to a BGP group or neighbor.
This explains a separate protocol behavior: A router has eBGP paths with equal relevant attributes and the operations team assumes both will automatically enter the forwarding table. In the current facts, the controlling mechanism is: Ordered Junos BGP export policies determine which eligible local routes are advertised to a BGP group or neighbor.
The statement can be true when A received iBGP route is visible in inet.0 but inactive because its BGP next hop cannot be resolved through the IGP. But it does not explain the reported failure. Here: A healthy BGP session does not bypass an export filter, and a local active prefix is not necessarily advertised to every peer.
A risk assessment at Silverpeak Data Networks identifies: An edge advertises unapproved internal prefixes after an operator broadens a BGP export term beyond the intended customer route set. Which practical consequence is most specifically tied to this failure?
The concern could occur elsewhere when A neighbor's agreed selective-routing behavior fails because a community is added after the rejecting export term rather than before policy selection. For the stated scenario, the immediate risk is: Overly broad export leaks internal routing information or turns the edge into unwanted transit; overly narrow policy withholds customers.
That consequence is more closely associated with another deficiency, such as: The provider expects a shorter AS path to win, but another path has a deliberately higher local preference and is selected instead. The described fault instead exposes: Overly broad export leaks internal routing information or turns the edge into unwanted transit; overly narrow policy withholds customers.
Overly broad export leaks internal routing information or turns the edge into unwanted transit; overly narrow policy withholds customers. The direct mitigation is: Constrain Junos BGP export terms to approved active prefixes and attributes, preserving explicit accept/reject behavior for the neighbor.
The concern could occur elsewhere when A BGP speaker learns a route from one iBGP peer but does not pass it to another internal peer, causing partial prefix visibility. For the stated scenario, the immediate risk is: Overly broad export leaks internal routing information or turns the edge into unwanted transit; overly narrow policy withholds customers.
The on-call engineer at Silverpeak Data Networks receives this fault report: An edge advertises unapproved internal prefixes after an operator broadens a BGP export term beyond the intended customer route set. What initial check best isolates the actual failing protocol stage?
Check source route active state and `show route advertising-protocol bgp` with ordered export terms for the exact prefix. A healthy BGP session does not bypass an export filter, and a local active prefix is not necessarily advertised to every peer.
That evidence could be normal while the reported defect persists. It is aimed at: A received iBGP route is visible in inet.0 but inactive because its BGP next hop cannot be resolved through the IGP. Instead inspect: Check source route active state and `show route advertising-protocol bgp` with ordered export terms for the exact prefix.
The check diagnoses a different layer of service. Its source issue is: A neighbor's agreed selective-routing behavior fails because a community is added after the rejecting export term rather than before policy selection. The relevant initial check is: Check source route active state and `show route advertising-protocol bgp` with ordered export terms for the exact prefix.
This check may help with another root cause, for example: A BGP speaker learns a route from one iBGP peer but does not pass it to another internal peer, causing partial prefix visibility. It does not test the first failed condition; start with: Check source route active state and `show route advertising-protocol bgp` with ordered export terms for the exact prefix.
Please check your mailbox for a message from support@examlabs.com and follow the directions.