Question 420
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: An aggregation policy advertises a broad prefix even though a critical more-specific contributor has been withdrawn and would black-hole traffic. Which operational control would best prevent a recurrence of this exact failure mode?
- Test representative distant-client best exits when expanding reflector geography.
- Monitor counts versus warning thresholds and rehearse a safe session recovery.
- Run policy tests against boundary subnet lengths before installing route filters.
- Test loss of the final contributor and partial site outage before advertising aggregates.
Explanation
Correct Answer
D:Test loss of the final contributor and partial site outage before advertising aggregates. The control limits repetition of the described root condition: Route aggregation can trade detailed reachability for a broad advertisement, so contributor rules and discard behavior govern correctness. During audits, confirm: The aggregate exists only under documented reachable-contributor conditions and traffic has valid forwarding paths.
Incorrect Answers
A:Test representative distant-client best exits when expanding reflector geography. This is a plausible preventive practice for a different BGP condition, specifically Route-reflector optimal exit perspective. A standard reflector chooses its best path from its own topology perspective, which can differ from widely distributed clients. In this scenario, however, the distinguishing issue is BGP aggregation hides contributors and the confirming observation is: The aggregate exists only under documented reachable-contributor conditions and traffic has valid forwarding paths.
B: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 aggregation hides contributors and the confirming observation is: The aggregate exists only under documented reachable-contributor conditions and traffic has valid forwarding paths.
C: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 aggregation hides contributors and the confirming observation is: The aggregate exists only under documented reachable-contributor conditions and traffic has valid forwarding paths.
Question 421
During an edge-to-core validation, an HPE Juniper Networking engineer investigates this situation: A customer prepends its own AS path on inbound routes but wants to influence how remote networks enter its service. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare the exported AS_PATH seen by external peers and the direction of the prepend policy.
- Verify the intended FlowSpec family, validation controls and match/action encoding before accepting rules.
- Compare origin codes and verify no earlier tie-break attributes differ.
- Inspect RIB active state and the presence of advertise-inactive or equivalent policy controls.
Explanation
Correct Answer
A:Compare the exported AS_PATH seen by external peers and the direction of the prepend policy. This check examines the decisive condition for BGP AS-path prepend direction before any unrelated changes are made. The underlying mechanism is: AS-path prepending changes the path presented outward and may influence remote path choices; inbound modifications do not accomplish the same outward signaling. The confirming observation is: External looking-glass routes show the intended added AS repeats in the advertised path.
Incorrect Answers
B:Verify the intended FlowSpec family, validation controls and match/action encoding before accepting rules. This is a plausible diagnostic check for a different BGP condition, specifically BGP flow specification mitigation. BGP FlowSpec distributes traffic-match rules with associated actions through BGP control-plane updates, subject to validation and platform support. In this scenario, however, the distinguishing issue is BGP AS-path prepend direction and the confirming observation is: External looking-glass routes show the intended added AS repeats in the advertised path.
C:Compare origin codes and verify no earlier tie-break attributes differ. This is a plausible diagnostic check 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 AS-path prepend direction and the confirming observation is: External looking-glass routes show the intended added AS repeats in the advertised path.
D:Inspect RIB active state and the presence of advertise-inactive or equivalent policy controls. This is a plausible diagnostic check for a different BGP condition, specifically Junos advertise-inactive semantics. BGP normally exports eligible active routes; advertise-inactive has bounded semantics and may permit a nonactive BGP path when a non-BGP route is active. In this scenario, however, the distinguishing issue is BGP AS-path prepend direction and the confirming observation is: External looking-glass routes show the intended added AS repeats in the advertised path.
Question 422
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: A customer prepends its own AS path on inbound routes but wants to influence how remote networks enter its service. Which routing or service mechanism best explains the reported behavior?
- BGP FlowSpec distributes traffic-match rules with associated actions through BGP control-plane updates, subject to validation and platform support.
- AS-path prepending changes the path presented outward and may influence remote path choices; inbound modifications do not accomplish the same outward signaling.
- At the applicable BGP selection stage, lower origin-type value (IGP before incomplete) is preferred.
- BGP normally exports eligible active routes; advertise-inactive has bounded semantics and may permit a nonactive BGP path when a non-BGP route is active.
Explanation
Correct Answer
B:AS-path prepending changes the path presented outward and may influence remote path choices; inbound modifications do not accomplish the same outward signaling. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: External looking-glass routes show the intended added AS repeats in the advertised path. The targeted correction is: Apply controlled prepend on the chosen outbound route advertisements while documenting remote policy uncertainties.
Incorrect Answers
A:BGP FlowSpec distributes traffic-match rules with associated actions through BGP control-plane updates, subject to validation and platform support. This is a plausible protocol explanation for a different BGP condition, specifically BGP flow specification mitigation. BGP FlowSpec distributes traffic-match rules with associated actions through BGP control-plane updates, subject to validation and platform support. In this scenario, however, the distinguishing issue is BGP AS-path prepend direction and the confirming observation is: External looking-glass routes show the intended added AS repeats in the advertised path.
C:At the applicable BGP selection stage, lower origin-type value (IGP before incomplete) is preferred. This is a plausible protocol explanation 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 AS-path prepend direction and the confirming observation is: External looking-glass routes show the intended added AS repeats in the advertised path.
D:BGP normally exports eligible active routes; advertise-inactive has bounded semantics and may permit a nonactive BGP path when a non-BGP route is active. This is a plausible protocol explanation for a different BGP condition, specifically Junos advertise-inactive semantics. BGP normally exports eligible active routes; advertise-inactive has bounded semantics and may permit a nonactive BGP path when a non-BGP route is active. In this scenario, however, the distinguishing issue is BGP AS-path prepend direction and the confirming observation is: External looking-glass routes show the intended added AS repeats in the advertised path.
Question 423
During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: A customer prepends its own AS path on inbound routes but wants to influence how remote networks enter its service. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The authorized FlowSpec rule appears on target routers and affects only test traffic matching its criteria.
- The route with the preferred origin becomes best under otherwise equal higher-priority attributes.
- External looking-glass routes show the intended added AS repeats in the advertised path.
- Neighbor advertisements include the intended nonactive BGP path only under supported and explicitly reviewed conditions.
Explanation
Correct Answer
C:External looking-glass routes show the intended added AS repeats in the advertised path. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: AS-path prepending changes the path presented outward and may influence remote path choices; inbound modifications do not accomplish the same outward signaling.
Incorrect Answers
A:The authorized FlowSpec rule appears on target routers and affects only test traffic matching its criteria. This is a plausible observed evidence for a different BGP condition, specifically BGP flow specification mitigation. BGP FlowSpec distributes traffic-match rules with associated actions through BGP control-plane updates, subject to validation and platform support. In this scenario, however, the distinguishing issue is BGP AS-path prepend direction and the confirming observation is: External looking-glass routes show the intended added AS repeats in the advertised path.
B:The route with the preferred origin becomes best under otherwise equal higher-priority attributes. This is a plausible observed evidence 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 AS-path prepend direction and the confirming observation is: External looking-glass routes show the intended added AS repeats in the advertised path.
D:Neighbor advertisements include the intended nonactive BGP path only under supported and explicitly reviewed conditions. This is a plausible observed evidence for a different BGP condition, specifically Junos advertise-inactive semantics. BGP normally exports eligible active routes; advertise-inactive has bounded semantics and may permit a nonactive BGP path when a non-BGP route is active. In this scenario, however, the distinguishing issue is BGP AS-path prepend direction and the confirming observation is: External looking-glass routes show the intended added AS repeats in the advertised path.
Question 424
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: A customer prepends its own AS path on inbound routes but wants to influence how remote networks enter its service. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Deploy controlled FlowSpec import validation and a bounded mitigation action for the exact attack signature.
- Correct unwanted origin-setting policy if the preferred path must differ.
- Use the documented advertise-inactive behavior where required, with loop and forwarding consistency checks.
- Apply controlled prepend on the chosen outbound route advertisements while documenting remote policy uncertainties.
Explanation
Correct Answer
D:Apply controlled prepend on the chosen outbound route advertisements while documenting remote policy uncertainties. The change addresses the root behavior described here: AS-path prepending changes the path presented outward and may influence remote path choices; inbound modifications do not accomplish the same outward signaling. Verify success with: External looking-glass routes show the intended added AS repeats in the advertised path.
Incorrect Answers
A:Deploy controlled FlowSpec import validation and a bounded mitigation action for the exact attack signature. This is a plausible configuration or operational fix for a different BGP condition, specifically BGP flow specification mitigation. BGP FlowSpec distributes traffic-match rules with associated actions through BGP control-plane updates, subject to validation and platform support. In this scenario, however, the distinguishing issue is BGP AS-path prepend direction and the confirming observation is: External looking-glass routes show the intended added AS repeats in the advertised path.
B:Correct unwanted origin-setting policy if the preferred path must differ. This is a plausible configuration or operational fix 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 AS-path prepend direction and the confirming observation is: External looking-glass routes show the intended added AS repeats in the advertised path.
C:Use the documented advertise-inactive behavior where required, with loop and forwarding consistency checks. This is a plausible configuration or operational fix for a different BGP condition, specifically Junos advertise-inactive semantics. BGP normally exports eligible active routes; advertise-inactive has bounded semantics and may permit a nonactive BGP path when a non-BGP route is active. In this scenario, however, the distinguishing issue is BGP AS-path prepend direction and the confirming observation is: External looking-glass routes show the intended added AS repeats in the advertised path.
Question 425
During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: A customer prepends its own AS path on inbound routes but wants to influence how remote networks enter its service. Which operational control would best prevent a recurrence of this exact failure mode?
- Monitor actual incoming traffic after changes; do not assume prepend guarantees deterministic remote selection.
- Enforce expiry, approval and emergency rollback for distributed traffic filters.
- Log origin attribute changes when redistributing or aggregating BGP routes.
- Document business exit priorities and verify local preference after peer resets.
Explanation
Correct Answer
A:Monitor actual incoming traffic after changes; do not assume prepend guarantees deterministic remote selection. The control limits repetition of the described root condition: AS-path prepending changes the path presented outward and may influence remote path choices; inbound modifications do not accomplish the same outward signaling. During audits, confirm: External looking-glass routes show the intended added AS repeats in the advertised path.
Incorrect Answers
B:Enforce expiry, approval and emergency rollback for distributed traffic filters. This is a plausible preventive practice for a different BGP condition, specifically BGP flow specification mitigation. BGP FlowSpec distributes traffic-match rules with associated actions through BGP control-plane updates, subject to validation and platform support. In this scenario, however, the distinguishing issue is BGP AS-path prepend direction and the confirming observation is: External looking-glass routes show the intended added AS repeats in the advertised path.
C: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 AS-path prepend direction and the confirming observation is: External looking-glass routes show the intended added AS repeats in the advertised path.
D:Document business exit priorities and verify local preference after peer resets. This is a plausible preventive practice 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 AS-path prepend direction and the confirming observation is: External looking-glass routes show the intended added AS repeats in the advertised path.
Question 426
During an inter-POP failover test, 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 targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect negotiated hold time, actual keepalive reception and reset reason.
- Inspect local preference and AS-path ranking before interpreting MED.
- Inspect the effective group and neighbor policy hierarchy rather than only the neighbor stanza.
- Inspect effective egress prefix filters and advertised-route counts for the customer BGP group.
Explanation
Correct Answer
B:Inspect local preference and AS-path ranking before interpreting MED. This check examines the decisive condition for BGP MED versus customer preferences before any unrelated changes are made. The underlying mechanism is: MED is considered only after more-preferred BGP attributes have been evaluated under configured comparison rules. The confirming observation is: The observed best path follows the documented attribute order rather than a stand-alone MED value.
Incorrect Answers
A: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 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: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 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:Inspect effective egress prefix filters and advertised-route counts for the customer BGP group. This is a plausible diagnostic check for a different BGP condition, specifically BGP outbound default-only policy. BGP export policy determines whether a neighbor receives a default route or unrestricted more-specific NLRI. In this scenario, however, the distinguishing issue is BGP 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 427
During a control-plane reliability review, 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 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.
- MED is considered only after more-preferred BGP attributes have been evaluated under configured comparison rules.
- BGP export policy determines whether a neighbor receives a default route or unrestricted more-specific NLRI.
Explanation
Correct Answer
C:MED is considered only after more-preferred BGP attributes have been evaluated under configured comparison rules. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The observed best path follows the documented attribute order rather than a stand-alone MED value. The targeted correction is: Align local preference first or document why MED should not override a business routing policy.
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 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.
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 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:BGP export policy determines whether a neighbor receives a default route or unrestricted more-specific NLRI. This is a plausible protocol explanation for a different BGP condition, specifically BGP outbound default-only policy. BGP export policy determines whether a neighbor receives a default route or unrestricted more-specific NLRI. In this scenario, however, the distinguishing issue is BGP 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 428
During a service-provider escalation, 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. 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 new neighbor's advertised prefixes and tags match an explicitly reviewed effective configuration.
- The neighbor receives the intended default and no unauthorized full-table routes.
- The observed best path follows the documented attribute order rather than a stand-alone MED value.
Explanation
Correct Answer
D:The observed best path follows the documented attribute order rather than a stand-alone MED value. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: MED is considered only after more-preferred BGP attributes have been evaluated under configured comparison rules.
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 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.
B: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 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:The neighbor receives the intended default and no unauthorized full-table routes. This is a plausible observed evidence for a different BGP condition, specifically BGP outbound default-only policy. BGP export policy determines whether a neighbor receives a default route or unrestricted more-specific NLRI. In this scenario, however, the distinguishing issue is BGP 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 429
During a new PE-router service turn-up, 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 response or focused corrective action best addresses this situation without changing unrelated components?
- Align local preference first or document why MED should not override a business routing policy.
- Restore transport reliability and choose compatible BGP timers for the intended failure-detection budget.
- Correct unwanted origin-setting policy if the preferred path must differ.
- Apply a specific default-only export policy at the customer boundary.
Explanation
Correct Answer
A:Align local preference first or document why MED should not override a business routing policy. The change addresses the root behavior described here: MED is considered only after more-preferred BGP attributes have been evaluated under configured comparison rules. Verify success with: The observed best path follows the documented attribute order rather than a stand-alone MED value.
Incorrect Answers
B: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 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:Correct unwanted origin-setting policy if the preferred path must differ. This is a plausible configuration or operational fix 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.
D:Apply a specific default-only export policy at the customer boundary. This is a plausible configuration or operational fix for a different BGP condition, specifically BGP outbound default-only policy. BGP export policy determines whether a neighbor receives a default route or unrestricted more-specific NLRI. In this scenario, however, the distinguishing issue is BGP 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 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.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests