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.
Question 321
During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: A BGP session between remote loopbacks remains in Active because both devices were configured as directly connected EBGP peers. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Check loopback reachability, peer source address, hop limit and matching peer AS on both sides.
- Inspect negotiated hold time, actual keepalive reception and reset reason.
- Trace the route's active status and ordered export policy terms for that neighbor.
- Correlate UPDATE withdrawals, received prefix history and export-policy or originating route changes.
Explanation
Correct Answer
A:Check loopback reachability, peer source address, hop limit and matching peer AS on both sides. This check examines the decisive condition for EBGP multihop loopback peering before any unrelated changes are made. The underlying mechanism is: Multihop EBGP through loopback addresses requires proper transport reachability and a hop limit that permits the path. The confirming observation is: TCP port 179 connects from the intended source addresses and the BGP state reaches Established.
Incorrect Answers
B:Inspect negotiated hold time, actual keepalive reception and reset reason. This is a plausible diagnostic check for a different BGP condition, specifically BGP hold-time negotiation. BGP session liveness relies on negotiated timers and timely keepalives; packet loss beyond a hold interval tears down the session. In this scenario, however, the distinguishing issue is EBGP multihop loopback peering and the confirming observation is: TCP port 179 connects from the intended source addresses and the BGP state reaches Established.
C:Trace the route's active status and ordered export policy terms for that neighbor. This is a plausible diagnostic check for a different BGP condition, specifically BGP outbound route policy reject. Export policy explicitly determines which active routes BGP may advertise; local route presence alone is not export approval. In this scenario, however, the distinguishing issue is EBGP multihop loopback peering and the confirming observation is: TCP port 179 connects from the intended source addresses and the BGP state reaches Established.
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 EBGP multihop loopback peering and the confirming observation is: TCP port 179 connects from the intended source addresses and the BGP state reaches Established.
Question 322
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: A BGP session between remote loopbacks remains in Active because both devices were configured as directly connected EBGP peers. Which routing or service mechanism best explains the reported behavior?
- BGP session liveness relies on negotiated timers and timely keepalives; packet loss beyond a hold interval tears down the session.
- Multihop EBGP through loopback addresses requires proper transport reachability and a hop limit that permits the path.
- Export policy explicitly determines which active routes BGP may advertise; local route presence alone is not export approval.
- BGP prefix churn can occur from an originator or policy without a TCP session flap, so transport-only troubleshooting is insufficient.
Explanation
Correct Answer
B:Multihop EBGP through loopback addresses requires proper transport reachability and a hop limit that permits the path. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: TCP port 179 connects from the intended source addresses and the BGP state reaches Established. The targeted correction is: Configure justified multihop and local-address settings with transport routing to the loopbacks.
Incorrect Answers
A:BGP session liveness relies on negotiated timers and timely keepalives; packet loss beyond a hold interval tears down the session. This is a plausible protocol explanation for a different BGP condition, specifically BGP hold-time negotiation. BGP session liveness relies on negotiated timers and timely keepalives; packet loss beyond a hold interval tears down the session. In this scenario, however, the distinguishing issue is EBGP multihop loopback peering and the confirming observation is: TCP port 179 connects from the intended source addresses and the BGP state reaches Established.
C:Export policy explicitly determines which active routes BGP may advertise; local route presence alone is not export approval. This is a plausible protocol explanation for a different BGP condition, specifically BGP outbound route policy reject. Export policy explicitly determines which active routes BGP may advertise; local route presence alone is not export approval. In this scenario, however, the distinguishing issue is EBGP multihop loopback peering and the confirming observation is: TCP port 179 connects from the intended source addresses and the BGP state reaches Established.
D: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 EBGP multihop loopback peering and the confirming observation is: TCP port 179 connects from the intended source addresses and the BGP state reaches Established.
Question 323
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: A BGP session between remote loopbacks remains in Active because both devices were configured as directly connected EBGP peers. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The session remains Established with stable keepalive reception and no hold-time-expired resets.
- The prefix appears in the BGP advertised-route view only after matching the intended permit condition.
- TCP port 179 connects from the intended source addresses and the BGP state reaches Established.
- Withdrawal timestamps correlate with the actual source route or policy event rather than BGP neighbor resets.
Explanation
Correct Answer
C:TCP port 179 connects from the intended source addresses and the BGP state reaches Established. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Multihop EBGP through loopback addresses requires proper transport reachability and a hop limit that permits the path.
Incorrect Answers
A:The session remains Established with stable keepalive reception and no hold-time-expired resets. This is a plausible observed evidence for a different BGP condition, specifically BGP hold-time negotiation. BGP session liveness relies on negotiated timers and timely keepalives; packet loss beyond a hold interval tears down the session. In this scenario, however, the distinguishing issue is EBGP multihop loopback peering and the confirming observation is: TCP port 179 connects from the intended source addresses and the BGP state reaches Established.
B:The prefix appears in the BGP advertised-route view only after matching the intended permit condition. This is a plausible observed evidence for a different BGP condition, specifically BGP outbound route policy reject. Export policy explicitly determines which active routes BGP may advertise; local route presence alone is not export approval. In this scenario, however, the distinguishing issue is EBGP multihop loopback peering and the confirming observation is: TCP port 179 connects from the intended source addresses and the BGP state reaches Established.
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 EBGP multihop loopback peering and the confirming observation is: TCP port 179 connects from the intended source addresses and the BGP state reaches Established.
Question 324
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: A BGP session between remote loopbacks remains in Active because both devices were configured as directly connected EBGP peers. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Restore transport reliability and choose compatible BGP timers for the intended failure-detection budget.
- Add a narrowly scoped route-export term before the terminating rejection.
- 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
D:Configure justified multihop and local-address settings with transport routing to the loopbacks. The change addresses the root behavior described here: Multihop EBGP through loopback addresses requires proper transport reachability and a hop limit that permits the path. Verify success with: TCP port 179 connects from the intended source addresses and the BGP state reaches Established.
Incorrect Answers
A:Restore transport reliability and choose compatible BGP timers for the intended failure-detection budget. This is a plausible configuration or operational fix for a different BGP condition, specifically BGP hold-time negotiation. BGP session liveness relies on negotiated timers and timely keepalives; packet loss beyond a hold interval tears down the session. In this scenario, however, the distinguishing issue is EBGP multihop loopback peering and the confirming observation is: TCP port 179 connects from the intended source addresses and the BGP state reaches Established.
B:Add a narrowly scoped route-export term before the terminating rejection. This is a plausible configuration or operational fix for a different BGP condition, specifically BGP outbound route policy reject. Export policy explicitly determines which active routes BGP may advertise; local route presence alone is not export approval. In this scenario, however, the distinguishing issue is EBGP multihop loopback peering and the confirming observation is: TCP port 179 connects from the intended source addresses and the BGP state reaches Established.
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 EBGP multihop loopback peering and the confirming observation is: TCP port 179 connects from the intended source addresses and the BGP state reaches Established.
Question 325
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: A BGP session between remote loopbacks remains in Active because both devices were configured as directly connected EBGP peers. Which operational control would best prevent a recurrence of this exact failure mode?
- Verify the path in each direction and control-plane filtering before enabling multihop EBGP.
- Monitor reset reasons and avoid timer reductions that outpace control-plane reliability.
- Keep a positive-and-negative prefix test table for each customer export policy.
- Monitor per-prefix churn independently of session uptime.
Explanation
Correct Answer
A:Verify the path in each direction and control-plane filtering before enabling multihop EBGP. The control limits repetition of the described root condition: Multihop EBGP through loopback addresses requires proper transport reachability and a hop limit that permits the path. During audits, confirm: TCP port 179 connects from the intended source addresses and the BGP state reaches Established.
Incorrect Answers
B:Monitor reset reasons and avoid timer reductions that outpace control-plane reliability. This is a plausible preventive practice for a different BGP condition, specifically BGP hold-time negotiation. BGP session liveness relies on negotiated timers and timely keepalives; packet loss beyond a hold interval tears down the session. In this scenario, however, the distinguishing issue is EBGP multihop loopback peering and the confirming observation is: TCP port 179 connects from the intended source addresses and the BGP state reaches Established.
C:Keep a positive-and-negative prefix test table for each customer export policy. This is a plausible preventive practice for a different BGP condition, specifically BGP outbound route policy reject. Export policy explicitly determines which active routes BGP may advertise; local route presence alone is not export approval. In this scenario, however, the distinguishing issue is EBGP multihop loopback peering and the confirming observation is: TCP port 179 connects from the intended source addresses and the BGP state reaches Established.
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 EBGP multihop loopback peering and the confirming observation is: TCP port 179 connects from the intended source addresses and the BGP state reaches Established.
Question 326
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: Core IP connectivity works but a new external BGP session stays in Connect while a security filter silently discards TCP destination port 179. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Correlate UPDATE withdrawals, received prefix history and export-policy or originating route changes.
- Inspect firewall counters and TCP establishment attempts between the configured BGP endpoints.
- Check prefix count, the configured maximum-prefix threshold and received-route update logs.
- Compare the configured peer-AS and the AS advertised in the remote OPEN message.
Explanation
Correct Answer
B:Inspect firewall counters and TCP establishment attempts between the configured BGP endpoints. This check examines the decisive condition for BGP TCP filtering before any unrelated changes are made. The underlying mechanism is: BGP relies on a permitted TCP session to exchange OPEN, KEEPALIVE and UPDATE messages. The confirming observation is: TCP handshake completes and BGP reaches Established after the targeted filter correction.
Incorrect Answers
A: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 TCP filtering and the confirming observation is: TCP handshake completes and BGP reaches Established after the targeted filter correction.
C:Check prefix count, the configured maximum-prefix threshold and received-route update logs. This is a plausible diagnostic check for a different BGP condition, specifically BGP maximum-prefix threshold. Maximum-prefix controls can intentionally protect a BGP session or router from excessive received prefixes. In this scenario, however, the distinguishing issue is BGP TCP filtering and the confirming observation is: TCP handshake completes and BGP reaches Established after the targeted filter correction.
D:Compare the configured peer-AS and the AS advertised in the remote OPEN message. This is a plausible diagnostic check for a different BGP condition, specifically BGP wrong remote AS. BGP OPEN validates autonomous-system identity; a peer-AS mismatch prevents a normal established session. In this scenario, however, the distinguishing issue is BGP TCP filtering and the confirming observation is: TCP handshake completes and BGP reaches Established after the targeted filter correction.
Question 327
During a core-routing migration rehearsal, an HPE Juniper Networking engineer investigates this situation: Core IP connectivity works but a new external BGP session stays in Connect while a security filter silently discards TCP destination port 179. Which routing or service mechanism best explains the reported behavior?
- BGP prefix churn can occur from an originator or policy without a TCP session flap, so transport-only troubleshooting is insufficient.
- Maximum-prefix controls can intentionally protect a BGP session or router from excessive received prefixes.
- BGP relies on a permitted TCP session to exchange OPEN, KEEPALIVE and UPDATE messages.
- BGP OPEN validates autonomous-system identity; a peer-AS mismatch prevents a normal established session.
Explanation
Correct Answer
C:BGP relies on a permitted TCP session to exchange OPEN, KEEPALIVE and UPDATE messages. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: TCP handshake completes and BGP reaches Established after the targeted filter correction. The targeted correction is: Allow the authorized BGP endpoint and TCP flow through the control-plane filter rather than disabling filtering globally.
Incorrect Answers
A: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 TCP filtering and the confirming observation is: TCP handshake completes and BGP reaches Established after the targeted filter correction.
B:Maximum-prefix controls can intentionally protect a BGP session or router from excessive received prefixes. This is a plausible protocol explanation for a different BGP condition, specifically BGP maximum-prefix threshold. Maximum-prefix controls can intentionally protect a BGP session or router from excessive received prefixes. In this scenario, however, the distinguishing issue is BGP TCP filtering and the confirming observation is: TCP handshake completes and BGP reaches Established after the targeted filter correction.
D:BGP OPEN validates autonomous-system identity; a peer-AS mismatch prevents a normal established session. This is a plausible protocol explanation for a different BGP condition, specifically BGP wrong remote AS. BGP OPEN validates autonomous-system identity; a peer-AS mismatch prevents a normal established session. In this scenario, however, the distinguishing issue is BGP TCP filtering and the confirming observation is: TCP handshake completes and BGP reaches Established after the targeted filter correction.
Question 328
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: Core IP connectivity works but a new external BGP session stays in Connect while a security filter silently discards TCP destination port 179. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Withdrawal timestamps correlate with the actual source route or policy event rather than BGP neighbor resets.
- After correcting the peer route leak, the accepted count falls below the configured limit and the session remains healthy.
- OPEN exchange succeeds and the neighbor remains Established with the expected peer AS.
- TCP handshake completes and BGP reaches Established after the targeted filter correction.
Explanation
Correct Answer
D:TCP handshake completes and BGP reaches Established after the targeted filter correction. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: BGP relies on a permitted TCP session to exchange OPEN, KEEPALIVE and UPDATE messages.
Incorrect Answers
A: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 TCP filtering and the confirming observation is: TCP handshake completes and BGP reaches Established after the targeted filter correction.
B:After correcting the peer route leak, the accepted count falls below the configured limit and the session remains healthy. This is a plausible observed evidence for a different BGP condition, specifically BGP maximum-prefix threshold. Maximum-prefix controls can intentionally protect a BGP session or router from excessive received prefixes. In this scenario, however, the distinguishing issue is BGP TCP filtering and the confirming observation is: TCP handshake completes and BGP reaches Established after the targeted filter correction.
C:OPEN exchange succeeds and the neighbor remains Established with the expected peer AS. This is a plausible observed evidence for a different BGP condition, specifically BGP wrong remote AS. BGP OPEN validates autonomous-system identity; a peer-AS mismatch prevents a normal established session. In this scenario, however, the distinguishing issue is BGP TCP filtering and the confirming observation is: TCP handshake completes and BGP reaches Established after the targeted filter correction.
Question 329
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: Core IP connectivity works but a new external BGP session stays in Connect while a security filter silently discards TCP destination port 179. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Allow the authorized BGP endpoint and TCP flow through the control-plane filter rather than disabling filtering globally.
- Fix the originating route instability or policy condition creating the repeated announcements.
- Fix the upstream leak and adjust any maximum-prefix threshold only against verified expected growth.
- Correct the neighbor peer-AS configuration and verify the authorized topology.
Explanation
Correct Answer
A:Allow the authorized BGP endpoint and TCP flow through the control-plane filter rather than disabling filtering globally. The change addresses the root behavior described here: BGP relies on a permitted TCP session to exchange OPEN, KEEPALIVE and UPDATE messages. Verify success with: TCP handshake completes and BGP reaches Established after the targeted filter correction.
Incorrect Answers
B: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 TCP filtering and the confirming observation is: TCP handshake completes and BGP reaches Established after the targeted filter correction.
C:Fix the upstream leak and adjust any maximum-prefix threshold only against verified expected growth. This is a plausible configuration or operational fix for a different BGP condition, specifically BGP maximum-prefix threshold. Maximum-prefix controls can intentionally protect a BGP session or router from excessive received prefixes. In this scenario, however, the distinguishing issue is BGP TCP filtering and the confirming observation is: TCP handshake completes and BGP reaches Established after the targeted filter correction.
D:Correct the neighbor peer-AS configuration and verify the authorized topology. This is a plausible configuration or operational fix for a different BGP condition, specifically BGP wrong remote AS. BGP OPEN validates autonomous-system identity; a peer-AS mismatch prevents a normal established session. In this scenario, however, the distinguishing issue is BGP TCP filtering and the confirming observation is: TCP handshake completes and BGP reaches Established after the targeted filter correction.
Question 330
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: Core IP connectivity works but a new external BGP session stays in Connect while a security filter silently discards TCP destination port 179. Which operational control would best prevent a recurrence of this exact failure mode?
- Monitor per-prefix churn independently of session uptime.
- Track approved BGP peer addresses and rule hits in edge firewall audits.
- Monitor counts versus warning thresholds and rehearse a safe session recovery.
- Cross-check peer-AS values against contracts and remote device inventory before maintenance.
Explanation
Correct Answer
B:Track approved BGP peer addresses and rule hits in edge firewall audits. The control limits repetition of the described root condition: BGP relies on a permitted TCP session to exchange OPEN, KEEPALIVE and UPDATE messages. During audits, confirm: TCP handshake completes and BGP reaches Established after the targeted filter correction.
Incorrect Answers
A: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 TCP filtering and the confirming observation is: TCP handshake completes and BGP reaches Established after the targeted filter correction.
C:Monitor counts versus warning thresholds and rehearse a safe session recovery. This is a plausible preventive practice for a different BGP condition, specifically BGP maximum-prefix threshold. Maximum-prefix controls can intentionally protect a BGP session or router from excessive received prefixes. In this scenario, however, the distinguishing issue is BGP TCP filtering and the confirming observation is: TCP handshake completes and BGP reaches Established after the targeted filter correction.
D:Cross-check peer-AS values against contracts and remote device inventory before maintenance. This is a plausible preventive practice for a different BGP condition, specifically BGP wrong remote AS. BGP OPEN validates autonomous-system identity; a peer-AS mismatch prevents a normal established session. In this scenario, however, the distinguishing issue is BGP TCP filtering and the confirming observation is: TCP handshake completes and BGP reaches Established after the targeted filter correction.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests