Question 380
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: A route reflector restarts and clients retain stale reachability longer than intended while convergence is incomplete. Which operational control would best prevent a recurrence of this exact failure mode?
- Test representative distant-client best exits when expanding reflector geography.
- Audit next-hop reachability from clients served by geographically remote reflectors.
- Test reflectors' failover and route availability across representative client pairs.
- Test abrupt failure separately from graceful restart to expose stale-route risks.
Explanation
Correct Answer
D:Test abrupt failure separately from graceful restart to expose stale-route risks. The control limits repetition of the described root condition: Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails. During audits, confirm: The restart completes within negotiated timers or stale routes are safely withdrawn.
Incorrect Answers
A:Test representative distant-client best exits when expanding reflector geography. This is a plausible preventive practice for a different BGP condition, specifically Route-reflector optimal exit perspective. A standard reflector chooses its best path from its own topology perspective, which can differ from widely distributed clients. In this scenario, however, the distinguishing issue is BGP graceful restart stale routes and the confirming observation is: The restart completes within negotiated timers or stale routes are safely withdrawn.
B:Audit next-hop reachability from clients served by geographically remote reflectors. This is a plausible preventive practice for a different BGP condition, specifically RR client next-hop preservation. Route reflection usually preserves the original BGP next hop; RR adjacency alone does not carry the required forwarding transport. In this scenario, however, the distinguishing issue is BGP graceful restart stale routes and the confirming observation is: The restart completes within negotiated timers or stale routes are safely withdrawn.
C:Test reflectors' failover and route availability across representative client pairs. This is a plausible preventive practice for a different BGP condition, specifically BGP route reflector scaling. Route reflection reduces the need for every IBGP router to maintain direct sessions to every other IBGP router. In this scenario, however, the distinguishing issue is BGP graceful restart stale routes and the confirming observation is: The restart completes within negotiated timers or stale routes are safely withdrawn.
Question 381
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: Two eligible paths have equal LOCAL_PREF and AS_PATH length, yet a path tagged incomplete origin loses to a route with IGP origin. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare origin codes and verify no earlier tie-break attributes differ.
- Compare local preference on the competing routes and verify their next hops resolve.
- Compare AS_PATH lengths and any policy that rewrites higher-priority attributes.
- Inspect the exact AS-path expression and run route-policy match tests on sample path strings.
Explanation
Correct Answer
A:Compare origin codes and verify no earlier tie-break attributes differ. This check examines the decisive condition for BGP ORIGIN attribute tie before any unrelated changes are made. The underlying mechanism is: At the applicable BGP selection stage, lower origin-type value (IGP before incomplete) is preferred. The confirming observation is: The route with the preferred origin becomes best under otherwise equal higher-priority attributes.
Incorrect Answers
B:Compare local preference on the competing routes and verify their next hops resolve. This is a plausible diagnostic check for a different BGP condition, specifically Local preference exit choice. Within an AS, higher BGP local preference is selected ahead of AS-path length when paths are otherwise eligible. In this scenario, however, the distinguishing issue is BGP ORIGIN attribute tie and the confirming observation is: The route with the preferred origin becomes best under otherwise equal higher-priority attributes.
C:Compare AS_PATH lengths and any policy that rewrites higher-priority attributes. This is a plausible diagnostic check for a different BGP condition, specifically AS-path length selection. After equal higher-priority selection attributes, BGP generally prefers the shorter AS path among eligible candidate paths. In this scenario, however, the distinguishing issue is BGP ORIGIN attribute tie and the confirming observation is: The route with the preferred origin becomes best under otherwise equal higher-priority attributes.
D:Inspect the exact AS-path expression and run route-policy match tests on sample path strings. This is a plausible diagnostic check for a different BGP condition, specifically AS-path regex filter. BGP AS-path regex syntax and anchoring determine whether matching targets the origin AS, any traversed AS, or the entire sequence. In this scenario, however, the distinguishing issue is BGP ORIGIN attribute tie and the confirming observation is: The route with the preferred origin becomes best under otherwise equal higher-priority attributes.
Question 382
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: Two eligible paths have equal LOCAL_PREF and AS_PATH length, yet a path tagged incomplete origin loses to a route with IGP origin. Which routing or service mechanism best explains the reported behavior?
- Within an AS, higher BGP local preference is selected ahead of AS-path length when paths are otherwise eligible.
- At the applicable BGP selection stage, lower origin-type value (IGP before incomplete) is preferred.
- After equal higher-priority selection attributes, BGP generally prefers the shorter AS path among eligible candidate paths.
- BGP AS-path regex syntax and anchoring determine whether matching targets the origin AS, any traversed AS, or the entire sequence.
Explanation
Correct Answer
B:At the applicable BGP selection stage, lower origin-type value (IGP before incomplete) is preferred. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The route with the preferred origin becomes best under otherwise equal higher-priority attributes. The targeted correction is: Correct unwanted origin-setting policy if the preferred path must differ.
Incorrect Answers
A:Within an AS, higher BGP local preference is selected ahead of AS-path length when paths are otherwise eligible. This is a plausible protocol explanation for a different BGP condition, specifically Local preference exit choice. Within an AS, higher BGP local preference is selected ahead of AS-path length when paths are otherwise eligible. In this scenario, however, the distinguishing issue is BGP ORIGIN attribute tie and the confirming observation is: The route with the preferred origin becomes best under otherwise equal higher-priority attributes.
C:After equal higher-priority selection attributes, BGP generally prefers the shorter AS path among eligible candidate paths. This is a plausible protocol explanation for a different BGP condition, specifically AS-path length selection. After equal higher-priority selection attributes, BGP generally prefers the shorter AS path among eligible candidate paths. In this scenario, however, the distinguishing issue is BGP ORIGIN attribute tie and the confirming observation is: The route with the preferred origin becomes best under otherwise equal higher-priority attributes.
D:BGP AS-path regex syntax and anchoring determine whether matching targets the origin AS, any traversed AS, or the entire sequence. This is a plausible protocol explanation for a different BGP condition, specifically AS-path regex filter. BGP AS-path regex syntax and anchoring determine whether matching targets the origin AS, any traversed AS, or the entire sequence. In this scenario, however, the distinguishing issue is BGP ORIGIN attribute tie and the confirming observation is: The route with the preferred origin becomes best under otherwise equal higher-priority attributes.
Question 383
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: Two eligible paths have equal LOCAL_PREF and AS_PATH length, yet a path tagged incomplete origin loses to a route with IGP origin. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The chosen active route uses the deliberately higher-local-preference exit while backup remains valid.
- The shortest eligible AS path becomes preferred once conflicting policy overrides are removed.
- The route with the preferred origin becomes best under otherwise equal higher-priority attributes.
- Known prohibited-origin paths are rejected while legitimate transit paths remain eligible.
Explanation
Correct Answer
C:The route with the preferred origin becomes best under otherwise equal higher-priority attributes. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: At the applicable BGP selection stage, lower origin-type value (IGP before incomplete) is preferred.
Incorrect Answers
A:The chosen active route uses the deliberately higher-local-preference exit while backup remains valid. This is a plausible observed evidence for a different BGP condition, specifically Local preference exit choice. Within an AS, higher BGP local preference is selected ahead of AS-path length when paths are otherwise eligible. In this scenario, however, the distinguishing issue is BGP ORIGIN attribute tie and the confirming observation is: The route with the preferred origin becomes best under otherwise equal higher-priority attributes.
B:The shortest eligible AS path becomes preferred once conflicting policy overrides are removed. This is a plausible observed evidence for a different BGP condition, specifically AS-path length selection. After equal higher-priority selection attributes, BGP generally prefers the shorter AS path among eligible candidate paths. In this scenario, however, the distinguishing issue is BGP ORIGIN attribute tie and the confirming observation is: The route with the preferred origin becomes best under otherwise equal higher-priority attributes.
D:Known prohibited-origin paths are rejected while legitimate transit paths remain eligible. This is a plausible observed evidence for a different BGP condition, specifically AS-path regex filter. BGP AS-path regex syntax and anchoring determine whether matching targets the origin AS, any traversed AS, or the entire sequence. In this scenario, however, the distinguishing issue is BGP ORIGIN attribute tie and the confirming observation is: The route with the preferred origin becomes best under otherwise equal higher-priority attributes.
Question 384
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: Two eligible paths have equal LOCAL_PREF and AS_PATH length, yet a path tagged incomplete origin loses to a route with IGP origin. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Use an inbound routing policy to set the desired local preference for approved prefixes.
- Correct route-policy attributes or prepend design to implement the intended preference.
- Replace the broad expression with the intended anchored AS-path match.
- Correct unwanted origin-setting policy if the preferred path must differ.
Explanation
Correct Answer
D:Correct unwanted origin-setting policy if the preferred path must differ. The change addresses the root behavior described here: At the applicable BGP selection stage, lower origin-type value (IGP before incomplete) is preferred. Verify success with: The route with the preferred origin becomes best under otherwise equal higher-priority attributes.
Incorrect Answers
A:Use an inbound routing policy to set the desired local preference for approved prefixes. This is a plausible configuration or operational fix for a different BGP condition, specifically Local preference exit choice. Within an AS, higher BGP local preference is selected ahead of AS-path length when paths are otherwise eligible. In this scenario, however, the distinguishing issue is BGP ORIGIN attribute tie and the confirming observation is: The route with the preferred origin becomes best under otherwise equal higher-priority attributes.
B:Correct route-policy attributes or prepend design to implement the intended preference. This is a plausible configuration or operational fix for a different BGP condition, specifically AS-path length selection. After equal higher-priority selection attributes, BGP generally prefers the shorter AS path among eligible candidate paths. In this scenario, however, the distinguishing issue is BGP ORIGIN attribute tie and the confirming observation is: The route with the preferred origin becomes best under otherwise equal higher-priority attributes.
C:Replace the broad expression with the intended anchored AS-path match. This is a plausible configuration or operational fix for a different BGP condition, specifically AS-path regex filter. BGP AS-path regex syntax and anchoring determine whether matching targets the origin AS, any traversed AS, or the entire sequence. In this scenario, however, the distinguishing issue is BGP ORIGIN attribute tie and the confirming observation is: The route with the preferred origin becomes best under otherwise equal higher-priority attributes.
Question 385
During a core-routing migration rehearsal, an HPE Juniper Networking engineer investigates this situation: Two eligible paths have equal LOCAL_PREF and AS_PATH length, yet a path tagged incomplete origin loses to a route with IGP origin. Which operational control would best prevent a recurrence of this exact failure mode?
- Log origin attribute changes when redistributing or aggregating BGP routes.
- Document business exit priorities and verify local preference after peer resets.
- Audit path-length and local preference before changing peering relationships.
- Maintain positive and negative example AS paths alongside policy expressions.
Explanation
Correct Answer
A:Log origin attribute changes when redistributing or aggregating BGP routes. The control limits repetition of the described root condition: At the applicable BGP selection stage, lower origin-type value (IGP before incomplete) is preferred. During audits, confirm: The route with the preferred origin becomes best under otherwise equal higher-priority attributes.
Incorrect Answers
B:Document business exit priorities and verify local preference after peer resets. This is a plausible preventive practice for a different BGP condition, specifically Local preference exit choice. Within an AS, higher BGP local preference is selected ahead of AS-path length when paths are otherwise eligible. In this scenario, however, the distinguishing issue is BGP ORIGIN attribute tie and the confirming observation is: The route with the preferred origin becomes best under otherwise equal higher-priority attributes.
C:Audit path-length and local preference before changing peering relationships. This is a plausible preventive practice for a different BGP condition, specifically AS-path length selection. After equal higher-priority selection attributes, BGP generally prefers the shorter AS path among eligible candidate paths. In this scenario, however, the distinguishing issue is BGP ORIGIN attribute tie and the confirming observation is: The route with the preferred origin becomes best under otherwise equal higher-priority attributes.
D:Maintain positive and negative example AS paths alongside policy expressions. This is a plausible preventive practice for a different BGP condition, specifically AS-path regex filter. BGP AS-path regex syntax and anchoring determine whether matching targets the origin AS, any traversed AS, or the entire sequence. In this scenario, however, the distinguishing issue is BGP ORIGIN attribute tie and the confirming observation is: The route with the preferred origin becomes best under otherwise equal higher-priority attributes.
Question 386
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: An IBGP route is hidden because its next hop recursively resolves through the same advertised prefix, creating a cyclic dependency. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Check earlier path attributes and verify each route's EBGP or IBGP origin.
- Trace recursive next-hop resolution and identify whether a route eventually reaches a connected usable transport.
- Count IBGP sessions and assess route reflector client and nonclient adjacency roles.
- Inspect client settings and the origin of the received route at the reflector.
Explanation
Correct Answer
B:Trace recursive next-hop resolution and identify whether a route eventually reaches a connected usable transport. This check examines the decisive condition for BGP next-hop recursive loop before any unrelated changes are made. The underlying mechanism is: A recursive next-hop chain must terminate at valid forwarding reachability, not loop back through the route being installed. The confirming observation is: The recursive resolution ends at a reachable interface and the BGP prefix can become active.
Incorrect Answers
A:Check earlier path attributes and verify each route's EBGP or IBGP origin. This is a plausible diagnostic check for a different BGP condition, specifically EBGP versus IBGP tie. For otherwise tied eligible BGP candidates, an EBGP-learned path is normally preferred over an IBGP-learned one at the relevant selection stage. In this scenario, however, the distinguishing issue is BGP next-hop recursive loop and the confirming observation is: The recursive resolution ends at a reachable interface and the BGP prefix can become active.
C:Count IBGP sessions and assess route reflector client and nonclient adjacency roles. This is a plausible diagnostic check for a different BGP condition, specifically BGP route reflector scaling. Route reflection reduces the need for every IBGP router to maintain direct sessions to every other IBGP router. In this scenario, however, the distinguishing issue is BGP next-hop recursive loop and the confirming observation is: The recursive resolution ends at a reachable interface and the BGP prefix can become active.
D:Inspect client settings and the origin of the received route at the reflector. This is a plausible diagnostic check for a different BGP condition, specifically Route-reflector client reflection rule. Route-reflection rules distinguish routes received from clients and nonclients; misclassified clients may prevent intended redistribution. In this scenario, however, the distinguishing issue is BGP next-hop recursive loop and the confirming observation is: The recursive resolution ends at a reachable interface and the BGP prefix can become active.
Question 387
During an edge-to-core validation, an HPE Juniper Networking engineer investigates this situation: An IBGP route is hidden because its next hop recursively resolves through the same advertised prefix, creating a cyclic dependency. Which routing or service mechanism best explains the reported behavior?
- Lower MED normally indicates the preferred entry for comparable routes from the same neighboring AS, after stronger attributes tie.
- For otherwise tied eligible BGP candidates, an EBGP-learned path is normally preferred over an IBGP-learned one at the relevant selection stage.
- A recursive next-hop chain must terminate at valid forwarding reachability, not loop back through the route being installed.
- Route reflection reduces the need for every IBGP router to maintain direct sessions to every other IBGP router.
Explanation
Correct Answer
C:A recursive next-hop chain must terminate at valid forwarding reachability, not loop back through the route being installed. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The recursive resolution ends at a reachable interface and the BGP prefix can become active. The targeted correction is: Repair the IGP or static next-hop route to provide nonrecursive transport connectivity.
Incorrect Answers
A:Lower MED normally indicates the preferred entry for comparable routes from the same neighboring AS, after stronger attributes tie. This is a plausible protocol explanation for a different BGP condition, specifically MED preference within neighbor AS. Lower MED normally indicates the preferred entry for comparable routes from the same neighboring AS, after stronger attributes tie. In this scenario, however, the distinguishing issue is BGP next-hop recursive loop and the confirming observation is: The recursive resolution ends at a reachable interface and the BGP prefix can become active.
B:For otherwise tied eligible BGP candidates, an EBGP-learned path is normally preferred over an IBGP-learned one at the relevant selection stage. This is a plausible protocol explanation for a different BGP condition, specifically EBGP versus IBGP tie. For otherwise tied eligible BGP candidates, an EBGP-learned path is normally preferred over an IBGP-learned one at the relevant selection stage. In this scenario, however, the distinguishing issue is BGP next-hop recursive loop and the confirming observation is: The recursive resolution ends at a reachable interface and the BGP prefix can become active.
D:Route reflection reduces the need for every IBGP router to maintain direct sessions to every other IBGP router. This is a plausible protocol explanation for a different BGP condition, specifically BGP route reflector scaling. Route reflection reduces the need for every IBGP router to maintain direct sessions to every other IBGP router. In this scenario, however, the distinguishing issue is BGP next-hop recursive loop and the confirming observation is: The recursive resolution ends at a reachable interface and the BGP prefix can become active.
Question 388
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: An IBGP route is hidden because its next hop recursively resolves through the same advertised prefix, creating a cyclic dependency. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The shortest eligible AS path becomes preferred once conflicting policy overrides are removed.
- The lower-MED eligible route is selected when upstream attributes and comparison scope permit it.
- The active path matches the external peer after earlier attribute mismatches are resolved.
- The recursive resolution ends at a reachable interface and the BGP prefix can become active.
Explanation
Correct Answer
D:The recursive resolution ends at a reachable interface and the BGP prefix can become active. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: A recursive next-hop chain must terminate at valid forwarding reachability, not loop back through the route being installed.
Incorrect Answers
A:The shortest eligible AS path becomes preferred once conflicting policy overrides are removed. This is a plausible observed evidence for a different BGP condition, specifically AS-path length selection. After equal higher-priority selection attributes, BGP generally prefers the shorter AS path among eligible candidate paths. In this scenario, however, the distinguishing issue is BGP next-hop recursive loop and the confirming observation is: The recursive resolution ends at a reachable interface and the BGP prefix can become active.
B:The lower-MED eligible route is selected when upstream attributes and comparison scope permit it. This is a plausible observed evidence for a different BGP condition, specifically MED preference within neighbor AS. Lower MED normally indicates the preferred entry for comparable routes from the same neighboring AS, after stronger attributes tie. In this scenario, however, the distinguishing issue is BGP next-hop recursive loop and the confirming observation is: The recursive resolution ends at a reachable interface and the BGP prefix can become active.
C:The active path matches the external peer after earlier attribute mismatches are resolved. This is a plausible observed evidence for a different BGP condition, specifically EBGP versus IBGP tie. For otherwise tied eligible BGP candidates, an EBGP-learned path is normally preferred over an IBGP-learned one at the relevant selection stage. In this scenario, however, the distinguishing issue is BGP next-hop recursive loop and the confirming observation is: The recursive resolution ends at a reachable interface and the BGP prefix can become active.
Question 389
During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: An IBGP route is hidden because its next hop recursively resolves through the same advertised prefix, creating a cyclic dependency. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Repair the IGP or static next-hop route to provide nonrecursive transport connectivity.
- Correct route-policy attributes or prepend design to implement the intended preference.
- Align MED policy and avoid assuming cross-AS MED comparison without explicit design.
- Remove unintended higher-priority policy effects before depending on EBGP versus IBGP tie-breaking.
Explanation
Correct Answer
A:Repair the IGP or static next-hop route to provide nonrecursive transport connectivity. The change addresses the root behavior described here: A recursive next-hop chain must terminate at valid forwarding reachability, not loop back through the route being installed. Verify success with: The recursive resolution ends at a reachable interface and the BGP prefix can become active.
Incorrect Answers
B:Correct route-policy attributes or prepend design to implement the intended preference. This is a plausible configuration or operational fix for a different BGP condition, specifically AS-path length selection. After equal higher-priority selection attributes, BGP generally prefers the shorter AS path among eligible candidate paths. In this scenario, however, the distinguishing issue is BGP next-hop recursive loop and the confirming observation is: The recursive resolution ends at a reachable interface and the BGP prefix can become active.
C:Align MED policy and avoid assuming cross-AS MED comparison without explicit design. This is a plausible configuration or operational fix for a different BGP condition, specifically MED preference within neighbor AS. Lower MED normally indicates the preferred entry for comparable routes from the same neighboring AS, after stronger attributes tie. In this scenario, however, the distinguishing issue is BGP next-hop recursive loop and the confirming observation is: The recursive resolution ends at a reachable interface and the BGP prefix can become active.
D:Remove unintended higher-priority policy effects before depending on EBGP versus IBGP tie-breaking. This is a plausible configuration or operational fix for a different BGP condition, specifically EBGP versus IBGP tie. For otherwise tied eligible BGP candidates, an EBGP-learned path is normally preferred over an IBGP-learned one at the relevant selection stage. In this scenario, however, the distinguishing issue is BGP next-hop recursive loop and the confirming observation is: The recursive resolution ends at a reachable interface and the BGP prefix can become active.
Question 390
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: An IBGP route is hidden because its next hop recursively resolves through the same advertised prefix, creating a cyclic dependency. Which operational control would best prevent a recurrence of this exact failure mode?
- Audit path-length and local preference before changing peering relationships.
- Test BGP next-hop resolution after aggregate and default route changes.
- Run deterministic best-path tests for equal-local-preference routes.
- Record the full ordered best-path decision chain in incident reviews.
Explanation
Correct Answer
B:Test BGP next-hop resolution after aggregate and default route changes. The control limits repetition of the described root condition: A recursive next-hop chain must terminate at valid forwarding reachability, not loop back through the route being installed. During audits, confirm: The recursive resolution ends at a reachable interface and the BGP prefix can become active.
Incorrect Answers
A:Audit path-length and local preference before changing peering relationships. This is a plausible preventive practice for a different BGP condition, specifically AS-path length selection. After equal higher-priority selection attributes, BGP generally prefers the shorter AS path among eligible candidate paths. In this scenario, however, the distinguishing issue is BGP next-hop recursive loop and the confirming observation is: The recursive resolution ends at a reachable interface and the BGP prefix can become active.
C:Run deterministic best-path tests for equal-local-preference routes. This is a plausible preventive practice for a different BGP condition, specifically MED preference within neighbor AS. Lower MED normally indicates the preferred entry for comparable routes from the same neighboring AS, after stronger attributes tie. In this scenario, however, the distinguishing issue is BGP next-hop recursive loop and the confirming observation is: The recursive resolution ends at a reachable interface and the BGP prefix can become active.
D:Record the full ordered best-path decision chain in incident reviews. This is a plausible preventive practice for a different BGP condition, specifically EBGP versus IBGP tie. For otherwise tied eligible BGP candidates, an EBGP-learned path is normally preferred over an IBGP-learned one at the relevant selection stage. In this scenario, however, the distinguishing issue is BGP next-hop recursive loop and the confirming observation is: The recursive resolution ends at a reachable interface and the BGP prefix can become active.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests