Question 80
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: A locally originated static service prefix is visible in a Junos table but remote OSPF routers never learn it as an external route. Which operational control would best prevent a recurrence of this exact failure mode?
- Record permitted LSA types and verify the default route before converting an area to stub.
- Monitor LSDB freshness and SPF processing during periods of churn.
- Test external metric-type assumptions after an ASBR topology or cost change.
- Review policy matches against a fixed allowlist after each redistribution change.
Explanation
Correct Answer
D:Review policy matches against a fixed allowlist after each redistribution change. The control limits repetition of the described root condition: Junos OSPF does not automatically redistribute arbitrary static prefixes; an export policy must explicitly permit the route. During audits, confirm: The originating ASBR generates the expected external advertisement and remote routers install the authorized prefix.
Incorrect Answers
A:Record permitted LSA types and verify the default route before converting an area to stub. This is a plausible preventive practice for a different OSPF condition, specifically Stub-area external reachability. A stub area excludes AS-external type 5 LSAs and relies on ABR-supplied reachability rather than importing individual external routes. In this scenario, however, the distinguishing issue is OSPF route export policy missing and the confirming observation is: The originating ASBR generates the expected external advertisement and remote routers install the authorized prefix.
B:Monitor LSDB freshness and SPF processing during periods of churn. This is a plausible preventive practice for a different OSPF condition, specifically LSDB sequence-age mismatch. Link-state routes depend on consistent current LSAs and completed SPF processing, not solely on neighbor Full status. In this scenario, however, the distinguishing issue is OSPF route export policy missing and the confirming observation is: The originating ASBR generates the expected external advertisement and remote routers install the authorized prefix.
C:Test external metric-type assumptions after an ASBR topology or cost change. This is a plausible preventive practice for a different OSPF condition, specifically External E1 versus E2 selection. An external E2 metric primarily represents the advertised external cost, whereas E1 accounts for internal cost toward the ASBR plus external cost. In this scenario, however, the distinguishing issue is OSPF route export policy missing and the confirming observation is: The originating ASBR generates the expected external advertisement and remote routers install the authorized prefix.
Question 81
During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: An operator applied a routing policy on one downstream node hoping to stop an unwanted OSPF LSA from being flooded across the entire area. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare the local route-install decision with LSA propagation in neighboring link-state databases.
- Inspect the ABR's area range configuration and the origin of interarea summary LSAs.
- Inspect the ABR aggregate's contributing prefixes and current summary advertisement conditions.
- Inspect external route types and compare the internal cost to each advertising ASBR.
Explanation
Correct Answer
A:Compare the local route-install decision with LSA propagation in neighboring link-state databases. This check examines the decisive condition for Inbound OSPF route filtering scope before any unrelated changes are made. The underlying mechanism is: A local routing-table import decision is not necessarily an LSA flooding filter in a link-state area. The confirming observation is: Neighbor LSDB inspection shows LSAs still flood even if local route installation differs.
Incorrect Answers
B:Inspect the ABR's area range configuration and the origin of interarea summary LSAs. This is a plausible diagnostic check for a different OSPF condition, specifically Route summarization at ABR. Interarea aggregation is performed by a suitable ABR; setting an unrelated import filter does not itself produce the expected summary. In this scenario, however, the distinguishing issue is Inbound OSPF route filtering scope and the confirming observation is: Neighbor LSDB inspection shows LSAs still flood even if local route installation differs.
C:Inspect the ABR aggregate's contributing prefixes and current summary advertisement conditions. This is a plausible diagnostic check for a different OSPF condition, specifically Area border prefix withdrawal. Summary advertisement must reflect actual reachable components and implementation rules to avoid attracting traffic to a missing site. In this scenario, however, the distinguishing issue is Inbound OSPF route filtering scope and the confirming observation is: Neighbor LSDB inspection shows LSAs still flood even if local route installation differs.
D:Inspect external route types and compare the internal cost to each advertising ASBR. This is a plausible diagnostic check for a different OSPF condition, specifically External E1 versus E2 selection. An external E2 metric primarily represents the advertised external cost, whereas E1 accounts for internal cost toward the ASBR plus external cost. In this scenario, however, the distinguishing issue is Inbound OSPF route filtering scope and the confirming observation is: Neighbor LSDB inspection shows LSAs still flood even if local route installation differs.
Question 82
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: An operator applied a routing policy on one downstream node hoping to stop an unwanted OSPF LSA from being flooded across the entire area. Which routing or service mechanism best explains the reported behavior?
- Interarea aggregation is performed by a suitable ABR; setting an unrelated import filter does not itself produce the expected summary.
- A local routing-table import decision is not necessarily an LSA flooding filter in a link-state area.
- Summary advertisement must reflect actual reachable components and implementation rules to avoid attracting traffic to a missing site.
- An external E2 metric primarily represents the advertised external cost, whereas E1 accounts for internal cost toward the ASBR plus external cost.
Explanation
Correct Answer
B:A local routing-table import decision is not necessarily an LSA flooding filter in a link-state area. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Neighbor LSDB inspection shows LSAs still flood even if local route installation differs. The targeted correction is: Place summarization or route-advertisement controls at appropriate area boundaries rather than assuming an ordinary local import policy changes flooding.
Incorrect Answers
A:Interarea aggregation is performed by a suitable ABR; setting an unrelated import filter does not itself produce the expected summary. This is a plausible protocol explanation for a different OSPF condition, specifically Route summarization at ABR. Interarea aggregation is performed by a suitable ABR; setting an unrelated import filter does not itself produce the expected summary. In this scenario, however, the distinguishing issue is Inbound OSPF route filtering scope and the confirming observation is: Neighbor LSDB inspection shows LSAs still flood even if local route installation differs.
C:Summary advertisement must reflect actual reachable components and implementation rules to avoid attracting traffic to a missing site. This is a plausible protocol explanation for a different OSPF condition, specifically Area border prefix withdrawal. Summary advertisement must reflect actual reachable components and implementation rules to avoid attracting traffic to a missing site. In this scenario, however, the distinguishing issue is Inbound OSPF route filtering scope and the confirming observation is: Neighbor LSDB inspection shows LSAs still flood even if local route installation differs.
D:An external E2 metric primarily represents the advertised external cost, whereas E1 accounts for internal cost toward the ASBR plus external cost. This is a plausible protocol explanation for a different OSPF condition, specifically External E1 versus E2 selection. An external E2 metric primarily represents the advertised external cost, whereas E1 accounts for internal cost toward the ASBR plus external cost. In this scenario, however, the distinguishing issue is Inbound OSPF route filtering scope and the confirming observation is: Neighbor LSDB inspection shows LSAs still flood even if local route installation differs.
Question 83
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: An operator applied a routing policy on one downstream node hoping to stop an unwanted OSPF LSA from being flooded across the entire area. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Remote areas see the aggregate summary and no unwanted individual component advertisements under the defined policy.
- Remote routing and ABR detail show the correct summary withdrawal or safe discard behavior after the component disappears.
- Neighbor LSDB inspection shows LSAs still flood even if local route installation differs.
- The calculated path ranking changes as predicted when an E1 policy considers internal cost to each exit.
Explanation
Correct Answer
C:Neighbor LSDB inspection shows LSAs still flood even if local route installation differs. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: A local routing-table import decision is not necessarily an LSA flooding filter in a link-state area.
Incorrect Answers
A:Remote areas see the aggregate summary and no unwanted individual component advertisements under the defined policy. This is a plausible observed evidence for a different OSPF condition, specifically Route summarization at ABR. Interarea aggregation is performed by a suitable ABR; setting an unrelated import filter does not itself produce the expected summary. In this scenario, however, the distinguishing issue is Inbound OSPF route filtering scope and the confirming observation is: Neighbor LSDB inspection shows LSAs still flood even if local route installation differs.
B:Remote routing and ABR detail show the correct summary withdrawal or safe discard behavior after the component disappears. This is a plausible observed evidence for a different OSPF condition, specifically Area border prefix withdrawal. Summary advertisement must reflect actual reachable components and implementation rules to avoid attracting traffic to a missing site. In this scenario, however, the distinguishing issue is Inbound OSPF route filtering scope and the confirming observation is: Neighbor LSDB inspection shows LSAs still flood even if local route installation differs.
D:The calculated path ranking changes as predicted when an E1 policy considers internal cost to each exit. This is a plausible observed evidence for a different OSPF condition, specifically External E1 versus E2 selection. An external E2 metric primarily represents the advertised external cost, whereas E1 accounts for internal cost toward the ASBR plus external cost. In this scenario, however, the distinguishing issue is Inbound OSPF route filtering scope and the confirming observation is: Neighbor LSDB inspection shows LSAs still flood even if local route installation differs.
Question 84
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: An operator applied a routing policy on one downstream node hoping to stop an unwanted OSPF LSA from being flooded across the entire area. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Configure the ABR area range with a prefix that genuinely covers the intended internal networks.
- Correct aggregation and route-discard policy for the intended contributor-dependent reachability.
- Use an E1 policy when internal path cost to an external exit must influence the selection.
- Place summarization or route-advertisement controls at appropriate area boundaries rather than assuming an ordinary local import policy changes flooding.
Explanation
Correct Answer
D:Place summarization or route-advertisement controls at appropriate area boundaries rather than assuming an ordinary local import policy changes flooding. The change addresses the root behavior described here: A local routing-table import decision is not necessarily an LSA flooding filter in a link-state area. Verify success with: Neighbor LSDB inspection shows LSAs still flood even if local route installation differs.
Incorrect Answers
A:Configure the ABR area range with a prefix that genuinely covers the intended internal networks. This is a plausible configuration or operational fix for a different OSPF condition, specifically Route summarization at ABR. Interarea aggregation is performed by a suitable ABR; setting an unrelated import filter does not itself produce the expected summary. In this scenario, however, the distinguishing issue is Inbound OSPF route filtering scope and the confirming observation is: Neighbor LSDB inspection shows LSAs still flood even if local route installation differs.
B:Correct aggregation and route-discard policy for the intended contributor-dependent reachability. This is a plausible configuration or operational fix for a different OSPF condition, specifically Area border prefix withdrawal. Summary advertisement must reflect actual reachable components and implementation rules to avoid attracting traffic to a missing site. In this scenario, however, the distinguishing issue is Inbound OSPF route filtering scope and the confirming observation is: Neighbor LSDB inspection shows LSAs still flood even if local route installation differs.
C:Use an E1 policy when internal path cost to an external exit must influence the selection. This is a plausible configuration or operational fix for a different OSPF condition, specifically External E1 versus E2 selection. An external E2 metric primarily represents the advertised external cost, whereas E1 accounts for internal cost toward the ASBR plus external cost. In this scenario, however, the distinguishing issue is Inbound OSPF route filtering scope and the confirming observation is: Neighbor LSDB inspection shows LSAs still flood even if local route installation differs.
Question 85
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: An operator applied a routing policy on one downstream node hoping to stop an unwanted OSPF LSA from being flooded across the entire area. Which operational control would best prevent a recurrence of this exact failure mode?
- Validate both forwarding routes and LSDB contents during policy design reviews.
- Verify summary coverage and black-hole risk whenever component routes change.
- Include full component withdrawal in summary-routing regression tests.
- Test external metric-type assumptions after an ASBR topology or cost change.
Explanation
Correct Answer
A:Validate both forwarding routes and LSDB contents during policy design reviews. The control limits repetition of the described root condition: A local routing-table import decision is not necessarily an LSA flooding filter in a link-state area. During audits, confirm: Neighbor LSDB inspection shows LSAs still flood even if local route installation differs.
Incorrect Answers
B:Verify summary coverage and black-hole risk whenever component routes change. This is a plausible preventive practice for a different OSPF condition, specifically Route summarization at ABR. Interarea aggregation is performed by a suitable ABR; setting an unrelated import filter does not itself produce the expected summary. In this scenario, however, the distinguishing issue is Inbound OSPF route filtering scope and the confirming observation is: Neighbor LSDB inspection shows LSAs still flood even if local route installation differs.
C:Include full component withdrawal in summary-routing regression tests. This is a plausible preventive practice for a different OSPF condition, specifically Area border prefix withdrawal. Summary advertisement must reflect actual reachable components and implementation rules to avoid attracting traffic to a missing site. In this scenario, however, the distinguishing issue is Inbound OSPF route filtering scope and the confirming observation is: Neighbor LSDB inspection shows LSAs still flood even if local route installation differs.
D:Test external metric-type assumptions after an ASBR topology or cost change. This is a plausible preventive practice for a different OSPF condition, specifically External E1 versus E2 selection. An external E2 metric primarily represents the advertised external cost, whereas E1 accounts for internal cost toward the ASBR plus external cost. In this scenario, however, the distinguishing issue is Inbound OSPF route filtering scope and the confirming observation is: Neighbor LSDB inspection shows LSAs still flood even if local route installation differs.
Question 86
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: A provider path is unexpectedly asymmetric after one side of an OSPF transit pair changes its interface cost. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Check the transit area's type and the endpoints' shared nonbackbone-area participation.
- Compare directional interface costs and run shortest-path calculations from each router's own LSDB view.
- Inspect both peers' OSPF interface network type and resulting designated-router state.
- Compare authentication type, key identifier and accepted keys during the rollover window.
Explanation
Correct Answer
B:Compare directional interface costs and run shortest-path calculations from each router's own LSDB view. This check examines the decisive condition for SPF metric asymmetry before any unrelated changes are made. The underlying mechanism is: OSPF SPF uses each router's outbound link metrics, so directional cost differences can yield asymmetric paths. The confirming observation is: The calculated shortest paths match measured next hops after directional costs are accounted for.
Incorrect Answers
A:Check the transit area's type and the endpoints' shared nonbackbone-area participation. This is a plausible diagnostic check for a different OSPF condition, specifically Virtual-link transit eligibility. A virtual link needs a valid nonstub transit area between ABRs; a stub area cannot serve as the transit. In this scenario, however, the distinguishing issue is SPF metric asymmetry and the confirming observation is: The calculated shortest paths match measured next hops after directional costs are accounted for.
C:Inspect both peers' OSPF interface network type and resulting designated-router state. This is a plausible diagnostic check for a different OSPF condition, specifically OSPF point-to-point on Ethernet. A point-to-point OSPF interface avoids broadcast DR/BDR election behavior when both sides use a consistent compatible type. In this scenario, however, the distinguishing issue is SPF metric asymmetry and the confirming observation is: The calculated shortest paths match measured next hops after directional costs are accounted for.
D:Compare authentication type, key identifier and accepted keys during the rollover window. This is a plausible diagnostic check for a different OSPF condition, specifically OSPF authentication key rollover. Incompatible OSPF authentication settings cause received packets to be rejected before neighbor state can progress. In this scenario, however, the distinguishing issue is SPF metric asymmetry and the confirming observation is: The calculated shortest paths match measured next hops after directional costs are accounted for.
Question 87
During a core-routing migration rehearsal, an HPE Juniper Networking engineer investigates this situation: A provider path is unexpectedly asymmetric after one side of an OSPF transit pair changes its interface cost. Which routing or service mechanism best explains the reported behavior?
- A virtual link needs a valid nonstub transit area between ABRs; a stub area cannot serve as the transit.
- A point-to-point OSPF interface avoids broadcast DR/BDR election behavior when both sides use a consistent compatible type.
- OSPF SPF uses each router's outbound link metrics, so directional cost differences can yield asymmetric paths.
- Incompatible OSPF authentication settings cause received packets to be rejected before neighbor state can progress.
Explanation
Correct Answer
C:OSPF SPF uses each router's outbound link metrics, so directional cost differences can yield asymmetric 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 calculated shortest paths match measured next hops after directional costs are accounted for. The targeted correction is: Normalize planned costs or explicitly accept asymmetry based on tested service requirements.
Incorrect Answers
A:A virtual link needs a valid nonstub transit area between ABRs; a stub area cannot serve as the transit. This is a plausible protocol explanation for a different OSPF condition, specifically Virtual-link transit eligibility. A virtual link needs a valid nonstub transit area between ABRs; a stub area cannot serve as the transit. In this scenario, however, the distinguishing issue is SPF metric asymmetry and the confirming observation is: The calculated shortest paths match measured next hops after directional costs are accounted for.
B:A point-to-point OSPF interface avoids broadcast DR/BDR election behavior when both sides use a consistent compatible type. This is a plausible protocol explanation for a different OSPF condition, specifically OSPF point-to-point on Ethernet. A point-to-point OSPF interface avoids broadcast DR/BDR election behavior when both sides use a consistent compatible type. In this scenario, however, the distinguishing issue is SPF metric asymmetry and the confirming observation is: The calculated shortest paths match measured next hops after directional costs are accounted for.
D:Incompatible OSPF authentication settings cause received packets to be rejected before neighbor state can progress. This is a plausible protocol explanation for a different OSPF condition, specifically OSPF authentication key rollover. Incompatible OSPF authentication settings cause received packets to be rejected before neighbor state can progress. In this scenario, however, the distinguishing issue is SPF metric asymmetry and the confirming observation is: The calculated shortest paths match measured next hops after directional costs are accounted for.
Question 88
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: A provider path is unexpectedly asymmetric after one side of an OSPF transit pair changes its interface cost. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The virtual-link adjacency establishes through an eligible common transit area and backbone routes synchronize.
- The pair reaches Full without a broadcast-segment DR/BDR election under the point-to-point design.
- Authentication counters and logs stop showing rejects and the existing adjacency returns to Full.
- The calculated shortest paths match measured next hops after directional costs are accounted for.
Explanation
Correct Answer
D:The calculated shortest paths match measured next hops after directional costs are accounted for. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: OSPF SPF uses each router's outbound link metrics, so directional cost differences can yield asymmetric paths.
Incorrect Answers
A:The virtual-link adjacency establishes through an eligible common transit area and backbone routes synchronize. This is a plausible observed evidence for a different OSPF condition, specifically Virtual-link transit eligibility. A virtual link needs a valid nonstub transit area between ABRs; a stub area cannot serve as the transit. In this scenario, however, the distinguishing issue is SPF metric asymmetry and the confirming observation is: The calculated shortest paths match measured next hops after directional costs are accounted for.
B:The pair reaches Full without a broadcast-segment DR/BDR election under the point-to-point design. This is a plausible observed evidence for a different OSPF condition, specifically OSPF point-to-point on Ethernet. A point-to-point OSPF interface avoids broadcast DR/BDR election behavior when both sides use a consistent compatible type. In this scenario, however, the distinguishing issue is SPF metric asymmetry and the confirming observation is: The calculated shortest paths match measured next hops after directional costs are accounted for.
C:Authentication counters and logs stop showing rejects and the existing adjacency returns to Full. This is a plausible observed evidence for a different OSPF condition, specifically OSPF authentication key rollover. Incompatible OSPF authentication settings cause received packets to be rejected before neighbor state can progress. In this scenario, however, the distinguishing issue is SPF metric asymmetry and the confirming observation is: The calculated shortest paths match measured next hops after directional costs are accounted for.
Question 89
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: A provider path is unexpectedly asymmetric after one side of an OSPF transit pair changes its interface cost. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Normalize planned costs or explicitly accept asymmetry based on tested service requirements.
- Select a normal transit area or redesign physical backbone connectivity instead of placing the virtual link through the stub.
- Use point-to-point OSPF interface operation consistently on the dedicated link.
- Coordinate compatible key-chain or key settings across both peers with an overlap period where supported.
Explanation
Correct Answer
A:Normalize planned costs or explicitly accept asymmetry based on tested service requirements. The change addresses the root behavior described here: OSPF SPF uses each router's outbound link metrics, so directional cost differences can yield asymmetric paths. Verify success with: The calculated shortest paths match measured next hops after directional costs are accounted for.
Incorrect Answers
B:Select a normal transit area or redesign physical backbone connectivity instead of placing the virtual link through the stub. This is a plausible configuration or operational fix for a different OSPF condition, specifically Virtual-link transit eligibility. A virtual link needs a valid nonstub transit area between ABRs; a stub area cannot serve as the transit. In this scenario, however, the distinguishing issue is SPF metric asymmetry and the confirming observation is: The calculated shortest paths match measured next hops after directional costs are accounted for.
C:Use point-to-point OSPF interface operation consistently on the dedicated link. This is a plausible configuration or operational fix for a different OSPF condition, specifically OSPF point-to-point on Ethernet. A point-to-point OSPF interface avoids broadcast DR/BDR election behavior when both sides use a consistent compatible type. In this scenario, however, the distinguishing issue is SPF metric asymmetry and the confirming observation is: The calculated shortest paths match measured next hops after directional costs are accounted for.
D:Coordinate compatible key-chain or key settings across both peers with an overlap period where supported. This is a plausible configuration or operational fix for a different OSPF condition, specifically OSPF authentication key rollover. Incompatible OSPF authentication settings cause received packets to be rejected before neighbor state can progress. In this scenario, however, the distinguishing issue is SPF metric asymmetry and the confirming observation is: The calculated shortest paths match measured next hops after directional costs are accounted for.
Question 90
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: A provider path is unexpectedly asymmetric after one side of an OSPF transit pair changes its interface cost. Which operational control would best prevent a recurrence of this exact failure mode?
- Document virtual links as a temporary remediation with a planned backbone simplification.
- Model forward and return paths after interface-cost maintenance.
- Require a backbone-continuity diagram and test reachability between nonbackbone areas during changes.
- Document OSPF network types for dedicated versus shared Ethernet circuits.
Explanation
Correct Answer
B:Model forward and return paths after interface-cost maintenance. The control limits repetition of the described root condition: OSPF SPF uses each router's outbound link metrics, so directional cost differences can yield asymmetric paths. During audits, confirm: The calculated shortest paths match measured next hops after directional costs are accounted for.
Incorrect Answers
A:Document virtual links as a temporary remediation with a planned backbone simplification. This is a plausible preventive practice for a different OSPF condition, specifically Virtual-link transit eligibility. A virtual link needs a valid nonstub transit area between ABRs; a stub area cannot serve as the transit. In this scenario, however, the distinguishing issue is SPF metric asymmetry and the confirming observation is: The calculated shortest paths match measured next hops after directional costs are accounted for.
C:Require a backbone-continuity diagram and test reachability between nonbackbone areas during changes. This is a plausible preventive practice for a different OSPF condition, specifically Backbone continuity through ABR. OSPF interarea routing normally depends on a continuous area 0 backbone reached through ABRs. In this scenario, however, the distinguishing issue is SPF metric asymmetry and the confirming observation is: The calculated shortest paths match measured next hops after directional costs are accounted for.
D:Document OSPF network types for dedicated versus shared Ethernet circuits. This is a plausible preventive practice for a different OSPF condition, specifically OSPF point-to-point on Ethernet. A point-to-point OSPF interface avoids broadcast DR/BDR election behavior when both sides use a consistent compatible type. In this scenario, however, the distinguishing issue is SPF metric asymmetry and the confirming observation is: The calculated shortest paths match measured next hops after directional costs are accounted for.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests