Question 290
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: A routing policy sets a new BGP community but accidentally removes the customer's preexisting service tag used downstream. Which operational control would best prevent a recurrence of this exact failure mode?
- Continuously check advertised prefix counts against each customer's contracted service.
- Include community-preservation tests in interdomain policy QA.
- Review inherited policy on a per-neighbor basis before moving BGP sessions.
- Audit path-length and local preference before changing peering relationships.
Explanation
Correct Answer
B:Include community-preservation tests in interdomain policy QA. The control limits repetition of the described root condition: Replacing an entire community attribute discards previously attached values, unlike adding a new value to the set. During audits, confirm: The downstream route retains both intended service and policy tags after the change.
Incorrect Answers
A:Continuously check advertised prefix counts against each customer's contracted service. This is a plausible preventive practice for a different BGP condition, specifically BGP outbound default-only policy. BGP export policy determines whether a neighbor receives a default route or unrestricted more-specific NLRI. In this scenario, however, the distinguishing issue is Community overwrite versus add and the confirming observation is: The downstream route retains both intended service and policy tags after the change.
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 Community overwrite versus add and the confirming observation is: The downstream route retains both intended service and policy tags after the change.
D: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 Community overwrite versus add and the confirming observation is: The downstream route retains both intended service and policy tags after the change.
Question 291
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: An export filter rejects routes whose origin AS is in a prohibited list, but a permissive regular expression also rejects legitimate transit paths. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare origin codes and verify no earlier tie-break attributes differ.
- Compare local preference on the competing routes and verify their next hops resolve.
- Inspect the exact AS-path expression and run route-policy match tests on sample path strings.
- Inspect route validation state and ordered import or export terms using that state.
Explanation
Correct Answer
C:Inspect the exact AS-path expression and run route-policy match tests on sample path strings. This check examines the decisive condition for AS-path regex filter before any unrelated changes are made. The underlying mechanism is: BGP AS-path regex syntax and anchoring determine whether matching targets the origin AS, any traversed AS, or the entire sequence. The confirming observation is: Known prohibited-origin paths are rejected while legitimate transit paths remain eligible.
Incorrect Answers
A: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 AS-path regex filter and the confirming observation is: Known prohibited-origin paths are rejected while legitimate transit paths remain eligible.
B: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 AS-path regex filter and the confirming observation is: Known prohibited-origin paths are rejected while legitimate transit paths remain eligible.
D:Inspect route validation state and ordered import or export terms using that state. This is a plausible diagnostic check for a different BGP condition, specifically BGP RPKI origin validation policy. RPKI origin validation classifies prefix-origin authorization, but routing behavior depends on operational policy decisions. In this scenario, however, the distinguishing issue is AS-path regex filter and the confirming observation is: Known prohibited-origin paths are rejected while legitimate transit paths remain eligible.
Question 292
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: An export filter rejects routes whose origin AS is in a prohibited list, but a permissive regular expression also rejects legitimate transit paths. Which routing or service mechanism best explains the reported behavior?
- At the applicable BGP selection stage, lower origin-type value (IGP before incomplete) is preferred.
- Within an AS, higher BGP local preference is selected ahead of AS-path length when paths are otherwise eligible.
- RPKI origin validation classifies prefix-origin authorization, but routing behavior depends on operational policy decisions.
- BGP AS-path regex syntax and anchoring determine whether matching targets the origin AS, any traversed AS, or the entire sequence.
Explanation
Correct Answer
D:BGP AS-path regex syntax and anchoring determine whether matching targets the origin AS, any traversed AS, or the entire sequence. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Known prohibited-origin paths are rejected while legitimate transit paths remain eligible. The targeted correction is: Replace the broad expression with the intended anchored AS-path match.
Incorrect Answers
A: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 AS-path regex filter and the confirming observation is: Known prohibited-origin paths are rejected while legitimate transit paths remain eligible.
B: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 AS-path regex filter and the confirming observation is: Known prohibited-origin paths are rejected while legitimate transit paths remain eligible.
C:RPKI origin validation classifies prefix-origin authorization, but routing behavior depends on operational policy decisions. This is a plausible protocol explanation for a different BGP condition, specifically BGP RPKI origin validation policy. RPKI origin validation classifies prefix-origin authorization, but routing behavior depends on operational policy decisions. In this scenario, however, the distinguishing issue is AS-path regex filter and the confirming observation is: Known prohibited-origin paths are rejected while legitimate transit paths remain eligible.
Question 293
During a core-routing migration rehearsal, an HPE Juniper Networking engineer investigates this situation: An export filter rejects routes whose origin AS is in a prohibited list, but a permissive regular expression also rejects legitimate transit paths. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Known prohibited-origin paths are rejected while legitimate transit paths remain eligible.
- The route with the preferred origin becomes best under otherwise equal higher-priority attributes.
- The chosen active route uses the deliberately higher-local-preference exit while backup remains valid.
- The new neighbor's advertised prefixes and tags match an explicitly reviewed effective configuration.
Explanation
Correct Answer
A:Known prohibited-origin paths are rejected while legitimate transit paths remain eligible. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: BGP AS-path regex syntax and anchoring determine whether matching targets the origin AS, any traversed AS, or the entire sequence.
Incorrect Answers
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 AS-path regex filter and the confirming observation is: Known prohibited-origin paths are rejected while legitimate transit paths remain eligible.
C: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 AS-path regex filter and the confirming observation is: Known prohibited-origin paths are rejected while legitimate transit paths remain eligible.
D: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 AS-path regex filter and the confirming observation is: Known prohibited-origin paths are rejected while legitimate transit paths remain eligible.
Question 294
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: An export filter rejects routes whose origin AS is in a prohibited list, but a permissive regular expression also rejects legitimate transit paths. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Correct unwanted origin-setting policy if the preferred path must differ.
- Replace the broad expression with the intended anchored AS-path match.
- Use an inbound routing policy to set the desired local preference for approved prefixes.
- Apply the intended validation-state route policy with a monitored exception process.
Explanation
Correct Answer
B:Replace the broad expression with the intended anchored AS-path match. The change addresses the root behavior described here: BGP AS-path regex syntax and anchoring determine whether matching targets the origin AS, any traversed AS, or the entire sequence. Verify success with: Known prohibited-origin paths are rejected while legitimate transit paths remain eligible.
Incorrect Answers
A: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 AS-path regex filter and the confirming observation is: Known prohibited-origin paths are rejected while legitimate transit paths remain eligible.
C: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 AS-path regex filter and the confirming observation is: Known prohibited-origin paths are rejected while legitimate transit paths remain eligible.
D:Apply the intended validation-state route policy with a monitored exception process. This is a plausible configuration or operational fix for a different BGP condition, specifically BGP RPKI origin validation policy. RPKI origin validation classifies prefix-origin authorization, but routing behavior depends on operational policy decisions. In this scenario, however, the distinguishing issue is AS-path regex filter and the confirming observation is: Known prohibited-origin paths are rejected while legitimate transit paths remain eligible.
Question 295
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: An export filter rejects routes whose origin AS is in a prohibited list, but a permissive regular expression also rejects legitimate transit paths. Which operational control would best prevent a recurrence of this exact failure mode?
- Log origin attribute changes when redistributing or aggregating BGP routes.
- Document business exit priorities and verify local preference after peer resets.
- Maintain positive and negative example AS paths alongside policy expressions.
- Track ROA changes and test policy for valid, invalid and unknown states.
Explanation
Correct Answer
C:Maintain positive and negative example AS paths alongside policy expressions. The control limits repetition of the described root condition: BGP AS-path regex syntax and anchoring determine whether matching targets the origin AS, any traversed AS, or the entire sequence. During audits, confirm: Known prohibited-origin paths are rejected while legitimate transit paths remain eligible.
Incorrect Answers
A: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 AS-path regex filter and the confirming observation is: Known prohibited-origin paths are rejected while legitimate transit paths remain eligible.
B: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 AS-path regex filter and the confirming observation is: Known prohibited-origin paths are rejected while legitimate transit paths remain eligible.
D:Track ROA changes and test policy for valid, invalid and unknown states. This is a plausible preventive practice for a different BGP condition, specifically BGP RPKI origin validation policy. RPKI origin validation classifies prefix-origin authorization, but routing behavior depends on operational policy decisions. In this scenario, however, the distinguishing issue is AS-path regex filter and the confirming observation is: Known prohibited-origin paths are rejected while legitimate transit paths remain eligible.
Question 296
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: A full-mesh IBGP design becomes operationally unmanageable as many new PEs join a single autonomous system. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect effective egress prefix filters and advertised-route counts for the customer BGP group.
- Inspect negotiated graceful-restart capability, restart timers and stale route handling.
- Inspect the BGP route next-hop value and its recursive resolution in the active IGP or label transport.
- Count IBGP sessions and assess route reflector client and nonclient adjacency roles.
Explanation
Correct Answer
D:Count IBGP sessions and assess route reflector client and nonclient adjacency roles. This check examines the decisive condition for BGP route reflector scaling before any unrelated changes are made. The underlying mechanism is: Route reflection reduces the need for every IBGP router to maintain direct sessions to every other IBGP router. The confirming observation is: Clients learn permitted routes from the reflector without adding all-to-all IBGP sessions.
Incorrect Answers
A: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 route reflector scaling and the confirming observation is: Clients learn permitted routes from the reflector without adding all-to-all IBGP sessions.
B:Inspect negotiated graceful-restart capability, restart timers and stale route handling. This is a plausible diagnostic check for a different BGP condition, specifically BGP graceful restart stale routes. Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails. In this scenario, however, the distinguishing issue is BGP route reflector scaling and the confirming observation is: Clients learn permitted routes from the reflector without adding all-to-all IBGP sessions.
C: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 route reflector scaling and the confirming observation is: Clients learn permitted routes from the reflector without adding all-to-all IBGP sessions.
Question 297
During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: A full-mesh IBGP design becomes operationally unmanageable as many new PEs join a single autonomous system. Which routing or service mechanism best explains the reported behavior?
- Route reflection reduces the need for every IBGP router to maintain direct sessions to every other IBGP router.
- BGP export policy determines whether a neighbor receives a default route or unrestricted more-specific NLRI.
- Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails.
- BGP path eligibility depends on being able to resolve the advertised next hop; a healthy TCP peering alone does not install the route.
Explanation
Correct Answer
A:Route reflection reduces the need for every IBGP router to maintain direct sessions to every other IBGP router. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Clients learn permitted routes from the reflector without adding all-to-all IBGP sessions. The targeted correction is: Deploy an appropriate redundant route-reflector design with explicit client configuration.
Incorrect Answers
B: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 route reflector scaling and the confirming observation is: Clients learn permitted routes from the reflector without adding all-to-all IBGP sessions.
C:Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails. This is a plausible protocol explanation for a different BGP condition, specifically BGP graceful restart stale routes. Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails. In this scenario, however, the distinguishing issue is BGP route reflector scaling and the confirming observation is: Clients learn permitted routes from the reflector without adding all-to-all IBGP sessions.
D: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 route reflector scaling and the confirming observation is: Clients learn permitted routes from the reflector without adding all-to-all IBGP sessions.
Question 298
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: A full-mesh IBGP design becomes operationally unmanageable as many new PEs join a single autonomous system. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The neighbor receives the intended default and no unauthorized full-table routes.
- Clients learn permitted routes from the reflector without adding all-to-all IBGP sessions.
- The restart completes within negotiated timers or stale routes are safely withdrawn.
- The route changes from hidden or unusable to active when a valid next-hop resolution path is available.
Explanation
Correct Answer
B:Clients learn permitted routes from the reflector without adding all-to-all IBGP sessions. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Route reflection reduces the need for every IBGP router to maintain direct sessions to every other IBGP router.
Incorrect Answers
A: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 route reflector scaling and the confirming observation is: Clients learn permitted routes from the reflector without adding all-to-all IBGP sessions.
C:The restart completes within negotiated timers or stale routes are safely withdrawn. This is a plausible observed evidence for a different BGP condition, specifically BGP graceful restart stale routes. Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails. In this scenario, however, the distinguishing issue is BGP route reflector scaling and the confirming observation is: Clients learn permitted routes from the reflector without adding all-to-all IBGP sessions.
D: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 route reflector scaling and the confirming observation is: Clients learn permitted routes from the reflector without adding all-to-all IBGP sessions.
Question 299
During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: A full-mesh IBGP design becomes operationally unmanageable as many new PEs join a single autonomous system. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Apply a specific default-only export policy at the customer boundary.
- Align graceful restart roles and timer expectations with real forwarding continuity capability.
- Deploy an appropriate redundant route-reflector design with explicit client configuration.
- Restore IGP or transport reachability to the advertised BGP next hop and retain appropriate next-hop policy.
Explanation
Correct Answer
C:Deploy an appropriate redundant route-reflector design with explicit client configuration. The change addresses the root behavior described here: Route reflection reduces the need for every IBGP router to maintain direct sessions to every other IBGP router. Verify success with: Clients learn permitted routes from the reflector without adding all-to-all IBGP sessions.
Incorrect Answers
A: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 route reflector scaling and the confirming observation is: Clients learn permitted routes from the reflector without adding all-to-all IBGP sessions.
B:Align graceful restart roles and timer expectations with real forwarding continuity capability. This is a plausible configuration or operational fix for a different BGP condition, specifically BGP graceful restart stale routes. Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails. In this scenario, however, the distinguishing issue is BGP route reflector scaling and the confirming observation is: Clients learn permitted routes from the reflector without adding all-to-all IBGP sessions.
D: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 route reflector scaling and the confirming observation is: Clients learn permitted routes from the reflector without adding all-to-all IBGP sessions.
Question 300
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: A full-mesh IBGP design becomes operationally unmanageable as many new PEs join a single autonomous system. Which operational control would best prevent a recurrence of this exact failure mode?
- Continuously check advertised prefix counts against each customer's contracted service.
- Test abrupt failure separately from graceful restart to expose stale-route risks.
- Monitor hidden BGP routes and next-hop resolution after core topology changes.
- Test reflectors' failover and route availability across representative client pairs.
Explanation
Correct Answer
D:Test reflectors' failover and route availability across representative client pairs. The control limits repetition of the described root condition: Route reflection reduces the need for every IBGP router to maintain direct sessions to every other IBGP router. During audits, confirm: Clients learn permitted routes from the reflector without adding all-to-all IBGP sessions.
Incorrect Answers
A:Continuously check advertised prefix counts against each customer's contracted service. This is a plausible preventive practice for a different BGP condition, specifically BGP outbound default-only policy. BGP export policy determines whether a neighbor receives a default route or unrestricted more-specific NLRI. In this scenario, however, the distinguishing issue is BGP route reflector scaling and the confirming observation is: Clients learn permitted routes from the reflector without adding all-to-all IBGP sessions.
B:Test abrupt failure separately from graceful restart to expose stale-route risks. This is a plausible preventive practice for a different BGP condition, specifically BGP graceful restart stale routes. Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails. In this scenario, however, the distinguishing issue is BGP route reflector scaling and the confirming observation is: Clients learn permitted routes from the reflector without adding all-to-all IBGP sessions.
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 route reflector scaling and the confirming observation is: Clients learn permitted routes from the reflector without adding all-to-all IBGP sessions.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests