JN0-650 Premium File
- 107 Questions & Answers
- Last Update: Nov 8, 2026
Two routers share BGP routes but their intended extended-community values are absent at a downstream policy boundary. The proposed correction is: Confirm the appropriate family and community propagation settings on the BGP peering path. Which observation MOST directly confirms this fault is resolved?
The intended extended-community values appear on the received route and relevant policies match them. This is the direct acceptance evidence for the observed failure: Two routers share BGP routes but their intended extended-community values are absent at a downstream policy boundary. The mechanism being validated is: Extended communities provide structured BGP route metadata for supported applications and policies.
The downstream advertised route shows the updated community without unplanned neighbor disruption. That would validate a different condition: A new BGP policy changes outbound community values, but previously advertised routes still display old metadata at the downstream peer. The decisive check for the current issue is: The intended extended-community values appear on the received route and relevant policies match them.
The targeted route is installed with a discard treatment, while unrelated routes are unaffected. That would validate a different condition: A border router receives a route tagged with an expected blackhole community, but no downstream filter implements the associated traffic-handling action. The decisive check for the current issue is: The intended extended-community values appear on the received route and relevant policies match them.
The accepted received AS path no longer violates the intended AS-loop policy at the upstream peer. That would validate a different condition: An EBGP peer unexpectedly rejects local advertisements after the enterprise appends its own AS number twice in an outbound policy. The decisive check for the current issue is: The intended extended-community values appear on the received route and relevant policies match them.
A Junos engineer proposes this response: Confirm the appropriate family and community propagation settings on the BGP peering path. The situation is: Two routers share BGP routes but their intended extended-community values are absent at a downstream policy boundary. Which technical principle BEST justifies the response?
Extended communities provide structured BGP route metadata for supported applications and policies. This is the controlling mechanism in the specific case: Two routers share BGP routes but their intended extended-community values are absent at a downstream policy boundary. It predicts the acceptance result: The intended extended-community values appear on the received route and relevant policies match them.
BGP advertisements reflect routing policy and may require controlled re-evaluation after changes. This principle explains a separate situation: A new BGP policy changes outbound community values, but previously advertised routes still display old metadata at the downstream peer. For this issue the relevant mechanism is: Extended communities provide structured BGP route metadata for supported applications and policies.
BGP AS-path length acts as a path-selection discriminator after local preference. This principle explains a separate situation: Two BGP routes are equal in local preference, but one includes three AS hops and the other one, and no earlier attribute resolves the comparison. For this issue the relevant mechanism is: Extended communities provide structured BGP route metadata for supported applications and policies.
BGP AS-path records traversed autonomous systems and supports AS-loop detection. This principle explains a separate situation: An EBGP peer unexpectedly rejects local advertisements after the enterprise appends its own AS number twice in an outbound policy. For this issue the relevant mechanism is: Extended communities provide structured BGP route metadata for supported applications and policies.
Two routers share BGP routes but their intended extended-community values are absent at a downstream policy boundary. If the team bypasses or fails to implement the targeted correction (Confirm the appropriate family and community propagation settings on the BGP peering path.), which direct operational risk or residual exposure is MOST relevant?
Losing required extended-community metadata can break downstream tagging or route-target policy. This is the consequence linked to the observed situation: Two routers share BGP routes but their intended extended-community values are absent at a downstream policy boundary. It is prevented by: Confirm the appropriate family and community propagation settings on the BGP peering path. The underlying reason is: Extended communities provide structured BGP route metadata for supported applications and policies.
Assuming a locally changed policy is already reflected remotely can conceal stale announcements. This risk belongs to a different operational problem: A new BGP policy changes outbound community values, but previously advertised routes still display old metadata at the downstream peer. The stated condition instead exposes this direct risk: Losing required extended-community metadata can break downstream tagging or route-target policy. The appropriate mitigation is: Confirm the appropriate family and community propagation settings on the BGP peering path.
Treating a community value as a universal automatic security filter leaves unwanted traffic permitted. This risk belongs to a different operational problem: A border router receives a route tagged with an expected blackhole community, but no downstream filter implements the associated traffic-handling action. The stated condition instead exposes this direct risk: Losing required extended-community metadata can break downstream tagging or route-target policy. The appropriate mitigation is: Confirm the appropriate family and community propagation settings on the BGP peering path.
Adjusting only MED on external advertisements may not control the enterprise's own outbound choice. This risk belongs to a different operational problem: An enterprise wants every internal BGP router to favor the primary upstream even though that primary route traverses more external autonomous systems. The stated condition instead exposes this direct risk: Losing required extended-community metadata can break downstream tagging or route-target policy. The appropriate mitigation is: Confirm the appropriate family and community propagation settings on the BGP peering path.
An IPv6-only prefix should be exchanged over an existing BGP neighbor but the group currently negotiates only inet unicast. Which targeted engineering change is MOST directly justified by the observed evidence?
Enable and verify the inet6-unicast NLRI family on both compatible peers. This change specifically addresses the reported evidence: An IPv6-only prefix should be exchanged over an existing BGP neighbor but the group currently negotiates only inet unicast. The relevant protocol mechanism is: BGP address families distinguish IPv4 inet from IPv6 inet6 reachability exchange. A decisive acceptance test would be: The BGP session reports inet6 capability and advertises the expected IPv6 prefix.
Match the intended BGP NLRI family and routing-instance policy to the actual service. This is a valid solution to a different Junos situation: A BGP neighbor advertises prefixes but the receiving Junos instance assigns them to the wrong logical routing table because family/instance design differs. It does not directly correct the specific failure evidence here: An IPv6-only prefix should be exchanged over an existing BGP neighbor but the group currently negotiates only inet unicast. The required targeted change is: Enable and verify the inet6-unicast NLRI family on both compatible peers.
Restore a usable unicast route to the BGP next hop before trying to override local preference. This is a valid solution to a different Junos situation: A route from an EBGP peer shows a valid next-hop address that cannot be resolved to any active transport route. It does not directly correct the specific failure evidence here: An IPv6-only prefix should be exchanged over an existing BGP neighbor but the group currently negotiates only inet unicast. The required targeted change is: Enable and verify the inet6-unicast NLRI family on both compatible peers.
Match the intended BGP community in a policy term and explicitly set the desired acceptance action. This is a valid solution to a different Junos situation: A BGP policy marks customer prefixes with a specific community, but the receiving policy has no match and permits unrestricted redistribution. It does not directly correct the specific failure evidence here: An IPv6-only prefix should be exchanged over an existing BGP neighbor but the group currently negotiates only inet unicast. The required targeted change is: Enable and verify the inet6-unicast NLRI family on both compatible peers.
An IPv6-only prefix should be exchanged over an existing BGP neighbor but the group currently negotiates only inet unicast. The proposed correction is: Enable and verify the inet6-unicast NLRI family on both compatible peers. Which observation MOST directly confirms this fault is resolved?
The BGP session reports inet6 capability and advertises the expected IPv6 prefix. This is the direct acceptance evidence for the observed failure: An IPv6-only prefix should be exchanged over an existing BGP neighbor but the group currently negotiates only inet unicast. The mechanism being validated is: BGP address families distinguish IPv4 inet from IPv6 inet6 reachability exchange.
The received prefixes appear in the correct table and resolve the intended next hops. That would validate a different condition: A BGP neighbor advertises prefixes but the receiving Junos instance assigns them to the wrong logical routing table because family/instance design differs. The decisive check for the current issue is: The BGP session reports inet6 capability and advertises the expected IPv6 prefix.
The next hop resolves and the received BGP prefix becomes eligible for active selection. That would validate a different condition: A route from an EBGP peer shows a valid next-hop address that cannot be resolved to any active transport route. The decisive check for the current issue is: The BGP session reports inet6 capability and advertises the expected IPv6 prefix.
Community-tagged routes are processed according to policy while other routes take the default rejection. That would validate a different condition: A BGP policy marks customer prefixes with a specific community, but the receiving policy has no match and permits unrestricted redistribution. The decisive check for the current issue is: The BGP session reports inet6 capability and advertises the expected IPv6 prefix.
A Junos engineer proposes this response: Enable and verify the inet6-unicast NLRI family on both compatible peers. The situation is: An IPv6-only prefix should be exchanged over an existing BGP neighbor but the group currently negotiates only inet unicast. Which technical principle BEST justifies the response?
BGP address families distinguish IPv4 inet from IPv6 inet6 reachability exchange. This is the controlling mechanism in the specific case: An IPv6-only prefix should be exchanged over an existing BGP neighbor but the group currently negotiates only inet unicast. It predicts the acceptance result: The BGP session reports inet6 capability and advertises the expected IPv6 prefix.
BGP address-family and routing-instance context determine where received routes are stored. This principle explains a separate situation: A BGP neighbor advertises prefixes but the receiving Junos instance assigns them to the wrong logical routing table because family/instance design differs. For this issue the relevant mechanism is: BGP address families distinguish IPv4 inet from IPv6 inet6 reachability exchange.
BGP next-hop reachability must be established before a route can be used for forwarding. This principle explains a separate situation: A route from an EBGP peer shows a valid next-hop address that cannot be resolved to any active transport route. For this issue the relevant mechanism is: BGP address families distinguish IPv4 inet from IPv6 inet6 reachability exchange.
BGP communities are attachable route tags used by configured routing policies. This principle explains a separate situation: A BGP policy marks customer prefixes with a specific community, but the receiving policy has no match and permits unrestricted redistribution. For this issue the relevant mechanism is: BGP address families distinguish IPv4 inet from IPv6 inet6 reachability exchange.
An IPv6-only prefix should be exchanged over an existing BGP neighbor but the group currently negotiates only inet unicast. If the team bypasses or fails to implement the targeted correction (Enable and verify the inet6-unicast NLRI family on both compatible peers.), which direct operational risk or residual exposure is MOST relevant?
A working IPv4 BGP session does not imply IPv6 unicast NLRI negotiation is enabled. This is the consequence linked to the observed situation: An IPv6-only prefix should be exchanged over an existing BGP neighbor but the group currently negotiates only inet unicast. It is prevented by: Enable and verify the inet6-unicast NLRI family on both compatible peers. The underlying reason is: BGP address families distinguish IPv4 inet from IPv6 inet6 reachability exchange.
Mixing route families or virtual tables can make reachable prefixes invisible to the intended service. This risk belongs to a different operational problem: A BGP neighbor advertises prefixes but the receiving Junos instance assigns them to the wrong logical routing table because family/instance design differs. The stated condition instead exposes this direct risk: A working IPv4 BGP session does not imply IPv6 unicast NLRI negotiation is enabled. The appropriate mitigation is: Enable and verify the inet6-unicast NLRI family on both compatible peers.
A high-preference route with an unreachable next hop cannot become a viable forwarding path. This risk belongs to a different operational problem: A route from an EBGP peer shows a valid next-hop address that cannot be resolved to any active transport route. The stated condition instead exposes this direct risk: A working IPv4 BGP session does not imply IPv6 unicast NLRI negotiation is enabled. The appropriate mitigation is: Enable and verify the inet6-unicast NLRI family on both compatible peers.
A community alone does not enforce traffic policy until a receiver applies a matching action. This risk belongs to a different operational problem: A BGP policy marks customer prefixes with a specific community, but the receiving policy has no match and permits unrestricted redistribution. The stated condition instead exposes this direct risk: A working IPv4 BGP session does not imply IPv6 unicast NLRI negotiation is enabled. The appropriate mitigation is: Enable and verify the inet6-unicast NLRI family on both compatible peers.
A BGP neighbor advertises prefixes but the receiving Junos instance assigns them to the wrong logical routing table because family/instance design differs. Which targeted engineering change is MOST directly justified by the observed evidence?
Match the intended BGP NLRI family and routing-instance policy to the actual service. This change specifically addresses the reported evidence: A BGP neighbor advertises prefixes but the receiving Junos instance assigns them to the wrong logical routing table because family/instance design differs. The relevant protocol mechanism is: BGP address-family and routing-instance context determine where received routes are stored. A decisive acceptance test would be: The received prefixes appear in the correct table and resolve the intended next hops.
Enable and verify the inet6-unicast NLRI family on both compatible peers. This is a valid solution to a different Junos situation: An IPv6-only prefix should be exchanged over an existing BGP neighbor but the group currently negotiates only inet unicast. It does not directly correct the specific failure evidence here: A BGP neighbor advertises prefixes but the receiving Junos instance assigns them to the wrong logical routing table because family/instance design differs. The required targeted change is: Match the intended BGP NLRI family and routing-instance policy to the actual service.
Inspect forwarding-table load-balancing policy and per-flow hash behavior rather than expecting per-packet alternation. This is a valid solution to a different Junos situation: Junos routing shows two equal-cost routes, but the forwarding table sends each tested flow down only one path while both next hops exist. It does not directly correct the specific failure evidence here: A BGP neighbor advertises prefixes but the receiving Junos instance assigns them to the wrong logical routing table because family/instance design differs. The required targeted change is: Match the intended BGP NLRI family and routing-instance policy to the actual service.
Prefer the valid path with higher local preference before comparing AS-path length under Junos BGP selection. This is a valid solution to a different Junos situation: Two valid BGP paths for one prefix have different local preference attributes, 180 on ISP-A and 100 on ISP-B, but the operator chooses the shorter AS path on B. It does not directly correct the specific failure evidence here: A BGP neighbor advertises prefixes but the receiving Junos instance assigns them to the wrong logical routing table because family/instance design differs. The required targeted change is: Match the intended BGP NLRI family and routing-instance policy to the actual service.
A BGP neighbor advertises prefixes but the receiving Junos instance assigns them to the wrong logical routing table because family/instance design differs. The proposed correction is: Match the intended BGP NLRI family and routing-instance policy to the actual service. Which observation MOST directly confirms this fault is resolved?
The received prefixes appear in the correct table and resolve the intended next hops. This is the direct acceptance evidence for the observed failure: A BGP neighbor advertises prefixes but the receiving Junos instance assigns them to the wrong logical routing table because family/instance design differs. The mechanism being validated is: BGP address-family and routing-instance context determine where received routes are stored.
Community-tagged routes are processed according to policy while other routes take the default rejection. That would validate a different condition: A BGP policy marks customer prefixes with a specific community, but the receiving policy has no match and permits unrestricted redistribution. The decisive check for the current issue is: The received prefixes appear in the correct table and resolve the intended next hops.
The peer receives precisely the eligible prefix and withdraws it when export conditions fail. That would validate a different condition: A partner asks a Junos edge to advertise a longer prefix only when a certain route is present in the active routing table. The decisive check for the current issue is: The received prefixes appear in the correct table and resolve the intended next hops.
The downstream advertised route shows the updated community without unplanned neighbor disruption. That would validate a different condition: A new BGP policy changes outbound community values, but previously advertised routes still display old metadata at the downstream peer. The decisive check for the current issue is: The received prefixes appear in the correct table and resolve the intended next hops.
A Junos engineer proposes this response: Match the intended BGP NLRI family and routing-instance policy to the actual service. The situation is: A BGP neighbor advertises prefixes but the receiving Junos instance assigns them to the wrong logical routing table because family/instance design differs. Which technical principle BEST justifies the response?
BGP address-family and routing-instance context determine where received routes are stored. This is the controlling mechanism in the specific case: A BGP neighbor advertises prefixes but the receiving Junos instance assigns them to the wrong logical routing table because family/instance design differs. It predicts the acceptance result: The received prefixes appear in the correct table and resolve the intended next hops.
BGP communities are attachable route tags used by configured routing policies. This principle explains a separate situation: A BGP policy marks customer prefixes with a specific community, but the receiving policy has no match and permits unrestricted redistribution. For this issue the relevant mechanism is: BGP address-family and routing-instance context determine where received routes are stored.
Junos BGP export policy controls which locally eligible routes enter peer advertisements. This principle explains a separate situation: A partner asks a Junos edge to advertise a longer prefix only when a certain route is present in the active routing table. For this issue the relevant mechanism is: BGP address-family and routing-instance context determine where received routes are stored.
BGP advertisements reflect routing policy and may require controlled re-evaluation after changes. This principle explains a separate situation: A new BGP policy changes outbound community values, but previously advertised routes still display old metadata at the downstream peer. For this issue the relevant mechanism is: BGP address-family and routing-instance context determine where received routes are stored.
A BGP neighbor advertises prefixes but the receiving Junos instance assigns them to the wrong logical routing table because family/instance design differs. If the team bypasses or fails to implement the targeted correction (Match the intended BGP NLRI family and routing-instance policy to the actual service.), which direct operational risk or residual exposure is MOST relevant?
Mixing route families or virtual tables can make reachable prefixes invisible to the intended service. This is the consequence linked to the observed situation: A BGP neighbor advertises prefixes but the receiving Junos instance assigns them to the wrong logical routing table because family/instance design differs. It is prevented by: Match the intended BGP NLRI family and routing-instance policy to the actual service. The underlying reason is: BGP address-family and routing-instance context determine where received routes are stored.
A community alone does not enforce traffic policy until a receiver applies a matching action. This risk belongs to a different operational problem: A BGP policy marks customer prefixes with a specific community, but the receiving policy has no match and permits unrestricted redistribution. The stated condition instead exposes this direct risk: Mixing route families or virtual tables can make reachable prefixes invisible to the intended service. The appropriate mitigation is: Match the intended BGP NLRI family and routing-instance policy to the actual service.
An unconditional export can leak prefixes when the intended backing reachability disappears. This risk belongs to a different operational problem: A partner asks a Junos edge to advertise a longer prefix only when a certain route is present in the active routing table. The stated condition instead exposes this direct risk: Mixing route families or virtual tables can make reachable prefixes invisible to the intended service. The appropriate mitigation is: Match the intended BGP NLRI family and routing-instance policy to the actual service.
Assuming a locally changed policy is already reflected remotely can conceal stale announcements. This risk belongs to a different operational problem: A new BGP policy changes outbound community values, but previously advertised routes still display old metadata at the downstream peer. The stated condition instead exposes this direct risk: Mixing route families or virtual tables can make reachable prefixes invisible to the intended service. The appropriate mitigation is: Match the intended BGP NLRI family and routing-instance policy to the actual service.
Please check your mailbox for a message from support@examlabs.com and follow the directions.