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.
Question 331
During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: An external session sends TCP traffic and immediately resets after BGP OPEN exchange when a peer-AS field was copied from another customer. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Check prefix count, the configured maximum-prefix threshold and received-route update logs.
- Inspect firewall counters and TCP establishment attempts between the configured BGP endpoints.
- Compare the configured peer-AS and the AS advertised in the remote OPEN message.
- Inspect the effective group and neighbor policy hierarchy rather than only the neighbor stanza.
Explanation
Correct Answer
C:Compare the configured peer-AS and the AS advertised in the remote OPEN message. This check examines the decisive condition for BGP wrong remote AS before any unrelated changes are made. The underlying mechanism is: BGP OPEN validates autonomous-system identity; a peer-AS mismatch prevents a normal established session. The confirming observation is: OPEN exchange succeeds and the neighbor remains Established with the expected peer AS.
Incorrect Answers
A: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 wrong remote AS and the confirming observation is: OPEN exchange succeeds and the neighbor remains Established with the expected peer AS.
B:Inspect firewall counters and TCP establishment attempts between the configured BGP endpoints. This is a plausible diagnostic check for a different BGP condition, specifically BGP TCP filtering. BGP relies on a permitted TCP session to exchange OPEN, KEEPALIVE and UPDATE messages. In this scenario, however, the distinguishing issue is BGP wrong remote AS and the confirming observation is: OPEN exchange succeeds and the neighbor remains Established with the expected peer AS.
D:Inspect the effective group and neighbor policy hierarchy rather than only the neighbor stanza. This is a plausible diagnostic check for a different BGP condition, specifically BGP peer group policy inheritance. Junos BGP peers inherit group-level settings unless correctly overridden, so peer placement changes effective policy. In this scenario, however, the distinguishing issue is BGP wrong remote AS and the confirming observation is: OPEN exchange succeeds and the neighbor remains Established with the expected peer AS.
Question 332
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: An external session sends TCP traffic and immediately resets after BGP OPEN exchange when a peer-AS field was copied from another customer. Which routing or service mechanism best explains the reported behavior?
- 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.
- Route-reflection rules distinguish routes received from clients and nonclients; misclassified clients may prevent intended redistribution.
- BGP OPEN validates autonomous-system identity; a peer-AS mismatch prevents a normal established session.
Explanation
Correct Answer
D:BGP OPEN validates autonomous-system identity; a peer-AS mismatch prevents a normal established session. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: OPEN exchange succeeds and the neighbor remains Established with the expected peer AS. The targeted correction is: Correct the neighbor peer-AS configuration and verify the authorized topology.
Incorrect Answers
A: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 wrong remote AS and the confirming observation is: OPEN exchange succeeds and the neighbor remains Established with the expected peer AS.
B:BGP relies on a permitted TCP session to exchange OPEN, KEEPALIVE and UPDATE messages. This is a plausible protocol explanation for a different BGP condition, specifically BGP TCP filtering. BGP relies on a permitted TCP session to exchange OPEN, KEEPALIVE and UPDATE messages. In this scenario, however, the distinguishing issue is BGP wrong remote AS and the confirming observation is: OPEN exchange succeeds and the neighbor remains Established with the expected peer AS.
C:Route-reflection rules distinguish routes received from clients and nonclients; misclassified clients may prevent intended redistribution. This is a plausible protocol explanation for a different BGP condition, specifically Route-reflector client reflection rule. Route-reflection rules distinguish routes received from clients and nonclients; misclassified clients may prevent intended redistribution. In this scenario, however, the distinguishing issue is BGP wrong remote AS and the confirming observation is: OPEN exchange succeeds and the neighbor remains Established with the expected peer AS.
Question 333
During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: An external session sends TCP traffic and immediately resets after BGP OPEN exchange when a peer-AS field was copied from another customer. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- OPEN exchange succeeds and the neighbor remains Established with the expected peer AS.
- After correcting the peer route leak, the accepted count falls below the configured limit and the session remains healthy.
- TCP handshake completes and BGP reaches Established after the targeted filter correction.
- The reflector advertises the client's eligible route to other configured clients as designed.
Explanation
Correct Answer
A:OPEN exchange succeeds and the neighbor remains Established with the expected peer AS. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: BGP OPEN validates autonomous-system identity; a peer-AS mismatch prevents a normal established session.
Incorrect Answers
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 wrong remote AS and the confirming observation is: OPEN exchange succeeds and the neighbor remains Established with the expected peer AS.
C:TCP handshake completes and BGP reaches Established after the targeted filter correction. This is a plausible observed evidence for a different BGP condition, specifically BGP TCP filtering. BGP relies on a permitted TCP session to exchange OPEN, KEEPALIVE and UPDATE messages. In this scenario, however, the distinguishing issue is BGP wrong remote AS and the confirming observation is: OPEN exchange succeeds and the neighbor remains Established with the expected peer AS.
D:The reflector advertises the client's eligible route to other configured clients as designed. This is a plausible observed evidence for a different BGP condition, specifically Route-reflector client reflection rule. Route-reflection rules distinguish routes received from clients and nonclients; misclassified clients may prevent intended redistribution. In this scenario, however, the distinguishing issue is BGP wrong remote AS and the confirming observation is: OPEN exchange succeeds and the neighbor remains Established with the expected peer AS.
Question 334
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: An external session sends TCP traffic and immediately resets after BGP OPEN exchange when a peer-AS field was copied from another customer. Which response or focused corrective action best addresses this situation without changing unrelated components?
- 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.
- Allow the authorized BGP endpoint and TCP flow through the control-plane filter rather than disabling filtering globally.
- Correct route-reflector-client relationships and keep route selection policy consistent.
Explanation
Correct Answer
B:Correct the neighbor peer-AS configuration and verify the authorized topology. The change addresses the root behavior described here: BGP OPEN validates autonomous-system identity; a peer-AS mismatch prevents a normal established session. Verify success with: OPEN exchange succeeds and the neighbor remains Established with the expected peer AS.
Incorrect Answers
A: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 wrong remote AS and the confirming observation is: OPEN exchange succeeds and the neighbor remains Established with the expected peer AS.
C:Allow the authorized BGP endpoint and TCP flow through the control-plane filter rather than disabling filtering globally. This is a plausible configuration or operational fix for a different BGP condition, specifically BGP TCP filtering. BGP relies on a permitted TCP session to exchange OPEN, KEEPALIVE and UPDATE messages. In this scenario, however, the distinguishing issue is BGP wrong remote AS and the confirming observation is: OPEN exchange succeeds and the neighbor remains Established with the expected peer AS.
D:Correct route-reflector-client relationships and keep route selection policy consistent. This is a plausible configuration or operational fix for a different BGP condition, specifically Route-reflector client reflection rule. Route-reflection rules distinguish routes received from clients and nonclients; misclassified clients may prevent intended redistribution. In this scenario, however, the distinguishing issue is BGP wrong remote AS and the confirming observation is: OPEN exchange succeeds and the neighbor remains Established with the expected peer AS.
Question 335
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: An external session sends TCP traffic and immediately resets after BGP OPEN exchange when a peer-AS field was copied from another customer. Which operational control would best prevent a recurrence of this exact failure mode?
- Monitor counts versus warning thresholds and rehearse a safe session recovery.
- Track approved BGP peer addresses and rule hits in edge firewall audits.
- Cross-check peer-AS values against contracts and remote device inventory before maintenance.
- Validate client-to-client route propagation in route-reflector regression tests.
Explanation
Correct Answer
C:Cross-check peer-AS values against contracts and remote device inventory before maintenance. The control limits repetition of the described root condition: BGP OPEN validates autonomous-system identity; a peer-AS mismatch prevents a normal established session. During audits, confirm: OPEN exchange succeeds and the neighbor remains Established with the expected peer AS.
Incorrect Answers
A: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 wrong remote AS and the confirming observation is: OPEN exchange succeeds and the neighbor remains Established with the expected peer AS.
B:Track approved BGP peer addresses and rule hits in edge firewall audits. This is a plausible preventive practice for a different BGP condition, specifically BGP TCP filtering. BGP relies on a permitted TCP session to exchange OPEN, KEEPALIVE and UPDATE messages. In this scenario, however, the distinguishing issue is BGP wrong remote AS and the confirming observation is: OPEN exchange succeeds and the neighbor remains Established with the expected peer AS.
D:Validate client-to-client route propagation in route-reflector regression tests. This is a plausible preventive practice for a different BGP condition, specifically Route-reflector client reflection rule. Route-reflection rules distinguish routes received from clients and nonclients; misclassified clients may prevent intended redistribution. In this scenario, however, the distinguishing issue is BGP wrong remote AS and the confirming observation is: OPEN exchange succeeds and the neighbor remains Established with the expected peer AS.
Question 336
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: An EBGP neighbor resets several times an hour after network jitter while its configured keepalive and hold-time assumptions differ from the operational negotiated values. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect the effective group and neighbor policy hierarchy rather than only the neighbor stanza.
- Check loopback reachability, peer source address, hop limit and matching peer AS on both sides.
- Inspect local preference and AS-path ranking before interpreting MED.
- Inspect negotiated hold time, actual keepalive reception and reset reason.
Explanation
Correct Answer
D:Inspect negotiated hold time, actual keepalive reception and reset reason. This check examines the decisive condition for BGP hold-time negotiation before any unrelated changes are made. The underlying mechanism is: BGP session liveness relies on negotiated timers and timely keepalives; packet loss beyond a hold interval tears down the session. The confirming observation is: The session remains Established with stable keepalive reception and no hold-time-expired resets.
Incorrect Answers
A:Inspect the effective group and neighbor policy hierarchy rather than only the neighbor stanza. This is a plausible diagnostic check for a different BGP condition, specifically BGP peer group policy inheritance. Junos BGP peers inherit group-level settings unless correctly overridden, so peer placement changes effective policy. In this scenario, however, the distinguishing issue is BGP hold-time negotiation and the confirming observation is: The session remains Established with stable keepalive reception and no hold-time-expired resets.
B: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 hold-time negotiation and the confirming observation is: The session remains Established with stable keepalive reception and no hold-time-expired resets.
C:Inspect local preference and AS-path ranking before interpreting MED. This is a plausible diagnostic check for a different BGP condition, specifically BGP MED versus customer preferences. MED is considered only after more-preferred BGP attributes have been evaluated under configured comparison rules. In this scenario, however, the distinguishing issue is BGP hold-time negotiation and the confirming observation is: The session remains Established with stable keepalive reception and no hold-time-expired resets.
Question 337
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: An EBGP neighbor resets several times an hour after network jitter while its configured keepalive and hold-time assumptions differ from the operational negotiated values. 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.
- Junos BGP peers inherit group-level settings unless correctly overridden, so peer placement changes effective policy.
- Multihop EBGP through loopback addresses requires proper transport reachability and a hop limit that permits the path.
- MED is considered only after more-preferred BGP attributes have been evaluated under configured comparison rules.
Explanation
Correct Answer
A:BGP session liveness relies on negotiated timers and timely keepalives; packet loss beyond a hold interval tears down the session. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The session remains Established with stable keepalive reception and no hold-time-expired resets. The targeted correction is: Restore transport reliability and choose compatible BGP timers for the intended failure-detection budget.
Incorrect Answers
B:Junos BGP peers inherit group-level settings unless correctly overridden, so peer placement changes effective policy. This is a plausible protocol explanation for a different BGP condition, specifically BGP peer group policy inheritance. Junos BGP peers inherit group-level settings unless correctly overridden, so peer placement changes effective policy. In this scenario, however, the distinguishing issue is BGP hold-time negotiation and the confirming observation is: The session remains Established with stable keepalive reception and no hold-time-expired resets.
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 hold-time negotiation and the confirming observation is: The session remains Established with stable keepalive reception and no hold-time-expired resets.
D:MED is considered only after more-preferred BGP attributes have been evaluated under configured comparison rules. This is a plausible protocol explanation for a different BGP condition, specifically BGP MED versus customer preferences. MED is considered only after more-preferred BGP attributes have been evaluated under configured comparison rules. In this scenario, however, the distinguishing issue is BGP hold-time negotiation and the confirming observation is: The session remains Established with stable keepalive reception and no hold-time-expired resets.
Question 338
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: An EBGP neighbor resets several times an hour after network jitter while its configured keepalive and hold-time assumptions differ from the operational negotiated values. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The new neighbor's advertised prefixes and tags match an explicitly reviewed effective configuration.
- The session remains Established with stable keepalive reception and no hold-time-expired resets.
- TCP port 179 connects from the intended source addresses and the BGP state reaches Established.
- The observed best path follows the documented attribute order rather than a stand-alone MED value.
Explanation
Correct Answer
B:The session remains Established with stable keepalive reception and no hold-time-expired resets. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: BGP session liveness relies on negotiated timers and timely keepalives; packet loss beyond a hold interval tears down the session.
Incorrect Answers
A:The new neighbor's advertised prefixes and tags match an explicitly reviewed effective configuration. This is a plausible observed evidence for a different BGP condition, specifically BGP peer group policy inheritance. Junos BGP peers inherit group-level settings unless correctly overridden, so peer placement changes effective policy. In this scenario, however, the distinguishing issue is BGP hold-time negotiation and the confirming observation is: The session remains Established with stable keepalive reception and no hold-time-expired resets.
C: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 hold-time negotiation and the confirming observation is: The session remains Established with stable keepalive reception and no hold-time-expired resets.
D:The observed best path follows the documented attribute order rather than a stand-alone MED value. This is a plausible observed evidence for a different BGP condition, specifically BGP MED versus customer preferences. MED is considered only after more-preferred BGP attributes have been evaluated under configured comparison rules. In this scenario, however, the distinguishing issue is BGP hold-time negotiation and the confirming observation is: The session remains Established with stable keepalive reception and no hold-time-expired resets.
Question 339
During a core-routing migration rehearsal, an HPE Juniper Networking engineer investigates this situation: An EBGP neighbor resets several times an hour after network jitter while its configured keepalive and hold-time assumptions differ from the operational negotiated values. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Move the peer to the intended group or override supported policy at the appropriate scope.
- Configure justified multihop and local-address settings with transport routing to the loopbacks.
- Restore transport reliability and choose compatible BGP timers for the intended failure-detection budget.
- Align local preference first or document why MED should not override a business routing policy.
Explanation
Correct Answer
C:Restore transport reliability and choose compatible BGP timers for the intended failure-detection budget. The change addresses the root behavior described here: BGP session liveness relies on negotiated timers and timely keepalives; packet loss beyond a hold interval tears down the session. Verify success with: The session remains Established with stable keepalive reception and no hold-time-expired resets.
Incorrect Answers
A:Move the peer to the intended group or override supported policy at the appropriate scope. This is a plausible configuration or operational fix for a different BGP condition, specifically BGP peer group policy inheritance. Junos BGP peers inherit group-level settings unless correctly overridden, so peer placement changes effective policy. In this scenario, however, the distinguishing issue is BGP hold-time negotiation and the confirming observation is: The session remains Established with stable keepalive reception and no hold-time-expired resets.
B: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 hold-time negotiation and the confirming observation is: The session remains Established with stable keepalive reception and no hold-time-expired resets.
D:Align local preference first or document why MED should not override a business routing policy. This is a plausible configuration or operational fix for a different BGP condition, specifically BGP MED versus customer preferences. MED is considered only after more-preferred BGP attributes have been evaluated under configured comparison rules. In this scenario, however, the distinguishing issue is BGP hold-time negotiation and the confirming observation is: The session remains Established with stable keepalive reception and no hold-time-expired resets.
Question 340
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: An EBGP neighbor resets several times an hour after network jitter while its configured keepalive and hold-time assumptions differ from the operational negotiated values. Which operational control would best prevent a recurrence of this exact failure mode?
- Review inherited policy on a per-neighbor basis before moving BGP sessions.
- Verify the path in each direction and control-plane filtering before enabling multihop EBGP.
- Record all earlier path-selection attributes in traffic engineering reviews.
- Monitor reset reasons and avoid timer reductions that outpace control-plane reliability.
Explanation
Correct Answer
D:Monitor reset reasons and avoid timer reductions that outpace control-plane reliability. The control limits repetition of the described root condition: BGP session liveness relies on negotiated timers and timely keepalives; packet loss beyond a hold interval tears down the session. During audits, confirm: The session remains Established with stable keepalive reception and no hold-time-expired resets.
Incorrect Answers
A:Review inherited policy on a per-neighbor basis before moving BGP sessions. This is a plausible preventive practice for a different BGP condition, specifically BGP peer group policy inheritance. Junos BGP peers inherit group-level settings unless correctly overridden, so peer placement changes effective policy. In this scenario, however, the distinguishing issue is BGP hold-time negotiation and the confirming observation is: The session remains Established with stable keepalive reception and no hold-time-expired resets.
B: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 BGP hold-time negotiation and the confirming observation is: The session remains Established with stable keepalive reception and no hold-time-expired resets.
C:Record all earlier path-selection attributes in traffic engineering reviews. This is a plausible preventive practice for a different BGP condition, specifically BGP MED versus customer preferences. MED is considered only after more-preferred BGP attributes have been evaluated under configured comparison rules. In this scenario, however, the distinguishing issue is BGP hold-time negotiation and the confirming observation is: The session remains Established with stable keepalive reception and no hold-time-expired resets.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests