Question 350
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: A new BGP import policy accepted an entire upstream aggregate range and inadvertently admitted a prohibited customer more-specific route. 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.
- Run policy tests against boundary subnet lengths before installing route filters.
- Test each rule against harmless nonmatching flows and maintain a rapid withdraw procedure.
- Audit path-length and local preference before changing peering relationships.
Explanation
Correct Answer
B:Run policy tests against boundary subnet lengths before installing route filters. The control limits repetition of the described root condition: Prefix matching can include unintended more-specifics when the term is broader than the intended exact route requirement. During audits, confirm: The prohibited route is hidden or rejected while the specifically approved routes remain installed.
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 import policy overmatching and the confirming observation is: The prohibited route is hidden or rejected while the specifically approved routes remain installed.
C:Test each rule against harmless nonmatching flows and maintain a rapid withdraw procedure. This is a plausible preventive practice 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 import policy overmatching and the confirming observation is: The prohibited route is hidden or rejected while the specifically approved routes remain installed.
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 BGP import policy overmatching and the confirming observation is: The prohibited route is hidden or rejected while the specifically approved routes remain installed.
Question 351
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: An OSPF internal route and a BGP route exist for an identical prefix; the BGP route has higher LOCAL_PREF but remains inactive on Junos. 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.
- Check whether blackhole actions match the exact planned community values rather than a loose regex pattern.
- Compare protocol preference values separately from BGP path attributes and verify eligible routes.
- Inspect RIB active state and the presence of advertise-inactive or equivalent policy controls.
Explanation
Correct Answer
C:Compare protocol preference values separately from BGP path attributes and verify eligible routes. This check examines the decisive condition for Route preference versus BGP local-pref before any unrelated changes are made. The underlying mechanism is: Junos chooses among protocols using route preference before BGP's local preference decides among BGP candidates. The confirming observation is: The installed path matches the lower global preference unless that policy is intentionally changed.
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 Route preference versus BGP local-pref and the confirming observation is: The installed path matches the lower global preference unless that policy is intentionally changed.
B:Check whether blackhole actions match the exact planned community values rather than a loose regex pattern. This is a plausible diagnostic check for a different BGP condition, specifically BGP bogon community tagging. Community-based blackholing is a policy convention and should only trigger for explicitly authorized tagged routes. In this scenario, however, the distinguishing issue is Route preference versus BGP local-pref and the confirming observation is: The installed path matches the lower global preference unless that policy is intentionally changed.
D:Inspect RIB active state and the presence of advertise-inactive or equivalent policy controls. This is a plausible diagnostic check for a different BGP condition, specifically Junos advertise-inactive semantics. BGP normally exports eligible active routes; advertise-inactive has bounded semantics and may permit a nonactive BGP path when a non-BGP route is active. In this scenario, however, the distinguishing issue is Route preference versus BGP local-pref and the confirming observation is: The installed path matches the lower global preference unless that policy is intentionally changed.
Question 352
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: An OSPF internal route and a BGP route exist for an identical prefix; the BGP route has higher LOCAL_PREF but remains inactive on Junos. 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.
- Community-based blackholing is a policy convention and should only trigger for explicitly authorized tagged routes.
- BGP normally exports eligible active routes; advertise-inactive has bounded semantics and may permit a nonactive BGP path when a non-BGP route is active.
- Junos chooses among protocols using route preference before BGP's local preference decides among BGP candidates.
Explanation
Correct Answer
D:Junos chooses among protocols using route preference before BGP's local preference decides among BGP candidates. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The installed path matches the lower global preference unless that policy is intentionally changed. The targeted correction is: Change a documented route preference or routing-policy design if protocol precedence must differ.
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 Route preference versus BGP local-pref and the confirming observation is: The installed path matches the lower global preference unless that policy is intentionally changed.
B:Community-based blackholing is a policy convention and should only trigger for explicitly authorized tagged routes. This is a plausible protocol explanation for a different BGP condition, specifically BGP bogon community tagging. Community-based blackholing is a policy convention and should only trigger for explicitly authorized tagged routes. In this scenario, however, the distinguishing issue is Route preference versus BGP local-pref and the confirming observation is: The installed path matches the lower global preference unless that policy is intentionally changed.
C:BGP normally exports eligible active routes; advertise-inactive has bounded semantics and may permit a nonactive BGP path when a non-BGP route is active. This is a plausible protocol explanation for a different BGP condition, specifically Junos advertise-inactive semantics. BGP normally exports eligible active routes; advertise-inactive has bounded semantics and may permit a nonactive BGP path when a non-BGP route is active. In this scenario, however, the distinguishing issue is Route preference versus BGP local-pref and the confirming observation is: The installed path matches the lower global preference unless that policy is intentionally changed.
Question 353
During an edge-to-core validation, an HPE Juniper Networking engineer investigates this situation: An OSPF internal route and a BGP route exist for an identical prefix; the BGP route has higher LOCAL_PREF but remains inactive on Junos. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The installed path matches the lower global preference unless that policy is intentionally changed.
- Clients resolve the original PE next hop and install the reflected service route.
- The prefix appears in the BGP advertised-route view only after matching the intended permit condition.
- A controlled test /32 or /128 can be dropped while ordinary customer routes remain unaffected.
Explanation
Correct Answer
A:The installed path matches the lower global preference unless that policy is intentionally changed. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Junos chooses among protocols using route preference before BGP's local preference decides among BGP candidates.
Incorrect Answers
B: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 Route preference versus BGP local-pref and the confirming observation is: The installed path matches the lower global preference unless that policy is intentionally changed.
C: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 Route preference versus BGP local-pref and the confirming observation is: The installed path matches the lower global preference unless that policy is intentionally changed.
D:A controlled test /32 or /128 can be dropped while ordinary customer routes remain unaffected. This is a plausible observed evidence for a different BGP condition, specifically BGP bogon community tagging. Community-based blackholing is a policy convention and should only trigger for explicitly authorized tagged routes. In this scenario, however, the distinguishing issue is Route preference versus BGP local-pref and the confirming observation is: The installed path matches the lower global preference unless that policy is intentionally changed.
Question 354
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: An OSPF internal route and a BGP route exist for an identical prefix; the BGP route has higher LOCAL_PREF but remains inactive on Junos. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Configure justified multihop and local-address settings with transport routing to the loopbacks.
- Change a documented route preference or routing-policy design if protocol precedence must differ.
- Restore underlay reachability or apply a justified next-hop policy at the appropriate edge.
- Add a narrowly scoped route-export term before the terminating rejection.
Explanation
Correct Answer
B:Change a documented route preference or routing-policy design if protocol precedence must differ. The change addresses the root behavior described here: Junos chooses among protocols using route preference before BGP's local preference decides among BGP candidates. Verify success with: The installed path matches the lower global preference unless that policy is intentionally changed.
Incorrect Answers
A:Configure justified multihop and local-address settings with transport routing to the loopbacks. This is a plausible configuration or operational fix for a different BGP condition, specifically EBGP multihop loopback peering. Multihop EBGP through loopback addresses requires proper transport reachability and a hop limit that permits the path. In this scenario, however, the distinguishing issue is Route preference versus BGP local-pref and the confirming observation is: The installed path matches the lower global preference unless that policy is intentionally changed.
C: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 Route preference versus BGP local-pref and the confirming observation is: The installed path matches the lower global preference unless that policy is intentionally changed.
D: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 Route preference versus BGP local-pref and the confirming observation is: The installed path matches the lower global preference unless that policy is intentionally changed.
Question 355
During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: An OSPF internal route and a BGP route exist for an identical prefix; the BGP route has higher LOCAL_PREF but remains inactive on Junos. Which operational control would best prevent a recurrence of this exact failure mode?
- Verify the path in each direction and control-plane filtering before enabling multihop EBGP.
- Audit next-hop reachability from clients served by geographically remote reflectors.
- Check interaction between RIB preference and BGP local preference in mixed-protocol reviews.
- Keep a positive-and-negative prefix test table for each customer export policy.
Explanation
Correct Answer
C:Check interaction between RIB preference and BGP local preference in mixed-protocol reviews. The control limits repetition of the described root condition: Junos chooses among protocols using route preference before BGP's local preference decides among BGP candidates. During audits, confirm: The installed path matches the lower global preference unless that policy is intentionally changed.
Incorrect Answers
A:Verify the path in each direction and control-plane filtering before enabling multihop EBGP. This is a plausible preventive practice for a different BGP condition, specifically EBGP multihop loopback peering. Multihop EBGP through loopback addresses requires proper transport reachability and a hop limit that permits the path. In this scenario, however, the distinguishing issue is Route preference versus BGP local-pref and the confirming observation is: The installed path matches the lower global preference unless that policy is intentionally changed.
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 Route preference versus BGP local-pref and the confirming observation is: The installed path matches the lower global preference unless that policy is intentionally changed.
D: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 Route preference versus BGP local-pref and the confirming observation is: The installed path matches the lower global preference unless that policy is intentionally changed.
Question 356
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: A Junos border router learns a BGP path but an active static route wins the RIB, so the BGP path is not exported as the team expected. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect outbound next-hop attributes at the AS border and the internal client's resolver routes.
- Compare protocol preference values separately from BGP path attributes and verify eligible routes.
- Compare origin codes and verify no earlier tie-break attributes differ.
- Inspect RIB active state and the presence of advertise-inactive or equivalent policy controls.
Explanation
Correct Answer
D:Inspect RIB active state and the presence of advertise-inactive or equivalent policy controls. This check examines the decisive condition for Junos advertise-inactive semantics before any unrelated changes are made. The underlying mechanism is: BGP normally exports eligible active routes; advertise-inactive has bounded semantics and may permit a nonactive BGP path when a non-BGP route is active. The confirming observation is: Neighbor advertisements include the intended nonactive BGP path only under supported and explicitly reviewed conditions.
Incorrect Answers
A:Inspect outbound next-hop attributes at the AS border and the internal client's resolver routes. This is a plausible diagnostic check for a different BGP condition, specifically BGP next-hop-self at border. Passing external reachability into IBGP without a reachable next hop can leave the route unusable for internal clients. In this scenario, however, the distinguishing issue is Junos advertise-inactive semantics and the confirming observation is: Neighbor advertisements include the intended nonactive BGP path only under supported and explicitly reviewed conditions.
B:Compare protocol preference values separately from BGP path attributes and verify eligible routes. This is a plausible diagnostic check 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 Junos advertise-inactive semantics and the confirming observation is: Neighbor advertisements include the intended nonactive BGP path only under supported and explicitly reviewed conditions.
C:Compare origin codes and verify no earlier tie-break attributes differ. This is a plausible diagnostic check for a different BGP condition, specifically BGP ORIGIN attribute tie. At the applicable BGP selection stage, lower origin-type value (IGP before incomplete) is preferred. In this scenario, however, the distinguishing issue is Junos advertise-inactive semantics and the confirming observation is: Neighbor advertisements include the intended nonactive BGP path only under supported and explicitly reviewed conditions.
Question 357
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: A Junos border router learns a BGP path but an active static route wins the RIB, so the BGP path is not exported as the team expected. Which routing or service mechanism best explains the reported behavior?
- BGP normally exports eligible active routes; advertise-inactive has bounded semantics and may permit a nonactive BGP path when a non-BGP route is active.
- Passing external reachability into IBGP without a reachable next hop can leave the route unusable for internal clients.
- Junos chooses among protocols using route preference before BGP's local preference decides among BGP candidates.
- At the applicable BGP selection stage, lower origin-type value (IGP before incomplete) is preferred.
Explanation
Correct Answer
A:BGP normally exports eligible active routes; advertise-inactive has bounded semantics and may permit a nonactive BGP path when a non-BGP route is active. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Neighbor advertisements include the intended nonactive BGP path only under supported and explicitly reviewed conditions. The targeted correction is: Use the documented advertise-inactive behavior where required, with loop and forwarding consistency checks.
Incorrect Answers
B:Passing external reachability into IBGP without a reachable next hop can leave the route unusable for internal clients. This is a plausible protocol explanation for a different BGP condition, specifically BGP next-hop-self at border. Passing external reachability into IBGP without a reachable next hop can leave the route unusable for internal clients. In this scenario, however, the distinguishing issue is Junos advertise-inactive semantics and the confirming observation is: Neighbor advertisements include the intended nonactive BGP path only under supported and explicitly reviewed conditions.
C: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 Junos advertise-inactive semantics and the confirming observation is: Neighbor advertisements include the intended nonactive BGP path only under supported and explicitly reviewed conditions.
D: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 Junos advertise-inactive semantics and the confirming observation is: Neighbor advertisements include the intended nonactive BGP path only under supported and explicitly reviewed conditions.
Question 358
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: A Junos border router learns a BGP path but an active static route wins the RIB, so the BGP path is not exported as the team expected. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Client route entries show a reachable border-router next hop and become active.
- Neighbor advertisements include the intended nonactive BGP path only under supported and explicitly reviewed conditions.
- The installed path matches the lower global preference unless that policy is intentionally changed.
- The route with the preferred origin becomes best under otherwise equal higher-priority attributes.
Explanation
Correct Answer
B:Neighbor advertisements include the intended nonactive BGP path only under supported and explicitly reviewed conditions. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: BGP normally exports eligible active routes; advertise-inactive has bounded semantics and may permit a nonactive BGP path when a non-BGP route is active.
Incorrect Answers
A:Client route entries show a reachable border-router next hop and become active. This is a plausible observed evidence for a different BGP condition, specifically BGP next-hop-self at border. Passing external reachability into IBGP without a reachable next hop can leave the route unusable for internal clients. In this scenario, however, the distinguishing issue is Junos advertise-inactive semantics and the confirming observation is: Neighbor advertisements include the intended nonactive BGP path only under supported and explicitly reviewed conditions.
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 Junos advertise-inactive semantics and the confirming observation is: Neighbor advertisements include the intended nonactive BGP path only under supported and explicitly reviewed conditions.
D: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 Junos advertise-inactive semantics and the confirming observation is: Neighbor advertisements include the intended nonactive BGP path only under supported and explicitly reviewed conditions.
Question 359
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: A Junos border router learns a BGP path but an active static route wins the RIB, so the BGP path is not exported as the team expected. 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.
- Apply an appropriate next-hop-self or next-hop policy on the border device while retaining forwarding consistency.
- Use the documented advertise-inactive behavior where required, with loop and forwarding consistency checks.
- Change a documented route preference or routing-policy design if protocol precedence must differ.
Explanation
Correct Answer
C:Use the documented advertise-inactive behavior where required, with loop and forwarding consistency checks. The change addresses the root behavior described here: BGP normally exports eligible active routes; advertise-inactive has bounded semantics and may permit a nonactive BGP path when a non-BGP route is active. Verify success with: Neighbor advertisements include the intended nonactive BGP path only under supported and explicitly reviewed conditions.
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 Junos advertise-inactive semantics and the confirming observation is: Neighbor advertisements include the intended nonactive BGP path only under supported and explicitly reviewed conditions.
B:Apply an appropriate next-hop-self or next-hop policy on the border device while retaining forwarding consistency. This is a plausible configuration or operational fix for a different BGP condition, specifically BGP next-hop-self at border. Passing external reachability into IBGP without a reachable next hop can leave the route unusable for internal clients. In this scenario, however, the distinguishing issue is Junos advertise-inactive semantics and the confirming observation is: Neighbor advertisements include the intended nonactive BGP path only under supported and explicitly reviewed conditions.
D: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 Junos advertise-inactive semantics and the confirming observation is: Neighbor advertisements include the intended nonactive BGP path only under supported and explicitly reviewed conditions.
Question 360
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: A Junos border router learns a BGP path but an active static route wins the RIB, so the BGP path is not exported as the team expected. Which operational control would best prevent a recurrence of this exact failure mode?
- Log origin attribute changes when redistributing or aggregating BGP routes.
- Check recursive next-hop reachability from representative internal routers when adding EBGP peers.
- Check interaction between RIB preference and BGP local preference in mixed-protocol reviews.
- Test what happens when the static winner disappears before permitting inactive advertisements.
Explanation
Correct Answer
D:Test what happens when the static winner disappears before permitting inactive advertisements. The control limits repetition of the described root condition: BGP normally exports eligible active routes; advertise-inactive has bounded semantics and may permit a nonactive BGP path when a non-BGP route is active. During audits, confirm: Neighbor advertisements include the intended nonactive BGP path only under supported and explicitly reviewed conditions.
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 Junos advertise-inactive semantics and the confirming observation is: Neighbor advertisements include the intended nonactive BGP path only under supported and explicitly reviewed conditions.
B:Check recursive next-hop reachability from representative internal routers when adding EBGP peers. This is a plausible preventive practice for a different BGP condition, specifically BGP next-hop-self at border. Passing external reachability into IBGP without a reachable next hop can leave the route unusable for internal clients. In this scenario, however, the distinguishing issue is Junos advertise-inactive semantics and the confirming observation is: Neighbor advertisements include the intended nonactive BGP path only under supported and explicitly reviewed conditions.
C: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 Junos advertise-inactive semantics and the confirming observation is: Neighbor advertisements include the intended nonactive BGP path only under supported and explicitly reviewed conditions.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests