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.
Question 391
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: A route reflector successfully reflects a service prefix but clients in a remote POP cannot forward because the reflected next hop remains unreachable. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare RR best-path IGP cost calculations with actual client-to-exit metrics.
- Inspect negotiated graceful-restart capability, restart timers and stale route handling.
- Compare the reflected BGP next-hop attribute with clients' IGP routes to the originating PE.
- Correlate UPDATE withdrawals, received prefix history and export-policy or originating route changes.
Explanation
Correct Answer
C:Compare the reflected BGP next-hop attribute with clients' IGP routes to the originating PE. This check examines the decisive condition for RR client next-hop preservation before any unrelated changes are made. The underlying mechanism is: Route reflection usually preserves the original BGP next hop; RR adjacency alone does not carry the required forwarding transport. The confirming observation is: Clients resolve the original PE next hop and install the reflected service route.
Incorrect Answers
A:Compare RR best-path IGP cost calculations with actual client-to-exit metrics. This is a plausible diagnostic check 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 RR client next-hop preservation and the confirming observation is: Clients resolve the original PE next hop and install the reflected service route.
B:Inspect negotiated graceful-restart capability, restart timers and stale route handling. This is a plausible diagnostic check for a different BGP condition, specifically BGP graceful restart stale routes. Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails. In this scenario, however, the distinguishing issue is RR client next-hop preservation and the confirming observation is: Clients resolve the original PE next hop and install the reflected service route.
D:Correlate UPDATE withdrawals, received prefix history and export-policy or originating route changes. This is a plausible diagnostic check for a different BGP condition, specifically BGP route flap versus underlay fault. BGP prefix churn can occur from an originator or policy without a TCP session flap, so transport-only troubleshooting is insufficient. In this scenario, however, the distinguishing issue is RR client next-hop preservation and the confirming observation is: Clients resolve the original PE next hop and install the reflected service route.
Question 392
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: A route reflector successfully reflects a service prefix but clients in a remote POP cannot forward because the reflected next hop remains unreachable. Which routing or service mechanism best explains the reported behavior?
- A standard reflector chooses its best path from its own topology perspective, which can differ from widely distributed clients.
- Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails.
- BGP prefix churn can occur from an originator or policy without a TCP session flap, so transport-only troubleshooting is insufficient.
- Route reflection usually preserves the original BGP next hop; RR adjacency alone does not carry the required forwarding transport.
Explanation
Correct Answer
D:Route reflection usually preserves the original BGP next hop; RR adjacency alone does not carry the required forwarding transport. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Clients resolve the original PE next hop and install the reflected service route. The targeted correction is: Restore underlay reachability or apply a justified next-hop policy at the appropriate edge.
Incorrect Answers
A:A standard reflector chooses its best path from its own topology perspective, which can differ from widely distributed clients. This is a plausible protocol explanation 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 RR client next-hop preservation and the confirming observation is: Clients resolve the original PE next hop and install the reflected service route.
B:Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails. This is a plausible protocol explanation for a different BGP condition, specifically BGP graceful restart stale routes. Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails. In this scenario, however, the distinguishing issue is RR client next-hop preservation and the confirming observation is: Clients resolve the original PE next hop and install the reflected service route.
C:BGP prefix churn can occur from an originator or policy without a TCP session flap, so transport-only troubleshooting is insufficient. This is a plausible protocol explanation for a different BGP condition, specifically BGP route flap versus underlay fault. BGP prefix churn can occur from an originator or policy without a TCP session flap, so transport-only troubleshooting is insufficient. In this scenario, however, the distinguishing issue is RR client next-hop preservation and the confirming observation is: Clients resolve the original PE next hop and install the reflected service route.
Question 393
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: A route reflector successfully reflects a service prefix but clients in a remote POP cannot forward because the reflected next hop remains unreachable. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Clients resolve the original PE next hop and install the reflected service route.
- Client route selection reflects an intended per-POP or supported optimal-reflection policy.
- The restart completes within negotiated timers or stale routes are safely withdrawn.
- Withdrawal timestamps correlate with the actual source route or policy event rather than BGP neighbor resets.
Explanation
Correct Answer
A:Clients resolve the original PE next hop and install the reflected service route. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Route reflection usually preserves the original BGP next hop; RR adjacency alone does not carry the required forwarding transport.
Incorrect Answers
B:Client route selection reflects an intended per-POP or supported optimal-reflection policy. This is a plausible observed evidence 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 RR client next-hop preservation and the confirming observation is: Clients resolve the original PE next hop and install the reflected service route.
C:The restart completes within negotiated timers or stale routes are safely withdrawn. This is a plausible observed evidence for a different BGP condition, specifically BGP graceful restart stale routes. Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails. In this scenario, however, the distinguishing issue is RR client next-hop preservation and the confirming observation is: Clients resolve the original PE next hop and install the reflected service route.
D:Withdrawal timestamps correlate with the actual source route or policy event rather than BGP neighbor resets. This is a plausible observed evidence for a different BGP condition, specifically BGP route flap versus underlay fault. BGP prefix churn can occur from an originator or policy without a TCP session flap, so transport-only troubleshooting is insufficient. In this scenario, however, the distinguishing issue is RR client next-hop preservation and the confirming observation is: Clients resolve the original PE next hop and install the reflected service route.
Question 394
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: A route reflector successfully reflects a service prefix but clients in a remote POP cannot forward because the reflected next hop remains unreachable. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Use suitable reflector placement or a supported optimal route reflection approach if topology diversity requires it.
- Restore underlay reachability or apply a justified next-hop policy at the appropriate edge.
- Fix the originating route instability or policy condition creating the repeated announcements.
- Align graceful restart roles and timer expectations with real forwarding continuity capability.
Explanation
Correct Answer
B:Restore underlay reachability or apply a justified next-hop policy at the appropriate edge. The change addresses the root behavior described here: Route reflection usually preserves the original BGP next hop; RR adjacency alone does not carry the required forwarding transport. Verify success with: Clients resolve the original PE next hop and install the reflected service route.
Incorrect Answers
A:Use suitable reflector placement or a supported optimal route reflection approach if topology diversity requires it. This is a plausible configuration or operational fix 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 RR client next-hop preservation and the confirming observation is: Clients resolve the original PE next hop and install the reflected service route.
C:Fix the originating route instability or policy condition creating the repeated announcements. This is a plausible configuration or operational fix for a different BGP condition, specifically BGP route flap versus underlay fault. BGP prefix churn can occur from an originator or policy without a TCP session flap, so transport-only troubleshooting is insufficient. In this scenario, however, the distinguishing issue is RR client next-hop preservation and the confirming observation is: Clients resolve the original PE next hop and install the reflected service route.
D:Align graceful restart roles and timer expectations with real forwarding continuity capability. This is a plausible configuration or operational fix for a different BGP condition, specifically BGP graceful restart stale routes. Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails. In this scenario, however, the distinguishing issue is RR client next-hop preservation and the confirming observation is: Clients resolve the original PE next hop and install the reflected service route.
Question 395
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: A route reflector successfully reflects a service prefix but clients in a remote POP cannot forward because the reflected next hop remains unreachable. Which operational control would best prevent a recurrence of this exact failure mode?
- Test representative distant-client best exits when expanding reflector geography.
- Test abrupt failure separately from graceful restart to expose stale-route risks.
- Audit next-hop reachability from clients served by geographically remote reflectors.
- Monitor per-prefix churn independently of session uptime.
Explanation
Correct Answer
C:Audit next-hop reachability from clients served by geographically remote reflectors. The control limits repetition of the described root condition: Route reflection usually preserves the original BGP next hop; RR adjacency alone does not carry the required forwarding transport. During audits, confirm: Clients resolve the original PE next hop and install the reflected service route.
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 RR client next-hop preservation and the confirming observation is: Clients resolve the original PE next hop and install the reflected service route.
B:Test abrupt failure separately from graceful restart to expose stale-route risks. This is a plausible preventive practice for a different BGP condition, specifically BGP graceful restart stale routes. Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails. In this scenario, however, the distinguishing issue is RR client next-hop preservation and the confirming observation is: Clients resolve the original PE next hop and install the reflected service route.
D:Monitor per-prefix churn independently of session uptime. This is a plausible preventive practice for a different BGP condition, specifically BGP route flap versus underlay fault. BGP prefix churn can occur from an originator or policy without a TCP session flap, so transport-only troubleshooting is insufficient. In this scenario, however, the distinguishing issue is RR client next-hop preservation and the confirming observation is: Clients resolve the original PE next hop and install the reflected service route.
Question 396
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: Clients in a distant POP follow the RR's chosen distant exit even though their local IGP metrics favor a different egress. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare the reflected BGP next-hop attribute with clients' IGP routes to the originating PE.
- Inspect aggregate route generation conditions and the set of eligible active contributors.
- Inspect negotiated graceful-restart capability, restart timers and stale route handling.
- Compare RR best-path IGP cost calculations with actual client-to-exit metrics.
Explanation
Correct Answer
D:Compare RR best-path IGP cost calculations with actual client-to-exit metrics. This check examines the decisive condition for Route-reflector optimal exit perspective before any unrelated changes are made. The underlying mechanism is: A standard reflector chooses its best path from its own topology perspective, which can differ from widely distributed clients. The confirming observation is: Client route selection reflects an intended per-POP or supported optimal-reflection policy.
Incorrect Answers
A:Compare the reflected BGP next-hop attribute with clients' IGP routes to the originating PE. This is a plausible diagnostic check 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 Route-reflector optimal exit perspective and the confirming observation is: Client route selection reflects an intended per-POP or supported optimal-reflection policy.
B:Inspect aggregate route generation conditions and the set of eligible active contributors. This is a plausible diagnostic check for a different BGP condition, specifically BGP aggregation hides contributors. Route aggregation can trade detailed reachability for a broad advertisement, so contributor rules and discard behavior govern correctness. In this scenario, however, the distinguishing issue is Route-reflector optimal exit perspective and the confirming observation is: Client route selection reflects an intended per-POP or supported optimal-reflection policy.
C:Inspect negotiated graceful-restart capability, restart timers and stale route handling. This is a plausible diagnostic check for a different BGP condition, specifically BGP graceful restart stale routes. Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails. In this scenario, however, the distinguishing issue is Route-reflector optimal exit perspective and the confirming observation is: Client route selection reflects an intended per-POP or supported optimal-reflection policy.
Question 397
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: Clients in a distant POP follow the RR's chosen distant exit even though their local IGP metrics favor a different egress. Which routing or service mechanism best explains the reported behavior?
- A standard reflector chooses its best path from its own topology perspective, which can differ from widely distributed clients.
- Route reflection usually preserves the original BGP next hop; RR adjacency alone does not carry the required forwarding transport.
- Route aggregation can trade detailed reachability for a broad advertisement, so contributor rules and discard behavior govern correctness.
- Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails.
Explanation
Correct Answer
A:A standard reflector chooses its best path from its own topology perspective, which can differ from widely distributed clients. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Client route selection reflects an intended per-POP or supported optimal-reflection policy. The targeted correction is: Use suitable reflector placement or a supported optimal route reflection approach if topology diversity requires it.
Incorrect Answers
B:Route reflection usually preserves the original BGP next hop; RR adjacency alone does not carry the required forwarding transport. This is a plausible protocol explanation 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 Route-reflector optimal exit perspective and the confirming observation is: Client route selection reflects an intended per-POP or supported optimal-reflection policy.
C:Route aggregation can trade detailed reachability for a broad advertisement, so contributor rules and discard behavior govern correctness. This is a plausible protocol explanation for a different BGP condition, specifically BGP aggregation hides contributors. Route aggregation can trade detailed reachability for a broad advertisement, so contributor rules and discard behavior govern correctness. In this scenario, however, the distinguishing issue is Route-reflector optimal exit perspective and the confirming observation is: Client route selection reflects an intended per-POP or supported optimal-reflection policy.
D:Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails. This is a plausible protocol explanation for a different BGP condition, specifically BGP graceful restart stale routes. Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails. In this scenario, however, the distinguishing issue is Route-reflector optimal exit perspective and the confirming observation is: Client route selection reflects an intended per-POP or supported optimal-reflection policy.
Question 398
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: Clients in a distant POP follow the RR's chosen distant exit even though their local IGP metrics favor a different egress. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The restart completes within negotiated timers or stale routes are safely withdrawn.
- Client route selection reflects an intended per-POP or supported optimal-reflection policy.
- Clients resolve the original PE next hop and install the reflected service route.
- The aggregate exists only under documented reachable-contributor conditions and traffic has valid forwarding paths.
Explanation
Correct Answer
B:Client route selection reflects an intended per-POP or supported optimal-reflection policy. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: A standard reflector chooses its best path from its own topology perspective, which can differ from widely distributed clients.
Incorrect Answers
A:The restart completes within negotiated timers or stale routes are safely withdrawn. This is a plausible observed evidence for a different BGP condition, specifically BGP graceful restart stale routes. Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails. In this scenario, however, the distinguishing issue is Route-reflector optimal exit perspective and the confirming observation is: Client route selection reflects an intended per-POP or supported optimal-reflection policy.
C:Clients resolve the original PE next hop and install the reflected service route. This is a plausible observed evidence 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 Route-reflector optimal exit perspective and the confirming observation is: Client route selection reflects an intended per-POP or supported optimal-reflection policy.
D:The aggregate exists only under documented reachable-contributor conditions and traffic has valid forwarding paths. This is a plausible observed evidence for a different BGP condition, specifically BGP aggregation hides contributors. Route aggregation can trade detailed reachability for a broad advertisement, so contributor rules and discard behavior govern correctness. In this scenario, however, the distinguishing issue is Route-reflector optimal exit perspective and the confirming observation is: Client route selection reflects an intended per-POP or supported optimal-reflection policy.
Question 399
During an edge-to-core validation, an HPE Juniper Networking engineer investigates this situation: Clients in a distant POP follow the RR's chosen distant exit even though their local IGP metrics favor a different egress. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Align graceful restart roles and timer expectations with real forwarding continuity capability.
- Restore underlay reachability or apply a justified next-hop policy at the appropriate edge.
- Use suitable reflector placement or a supported optimal route reflection approach if topology diversity requires it.
- Adjust aggregate generation and forwarding/discard controls to match actual service coverage.
Explanation
Correct Answer
C:Use suitable reflector placement or a supported optimal route reflection approach if topology diversity requires it. The change addresses the root behavior described here: A standard reflector chooses its best path from its own topology perspective, which can differ from widely distributed clients. Verify success with: Client route selection reflects an intended per-POP or supported optimal-reflection policy.
Incorrect Answers
A:Align graceful restart roles and timer expectations with real forwarding continuity capability. This is a plausible configuration or operational fix for a different BGP condition, specifically BGP graceful restart stale routes. Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails. In this scenario, however, the distinguishing issue is Route-reflector optimal exit perspective and the confirming observation is: Client route selection reflects an intended per-POP or supported optimal-reflection policy.
B:Restore underlay reachability or apply a justified next-hop policy at the appropriate edge. This is a plausible configuration or operational fix 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 Route-reflector optimal exit perspective and the confirming observation is: Client route selection reflects an intended per-POP or supported optimal-reflection policy.
D:Adjust aggregate generation and forwarding/discard controls to match actual service coverage. This is a plausible configuration or operational fix for a different BGP condition, specifically BGP aggregation hides contributors. Route aggregation can trade detailed reachability for a broad advertisement, so contributor rules and discard behavior govern correctness. In this scenario, however, the distinguishing issue is Route-reflector optimal exit perspective and the confirming observation is: Client route selection reflects an intended per-POP or supported optimal-reflection policy.
Question 400
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: Clients in a distant POP follow the RR's chosen distant exit even though their local IGP metrics favor a different egress. Which operational control would best prevent a recurrence of this exact failure mode?
- Test abrupt failure separately from graceful restart to expose stale-route risks.
- Audit next-hop reachability from clients served by geographically remote reflectors.
- Test loss of the final contributor and partial site outage before advertising aggregates.
- Test representative distant-client best exits when expanding reflector geography.
Explanation
Correct Answer
D:Test representative distant-client best exits when expanding reflector geography. The control limits repetition of the described root condition: A standard reflector chooses its best path from its own topology perspective, which can differ from widely distributed clients. During audits, confirm: Client route selection reflects an intended per-POP or supported optimal-reflection policy.
Incorrect Answers
A:Test abrupt failure separately from graceful restart to expose stale-route risks. This is a plausible preventive practice for a different BGP condition, specifically BGP graceful restart stale routes. Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails. In this scenario, however, the distinguishing issue is Route-reflector optimal exit perspective and the confirming observation is: Client route selection reflects an intended per-POP or supported optimal-reflection policy.
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 Route-reflector optimal exit perspective and the confirming observation is: Client route selection reflects an intended per-POP or supported optimal-reflection policy.
C:Test loss of the final contributor and partial site outage before advertising aggregates. This is a plausible preventive practice for a different BGP condition, specifically BGP aggregation hides contributors. Route aggregation can trade detailed reachability for a broad advertisement, so contributor rules and discard behavior govern correctness. In this scenario, however, the distinguishing issue is Route-reflector optimal exit perspective and the confirming observation is: Client route selection reflects an intended per-POP or supported optimal-reflection policy.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests