JN0-650 Premium File
- 107 Questions & Answers
- Last Update: Nov 8, 2026
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.
An operator wants the same exit prefix installed with two eligible BGP next hops but only one is programmed even though costs are equal. Which targeted engineering change is MOST directly justified by the observed evidence?
Evaluate supported BGP multipath settings and confirm that candidate attributes satisfy multipath rules. This change specifically addresses the reported evidence: An operator wants the same exit prefix installed with two eligible BGP next hops but only one is programmed even though costs are equal. The relevant protocol mechanism is: BGP multipath can use multiple qualifying paths without making every non-best path eligible. A decisive acceptance test would be: The active route lists multiple eligible next hops and forwarding shows the intended load-sharing behavior.
Confirm the appropriate family and community propagation settings on the BGP peering path. This is a valid solution to a different Junos situation: Two routers share BGP routes but their intended extended-community values are absent at a downstream policy boundary. It does not directly correct the specific failure evidence here: An operator wants the same exit prefix installed with two eligible BGP next hops but only one is programmed even though costs are equal. The required targeted change is: Evaluate supported BGP multipath settings and confirm that candidate attributes satisfy multipath rules.
Trigger and verify an appropriate policy refresh or update mechanism supported by the BGP peers. This is a valid solution to a different Junos situation: A new BGP policy changes outbound community values, but previously advertised routes still display old metadata at the downstream peer. It does not directly correct the specific failure evidence here: An operator wants the same exit prefix installed with two eligible BGP next hops but only one is programmed even though costs are equal. The required targeted change is: Evaluate supported BGP multipath settings and confirm that candidate attributes satisfy multipath rules.
Replace catchall acceptance with ordered exact route-filter terms for permitted customer prefixes. This is a valid solution to a different Junos situation: A BGP edge is advertising an unintended private infrastructure prefix because a catchall export policy term accepted every active route. It does not directly correct the specific failure evidence here: An operator wants the same exit prefix installed with two eligible BGP next hops but only one is programmed even though costs are equal. The required targeted change is: Evaluate supported BGP multipath settings and confirm that candidate attributes satisfy multipath rules.
An operator wants the same exit prefix installed with two eligible BGP next hops but only one is programmed even though costs are equal. The proposed correction is: Evaluate supported BGP multipath settings and confirm that candidate attributes satisfy multipath rules. Which observation MOST directly confirms this fault is resolved?
The active route lists multiple eligible next hops and forwarding shows the intended load-sharing behavior. This is the direct acceptance evidence for the observed failure: An operator wants the same exit prefix installed with two eligible BGP next hops but only one is programmed even though costs are equal. The mechanism being validated is: BGP multipath can use multiple qualifying paths without making every non-best path eligible.
The intended extended-community values appear on the received route and relevant policies match them. That would validate a different condition: Two routers share BGP routes but their intended extended-community values are absent at a downstream policy boundary. The decisive check for the current issue is: The active route lists multiple eligible next hops and forwarding shows the intended load-sharing behavior.
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 active route lists multiple eligible next hops and forwarding shows the intended load-sharing behavior.
Only customer-approved routes are exported and the private infrastructure prefix remains hidden. That would validate a different condition: A BGP edge is advertising an unintended private infrastructure prefix because a catchall export policy term accepted every active route. The decisive check for the current issue is: The active route lists multiple eligible next hops and forwarding shows the intended load-sharing behavior.
A Junos engineer proposes this response: Evaluate supported BGP multipath settings and confirm that candidate attributes satisfy multipath rules. The situation is: An operator wants the same exit prefix installed with two eligible BGP next hops but only one is programmed even though costs are equal. Which technical principle BEST justifies the response?
BGP multipath can use multiple qualifying paths without making every non-best path eligible. This is the controlling mechanism in the specific case: An operator wants the same exit prefix installed with two eligible BGP next hops but only one is programmed even though costs are equal. It predicts the acceptance result: The active route lists multiple eligible next hops and forwarding shows the intended load-sharing behavior.
Extended communities provide structured BGP route metadata for supported applications and policies. This principle explains a separate situation: Two routers share BGP routes but their intended extended-community values are absent at a downstream policy boundary. For this issue the relevant mechanism is: BGP multipath can use multiple qualifying paths without making every non-best path eligible.
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 multipath can use multiple qualifying paths without making every non-best path eligible.
Junos routing policy evaluates ordered matching terms and their explicit accept or reject actions. This principle explains a separate situation: A BGP edge is advertising an unintended private infrastructure prefix because a catchall export policy term accepted every active route. For this issue the relevant mechanism is: BGP multipath can use multiple qualifying paths without making every non-best path eligible.
An operator wants the same exit prefix installed with two eligible BGP next hops but only one is programmed even though costs are equal. If the team bypasses or fails to implement the targeted correction (Evaluate supported BGP multipath settings and confirm that candidate attributes satisfy multipath rules.), which direct operational risk or residual exposure is MOST relevant?
Enabling generic ECMP cannot force unequal policy paths to qualify for BGP multipath. This is the consequence linked to the observed situation: An operator wants the same exit prefix installed with two eligible BGP next hops but only one is programmed even though costs are equal. It is prevented by: Evaluate supported BGP multipath settings and confirm that candidate attributes satisfy multipath rules. The underlying reason is: BGP multipath can use multiple qualifying paths without making every non-best path eligible.
Losing required extended-community metadata can break downstream tagging or route-target policy. This risk belongs to a different operational problem: Two routers share BGP routes but their intended extended-community values are absent at a downstream policy boundary. The stated condition instead exposes this direct risk: Enabling generic ECMP cannot force unequal policy paths to qualify for BGP multipath. The appropriate mitigation is: Evaluate supported BGP multipath settings and confirm that candidate attributes satisfy multipath rules.
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: Enabling generic ECMP cannot force unequal policy paths to qualify for BGP multipath. The appropriate mitigation is: Evaluate supported BGP multipath settings and confirm that candidate attributes satisfy multipath rules.
A permissive final term can leak sensitive topology into external BGP advertisements. This risk belongs to a different operational problem: A BGP edge is advertising an unintended private infrastructure prefix because a catchall export policy term accepted every active route. The stated condition instead exposes this direct risk: Enabling generic ECMP cannot force unequal policy paths to qualify for BGP multipath. The appropriate mitigation is: Evaluate supported BGP multipath settings and confirm that candidate attributes satisfy multipath rules.
Junos routing shows two equal-cost routes, but the forwarding table sends each tested flow down only one path while both next hops exist. Which targeted engineering change is MOST directly justified by the observed evidence?
Inspect forwarding-table load-balancing policy and per-flow hash behavior rather than expecting per-packet alternation. This change specifically addresses the reported evidence: Junos routing shows two equal-cost routes, but the forwarding table sends each tested flow down only one path while both next hops exist. The relevant protocol mechanism is: Junos may install multipath forwarding choices while flow hashing selects one path per flow. A decisive acceptance test would be: Multiple distinct test flows distribute across eligible next hops while each flow retains packet order.
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: Junos routing shows two equal-cost routes, but the forwarding table sends each tested flow down only one path while both next hops exist. The required targeted change is: Inspect forwarding-table load-balancing policy and per-flow hash behavior rather than expecting per-packet alternation.
Use a term-based BGP export policy that matches the authorized active route and accepted prefix. This is a valid solution to a different Junos situation: A partner asks a Junos edge to advertise a longer prefix only when a certain route is present in the active routing table. It does not directly correct the specific failure evidence here: Junos routing shows two equal-cost routes, but the forwarding table sends each tested flow down only one path while both next hops exist. The required targeted change is: Inspect forwarding-table load-balancing policy and per-flow hash behavior rather than expecting per-packet alternation.
Inspect next-hop recursive resolution and refresh the relevant IGP reachability before tuning BGP attributes. This is a valid solution to a different Junos situation: After a redundancy event, BGP still prefers an old path whose underlying transport next hop stopped resolving in the new IGP topology. It does not directly correct the specific failure evidence here: Junos routing shows two equal-cost routes, but the forwarding table sends each tested flow down only one path while both next hops exist. The required targeted change is: Inspect forwarding-table load-balancing policy and per-flow hash behavior rather than expecting per-packet alternation.
Junos routing shows two equal-cost routes, but the forwarding table sends each tested flow down only one path while both next hops exist. The proposed correction is: Inspect forwarding-table load-balancing policy and per-flow hash behavior rather than expecting per-packet alternation. Which observation MOST directly confirms this fault is resolved?
Multiple distinct test flows distribute across eligible next hops while each flow retains packet order. This is the direct acceptance evidence for the observed failure: Junos routing shows two equal-cost routes, but the forwarding table sends each tested flow down only one path while both next hops exist. The mechanism being validated is: Junos may install multipath forwarding choices while flow hashing selects one path per flow.
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: Multiple distinct test flows distribute across eligible next hops while each flow retains packet order.
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: Multiple distinct test flows distribute across eligible next hops while each flow retains packet order.
The unreachable candidate is rejected and an eligible alternative becomes active when reachable. That would validate a different condition: After a redundancy event, BGP still prefers an old path whose underlying transport next hop stopped resolving in the new IGP topology. The decisive check for the current issue is: Multiple distinct test flows distribute across eligible next hops while each flow retains packet order.
A Junos engineer proposes this response: Inspect forwarding-table load-balancing policy and per-flow hash behavior rather than expecting per-packet alternation. The situation is: Junos routing shows two equal-cost routes, but the forwarding table sends each tested flow down only one path while both next hops exist. Which technical principle BEST justifies the response?
Junos may install multipath forwarding choices while flow hashing selects one path per flow. This is the controlling mechanism in the specific case: 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 predicts the acceptance result: Multiple distinct test flows distribute across eligible next hops while each flow retains packet order.
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: Junos may install multipath forwarding choices while flow hashing selects one path per flow.
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: Junos may install multipath forwarding choices while flow hashing selects one path per flow.
BGP next-hop resolution depends on current reachability supplied by the routing table. This principle explains a separate situation: After a redundancy event, BGP still prefers an old path whose underlying transport next hop stopped resolving in the new IGP topology. For this issue the relevant mechanism is: Junos may install multipath forwarding choices while flow hashing selects one path per flow.
Junos routing shows two equal-cost routes, but the forwarding table sends each tested flow down only one path while both next hops exist. If the team bypasses or fails to implement the targeted correction (Inspect forwarding-table load-balancing policy and per-flow hash behavior rather than expecting per-packet alternation.), which direct operational risk or residual exposure is MOST relevant?
Interpreting one test flow as proof that ECMP is disabled can lead to needless changes. This is the consequence linked to the observed 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 is prevented by: Inspect forwarding-table load-balancing policy and per-flow hash behavior rather than expecting per-packet alternation. The underlying reason is: Junos may install multipath forwarding choices while flow hashing selects one path per flow.
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: Interpreting one test flow as proof that ECMP is disabled can lead to needless changes. The appropriate mitigation is: Inspect forwarding-table load-balancing policy and per-flow hash behavior rather than expecting per-packet alternation.
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: Interpreting one test flow as proof that ECMP is disabled can lead to needless changes. The appropriate mitigation is: Inspect forwarding-table load-balancing policy and per-flow hash behavior rather than expecting per-packet alternation.
Keeping an invalid recursive next hop can create a control-plane route without usable forwarding. This risk belongs to a different operational problem: After a redundancy event, BGP still prefers an old path whose underlying transport next hop stopped resolving in the new IGP topology. The stated condition instead exposes this direct risk: Interpreting one test flow as proof that ECMP is disabled can lead to needless changes. The appropriate mitigation is: Inspect forwarding-table load-balancing policy and per-flow hash behavior rather than expecting per-packet alternation.
The enterprise wants to steer traffic toward the upstream with lower IGP cost only after local preference and AS-path checks tie. Which targeted engineering change is MOST directly justified by the observed evidence?
Check Junos BGP selection order and the IGP cost to each reachable next hop. This change specifically addresses the reported evidence: The enterprise wants to steer traffic toward the upstream with lower IGP cost only after local preference and AS-path checks tie. The relevant protocol mechanism is: BGP path selection considers interior cost only after higher-priority BGP attribute comparisons. A decisive acceptance test would be: The chosen best path follows the correct egress-cost tie-break once earlier attributes tie.
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: The enterprise wants to steer traffic toward the upstream with lower IGP cost only after local preference and AS-path checks tie. The required targeted change is: Check Junos BGP selection order and the IGP cost to each reachable next hop.
Prefer the valid shorter AS path after earlier path-selection criteria tie. This is a valid solution to a different Junos 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. It does not directly correct the specific failure evidence here: The enterprise wants to steer traffic toward the upstream with lower IGP cost only after local preference and AS-path checks tie. The required targeted change is: Check Junos BGP selection order and the IGP cost to each reachable next hop.
Evaluate supported BGP multipath settings and confirm that candidate attributes satisfy multipath rules. This is a valid solution to a different Junos situation: An operator wants the same exit prefix installed with two eligible BGP next hops but only one is programmed even though costs are equal. It does not directly correct the specific failure evidence here: The enterprise wants to steer traffic toward the upstream with lower IGP cost only after local preference and AS-path checks tie. The required targeted change is: Check Junos BGP selection order and the IGP cost to each reachable next hop.
The enterprise wants to steer traffic toward the upstream with lower IGP cost only after local preference and AS-path checks tie. The proposed correction is: Check Junos BGP selection order and the IGP cost to each reachable next hop. Which observation MOST directly confirms this fault is resolved?
The chosen best path follows the correct egress-cost tie-break once earlier attributes tie. This is the direct acceptance evidence for the observed failure: The enterprise wants to steer traffic toward the upstream with lower IGP cost only after local preference and AS-path checks tie. The mechanism being validated is: BGP path selection considers interior cost only after higher-priority BGP attribute comparisons.
The best-path display chooses ISP-A when reachability and earlier selection criteria are satisfied. That would validate a different condition: 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. The decisive check for the current issue is: The chosen best path follows the correct egress-cost tie-break once earlier attributes tie.
The path with one AS hop becomes the BGP best path under the controlled comparison. That would validate a different condition: 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. The decisive check for the current issue is: The chosen best path follows the correct egress-cost tie-break once earlier attributes tie.
The active route lists multiple eligible next hops and forwarding shows the intended load-sharing behavior. That would validate a different condition: An operator wants the same exit prefix installed with two eligible BGP next hops but only one is programmed even though costs are equal. The decisive check for the current issue is: The chosen best path follows the correct egress-cost tie-break once earlier attributes tie.
Please check your mailbox for a message from support@examlabs.com and follow the directions.