Question 410
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: A customer route marked invalid by the origin validation process is still accepted into a production export policy that was meant to reject invalid origins. Which operational control would best prevent a recurrence of this exact failure mode?
- Maintain positive and negative example AS paths alongside policy expressions.
- Track ROA changes and test policy for valid, invalid and unknown states.
- Include community-preservation tests in interdomain policy QA.
- Document business exit priorities and verify local preference after peer resets.
Explanation
Correct Answer
B:Track ROA changes and test policy for valid, invalid and unknown states. The control limits repetition of the described root condition: RPKI origin validation classifies prefix-origin authorization, but routing behavior depends on operational policy decisions. During audits, confirm: Routes with invalid origin state are rejected under the agreed policy while valid routes remain accepted.
Incorrect Answers
A:Maintain positive and negative example AS paths alongside policy expressions. This is a plausible preventive practice for a different BGP condition, specifically AS-path regex filter. BGP AS-path regex syntax and anchoring determine whether matching targets the origin AS, any traversed AS, or the entire sequence. In this scenario, however, the distinguishing issue is BGP RPKI origin validation policy and the confirming observation is: Routes with invalid origin state are rejected under the agreed policy while valid routes remain accepted.
C:Include community-preservation tests in interdomain policy QA. This is a plausible preventive practice for a different BGP condition, specifically Community overwrite versus add. Replacing an entire community attribute discards previously attached values, unlike adding a new value to the set. In this scenario, however, the distinguishing issue is BGP RPKI origin validation policy and the confirming observation is: Routes with invalid origin state are rejected under the agreed policy while valid routes remain accepted.
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 RPKI origin validation policy and the confirming observation is: Routes with invalid origin state are rejected under the agreed policy while valid routes remain accepted.
Question 411
During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: A service provider classifies routes for internal blackhole handling but a broad community match accidentally includes customer ordinary transit prefixes. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect the exact AS-path expression and run route-policy match tests on sample path strings.
- Inspect FlowSpec destination-prefix and protocol/port components and active actions.
- Check whether blackhole actions match the exact planned community values rather than a loose regex pattern.
- Inspect the BGP route next-hop value and its recursive resolution in the active IGP or label transport.
Explanation
Correct Answer
C:Check whether blackhole actions match the exact planned community values rather than a loose regex pattern. This check examines the decisive condition for BGP bogon community tagging before any unrelated changes are made. The underlying mechanism is: Community-based blackholing is a policy convention and should only trigger for explicitly authorized tagged routes. The confirming observation is: A controlled test /32 or /128 can be dropped while ordinary customer routes remain unaffected.
Incorrect Answers
A:Inspect the exact AS-path expression and run route-policy match tests on sample path strings. This is a plausible diagnostic check for a different BGP condition, specifically AS-path regex filter. BGP AS-path regex syntax and anchoring determine whether matching targets the origin AS, any traversed AS, or the entire sequence. In this scenario, however, the distinguishing issue is BGP bogon community tagging and the confirming observation is: A controlled test /32 or /128 can be dropped while ordinary customer routes remain unaffected.
B:Inspect FlowSpec destination-prefix and protocol/port components and active actions. This is a plausible diagnostic check for a different BGP condition, specifically FlowSpec overbroad destination prefix. A FlowSpec rule's match components directly determine which packets receive the advertised mitigation. In this scenario, however, the distinguishing issue is BGP bogon community tagging and the confirming observation is: A controlled test /32 or /128 can be dropped while ordinary customer routes remain unaffected.
D: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 bogon community tagging and the confirming observation is: A controlled test /32 or /128 can be dropped while ordinary customer routes remain unaffected.
Question 412
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: A service provider classifies routes for internal blackhole handling but a broad community match accidentally includes customer ordinary transit prefixes. Which routing or service mechanism best explains the reported behavior?
- Route aggregation can trade detailed reachability for a broad advertisement, so contributor rules and discard behavior govern correctness.
- Junos chooses among protocols using route preference before BGP's local preference decides among BGP candidates.
- BGP AS-path regex syntax and anchoring determine whether matching targets the origin AS, any traversed AS, or the entire sequence.
- Community-based blackholing is a policy convention and should only trigger for explicitly authorized tagged routes.
Explanation
Correct Answer
D:Community-based blackholing is a policy convention and should only trigger for explicitly authorized tagged routes. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: A controlled test /32 or /128 can be dropped while ordinary customer routes remain unaffected. The targeted correction is: Tighten community match and ingress authorization for blackhole signaling.
Incorrect Answers
A:Route aggregation can trade detailed reachability for a broad advertisement, so contributor rules and discard behavior govern correctness. This is a plausible protocol explanation 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 bogon community tagging and the confirming observation is: A controlled test /32 or /128 can be dropped while ordinary customer routes remain unaffected.
B:Junos chooses among protocols using route preference before BGP's local preference decides among BGP candidates. This is a plausible protocol explanation for a different BGP condition, specifically Route preference versus BGP local-pref. Junos chooses among protocols using route preference before BGP's local preference decides among BGP candidates. In this scenario, however, the distinguishing issue is BGP bogon community tagging and the confirming observation is: A controlled test /32 or /128 can be dropped while ordinary customer routes remain unaffected.
C:BGP AS-path regex syntax and anchoring determine whether matching targets the origin AS, any traversed AS, or the entire sequence. This is a plausible protocol explanation for a different BGP condition, specifically AS-path regex filter. BGP AS-path regex syntax and anchoring determine whether matching targets the origin AS, any traversed AS, or the entire sequence. In this scenario, however, the distinguishing issue is BGP bogon community tagging and the confirming observation is: A controlled test /32 or /128 can be dropped while ordinary customer routes remain unaffected.
Question 413
During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: A service provider classifies routes for internal blackhole handling but a broad community match accidentally includes customer ordinary transit prefixes. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- A controlled test /32 or /128 can be dropped while ordinary customer routes remain unaffected.
- The aggregate exists only under documented reachable-contributor conditions and traffic has valid forwarding paths.
- The installed path matches the lower global preference unless that policy is intentionally changed.
- Known prohibited-origin paths are rejected while legitimate transit paths remain eligible.
Explanation
Correct Answer
A:A controlled test /32 or /128 can be dropped while ordinary customer routes remain unaffected. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Community-based blackholing is a policy convention and should only trigger for explicitly authorized tagged routes.
Incorrect Answers
B:The aggregate exists only under documented reachable-contributor conditions and traffic has valid forwarding paths. This is a plausible observed evidence 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 bogon community tagging and the confirming observation is: A controlled test /32 or /128 can be dropped while ordinary customer routes remain unaffected.
C:The installed path matches the lower global preference unless that policy is intentionally changed. This is a plausible observed evidence for a different BGP condition, specifically Route preference versus BGP local-pref. Junos chooses among protocols using route preference before BGP's local preference decides among BGP candidates. In this scenario, however, the distinguishing issue is BGP bogon community tagging and the confirming observation is: A controlled test /32 or /128 can be dropped while ordinary customer routes remain unaffected.
D:Known prohibited-origin paths are rejected while legitimate transit paths remain eligible. This is a plausible observed evidence for a different BGP condition, specifically AS-path regex filter. BGP AS-path regex syntax and anchoring determine whether matching targets the origin AS, any traversed AS, or the entire sequence. In this scenario, however, the distinguishing issue is BGP bogon community tagging and the confirming observation is: A controlled test /32 or /128 can be dropped while ordinary customer routes remain unaffected.
Question 414
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: A service provider classifies routes for internal blackhole handling but a broad community match accidentally includes customer ordinary transit prefixes. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Adjust aggregate generation and forwarding/discard controls to match actual service coverage.
- Tighten community match and ingress authorization for blackhole signaling.
- Change a documented route preference or routing-policy design if protocol precedence must differ.
- Replace the broad expression with the intended anchored AS-path match.
Explanation
Correct Answer
B:Tighten community match and ingress authorization for blackhole signaling. The change addresses the root behavior described here: Community-based blackholing is a policy convention and should only trigger for explicitly authorized tagged routes. Verify success with: A controlled test /32 or /128 can be dropped while ordinary customer routes remain unaffected.
Incorrect Answers
A:Adjust aggregate generation and forwarding/discard controls to match actual service coverage. This is a plausible configuration or operational fix 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 bogon community tagging and the confirming observation is: A controlled test /32 or /128 can be dropped while ordinary customer routes remain unaffected.
C:Change a documented route preference or routing-policy design if protocol precedence must differ. This is a plausible configuration or operational fix for a different BGP condition, specifically Route preference versus BGP local-pref. Junos chooses among protocols using route preference before BGP's local preference decides among BGP candidates. In this scenario, however, the distinguishing issue is BGP bogon community tagging and the confirming observation is: A controlled test /32 or /128 can be dropped while ordinary customer routes remain unaffected.
D:Replace the broad expression with the intended anchored AS-path match. This is a plausible configuration or operational fix for a different BGP condition, specifically AS-path regex filter. BGP AS-path regex syntax and anchoring determine whether matching targets the origin AS, any traversed AS, or the entire sequence. In this scenario, however, the distinguishing issue is BGP bogon community tagging and the confirming observation is: A controlled test /32 or /128 can be dropped while ordinary customer routes remain unaffected.
Question 415
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: A service provider classifies routes for internal blackhole handling but a broad community match accidentally includes customer ordinary transit prefixes. Which operational control would best prevent a recurrence of this exact failure mode?
- Test loss of the final contributor and partial site outage before advertising aggregates.
- Check interaction between RIB preference and BGP local preference in mixed-protocol reviews.
- Require per-peer tag permission tests and change logs before enabling blackhole services.
- Maintain positive and negative example AS paths alongside policy expressions.
Explanation
Correct Answer
C:Require per-peer tag permission tests and change logs before enabling blackhole services. The control limits repetition of the described root condition: Community-based blackholing is a policy convention and should only trigger for explicitly authorized tagged routes. During audits, confirm: A controlled test /32 or /128 can be dropped while ordinary customer routes remain unaffected.
Incorrect Answers
A:Test loss of the final contributor and partial site outage before advertising aggregates. This is a plausible preventive practice 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 bogon community tagging and the confirming observation is: A controlled test /32 or /128 can be dropped while ordinary customer routes remain unaffected.
B:Check interaction between RIB preference and BGP local preference in mixed-protocol reviews. This is a plausible preventive practice for a different BGP condition, specifically Route preference versus BGP local-pref. Junos chooses among protocols using route preference before BGP's local preference decides among BGP candidates. In this scenario, however, the distinguishing issue is BGP bogon community tagging and the confirming observation is: A controlled test /32 or /128 can be dropped while ordinary customer routes remain unaffected.
D:Maintain positive and negative example AS paths alongside policy expressions. This is a plausible preventive practice for a different BGP condition, specifically AS-path regex filter. BGP AS-path regex syntax and anchoring determine whether matching targets the origin AS, any traversed AS, or the entire sequence. In this scenario, however, the distinguishing issue is BGP bogon community tagging and the confirming observation is: A controlled test /32 or /128 can be dropped while ordinary customer routes remain unaffected.
Question 416
During a service-provider escalation, 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 targeted check most directly distinguishes the likely cause before a configuration change?
- Examine prefix-match length logic, policy order and received route attributes.
- Compare RR best-path IGP cost calculations with actual client-to-exit metrics.
- Check prefix count, the configured maximum-prefix threshold and received-route update logs.
- Inspect aggregate route generation conditions and the set of eligible active contributors.
Explanation
Correct Answer
D:Inspect aggregate route generation conditions and the set of eligible active contributors. This check examines the decisive condition for BGP aggregation hides contributors before any unrelated changes are made. The underlying mechanism is: Route aggregation can trade detailed reachability for a broad advertisement, so contributor rules and discard behavior govern correctness. The confirming observation is: The aggregate exists only under documented reachable-contributor conditions and traffic has valid forwarding paths.
Incorrect Answers
A:Examine prefix-match length logic, policy order and received route attributes. This is a plausible diagnostic check 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.
B:Compare RR best-path IGP cost calculations with actual client-to-exit metrics. This is a plausible diagnostic check 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.
C:Check prefix count, the configured maximum-prefix threshold and received-route update logs. This is a plausible diagnostic check for a different BGP condition, specifically BGP maximum-prefix threshold. Maximum-prefix controls can intentionally protect a BGP session or router from excessive received prefixes. In this scenario, however, the distinguishing issue is BGP aggregation hides contributors and the confirming observation is: The aggregate exists only under documented reachable-contributor conditions and traffic has valid forwarding paths.
Question 417
During a new PE-router service turn-up, 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 routing or service mechanism best explains the reported behavior?
- Route aggregation can trade detailed reachability for a broad advertisement, so contributor rules and discard behavior govern correctness.
- Prefix matching can include unintended more-specifics when the term is broader than the intended exact route requirement.
- A standard reflector chooses its best path from its own topology perspective, which can differ from widely distributed clients.
- Maximum-prefix controls can intentionally protect a BGP session or router from excessive received prefixes.
Explanation
Correct Answer
A:Route aggregation can trade detailed reachability for a broad advertisement, so contributor rules and discard behavior govern correctness. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The aggregate exists only under documented reachable-contributor conditions and traffic has valid forwarding paths. The targeted correction is: Adjust aggregate generation and forwarding/discard controls to match actual service coverage.
Incorrect Answers
B: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 aggregation hides contributors and the confirming observation is: The aggregate exists only under documented reachable-contributor conditions and traffic has valid forwarding paths.
C:A standard reflector chooses its best path from its own topology perspective, which can differ from widely distributed clients. This is a plausible protocol explanation 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.
D: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 aggregation hides contributors and the confirming observation is: The aggregate exists only under documented reachable-contributor conditions and traffic has valid forwarding paths.
Question 418
During a customer VPN change window, 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. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The prohibited route is hidden or rejected while the specifically approved routes remain installed.
- The aggregate exists only under documented reachable-contributor conditions and traffic has valid forwarding paths.
- Client route selection reflects an intended per-POP or supported optimal-reflection policy.
- After correcting the peer route leak, the accepted count falls below the configured limit and the session remains healthy.
Explanation
Correct Answer
B:The aggregate exists only under documented reachable-contributor conditions and traffic has valid forwarding paths. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Route aggregation can trade detailed reachability for a broad advertisement, so contributor rules and discard behavior govern correctness.
Incorrect Answers
A: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 aggregation hides contributors and the confirming observation is: The aggregate exists only under documented reachable-contributor conditions and traffic has valid forwarding paths.
C:Client route selection reflects an intended per-POP or supported optimal-reflection policy. This is a plausible observed evidence 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.
D: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 aggregation hides contributors and the confirming observation is: The aggregate exists only under documented reachable-contributor conditions and traffic has valid forwarding paths.
Question 419
During a core-routing migration rehearsal, 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 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.
- Constrain the prefix list or route-filter match semantics to the intended prefix lengths.
- Adjust aggregate generation and forwarding/discard controls to match actual service coverage.
- Use suitable reflector placement or a supported optimal route reflection approach if topology diversity requires it.
Explanation
Correct Answer
C:Adjust aggregate generation and forwarding/discard controls to match actual service coverage. The change addresses the root behavior described here: Route aggregation can trade detailed reachability for a broad advertisement, so contributor rules and discard behavior govern correctness. Verify success with: The aggregate exists only under documented reachable-contributor conditions and traffic has valid forwarding paths.
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 aggregation hides contributors and the confirming observation is: The aggregate exists only under documented reachable-contributor conditions and traffic has valid forwarding paths.
B: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 aggregation hides contributors and the confirming observation is: The aggregate exists only under documented reachable-contributor conditions and traffic has valid forwarding paths.
D:Use suitable reflector placement or a supported optimal route reflection approach if topology diversity requires it. This is a plausible configuration or operational fix 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.
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.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests