Question 260
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: Two valid BGP exits have equal AS-path length and origin attributes, but the network must consistently prefer one provider for outbound traffic. Which operational control would best prevent a recurrence of this exact failure mode?
- Log origin attribute changes when redistributing or aggregating BGP routes.
- Audit path-length and local preference before changing peering relationships.
- Maintain positive and negative example AS paths alongside policy expressions.
- Document business exit priorities and verify local preference after peer resets.
Explanation
Correct Answer
D:Document business exit priorities and verify local preference after peer resets. The control limits repetition of the described root condition: Within an AS, higher BGP local preference is selected ahead of AS-path length when paths are otherwise eligible. During audits, confirm: The chosen active route uses the deliberately higher-local-preference exit while backup remains valid.
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 Local preference exit choice and the confirming observation is: The chosen active route uses the deliberately higher-local-preference exit while backup remains valid.
B: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 Local preference exit choice and the confirming observation is: The chosen active route uses the deliberately higher-local-preference exit while backup remains valid.
C:Maintain positive and negative example AS paths alongside policy expressions. This is a plausible preventive practice for a different BGP condition, specifically AS-path regex filter. BGP AS-path regex syntax and anchoring determine whether matching targets the origin AS, any traversed AS, or the entire sequence. In this scenario, however, the distinguishing issue is Local preference exit choice and the confirming observation is: The chosen active route uses the deliberately higher-local-preference exit while backup remains valid.
Question 261
During an edge-to-core validation, an HPE Juniper Networking engineer investigates this situation: Two eligible EBGP routes have the same local preference but one AS path is notably longer and is being chosen by an unintended policy. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare AS_PATH lengths and any policy that rewrites higher-priority attributes.
- 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 BGP community type and route-policy match expression format.
Explanation
Correct Answer
A:Compare AS_PATH lengths and any policy that rewrites higher-priority attributes. This check examines the decisive condition for AS-path length selection before any unrelated changes are made. The underlying mechanism is: After equal higher-priority selection attributes, BGP generally prefers the shorter AS path among eligible candidate paths. The confirming observation is: The shortest eligible AS path becomes preferred once conflicting policy overrides are removed.
Incorrect Answers
B: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 length selection and the confirming observation is: The shortest eligible AS path becomes preferred once conflicting policy overrides are removed.
C: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 length selection and the confirming observation is: The shortest eligible AS path becomes preferred once conflicting policy overrides are removed.
D:Inspect the BGP community type and route-policy match expression format. This is a plausible diagnostic check for a different BGP condition, specifically BGP large community matching. Large communities have different encoding and syntax from standard communities; policy must match the received attribute family. In this scenario, however, the distinguishing issue is AS-path length selection and the confirming observation is: The shortest eligible AS path becomes preferred once conflicting policy overrides are removed.
Question 262
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: Two eligible EBGP routes have the same local preference but one AS path is notably longer and is being chosen by an unintended policy. 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.
- After equal higher-priority selection attributes, BGP generally prefers the shorter AS path among eligible candidate paths.
- Large communities have different encoding and syntax from standard communities; policy must match the received attribute family.
- Export policy explicitly determines which active routes BGP may advertise; local route presence alone is not export approval.
Explanation
Correct Answer
B:After equal higher-priority selection attributes, BGP generally prefers the shorter AS path among eligible candidate paths. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The shortest eligible AS path becomes preferred once conflicting policy overrides are removed. The targeted correction is: Correct route-policy attributes or prepend design to implement the intended preference.
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 length selection and the confirming observation is: The shortest eligible AS path becomes preferred once conflicting policy overrides are removed.
C:Large communities have different encoding and syntax from standard communities; policy must match the received attribute family. This is a plausible protocol explanation for a different BGP condition, specifically BGP large community matching. Large communities have different encoding and syntax from standard communities; policy must match the received attribute family. In this scenario, however, the distinguishing issue is AS-path length selection and the confirming observation is: The shortest eligible AS path becomes preferred once conflicting policy overrides are removed.
D: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 AS-path length selection and the confirming observation is: The shortest eligible AS path becomes preferred once conflicting policy overrides are removed.
Question 263
During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: Two eligible EBGP routes have the same local preference but one AS path is notably longer and is being chosen by an unintended policy. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- 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 shortest eligible AS path becomes preferred once conflicting policy overrides are removed.
- The intended large-community value is visible and the correct service policy term matches.
Explanation
Correct Answer
C:The shortest eligible AS path becomes preferred once conflicting policy overrides are removed. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: After equal higher-priority selection attributes, BGP generally prefers the shorter AS path among eligible candidate paths.
Incorrect Answers
A: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 length selection and the confirming observation is: The shortest eligible AS path becomes preferred once conflicting policy overrides are removed.
B: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 length selection and the confirming observation is: The shortest eligible AS path becomes preferred once conflicting policy overrides are removed.
D:The intended large-community value is visible and the correct service policy term matches. This is a plausible observed evidence for a different BGP condition, specifically BGP large community matching. Large communities have different encoding and syntax from standard communities; policy must match the received attribute family. In this scenario, however, the distinguishing issue is AS-path length selection and the confirming observation is: The shortest eligible AS path becomes preferred once conflicting policy overrides are removed.
Question 264
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: Two eligible EBGP routes have the same local preference but one AS path is notably longer and is being chosen by an unintended policy. 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.
- Use the supported large-community match configuration without coercing tags into standard-community form.
- Add a narrowly scoped route-export term before the terminating rejection.
- Correct route-policy attributes or prepend design to implement the intended preference.
Explanation
Correct Answer
D:Correct route-policy attributes or prepend design to implement the intended preference. The change addresses the root behavior described here: After equal higher-priority selection attributes, BGP generally prefers the shorter AS path among eligible candidate paths. Verify success with: The shortest eligible AS path becomes preferred once conflicting policy overrides are removed.
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 length selection and the confirming observation is: The shortest eligible AS path becomes preferred once conflicting policy overrides are removed.
B:Use the supported large-community match configuration without coercing tags into standard-community form. This is a plausible configuration or operational fix for a different BGP condition, specifically BGP large community matching. Large communities have different encoding and syntax from standard communities; policy must match the received attribute family. In this scenario, however, the distinguishing issue is AS-path length selection and the confirming observation is: The shortest eligible AS path becomes preferred once conflicting policy overrides are removed.
C: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 AS-path length selection and the confirming observation is: The shortest eligible AS path becomes preferred once conflicting policy overrides are removed.
Question 265
During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: Two eligible EBGP routes have the same local preference but one AS path is notably longer and is being chosen by an unintended policy. Which operational control would best prevent a recurrence of this exact failure mode?
- Audit path-length and local preference before changing peering relationships.
- Log origin attribute changes when redistributing or aggregating BGP routes.
- Document business exit priorities and verify local preference after peer resets.
- Validate tagged routes in configuration tests after community-format changes.
Explanation
Correct Answer
A:Audit path-length and local preference before changing peering relationships. The control limits repetition of the described root condition: After equal higher-priority selection attributes, BGP generally prefers the shorter AS path among eligible candidate paths. During audits, confirm: The shortest eligible AS path becomes preferred once conflicting policy overrides are removed.
Incorrect Answers
B: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 length selection and the confirming observation is: The shortest eligible AS path becomes preferred once conflicting policy overrides are removed.
C: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 length selection and the confirming observation is: The shortest eligible AS path becomes preferred once conflicting policy overrides are removed.
D:Validate tagged routes in configuration tests after community-format changes. This is a plausible preventive practice for a different BGP condition, specifically BGP large community matching. Large communities have different encoding and syntax from standard communities; policy must match the received attribute family. In this scenario, however, the distinguishing issue is AS-path length selection and the confirming observation is: The shortest eligible AS path becomes preferred once conflicting policy overrides are removed.
Question 266
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: A provider compares otherwise equivalent routes from the same neighboring AS and selects a higher-MED exit against the traffic engineering plan. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare AS_PATH lengths and any policy that rewrites higher-priority attributes.
- Check MED values, neighboring-AS comparability, and earlier BGP decision steps.
- Compare multipath configuration and the eligibility attributes required for both candidate paths.
- Trace recursive next-hop resolution and identify whether a route eventually reaches a connected usable transport.
Explanation
Correct Answer
B:Check MED values, neighboring-AS comparability, and earlier BGP decision steps. This check examines the decisive condition for MED preference within neighbor AS before any unrelated changes are made. The underlying mechanism is: Lower MED normally indicates the preferred entry for comparable routes from the same neighboring AS, after stronger attributes tie. The confirming observation is: The lower-MED eligible route is selected when upstream attributes and comparison scope permit it.
Incorrect Answers
A:Compare AS_PATH lengths and any policy that rewrites higher-priority attributes. This is a plausible diagnostic check 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 MED preference within neighbor AS and the confirming observation is: The lower-MED eligible route is selected when upstream attributes and comparison scope permit it.
C:Compare multipath configuration and the eligibility attributes required for both candidate paths. This is a plausible diagnostic check for a different BGP condition, specifically BGP multipath prerequisites. BGP multipath requires compatible candidate paths and implementation-specific settings in addition to multiple route advertisements. In this scenario, however, the distinguishing issue is MED preference within neighbor AS and the confirming observation is: The lower-MED eligible route is selected when upstream attributes and comparison scope permit it.
D:Trace recursive next-hop resolution and identify whether a route eventually reaches a connected usable transport. This is a plausible diagnostic check for a different BGP condition, specifically BGP next-hop recursive loop. A recursive next-hop chain must terminate at valid forwarding reachability, not loop back through the route being installed. In this scenario, however, the distinguishing issue is MED preference within neighbor AS and the confirming observation is: The lower-MED eligible route is selected when upstream attributes and comparison scope permit it.
Question 267
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: A provider compares otherwise equivalent routes from the same neighboring AS and selects a higher-MED exit against the traffic engineering plan. Which routing or service mechanism best explains the reported behavior?
- After equal higher-priority selection attributes, BGP generally prefers the shorter AS path among eligible candidate paths.
- BGP multipath requires compatible candidate paths and implementation-specific settings in addition to multiple route advertisements.
- Lower MED normally indicates the preferred entry for comparable routes from the same neighboring AS, after stronger attributes tie.
- A recursive next-hop chain must terminate at valid forwarding reachability, not loop back through the route being installed.
Explanation
Correct Answer
C:Lower MED normally indicates the preferred entry for comparable routes from the same neighboring AS, after stronger attributes tie. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The lower-MED eligible route is selected when upstream attributes and comparison scope permit it. The targeted correction is: Align MED policy and avoid assuming cross-AS MED comparison without explicit design.
Incorrect Answers
A:After equal higher-priority selection attributes, BGP generally prefers the shorter AS path among eligible candidate paths. This is a plausible protocol explanation 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 MED preference within neighbor AS and the confirming observation is: The lower-MED eligible route is selected when upstream attributes and comparison scope permit it.
B:BGP multipath requires compatible candidate paths and implementation-specific settings in addition to multiple route advertisements. This is a plausible protocol explanation for a different BGP condition, specifically BGP multipath prerequisites. BGP multipath requires compatible candidate paths and implementation-specific settings in addition to multiple route advertisements. In this scenario, however, the distinguishing issue is MED preference within neighbor AS and the confirming observation is: The lower-MED eligible route is selected when upstream attributes and comparison scope permit it.
D:A recursive next-hop chain must terminate at valid forwarding reachability, not loop back through the route being installed. This is a plausible protocol explanation for a different BGP condition, specifically BGP next-hop recursive loop. A recursive next-hop chain must terminate at valid forwarding reachability, not loop back through the route being installed. In this scenario, however, the distinguishing issue is MED preference within neighbor AS and the confirming observation is: The lower-MED eligible route is selected when upstream attributes and comparison scope permit it.
Question 268
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: A provider compares otherwise equivalent routes from the same neighboring AS and selects a higher-MED exit against the traffic engineering plan. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The shortest eligible AS path becomes preferred once conflicting policy overrides are removed.
- The forwarding entry contains both eligible next hops with operationally verified reachability.
- The recursive resolution ends at a reachable interface and the BGP prefix can become active.
- The lower-MED eligible route is selected when upstream attributes and comparison scope permit it.
Explanation
Correct Answer
D:The lower-MED eligible route is selected when upstream attributes and comparison scope permit it. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Lower MED normally indicates the preferred entry for comparable routes from the same neighboring AS, after stronger attributes tie.
Incorrect Answers
A:The shortest eligible AS path becomes preferred once conflicting policy overrides are removed. This is a plausible observed evidence 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 MED preference within neighbor AS and the confirming observation is: The lower-MED eligible route is selected when upstream attributes and comparison scope permit it.
B:The forwarding entry contains both eligible next hops with operationally verified reachability. This is a plausible observed evidence for a different BGP condition, specifically BGP multipath prerequisites. BGP multipath requires compatible candidate paths and implementation-specific settings in addition to multiple route advertisements. In this scenario, however, the distinguishing issue is MED preference within neighbor AS and the confirming observation is: The lower-MED eligible route is selected when upstream attributes and comparison scope permit it.
C:The recursive resolution ends at a reachable interface and the BGP prefix can become active. This is a plausible observed evidence for a different BGP condition, specifically BGP next-hop recursive loop. A recursive next-hop chain must terminate at valid forwarding reachability, not loop back through the route being installed. In this scenario, however, the distinguishing issue is MED preference within neighbor AS and the confirming observation is: The lower-MED eligible route is selected when upstream attributes and comparison scope permit it.
Question 269
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: A provider compares otherwise equivalent routes from the same neighboring AS and selects a higher-MED exit against the traffic engineering plan. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Align MED policy and avoid assuming cross-AS MED comparison without explicit design.
- Correct route-policy attributes or prepend design to implement the intended preference.
- Enable supported BGP multipath under explicit attribute constraints instead of forcing unequal paths.
- Repair the IGP or static next-hop route to provide nonrecursive transport connectivity.
Explanation
Correct Answer
A:Align MED policy and avoid assuming cross-AS MED comparison without explicit design. The change addresses the root behavior described here: Lower MED normally indicates the preferred entry for comparable routes from the same neighboring AS, after stronger attributes tie. Verify success with: The lower-MED eligible route is selected when upstream attributes and comparison scope permit it.
Incorrect Answers
B:Correct route-policy attributes or prepend design to implement the intended preference. This is a plausible configuration or operational fix 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 MED preference within neighbor AS and the confirming observation is: The lower-MED eligible route is selected when upstream attributes and comparison scope permit it.
C:Enable supported BGP multipath under explicit attribute constraints instead of forcing unequal paths. This is a plausible configuration or operational fix for a different BGP condition, specifically BGP multipath prerequisites. BGP multipath requires compatible candidate paths and implementation-specific settings in addition to multiple route advertisements. In this scenario, however, the distinguishing issue is MED preference within neighbor AS and the confirming observation is: The lower-MED eligible route is selected when upstream attributes and comparison scope permit it.
D:Repair the IGP or static next-hop route to provide nonrecursive transport connectivity. This is a plausible configuration or operational fix for a different BGP condition, specifically BGP next-hop recursive loop. A recursive next-hop chain must terminate at valid forwarding reachability, not loop back through the route being installed. In this scenario, however, the distinguishing issue is MED preference within neighbor AS and the confirming observation is: The lower-MED eligible route is selected when upstream attributes and comparison scope permit it.
Question 270
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: A provider compares otherwise equivalent routes from the same neighboring AS and selects a higher-MED exit against the traffic engineering plan. Which operational control would best prevent a recurrence of this exact failure mode?
- Review next-hop and attribute comparability before adding paths to ECMP service.
- Run deterministic best-path tests for equal-local-preference routes.
- Test BGP next-hop resolution after aggregate and default route changes.
- Test representative distant-client best exits when expanding reflector geography.
Explanation
Correct Answer
B:Run deterministic best-path tests for equal-local-preference routes. The control limits repetition of the described root condition: Lower MED normally indicates the preferred entry for comparable routes from the same neighboring AS, after stronger attributes tie. During audits, confirm: The lower-MED eligible route is selected when upstream attributes and comparison scope permit it.
Incorrect Answers
A:Review next-hop and attribute comparability before adding paths to ECMP service. This is a plausible preventive practice for a different BGP condition, specifically BGP multipath prerequisites. BGP multipath requires compatible candidate paths and implementation-specific settings in addition to multiple route advertisements. In this scenario, however, the distinguishing issue is MED preference within neighbor AS and the confirming observation is: The lower-MED eligible route is selected when upstream attributes and comparison scope permit it.
C:Test BGP next-hop resolution after aggregate and default route changes. This is a plausible preventive practice for a different BGP condition, specifically BGP next-hop recursive loop. A recursive next-hop chain must terminate at valid forwarding reachability, not loop back through the route being installed. In this scenario, however, the distinguishing issue is MED preference within neighbor AS and the confirming observation is: The lower-MED eligible route is selected when upstream attributes and comparison scope permit it.
D: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 MED preference within neighbor AS and the confirming observation is: The lower-MED eligible route is selected when upstream attributes and comparison scope permit it.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests