Question 370
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: A newly distributed FlowSpec rule drops legitimate customer traffic because its destination match covers an entire customer aggregate instead of one attacked host. Which operational control would best prevent a recurrence of this exact failure mode?
- Run policy tests against boundary subnet lengths before installing route filters.
- Test each rule against harmless nonmatching flows and maintain a rapid withdraw procedure.
- Validate client-to-client route propagation in route-reflector regression tests.
- Review inherited policy on a per-neighbor basis before moving BGP sessions.
Explanation
Correct Answer
B:Test each rule against harmless nonmatching flows and maintain a rapid withdraw procedure. The control limits repetition of the described root condition: A FlowSpec rule's match components directly determine which packets receive the advertised mitigation. During audits, confirm: Test traffic to unaffected hosts remains forwarded while traffic to the attacked destination matches the intended action.
Incorrect Answers
A: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 FlowSpec overbroad destination prefix and the confirming observation is: Test traffic to unaffected hosts remains forwarded while traffic to the attacked destination matches the intended action.
C:Validate client-to-client route propagation in route-reflector regression tests. This is a plausible preventive practice for a different BGP condition, specifically Route-reflector client reflection rule. Route-reflection rules distinguish routes received from clients and nonclients; misclassified clients may prevent intended redistribution. In this scenario, however, the distinguishing issue is FlowSpec overbroad destination prefix and the confirming observation is: Test traffic to unaffected hosts remains forwarded while traffic to the attacked destination matches the intended action.
D: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 FlowSpec overbroad destination prefix and the confirming observation is: Test traffic to unaffected hosts remains forwarded while traffic to the attacked destination matches the intended action.
Question 371
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: IPv4 unicast routes exchange normally with a peer, but VPNv4 or EVPN NLRI never appears in received routes. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Trace the route's active status and ordered export policy terms for that neighbor.
- Inspect the BGP route next-hop value and its recursive resolution in the active IGP or label transport.
- Inspect negotiated address families and MP-BGP capabilities on the relevant session.
- Compare the configured peer-AS and the AS advertised in the remote OPEN message.
Explanation
Correct Answer
C:Inspect negotiated address families and MP-BGP capabilities on the relevant session. This check examines the decisive condition for Multiprotocol BGP family omission before any unrelated changes are made. The underlying mechanism is: A BGP session being Established for one family does not guarantee that another address family was negotiated. The confirming observation is: Both peers negotiate the intended family and the corresponding NLRI arrives after configuration.
Incorrect Answers
A:Trace the route's active status and ordered export policy terms for that neighbor. This is a plausible diagnostic check for a different BGP condition, specifically BGP outbound route policy reject. Export policy explicitly determines which active routes BGP may advertise; local route presence alone is not export approval. In this scenario, however, the distinguishing issue is Multiprotocol BGP family omission and the confirming observation is: Both peers negotiate the intended family and the corresponding NLRI arrives after configuration.
B:Inspect the BGP route next-hop value and its recursive resolution in the active IGP or label transport. This is a plausible diagnostic check for a different BGP condition, specifically IBGP next-hop unresolvable. BGP path eligibility depends on being able to resolve the advertised next hop; a healthy TCP peering alone does not install the route. In this scenario, however, the distinguishing issue is Multiprotocol BGP family omission and the confirming observation is: Both peers negotiate the intended family and the corresponding NLRI arrives after configuration.
D:Compare the configured peer-AS and the AS advertised in the remote OPEN message. This is a plausible diagnostic check for a different BGP condition, specifically BGP wrong remote AS. BGP OPEN validates autonomous-system identity; a peer-AS mismatch prevents a normal established session. In this scenario, however, the distinguishing issue is Multiprotocol BGP family omission and the confirming observation is: Both peers negotiate the intended family and the corresponding NLRI arrives after configuration.
Question 372
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: IPv4 unicast routes exchange normally with a peer, but VPNv4 or EVPN NLRI never appears in received routes. Which routing or service mechanism best explains the reported behavior?
- Export policy explicitly determines which active routes BGP may advertise; local route presence alone is not export approval.
- BGP path eligibility depends on being able to resolve the advertised next hop; a healthy TCP peering alone does not install the route.
- BGP OPEN validates autonomous-system identity; a peer-AS mismatch prevents a normal established session.
- A BGP session being Established for one family does not guarantee that another address family was negotiated.
Explanation
Correct Answer
D:A BGP session being Established for one family does not guarantee that another address family was negotiated. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Both peers negotiate the intended family and the corresponding NLRI arrives after configuration. The targeted correction is: Enable the required MP-BGP family on both peers and preserve appropriate policy.
Incorrect Answers
A:Export policy explicitly determines which active routes BGP may advertise; local route presence alone is not export approval. This is a plausible protocol explanation for a different BGP condition, specifically BGP outbound route policy reject. Export policy explicitly determines which active routes BGP may advertise; local route presence alone is not export approval. In this scenario, however, the distinguishing issue is Multiprotocol BGP family omission and the confirming observation is: Both peers negotiate the intended family and the corresponding NLRI arrives after configuration.
B: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 Multiprotocol BGP family omission and the confirming observation is: Both peers negotiate the intended family and the corresponding NLRI arrives after configuration.
C:BGP OPEN validates autonomous-system identity; a peer-AS mismatch prevents a normal established session. This is a plausible protocol explanation for a different BGP condition, specifically BGP wrong remote AS. BGP OPEN validates autonomous-system identity; a peer-AS mismatch prevents a normal established session. In this scenario, however, the distinguishing issue is Multiprotocol BGP family omission and the confirming observation is: Both peers negotiate the intended family and the corresponding NLRI arrives after configuration.
Question 373
During a core-routing migration rehearsal, an HPE Juniper Networking engineer investigates this situation: IPv4 unicast routes exchange normally with a peer, but VPNv4 or EVPN NLRI never appears in received routes. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Both peers negotiate the intended family and the corresponding NLRI arrives after configuration.
- The prefix appears in the BGP advertised-route view only after matching the intended permit condition.
- The route changes from hidden or unusable to active when a valid next-hop resolution path is available.
- OPEN exchange succeeds and the neighbor remains Established with the expected peer AS.
Explanation
Correct Answer
A:Both peers negotiate the intended family and the corresponding NLRI arrives after configuration. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: A BGP session being Established for one family does not guarantee that another address family was negotiated.
Incorrect Answers
B:The prefix appears in the BGP advertised-route view only after matching the intended permit condition. This is a plausible observed evidence for a different BGP condition, specifically BGP outbound route policy reject. Export policy explicitly determines which active routes BGP may advertise; local route presence alone is not export approval. In this scenario, however, the distinguishing issue is Multiprotocol BGP family omission and the confirming observation is: Both peers negotiate the intended family and the corresponding NLRI arrives after configuration.
C:The route changes from hidden or unusable to active when a valid next-hop resolution path is available. This is a plausible observed evidence for a different BGP condition, specifically IBGP next-hop unresolvable. BGP path eligibility depends on being able to resolve the advertised next hop; a healthy TCP peering alone does not install the route. In this scenario, however, the distinguishing issue is Multiprotocol BGP family omission and the confirming observation is: Both peers negotiate the intended family and the corresponding NLRI arrives after configuration.
D:OPEN exchange succeeds and the neighbor remains Established with the expected peer AS. This is a plausible observed evidence for a different BGP condition, specifically BGP wrong remote AS. BGP OPEN validates autonomous-system identity; a peer-AS mismatch prevents a normal established session. In this scenario, however, the distinguishing issue is Multiprotocol BGP family omission and the confirming observation is: Both peers negotiate the intended family and the corresponding NLRI arrives after configuration.
Question 374
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: IPv4 unicast routes exchange normally with a peer, but VPNv4 or EVPN NLRI never appears in received routes. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Add a narrowly scoped route-export term before the terminating rejection.
- Enable the required MP-BGP family on both peers and preserve appropriate policy.
- Restore IGP or transport reachability to the advertised BGP next hop and retain appropriate next-hop policy.
- Correct the neighbor peer-AS configuration and verify the authorized topology.
Explanation
Correct Answer
B:Enable the required MP-BGP family on both peers and preserve appropriate policy. The change addresses the root behavior described here: A BGP session being Established for one family does not guarantee that another address family was negotiated. Verify success with: Both peers negotiate the intended family and the corresponding NLRI arrives after configuration.
Incorrect Answers
A:Add a narrowly scoped route-export term before the terminating rejection. This is a plausible configuration or operational fix for a different BGP condition, specifically BGP outbound route policy reject. Export policy explicitly determines which active routes BGP may advertise; local route presence alone is not export approval. In this scenario, however, the distinguishing issue is Multiprotocol BGP family omission and the confirming observation is: Both peers negotiate the intended family and the corresponding NLRI arrives after configuration.
C: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 Multiprotocol BGP family omission and the confirming observation is: Both peers negotiate the intended family and the corresponding NLRI arrives after configuration.
D:Correct the neighbor peer-AS configuration and verify the authorized topology. This is a plausible configuration or operational fix for a different BGP condition, specifically BGP wrong remote AS. BGP OPEN validates autonomous-system identity; a peer-AS mismatch prevents a normal established session. In this scenario, however, the distinguishing issue is Multiprotocol BGP family omission and the confirming observation is: Both peers negotiate the intended family and the corresponding NLRI arrives after configuration.
Question 375
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: IPv4 unicast routes exchange normally with a peer, but VPNv4 or EVPN NLRI never appears in received routes. Which operational control would best prevent a recurrence of this exact failure mode?
- Keep a positive-and-negative prefix test table for each customer export policy.
- Monitor hidden BGP routes and next-hop resolution after core topology changes.
- Track negotiated address families in peer commissioning checklists.
- Cross-check peer-AS values against contracts and remote device inventory before maintenance.
Explanation
Correct Answer
C:Track negotiated address families in peer commissioning checklists. The control limits repetition of the described root condition: A BGP session being Established for one family does not guarantee that another address family was negotiated. During audits, confirm: Both peers negotiate the intended family and the corresponding NLRI arrives after configuration.
Incorrect Answers
A:Keep a positive-and-negative prefix test table for each customer export policy. This is a plausible preventive practice for a different BGP condition, specifically BGP outbound route policy reject. Export policy explicitly determines which active routes BGP may advertise; local route presence alone is not export approval. In this scenario, however, the distinguishing issue is Multiprotocol BGP family omission and the confirming observation is: Both peers negotiate the intended family and the corresponding NLRI arrives after configuration.
B: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 Multiprotocol BGP family omission and the confirming observation is: Both peers negotiate the intended family and the corresponding NLRI arrives after configuration.
D:Cross-check peer-AS values against contracts and remote device inventory before maintenance. This is a plausible preventive practice for a different BGP condition, specifically BGP wrong remote AS. BGP OPEN validates autonomous-system identity; a peer-AS mismatch prevents a normal established session. In this scenario, however, the distinguishing issue is Multiprotocol BGP family omission and the confirming observation is: Both peers negotiate the intended family and the corresponding NLRI arrives after configuration.
Question 376
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: A route reflector restarts and clients retain stale reachability longer than intended while convergence is incomplete. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare RR best-path IGP cost calculations with actual client-to-exit metrics.
- Compare the reflected BGP next-hop attribute with clients' IGP routes to the originating PE.
- Count IBGP sessions and assess route reflector client and nonclient adjacency roles.
- Inspect negotiated graceful-restart capability, restart timers and stale route handling.
Explanation
Correct Answer
D:Inspect negotiated graceful-restart capability, restart timers and stale route handling. This check examines the decisive condition for BGP graceful restart stale routes before any unrelated changes are made. The underlying mechanism is: Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails. The confirming observation is: The restart completes within negotiated timers or stale routes are safely withdrawn.
Incorrect Answers
A: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 graceful restart stale routes and the confirming observation is: The restart completes within negotiated timers or stale routes are safely withdrawn.
B:Compare the reflected BGP next-hop attribute with clients' IGP routes to the originating PE. This is a plausible diagnostic check for a different BGP condition, specifically RR client next-hop preservation. Route reflection usually preserves the original BGP next hop; RR adjacency alone does not carry the required forwarding transport. In this scenario, however, the distinguishing issue is BGP graceful restart stale routes and the confirming observation is: The restart completes within negotiated timers or stale routes are safely withdrawn.
C:Count IBGP sessions and assess route reflector client and nonclient adjacency roles. This is a plausible diagnostic check for a different BGP condition, specifically BGP route reflector scaling. Route reflection reduces the need for every IBGP router to maintain direct sessions to every other IBGP router. In this scenario, however, the distinguishing issue is BGP graceful restart stale routes and the confirming observation is: The restart completes within negotiated timers or stale routes are safely withdrawn.
Question 377
During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: A route reflector restarts and clients retain stale reachability longer than intended while convergence is incomplete. Which routing or service mechanism best explains the reported behavior?
- Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails.
- A standard reflector chooses its best path from its own topology perspective, which can differ from widely distributed clients.
- Route reflection usually preserves the original BGP next hop; RR adjacency alone does not carry the required forwarding transport.
- Route reflection reduces the need for every IBGP router to maintain direct sessions to every other IBGP router.
Explanation
Correct Answer
A:Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The restart completes within negotiated timers or stale routes are safely withdrawn. The targeted correction is: Align graceful restart roles and timer expectations with real forwarding continuity capability.
Incorrect Answers
B: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 graceful restart stale routes and the confirming observation is: The restart completes within negotiated timers or stale routes are safely withdrawn.
C:Route reflection usually preserves the original BGP next hop; RR adjacency alone does not carry the required forwarding transport. This is a plausible protocol explanation for a different BGP condition, specifically RR client next-hop preservation. Route reflection usually preserves the original BGP next hop; RR adjacency alone does not carry the required forwarding transport. In this scenario, however, the distinguishing issue is BGP graceful restart stale routes and the confirming observation is: The restart completes within negotiated timers or stale routes are safely withdrawn.
D:Route reflection reduces the need for every IBGP router to maintain direct sessions to every other IBGP router. This is a plausible protocol explanation for a different BGP condition, specifically BGP route reflector scaling. Route reflection reduces the need for every IBGP router to maintain direct sessions to every other IBGP router. In this scenario, however, the distinguishing issue is BGP graceful restart stale routes and the confirming observation is: The restart completes within negotiated timers or stale routes are safely withdrawn.
Question 378
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: A route reflector restarts and clients retain stale reachability longer than intended while convergence is incomplete. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Client route selection reflects an intended per-POP or supported optimal-reflection policy.
- The restart completes within negotiated timers or stale routes are safely withdrawn.
- Clients resolve the original PE next hop and install the reflected service route.
- Clients learn permitted routes from the reflector without adding all-to-all IBGP sessions.
Explanation
Correct Answer
B:The restart completes within negotiated timers or stale routes are safely withdrawn. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails.
Incorrect Answers
A: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 graceful restart stale routes and the confirming observation is: The restart completes within negotiated timers or stale routes are safely withdrawn.
C:Clients resolve the original PE next hop and install the reflected service route. This is a plausible observed evidence for a different BGP condition, specifically RR client next-hop preservation. Route reflection usually preserves the original BGP next hop; RR adjacency alone does not carry the required forwarding transport. In this scenario, however, the distinguishing issue is BGP graceful restart stale routes and the confirming observation is: The restart completes within negotiated timers or stale routes are safely withdrawn.
D:Clients learn permitted routes from the reflector without adding all-to-all IBGP sessions. This is a plausible observed evidence for a different BGP condition, specifically BGP route reflector scaling. Route reflection reduces the need for every IBGP router to maintain direct sessions to every other IBGP router. In this scenario, however, the distinguishing issue is BGP graceful restart stale routes and the confirming observation is: The restart completes within negotiated timers or stale routes are safely withdrawn.
Question 379
During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: A route reflector restarts and clients retain stale reachability longer than intended while convergence is incomplete. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Use suitable reflector placement or a supported optimal route reflection approach if topology diversity requires it.
- Restore underlay reachability or apply a justified next-hop policy at the appropriate edge.
- Align graceful restart roles and timer expectations with real forwarding continuity capability.
- Deploy an appropriate redundant route-reflector design with explicit client configuration.
Explanation
Correct Answer
C:Align graceful restart roles and timer expectations with real forwarding continuity capability. The change addresses the root behavior described here: Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails. Verify success with: The restart completes within negotiated timers or stale routes are safely withdrawn.
Incorrect Answers
A: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 graceful restart stale routes and the confirming observation is: The restart completes within negotiated timers or stale routes are safely withdrawn.
B:Restore underlay reachability or apply a justified next-hop policy at the appropriate edge. This is a plausible configuration or operational fix for a different BGP condition, specifically RR client next-hop preservation. Route reflection usually preserves the original BGP next hop; RR adjacency alone does not carry the required forwarding transport. In this scenario, however, the distinguishing issue is BGP graceful restart stale routes and the confirming observation is: The restart completes within negotiated timers or stale routes are safely withdrawn.
D:Deploy an appropriate redundant route-reflector design with explicit client configuration. This is a plausible configuration or operational fix for a different BGP condition, specifically BGP route reflector scaling. Route reflection reduces the need for every IBGP router to maintain direct sessions to every other IBGP router. In this scenario, however, the distinguishing issue is BGP graceful restart stale routes and the confirming observation is: The restart completes within negotiated timers or stale routes are safely withdrawn.
Question 380
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: A route reflector restarts and clients retain stale reachability longer than intended while convergence is incomplete. Which operational control would best prevent a recurrence of this exact failure mode?
- Test representative distant-client best exits when expanding reflector geography.
- Audit next-hop reachability from clients served by geographically remote reflectors.
- Test reflectors' failover and route availability across representative client pairs.
- Test abrupt failure separately from graceful restart to expose stale-route risks.
Explanation
Correct Answer
D:Test abrupt failure separately from graceful restart to expose stale-route risks. The control limits repetition of the described root condition: Graceful restart can retain forwarding or route state through controlled restarts but must bound stale information when recovery fails. During audits, confirm: The restart completes within negotiated timers or stale routes are safely withdrawn.
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 graceful restart stale routes and the confirming observation is: The restart completes within negotiated timers or stale routes are safely withdrawn.
B:Audit next-hop reachability from clients served by geographically remote reflectors. This is a plausible preventive practice for a different BGP condition, specifically RR client next-hop preservation. Route reflection usually preserves the original BGP next hop; RR adjacency alone does not carry the required forwarding transport. In this scenario, however, the distinguishing issue is BGP graceful restart stale routes and the confirming observation is: The restart completes within negotiated timers or stale routes are safely withdrawn.
C:Test reflectors' failover and route availability across representative client pairs. This is a plausible preventive practice for a different BGP condition, specifically BGP route reflector scaling. Route reflection reduces the need for every IBGP router to maintain direct sessions to every other IBGP router. In this scenario, however, the distinguishing issue is BGP graceful restart stale routes and the confirming observation is: The restart completes within negotiated timers or stale routes are safely withdrawn.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests