Question 310
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: Routes are repeatedly rejected after adding a second reflector because both reflectors use an inconsistent cluster design. 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.
- Review CLUSTER_LIST paths when commissioning redundant reflection topologies.
- Monitor per-prefix churn independently of session uptime.
- Verify the path in each direction and control-plane filtering before enabling multihop EBGP.
Explanation
Correct Answer
B:Review CLUSTER_LIST paths when commissioning redundant reflection topologies. The control limits repetition of the described root condition: The cluster list is a route-reflection loop-prevention mechanism, so repeated cluster IDs or unexpected reflection paths can suppress routes. During audits, confirm: Reflected routes have consistent cluster metadata and no unintended loop-prevention drops.
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 cluster loop and the confirming observation is: Reflected routes have consistent cluster metadata and no unintended loop-prevention drops.
C: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 Route-reflector cluster loop and the confirming observation is: Reflected routes have consistent cluster metadata and no unintended loop-prevention drops.
D:Verify the path in each direction and control-plane filtering before enabling multihop EBGP. This is a plausible preventive practice for a different BGP condition, specifically EBGP multihop loopback peering. Multihop EBGP through loopback addresses requires proper transport reachability and a hop limit that permits the path. In this scenario, however, the distinguishing issue is Route-reflector cluster loop and the confirming observation is: Reflected routes have consistent cluster metadata and no unintended loop-prevention drops.
Question 311
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: A customer prefix that flapped frequently remains suppressed long after the physical circuit recovers. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare protocol preference values separately from BGP path attributes and verify eligible routes.
- Correlate UPDATE withdrawals, received prefix history and export-policy or originating route changes.
- Inspect damping penalty, suppress and reuse thresholds for the affected route.
- Check loopback reachability, peer source address, hop limit and matching peer AS on both sides.
Explanation
Correct Answer
C:Inspect damping penalty, suppress and reuse thresholds for the affected route. This check examines the decisive condition for BGP route damping instability before any unrelated changes are made. The underlying mechanism is: BGP damping can suppress repeatedly unstable routes until a decaying penalty drops below a reuse threshold. The confirming observation is: The route becomes eligible after the damping state clears and remains stable across observation intervals.
Incorrect Answers
A:Compare protocol preference values separately from BGP path attributes and verify eligible routes. This is a plausible diagnostic check for a different BGP condition, specifically Route preference versus BGP local-pref. Junos chooses among protocols using route preference before BGP's local preference decides among BGP candidates. In this scenario, however, the distinguishing issue is BGP route damping instability and the confirming observation is: The route becomes eligible after the damping state clears and remains stable across observation intervals.
B: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 BGP route damping instability and the confirming observation is: The route becomes eligible after the damping state clears and remains stable across observation intervals.
D:Check loopback reachability, peer source address, hop limit and matching peer AS on both sides. This is a plausible diagnostic check for a different BGP condition, specifically EBGP multihop loopback peering. Multihop EBGP through loopback addresses requires proper transport reachability and a hop limit that permits the path. In this scenario, however, the distinguishing issue is BGP route damping instability and the confirming observation is: The route becomes eligible after the damping state clears and remains stable across observation intervals.
Question 312
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: A customer prefix that flapped frequently remains suppressed long after the physical circuit recovers. Which routing or service mechanism best explains the reported behavior?
- Junos chooses among protocols using route preference before BGP's local preference decides among BGP candidates.
- BGP prefix churn can occur from an originator or policy without a TCP session flap, so transport-only troubleshooting is insufficient.
- Multihop EBGP through loopback addresses requires proper transport reachability and a hop limit that permits the path.
- BGP damping can suppress repeatedly unstable routes until a decaying penalty drops below a reuse threshold.
Explanation
Correct Answer
D:BGP damping can suppress repeatedly unstable routes until a decaying penalty drops below a reuse threshold. 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 becomes eligible after the damping state clears and remains stable across observation intervals. The targeted correction is: Fix the underlying flapping source and tune or disable damping only with documented policy justification.
Incorrect Answers
A:Junos chooses among protocols using route preference before BGP's local preference decides among BGP candidates. This is a plausible protocol explanation for a different BGP condition, specifically Route preference versus BGP local-pref. Junos chooses among protocols using route preference before BGP's local preference decides among BGP candidates. In this scenario, however, the distinguishing issue is BGP route damping instability and the confirming observation is: The route becomes eligible after the damping state clears and remains stable across observation intervals.
B: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 BGP route damping instability and the confirming observation is: The route becomes eligible after the damping state clears and remains stable across observation intervals.
C:Multihop EBGP through loopback addresses requires proper transport reachability and a hop limit that permits the path. This is a plausible protocol explanation for a different BGP condition, specifically EBGP multihop loopback peering. Multihop EBGP through loopback addresses requires proper transport reachability and a hop limit that permits the path. In this scenario, however, the distinguishing issue is BGP route damping instability and the confirming observation is: The route becomes eligible after the damping state clears and remains stable across observation intervals.
Question 313
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: A customer prefix that flapped frequently remains suppressed long after the physical circuit recovers. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The route becomes eligible after the damping state clears and remains stable across observation intervals.
- The installed path matches the lower global preference unless that policy is intentionally changed.
- Withdrawal timestamps correlate with the actual source route or policy event rather than BGP neighbor resets.
- TCP port 179 connects from the intended source addresses and the BGP state reaches Established.
Explanation
Correct Answer
A:The route becomes eligible after the damping state clears and remains stable across observation intervals. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: BGP damping can suppress repeatedly unstable routes until a decaying penalty drops below a reuse threshold.
Incorrect Answers
B:The installed path matches the lower global preference unless that policy is intentionally changed. This is a plausible observed evidence for a different BGP condition, specifically Route preference versus BGP local-pref. Junos chooses among protocols using route preference before BGP's local preference decides among BGP candidates. In this scenario, however, the distinguishing issue is BGP route damping instability and the confirming observation is: The route becomes eligible after the damping state clears and remains stable across observation intervals.
C: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 BGP route damping instability and the confirming observation is: The route becomes eligible after the damping state clears and remains stable across observation intervals.
D:TCP port 179 connects from the intended source addresses and the BGP state reaches Established. This is a plausible observed evidence for a different BGP condition, specifically EBGP multihop loopback peering. Multihop EBGP through loopback addresses requires proper transport reachability and a hop limit that permits the path. In this scenario, however, the distinguishing issue is BGP route damping instability and the confirming observation is: The route becomes eligible after the damping state clears and remains stable across observation intervals.
Question 314
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: A customer prefix that flapped frequently remains suppressed long after the physical circuit recovers. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Change a documented route preference or routing-policy design if protocol precedence must differ.
- Fix the underlying flapping source and tune or disable damping only with documented policy justification.
- Fix the originating route instability or policy condition creating the repeated announcements.
- Configure justified multihop and local-address settings with transport routing to the loopbacks.
Explanation
Correct Answer
B:Fix the underlying flapping source and tune or disable damping only with documented policy justification. The change addresses the root behavior described here: BGP damping can suppress repeatedly unstable routes until a decaying penalty drops below a reuse threshold. Verify success with: The route becomes eligible after the damping state clears and remains stable across observation intervals.
Incorrect Answers
A:Change a documented route preference or routing-policy design if protocol precedence must differ. This is a plausible configuration or operational fix for a different BGP condition, specifically Route preference versus BGP local-pref. Junos chooses among protocols using route preference before BGP's local preference decides among BGP candidates. In this scenario, however, the distinguishing issue is BGP route damping instability and the confirming observation is: The route becomes eligible after the damping state clears and remains stable across observation intervals.
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 BGP route damping instability and the confirming observation is: The route becomes eligible after the damping state clears and remains stable across observation intervals.
D:Configure justified multihop and local-address settings with transport routing to the loopbacks. This is a plausible configuration or operational fix for a different BGP condition, specifically EBGP multihop loopback peering. Multihop EBGP through loopback addresses requires proper transport reachability and a hop limit that permits the path. In this scenario, however, the distinguishing issue is BGP route damping instability and the confirming observation is: The route becomes eligible after the damping state clears and remains stable across observation intervals.
Question 315
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: A customer prefix that flapped frequently remains suppressed long after the physical circuit recovers. Which operational control would best prevent a recurrence of this exact failure mode?
- Audit next-hop reachability from clients served by geographically remote reflectors.
- Check interaction between RIB preference and BGP local preference in mixed-protocol reviews.
- Track suppressed-prefix counts and avoid broad damping policies that hurt convergence.
- Monitor per-prefix churn independently of session uptime.
Explanation
Correct Answer
C:Track suppressed-prefix counts and avoid broad damping policies that hurt convergence. The control limits repetition of the described root condition: BGP damping can suppress repeatedly unstable routes until a decaying penalty drops below a reuse threshold. During audits, confirm: The route becomes eligible after the damping state clears and remains stable across observation intervals.
Incorrect Answers
A: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 route damping instability and the confirming observation is: The route becomes eligible after the damping state clears and remains stable across observation intervals.
B:Check interaction between RIB preference and BGP local preference in mixed-protocol reviews. This is a plausible preventive practice for a different BGP condition, specifically Route preference versus BGP local-pref. Junos chooses among protocols using route preference before BGP's local preference decides among BGP candidates. In this scenario, however, the distinguishing issue is BGP route damping instability and the confirming observation is: The route becomes eligible after the damping state clears and remains stable across observation intervals.
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 BGP route damping instability and the confirming observation is: The route becomes eligible after the damping state clears and remains stable across observation intervals.
Question 316
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: Two EBGP paths appear in the BGP table but only one forwarding next hop is installed despite a plan to load-share traffic. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect outbound next-hop attributes at the AS border and the internal client's resolver routes.
- Inspect effective egress prefix filters and advertised-route counts for the customer BGP group.
- Inspect the BGP route next-hop value and its recursive resolution in the active IGP or label transport.
- Compare multipath configuration and the eligibility attributes required for both candidate paths.
Explanation
Correct Answer
D:Compare multipath configuration and the eligibility attributes required for both candidate paths. This check examines the decisive condition for BGP multipath prerequisites before any unrelated changes are made. The underlying mechanism is: BGP multipath requires compatible candidate paths and implementation-specific settings in addition to multiple route advertisements. The confirming observation is: The forwarding entry contains both eligible next hops with operationally verified reachability.
Incorrect Answers
A:Inspect outbound next-hop attributes at the AS border and the internal client's resolver routes. This is a plausible diagnostic check for a different BGP condition, specifically BGP next-hop-self at border. Passing external reachability into IBGP without a reachable next hop can leave the route unusable for internal clients. In this scenario, however, the distinguishing issue is BGP multipath prerequisites and the confirming observation is: The forwarding entry contains both eligible next hops with operationally verified reachability.
B:Inspect effective egress prefix filters and advertised-route counts for the customer BGP group. This is a plausible diagnostic check for a different BGP condition, specifically BGP outbound default-only policy. BGP export policy determines whether a neighbor receives a default route or unrestricted more-specific NLRI. In this scenario, however, the distinguishing issue is BGP multipath prerequisites and the confirming observation is: The forwarding entry contains both eligible next hops with operationally verified reachability.
C:Inspect the BGP route next-hop value and its recursive resolution in the active IGP or label transport. This is a plausible diagnostic check for a different BGP condition, specifically IBGP next-hop unresolvable. BGP path eligibility depends on being able to resolve the advertised next hop; a healthy TCP peering alone does not install the route. In this scenario, however, the distinguishing issue is BGP multipath prerequisites and the confirming observation is: The forwarding entry contains both eligible next hops with operationally verified reachability.
Question 317
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: Two EBGP paths appear in the BGP table but only one forwarding next hop is installed despite a plan to load-share traffic. Which routing or service mechanism best explains the reported behavior?
- BGP multipath requires compatible candidate paths and implementation-specific settings in addition to multiple route advertisements.
- Passing external reachability into IBGP without a reachable next hop can leave the route unusable for internal clients.
- BGP export policy determines whether a neighbor receives a default route or unrestricted more-specific NLRI.
- BGP path eligibility depends on being able to resolve the advertised next hop; a healthy TCP peering alone does not install the route.
Explanation
Correct Answer
A:BGP multipath requires compatible candidate paths and implementation-specific settings in addition to multiple route advertisements. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The forwarding entry contains both eligible next hops with operationally verified reachability. The targeted correction is: Enable supported BGP multipath under explicit attribute constraints instead of forcing unequal paths.
Incorrect Answers
B:Passing external reachability into IBGP without a reachable next hop can leave the route unusable for internal clients. This is a plausible protocol explanation for a different BGP condition, specifically BGP next-hop-self at border. Passing external reachability into IBGP without a reachable next hop can leave the route unusable for internal clients. In this scenario, however, the distinguishing issue is BGP multipath prerequisites and the confirming observation is: The forwarding entry contains both eligible next hops with operationally verified reachability.
C:BGP export policy determines whether a neighbor receives a default route or unrestricted more-specific NLRI. This is a plausible protocol explanation for a different BGP condition, specifically BGP outbound default-only policy. BGP export policy determines whether a neighbor receives a default route or unrestricted more-specific NLRI. In this scenario, however, the distinguishing issue is BGP multipath prerequisites and the confirming observation is: The forwarding entry contains both eligible next hops with operationally verified reachability.
D:BGP path eligibility depends on being able to resolve the advertised next hop; a healthy TCP peering alone does not install the route. This is a plausible protocol explanation for a different BGP condition, specifically IBGP next-hop unresolvable. BGP path eligibility depends on being able to resolve the advertised next hop; a healthy TCP peering alone does not install the route. In this scenario, however, the distinguishing issue is BGP multipath prerequisites and the confirming observation is: The forwarding entry contains both eligible next hops with operationally verified reachability.
Question 318
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: Two EBGP paths appear in the BGP table but only one forwarding next hop is installed despite a plan to load-share traffic. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Client route entries show a reachable border-router next hop and become active.
- The forwarding entry contains both eligible next hops with operationally verified reachability.
- The neighbor receives the intended default and no unauthorized full-table routes.
- The route changes from hidden or unusable to active when a valid next-hop resolution path is available.
Explanation
Correct Answer
B:The forwarding entry contains both eligible next hops with operationally verified reachability. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: BGP multipath requires compatible candidate paths and implementation-specific settings in addition to multiple route advertisements.
Incorrect Answers
A:Client route entries show a reachable border-router next hop and become active. This is a plausible observed evidence for a different BGP condition, specifically BGP next-hop-self at border. Passing external reachability into IBGP without a reachable next hop can leave the route unusable for internal clients. In this scenario, however, the distinguishing issue is BGP multipath prerequisites and the confirming observation is: The forwarding entry contains both eligible next hops with operationally verified reachability.
C:The neighbor receives the intended default and no unauthorized full-table routes. This is a plausible observed evidence for a different BGP condition, specifically BGP outbound default-only policy. BGP export policy determines whether a neighbor receives a default route or unrestricted more-specific NLRI. In this scenario, however, the distinguishing issue is BGP multipath prerequisites and the confirming observation is: The forwarding entry contains both eligible next hops with operationally verified reachability.
D:The route changes from hidden or unusable to active when a valid next-hop resolution path is available. This is a plausible observed evidence for a different BGP condition, specifically IBGP next-hop unresolvable. BGP path eligibility depends on being able to resolve the advertised next hop; a healthy TCP peering alone does not install the route. In this scenario, however, the distinguishing issue is BGP multipath prerequisites and the confirming observation is: The forwarding entry contains both eligible next hops with operationally verified reachability.
Question 319
During an edge-to-core validation, an HPE Juniper Networking engineer investigates this situation: Two EBGP paths appear in the BGP table but only one forwarding next hop is installed despite a plan to load-share traffic. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Apply an appropriate next-hop-self or next-hop policy on the border device while retaining forwarding consistency.
- Apply a specific default-only export policy at the customer boundary.
- Enable supported BGP multipath under explicit attribute constraints instead of forcing unequal paths.
- Restore IGP or transport reachability to the advertised BGP next hop and retain appropriate next-hop policy.
Explanation
Correct Answer
C:Enable supported BGP multipath under explicit attribute constraints instead of forcing unequal paths. The change addresses the root behavior described here: BGP multipath requires compatible candidate paths and implementation-specific settings in addition to multiple route advertisements. Verify success with: The forwarding entry contains both eligible next hops with operationally verified reachability.
Incorrect Answers
A:Apply an appropriate next-hop-self or next-hop policy on the border device while retaining forwarding consistency. This is a plausible configuration or operational fix for a different BGP condition, specifically BGP next-hop-self at border. Passing external reachability into IBGP without a reachable next hop can leave the route unusable for internal clients. In this scenario, however, the distinguishing issue is BGP multipath prerequisites and the confirming observation is: The forwarding entry contains both eligible next hops with operationally verified reachability.
B:Apply a specific default-only export policy at the customer boundary. This is a plausible configuration or operational fix for a different BGP condition, specifically BGP outbound default-only policy. BGP export policy determines whether a neighbor receives a default route or unrestricted more-specific NLRI. In this scenario, however, the distinguishing issue is BGP multipath prerequisites and the confirming observation is: The forwarding entry contains both eligible next hops with operationally verified reachability.
D:Restore IGP or transport reachability to the advertised BGP next hop and retain appropriate next-hop policy. This is a plausible configuration or operational fix for a different BGP condition, specifically IBGP next-hop unresolvable. BGP path eligibility depends on being able to resolve the advertised next hop; a healthy TCP peering alone does not install the route. In this scenario, however, the distinguishing issue is BGP multipath prerequisites and the confirming observation is: The forwarding entry contains both eligible next hops with operationally verified reachability.
Question 320
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: Two EBGP paths appear in the BGP table but only one forwarding next hop is installed despite a plan to load-share traffic. Which operational control would best prevent a recurrence of this exact failure mode?
- Monitor hidden BGP routes and next-hop resolution after core topology changes.
- Check recursive next-hop reachability from representative internal routers when adding EBGP peers.
- Continuously check advertised prefix counts against each customer's contracted service.
- Review next-hop and attribute comparability before adding paths to ECMP service.
Explanation
Correct Answer
D:Review next-hop and attribute comparability before adding paths to ECMP service. The control limits repetition of the described root condition: BGP multipath requires compatible candidate paths and implementation-specific settings in addition to multiple route advertisements. During audits, confirm: The forwarding entry contains both eligible next hops with operationally verified reachability.
Incorrect Answers
A:Monitor hidden BGP routes and next-hop resolution after core topology changes. This is a plausible preventive practice for a different BGP condition, specifically IBGP next-hop unresolvable. BGP path eligibility depends on being able to resolve the advertised next hop; a healthy TCP peering alone does not install the route. In this scenario, however, the distinguishing issue is BGP multipath prerequisites and the confirming observation is: The forwarding entry contains both eligible next hops with operationally verified reachability.
B:Check recursive next-hop reachability from representative internal routers when adding EBGP peers. This is a plausible preventive practice for a different BGP condition, specifically BGP next-hop-self at border. Passing external reachability into IBGP without a reachable next hop can leave the route unusable for internal clients. In this scenario, however, the distinguishing issue is BGP multipath prerequisites and the confirming observation is: The forwarding entry contains both eligible next hops with operationally verified reachability.
C:Continuously check advertised prefix counts against each customer's contracted service. This is a plausible preventive practice for a different BGP condition, specifically BGP outbound default-only policy. BGP export policy determines whether a neighbor receives a default route or unrestricted more-specific NLRI. In this scenario, however, the distinguishing issue is BGP multipath prerequisites and the confirming observation is: The forwarding entry contains both eligible next hops with operationally verified reachability.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests