Question 430
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: Two customer access routes differ by MED, but the local router ignores the lower MED because the routes first differ in LOCAL_PREF. Which operational control would best prevent a recurrence of this exact failure mode?
- Monitor reset reasons and avoid timer reductions that outpace control-plane reliability.
- Record all earlier path-selection attributes in traffic engineering reviews.
- Review inherited policy on a per-neighbor basis before moving BGP sessions.
- Log origin attribute changes when redistributing or aggregating BGP routes.
Explanation
Correct Answer
B:Record all earlier path-selection attributes in traffic engineering reviews. The control limits repetition of the described root condition: MED is considered only after more-preferred BGP attributes have been evaluated under configured comparison rules. During audits, confirm: The observed best path follows the documented attribute order rather than a stand-alone MED value.
Incorrect Answers
A: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 BGP MED versus customer preferences and the confirming observation is: The observed best path follows the documented attribute order rather than a stand-alone MED value.
C: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 MED versus customer preferences and the confirming observation is: The observed best path follows the documented attribute order rather than a stand-alone MED value.
D:Log origin attribute changes when redistributing or aggregating BGP routes. This is a plausible preventive practice for a different BGP condition, specifically BGP ORIGIN attribute tie. At the applicable BGP selection stage, lower origin-type value (IGP before incomplete) is preferred. In this scenario, however, the distinguishing issue is BGP MED versus customer preferences and the confirming observation is: The observed best path follows the documented attribute order rather than a stand-alone MED value.
Question 431
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: An ISP moves policy tags to large-community values but its older standard-community matcher no longer detects the intended tenant designation. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare AS_PATH lengths and any policy that rewrites higher-priority attributes.
- Inspect negotiated hold time, actual keepalive reception and reset reason.
- Inspect the BGP community type and route-policy match expression format.
- Inspect aggregate route generation conditions and the set of eligible active contributors.
Explanation
Correct Answer
C:Inspect the BGP community type and route-policy match expression format. This check examines the decisive condition for BGP large community matching before any unrelated changes are made. The underlying mechanism is: Large communities have different encoding and syntax from standard communities; policy must match the received attribute family. The confirming observation is: The intended large-community value is visible and the correct service policy term matches.
Incorrect Answers
A:Compare AS_PATH lengths and any policy that rewrites higher-priority attributes. This is a plausible diagnostic check for a different BGP condition, specifically AS-path length selection. After equal higher-priority selection attributes, BGP generally prefers the shorter AS path among eligible candidate paths. In this scenario, however, the distinguishing issue is BGP large community matching and the confirming observation is: The intended large-community value is visible and the correct service policy term matches.
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 BGP large community matching and the confirming observation is: The intended large-community value is visible and the correct service policy term matches.
D:Inspect aggregate route generation conditions and the set of eligible active contributors. This is a plausible diagnostic check for a different BGP condition, specifically BGP aggregation hides contributors. Route aggregation can trade detailed reachability for a broad advertisement, so contributor rules and discard behavior govern correctness. In this scenario, however, the distinguishing issue is BGP large community matching and the confirming observation is: The intended large-community value is visible and the correct service policy term matches.
Question 432
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: An ISP moves policy tags to large-community values but its older standard-community matcher no longer detects the intended tenant designation. Which routing or service mechanism best explains the reported behavior?
- After equal higher-priority selection attributes, BGP generally prefers the shorter AS path among eligible candidate paths.
- BGP session liveness relies on negotiated timers and timely keepalives; packet loss beyond a hold interval tears down the session.
- Prefix matching can include unintended more-specifics when the term is broader than the intended exact route requirement.
- Large communities have different encoding and syntax from standard communities; policy must match the received attribute family.
Explanation
Correct Answer
D:Large communities have different encoding and syntax from standard communities; policy must match the received attribute family. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The intended large-community value is visible and the correct service policy term matches. The targeted correction is: Use the supported large-community match configuration without coercing tags into standard-community form.
Incorrect Answers
A:After equal higher-priority selection attributes, BGP generally prefers the shorter AS path among eligible candidate paths. This is a plausible protocol explanation for a different BGP condition, specifically AS-path length selection. After equal higher-priority selection attributes, BGP generally prefers the shorter AS path among eligible candidate paths. In this scenario, however, the distinguishing issue is BGP large community matching and the confirming observation is: The intended large-community value is visible and the correct service policy term matches.
B: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 BGP large community matching and the confirming observation is: The intended large-community value is visible and the correct service policy term matches.
C:Prefix matching can include unintended more-specifics when the term is broader than the intended exact route requirement. This is a plausible protocol explanation for a different BGP condition, specifically BGP import policy overmatching. Prefix matching can include unintended more-specifics when the term is broader than the intended exact route requirement. In this scenario, however, the distinguishing issue is BGP large community matching and the confirming observation is: The intended large-community value is visible and the correct service policy term matches.
Question 433
During an edge-to-core validation, an HPE Juniper Networking engineer investigates this situation: An ISP moves policy tags to large-community values but its older standard-community matcher no longer detects the intended tenant designation. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The intended large-community value is visible and the correct service policy term matches.
- The shortest eligible AS path becomes preferred once conflicting policy overrides are removed.
- The session remains Established with stable keepalive reception and no hold-time-expired resets.
- The prohibited route is hidden or rejected while the specifically approved routes remain installed.
Explanation
Correct Answer
A:The intended large-community value is visible and the correct service policy term matches. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Large communities have different encoding and syntax from standard communities; policy must match the received attribute family.
Incorrect Answers
B:The shortest eligible AS path becomes preferred once conflicting policy overrides are removed. This is a plausible observed evidence for a different BGP condition, specifically AS-path length selection. After equal higher-priority selection attributes, BGP generally prefers the shorter AS path among eligible candidate paths. In this scenario, however, the distinguishing issue is BGP large community matching and the confirming observation is: The intended large-community value is visible and the correct service policy term matches.
C: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 BGP large community matching and the confirming observation is: The intended large-community value is visible and the correct service policy term matches.
D:The prohibited route is hidden or rejected while the specifically approved routes remain installed. This is a plausible observed evidence for a different BGP condition, specifically BGP import policy overmatching. Prefix matching can include unintended more-specifics when the term is broader than the intended exact route requirement. In this scenario, however, the distinguishing issue is BGP large community matching and the confirming observation is: The intended large-community value is visible and the correct service policy term matches.
Question 434
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: An ISP moves policy tags to large-community values but its older standard-community matcher no longer detects the intended tenant designation. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Correct route-policy attributes or prepend design to implement the intended preference.
- Use the supported large-community match configuration without coercing tags into standard-community form.
- Restore transport reliability and choose compatible BGP timers for the intended failure-detection budget.
- Constrain the prefix list or route-filter match semantics to the intended prefix lengths.
Explanation
Correct Answer
B:Use the supported large-community match configuration without coercing tags into standard-community form. The change addresses the root behavior described here: Large communities have different encoding and syntax from standard communities; policy must match the received attribute family. Verify success with: The intended large-community value is visible and the correct service policy term matches.
Incorrect Answers
A:Correct route-policy attributes or prepend design to implement the intended preference. This is a plausible configuration or operational fix for a different BGP condition, specifically AS-path length selection. After equal higher-priority selection attributes, BGP generally prefers the shorter AS path among eligible candidate paths. In this scenario, however, the distinguishing issue is BGP large community matching and the confirming observation is: The intended large-community value is visible and the correct service policy term matches.
C: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 BGP large community matching and the confirming observation is: The intended large-community value is visible and the correct service policy term matches.
D:Constrain the prefix list or route-filter match semantics to the intended prefix lengths. This is a plausible configuration or operational fix for a different BGP condition, specifically BGP import policy overmatching. Prefix matching can include unintended more-specifics when the term is broader than the intended exact route requirement. In this scenario, however, the distinguishing issue is BGP large community matching and the confirming observation is: The intended large-community value is visible and the correct service policy term matches.
Question 435
During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: An ISP moves policy tags to large-community values but its older standard-community matcher no longer detects the intended tenant designation. Which operational control would best prevent a recurrence of this exact failure mode?
- Audit path-length and local preference before changing peering relationships.
- Monitor reset reasons and avoid timer reductions that outpace control-plane reliability.
- Validate tagged routes in configuration tests after community-format changes.
- Run policy tests against boundary subnet lengths before installing route filters.
Explanation
Correct Answer
C:Validate tagged routes in configuration tests after community-format changes. The control limits repetition of the described root condition: Large communities have different encoding and syntax from standard communities; policy must match the received attribute family. During audits, confirm: The intended large-community value is visible and the correct service policy term matches.
Incorrect Answers
A:Audit path-length and local preference before changing peering relationships. This is a plausible preventive practice for a different BGP condition, specifically AS-path length selection. After equal higher-priority selection attributes, BGP generally prefers the shorter AS path among eligible candidate paths. In this scenario, however, the distinguishing issue is BGP large community matching and the confirming observation is: The intended large-community value is visible and the correct service policy term matches.
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 BGP large community matching and the confirming observation is: The intended large-community value is visible and the correct service policy term matches.
D:Run policy tests against boundary subnet lengths before installing route filters. This is a plausible preventive practice for a different BGP condition, specifically BGP import policy overmatching. Prefix matching can include unintended more-specifics when the term is broader than the intended exact route requirement. In this scenario, however, the distinguishing issue is BGP large community matching and the confirming observation is: The intended large-community value is visible and the correct service policy term matches.
Question 436
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: A small customer contracted for default-only BGP delivery suddenly receives the provider's full table, overwhelming the access router. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare multipath configuration and the eligibility attributes required for both candidate paths.
- Inspect the BGP route next-hop value and its recursive resolution in the active IGP or label transport.
- Compare local preference on the competing routes and verify their next hops resolve.
- Inspect effective egress prefix filters and advertised-route counts for the customer BGP group.
Explanation
Correct Answer
D:Inspect effective egress prefix filters and advertised-route counts for the customer BGP group. This check examines the decisive condition for BGP outbound default-only policy before any unrelated changes are made. The underlying mechanism is: BGP export policy determines whether a neighbor receives a default route or unrestricted more-specific NLRI. The confirming observation is: The neighbor receives the intended default and no unauthorized full-table routes.
Incorrect Answers
A:Compare multipath configuration and the eligibility attributes required for both candidate paths. This is a plausible diagnostic check for a different BGP condition, specifically BGP multipath prerequisites. BGP multipath requires compatible candidate paths and implementation-specific settings in addition to multiple route advertisements. In this scenario, however, the distinguishing issue is BGP outbound default-only policy and the confirming observation is: The neighbor receives the intended default and no unauthorized full-table routes.
B: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 outbound default-only policy and the confirming observation is: The neighbor receives the intended default and no unauthorized full-table routes.
C:Compare local preference on the competing routes and verify their next hops resolve. This is a plausible diagnostic check for a different BGP condition, specifically Local preference exit choice. Within an AS, higher BGP local preference is selected ahead of AS-path length when paths are otherwise eligible. In this scenario, however, the distinguishing issue is BGP outbound default-only policy and the confirming observation is: The neighbor receives the intended default and no unauthorized full-table routes.
Question 437
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: A small customer contracted for default-only BGP delivery suddenly receives the provider's full table, overwhelming the access router. Which routing or service mechanism best explains the reported behavior?
- BGP export policy determines whether a neighbor receives a default route or unrestricted more-specific NLRI.
- BGP multipath requires compatible candidate paths and implementation-specific settings in addition to multiple route advertisements.
- BGP path eligibility depends on being able to resolve the advertised next hop; a healthy TCP peering alone does not install the route.
- Within an AS, higher BGP local preference is selected ahead of AS-path length when paths are otherwise eligible.
Explanation
Correct Answer
A:BGP export policy determines whether a neighbor receives a default route or unrestricted more-specific NLRI. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The neighbor receives the intended default and no unauthorized full-table routes. The targeted correction is: Apply a specific default-only export policy at the customer boundary.
Incorrect Answers
B:BGP multipath requires compatible candidate paths and implementation-specific settings in addition to multiple route advertisements. This is a plausible protocol explanation for a different BGP condition, specifically BGP multipath prerequisites. BGP multipath requires compatible candidate paths and implementation-specific settings in addition to multiple route advertisements. In this scenario, however, the distinguishing issue is BGP outbound default-only policy and the confirming observation is: The neighbor receives the intended default and no unauthorized full-table routes.
C: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 outbound default-only policy and the confirming observation is: The neighbor receives the intended default and no unauthorized full-table routes.
D:Within an AS, higher BGP local preference is selected ahead of AS-path length when paths are otherwise eligible. This is a plausible protocol explanation for a different BGP condition, specifically Local preference exit choice. Within an AS, higher BGP local preference is selected ahead of AS-path length when paths are otherwise eligible. In this scenario, however, the distinguishing issue is BGP outbound default-only policy and the confirming observation is: The neighbor receives the intended default and no unauthorized full-table routes.
Question 438
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: A small customer contracted for default-only BGP delivery suddenly receives the provider's full table, overwhelming the access router. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- 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.
- The chosen active route uses the deliberately higher-local-preference exit while backup remains valid.
Explanation
Correct Answer
B:The neighbor receives the intended default and no unauthorized full-table routes. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: BGP export policy determines whether a neighbor receives a default route or unrestricted more-specific NLRI.
Incorrect Answers
A:The forwarding entry contains both eligible next hops with operationally verified reachability. This is a plausible observed evidence for a different BGP condition, specifically BGP multipath prerequisites. BGP multipath requires compatible candidate paths and implementation-specific settings in addition to multiple route advertisements. In this scenario, however, the distinguishing issue is BGP outbound default-only policy and the confirming observation is: The neighbor receives the intended default and no unauthorized full-table routes.
C: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 outbound default-only policy and the confirming observation is: The neighbor receives the intended default and no unauthorized full-table routes.
D:The chosen active route uses the deliberately higher-local-preference exit while backup remains valid. This is a plausible observed evidence for a different BGP condition, specifically Local preference exit choice. Within an AS, higher BGP local preference is selected ahead of AS-path length when paths are otherwise eligible. In this scenario, however, the distinguishing issue is BGP outbound default-only policy and the confirming observation is: The neighbor receives the intended default and no unauthorized full-table routes.
Question 439
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: A small customer contracted for default-only BGP delivery suddenly receives the provider's full table, overwhelming the access router. Which response or focused corrective action best addresses this situation without changing unrelated components?
- 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.
- Apply a specific default-only export policy at the customer boundary.
- Use an inbound routing policy to set the desired local preference for approved prefixes.
Explanation
Correct Answer
C:Apply a specific default-only export policy at the customer boundary. The change addresses the root behavior described here: BGP export policy determines whether a neighbor receives a default route or unrestricted more-specific NLRI. Verify success with: The neighbor receives the intended default and no unauthorized full-table routes.
Incorrect Answers
A:Enable supported BGP multipath under explicit attribute constraints instead of forcing unequal paths. This is a plausible configuration or operational fix for a different BGP condition, specifically BGP multipath prerequisites. BGP multipath requires compatible candidate paths and implementation-specific settings in addition to multiple route advertisements. In this scenario, however, the distinguishing issue is BGP outbound default-only policy and the confirming observation is: The neighbor receives the intended default and no unauthorized full-table routes.
B: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 outbound default-only policy and the confirming observation is: The neighbor receives the intended default and no unauthorized full-table routes.
D:Use an inbound routing policy to set the desired local preference for approved prefixes. This is a plausible configuration or operational fix for a different BGP condition, specifically Local preference exit choice. Within an AS, higher BGP local preference is selected ahead of AS-path length when paths are otherwise eligible. In this scenario, however, the distinguishing issue is BGP outbound default-only policy and the confirming observation is: The neighbor receives the intended default and no unauthorized full-table routes.
Question 440
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: A small customer contracted for default-only BGP delivery suddenly receives the provider's full table, overwhelming the access router. Which operational control would best prevent a recurrence of this exact failure mode?
- Review next-hop and attribute comparability before adding paths to ECMP service.
- Test reflectors' failover and route availability across representative client pairs.
- Monitor hidden BGP routes and next-hop resolution after core topology changes.
- Continuously check advertised prefix counts against each customer's contracted service.
Explanation
Correct Answer
D:Continuously check advertised prefix counts against each customer's contracted service. The control limits repetition of the described root condition: BGP export policy determines whether a neighbor receives a default route or unrestricted more-specific NLRI. During audits, confirm: The neighbor receives the intended default and no unauthorized full-table routes.
Incorrect Answers
A:Review next-hop and attribute comparability before adding paths to ECMP service. This is a plausible preventive practice for a different BGP condition, specifically BGP multipath prerequisites. BGP multipath requires compatible candidate paths and implementation-specific settings in addition to multiple route advertisements. In this scenario, however, the distinguishing issue is BGP outbound default-only policy and the confirming observation is: The neighbor receives the intended default and no unauthorized full-table routes.
B:Test reflectors' failover and route availability across representative client pairs. This is a plausible preventive practice for a different BGP condition, specifically BGP route reflector scaling. Route reflection reduces the need for every IBGP router to maintain direct sessions to every other IBGP router. In this scenario, however, the distinguishing issue is BGP outbound default-only policy and the confirming observation is: The neighbor receives the intended default and no unauthorized full-table routes.
C: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 outbound default-only policy and the confirming observation is: The neighbor receives the intended default and no unauthorized full-table routes.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests