Question 1
During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: A provider access area was converted to an OSPF stub, after which the routers stopped receiving individual AS-external prefixes even though internal prefixes remain reachable. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare the area's stub configuration and its LSA types with the missing external destinations.
- Inspect the ABR's area range configuration and the origin of interarea summary LSAs.
- Inspect backbone reachability and actual upstream service path behind the advertised default.
- Inspect both peers' OSPF interface network type and resulting designated-router state.
Explanation
Correct Answer
A:Compare the area's stub configuration and its LSA types with the missing external destinations. This check examines the decisive condition for Stub-area external reachability before any unrelated changes are made. The underlying mechanism is: A stub area excludes AS-external type 5 LSAs and relies on ABR-supplied reachability rather than importing individual external routes. The confirming observation is: The local LSDB lacks type 5 LSAs while an ABR-provided default can still be installed.
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 Stub-area external reachability and the confirming observation is: The local LSDB lacks type 5 LSAs while an ABR-provided default can still be installed.
C:Inspect backbone reachability and actual upstream service path behind the advertised default. This is a plausible diagnostic check for a different OSPF condition, specifically OSPF ABR default-route validation. Receiving an OSPF default route only indicates a routing advertisement; it does not guarantee a healthy upstream service path. In this scenario, however, the distinguishing issue is Stub-area external reachability and the confirming observation is: The local LSDB lacks type 5 LSAs while an ABR-provided default can still be installed.
D: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 Stub-area external reachability and the confirming observation is: The local LSDB lacks type 5 LSAs while an ABR-provided default can still be installed.
Question 2
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: A provider access area was converted to an OSPF stub, after which the routers stopped receiving individual AS-external prefixes even though internal prefixes remain reachable. 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 stub area excludes AS-external type 5 LSAs and relies on ABR-supplied reachability rather than importing individual external routes.
- Receiving an OSPF default route only indicates a routing advertisement; it does not guarantee a healthy upstream service path.
- A point-to-point OSPF interface avoids broadcast DR/BDR election behavior when both sides use a consistent compatible type.
Explanation
Correct Answer
B:A stub area excludes AS-external type 5 LSAs and relies on ABR-supplied reachability rather than importing individual external routes. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The local LSDB lacks type 5 LSAs while an ABR-provided default can still be installed. The targeted correction is: Use a normal area if individual external LSAs are required, or explicitly design default-route reachability through the ABR.
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 Stub-area external reachability and the confirming observation is: The local LSDB lacks type 5 LSAs while an ABR-provided default can still be installed.
C:Receiving an OSPF default route only indicates a routing advertisement; it does not guarantee a healthy upstream service path. This is a plausible protocol explanation for a different OSPF condition, specifically OSPF ABR default-route validation. Receiving an OSPF default route only indicates a routing advertisement; it does not guarantee a healthy upstream service path. In this scenario, however, the distinguishing issue is Stub-area external reachability and the confirming observation is: The local LSDB lacks type 5 LSAs while an ABR-provided default can still be installed.
D: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 Stub-area external reachability and the confirming observation is: The local LSDB lacks type 5 LSAs while an ABR-provided default can still be installed.
Question 3
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: A provider access area was converted to an OSPF stub, after which the routers stopped receiving individual AS-external prefixes even though internal prefixes remain reachable. 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.
- End-to-end checks through the ABR succeed while its advertised default is valid and failover behavior is documented.
- The local LSDB lacks type 5 LSAs while an ABR-provided default can still be installed.
- The pair reaches Full without a broadcast-segment DR/BDR election under the point-to-point design.
Explanation
Correct Answer
C:The local LSDB lacks type 5 LSAs while an ABR-provided default can still be installed. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: A stub area excludes AS-external type 5 LSAs and relies on ABR-supplied reachability rather than importing individual external routes.
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 Stub-area external reachability and the confirming observation is: The local LSDB lacks type 5 LSAs while an ABR-provided default can still be installed.
B:End-to-end checks through the ABR succeed while its advertised default is valid and failover behavior is documented. This is a plausible observed evidence for a different OSPF condition, specifically OSPF ABR default-route validation. Receiving an OSPF default route only indicates a routing advertisement; it does not guarantee a healthy upstream service path. In this scenario, however, the distinguishing issue is Stub-area external reachability and the confirming observation is: The local LSDB lacks type 5 LSAs while an ABR-provided default can still be installed.
D: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 Stub-area external reachability and the confirming observation is: The local LSDB lacks type 5 LSAs while an ABR-provided default can still be installed.
Question 4
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: A provider access area was converted to an OSPF stub, after which the routers stopped receiving individual AS-external prefixes even though internal prefixes remain reachable. 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.
- Tie default-origination behavior to the intended exit architecture and upstream monitoring where feasible.
- Use point-to-point OSPF interface operation consistently on the dedicated link.
- Use a normal area if individual external LSAs are required, or explicitly design default-route reachability through the ABR.
Explanation
Correct Answer
D:Use a normal area if individual external LSAs are required, or explicitly design default-route reachability through the ABR. The change addresses the root behavior described here: A stub area excludes AS-external type 5 LSAs and relies on ABR-supplied reachability rather than importing individual external routes. Verify success with: The local LSDB lacks type 5 LSAs while an ABR-provided default can still be installed.
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 Stub-area external reachability and the confirming observation is: The local LSDB lacks type 5 LSAs while an ABR-provided default can still be installed.
B:Tie default-origination behavior to the intended exit architecture and upstream monitoring where feasible. This is a plausible configuration or operational fix for a different OSPF condition, specifically OSPF ABR default-route validation. Receiving an OSPF default route only indicates a routing advertisement; it does not guarantee a healthy upstream service path. In this scenario, however, the distinguishing issue is Stub-area external reachability and the confirming observation is: The local LSDB lacks type 5 LSAs while an ABR-provided default can still be installed.
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 Stub-area external reachability and the confirming observation is: The local LSDB lacks type 5 LSAs while an ABR-provided default can still be installed.
Question 5
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: A provider access area was converted to an OSPF stub, after which the routers stopped receiving individual AS-external prefixes even though internal prefixes remain reachable. 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.
- Verify summary coverage and black-hole risk whenever component routes change.
- Test loss of upstream connectivity separately from loss of the local OSPF adjacency.
- Document OSPF network types for dedicated versus shared Ethernet circuits.
Explanation
Correct Answer
A:Record permitted LSA types and verify the default route before converting an area to stub. The control limits repetition of the described root condition: A stub area excludes AS-external type 5 LSAs and relies on ABR-supplied reachability rather than importing individual external routes. During audits, confirm: The local LSDB lacks type 5 LSAs while an ABR-provided default can still be installed.
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 Stub-area external reachability and the confirming observation is: The local LSDB lacks type 5 LSAs while an ABR-provided default can still be installed.
C:Test loss of upstream connectivity separately from loss of the local OSPF adjacency. This is a plausible preventive practice for a different OSPF condition, specifically OSPF ABR default-route validation. Receiving an OSPF default route only indicates a routing advertisement; it does not guarantee a healthy upstream service path. In this scenario, however, the distinguishing issue is Stub-area external reachability and the confirming observation is: The local LSDB lacks type 5 LSAs while an ABR-provided default can still be installed.
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 Stub-area external reachability and the confirming observation is: The local LSDB lacks type 5 LSAs while an ABR-provided default can still be installed.
Question 6
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: A remote OSPF area must inject a branch-only external prefix but the access router is not allowed to flood ordinary type 5 LSAs within the area. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect the ABR's area range configuration and the origin of interarea summary LSAs.
- Inspect NSSA configuration and the presence and translation of type 7 LSAs at its ABR.
- Inspect backbone reachability and actual upstream service path behind the advertised default.
- Inspect LSA sequence numbers, age and LSDB synchronization before adjusting interface bandwidth.
Explanation
Correct Answer
B:Inspect NSSA configuration and the presence and translation of type 7 LSAs at its ABR. This check examines the decisive condition for NSSA external redistribution before any unrelated changes are made. The underlying mechanism is: An NSSA can carry locally redistributed externals as type 7 LSAs, which an eligible ABR translates to type 5 outside the NSSA. The confirming observation is: The NSSA LSDB contains the type 7 prefix and another area receives the translated external advertisement.
Incorrect Answers
A: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 NSSA external redistribution and the confirming observation is: The NSSA LSDB contains the type 7 prefix and another area receives the translated external advertisement.
C:Inspect backbone reachability and actual upstream service path behind the advertised default. This is a plausible diagnostic check for a different OSPF condition, specifically OSPF ABR default-route validation. Receiving an OSPF default route only indicates a routing advertisement; it does not guarantee a healthy upstream service path. In this scenario, however, the distinguishing issue is NSSA external redistribution and the confirming observation is: The NSSA LSDB contains the type 7 prefix and another area receives the translated external advertisement.
D:Inspect LSA sequence numbers, age and LSDB synchronization before adjusting interface bandwidth. This is a plausible diagnostic check 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 NSSA external redistribution and the confirming observation is: The NSSA LSDB contains the type 7 prefix and another area receives the translated external advertisement.
Question 7
During a core-routing migration rehearsal, an HPE Juniper Networking engineer investigates this situation: A remote OSPF area must inject a branch-only external prefix but the access router is not allowed to flood ordinary type 5 LSAs within the 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.
- Receiving an OSPF default route only indicates a routing advertisement; it does not guarantee a healthy upstream service path.
- An NSSA can carry locally redistributed externals as type 7 LSAs, which an eligible ABR translates to type 5 outside the NSSA.
- Link-state routes depend on consistent current LSAs and completed SPF processing, not solely on neighbor Full status.
Explanation
Correct Answer
C:An NSSA can carry locally redistributed externals as type 7 LSAs, which an eligible ABR translates to type 5 outside the NSSA. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The NSSA LSDB contains the type 7 prefix and another area receives the translated external advertisement. The targeted correction is: Configure the required area as NSSA and authorize controlled redistribution and type 7 translation.
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 NSSA external redistribution and the confirming observation is: The NSSA LSDB contains the type 7 prefix and another area receives the translated external advertisement.
B:Receiving an OSPF default route only indicates a routing advertisement; it does not guarantee a healthy upstream service path. This is a plausible protocol explanation for a different OSPF condition, specifically OSPF ABR default-route validation. Receiving an OSPF default route only indicates a routing advertisement; it does not guarantee a healthy upstream service path. In this scenario, however, the distinguishing issue is NSSA external redistribution and the confirming observation is: The NSSA LSDB contains the type 7 prefix and another area receives the translated external advertisement.
D:Link-state routes depend on consistent current LSAs and completed SPF processing, not solely on neighbor Full status. This is a plausible protocol explanation 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 NSSA external redistribution and the confirming observation is: The NSSA LSDB contains the type 7 prefix and another area receives the translated external advertisement.
Question 8
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: A remote OSPF area must inject a branch-only external prefix but the access router is not allowed to flood ordinary type 5 LSAs within the 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.
- End-to-end checks through the ABR succeed while its advertised default is valid and failover behavior is documented.
- Both routers hold the current LSA instance and SPF results match the intended next-hop behavior.
- The NSSA LSDB contains the type 7 prefix and another area receives the translated external advertisement.
Explanation
Correct Answer
D:The NSSA LSDB contains the type 7 prefix and another area receives the translated external advertisement. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: An NSSA can carry locally redistributed externals as type 7 LSAs, which an eligible ABR translates to type 5 outside the NSSA.
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 NSSA external redistribution and the confirming observation is: The NSSA LSDB contains the type 7 prefix and another area receives the translated external advertisement.
B:End-to-end checks through the ABR succeed while its advertised default is valid and failover behavior is documented. This is a plausible observed evidence for a different OSPF condition, specifically OSPF ABR default-route validation. Receiving an OSPF default route only indicates a routing advertisement; it does not guarantee a healthy upstream service path. In this scenario, however, the distinguishing issue is NSSA external redistribution and the confirming observation is: The NSSA LSDB contains the type 7 prefix and another area receives the translated external advertisement.
C:Both routers hold the current LSA instance and SPF results match the intended next-hop behavior. This is a plausible observed evidence 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 NSSA external redistribution and the confirming observation is: The NSSA LSDB contains the type 7 prefix and another area receives the translated external advertisement.
Question 9
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: A remote OSPF area must inject a branch-only external prefix but the access router is not allowed to flood ordinary type 5 LSAs within the area. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Configure the required area as NSSA and authorize controlled redistribution and type 7 translation.
- Configure the ABR area range with a prefix that genuinely covers the intended internal networks.
- Tie default-origination behavior to the intended exit architecture and upstream monitoring where feasible.
- Correct LSA synchronization or update flooding causes, then allow the SPF process to converge.
Explanation
Correct Answer
A:Configure the required area as NSSA and authorize controlled redistribution and type 7 translation. The change addresses the root behavior described here: An NSSA can carry locally redistributed externals as type 7 LSAs, which an eligible ABR translates to type 5 outside the NSSA. Verify success with: The NSSA LSDB contains the type 7 prefix and another area receives the translated external advertisement.
Incorrect Answers
B: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 NSSA external redistribution and the confirming observation is: The NSSA LSDB contains the type 7 prefix and another area receives the translated external advertisement.
C:Tie default-origination behavior to the intended exit architecture and upstream monitoring where feasible. This is a plausible configuration or operational fix for a different OSPF condition, specifically OSPF ABR default-route validation. Receiving an OSPF default route only indicates a routing advertisement; it does not guarantee a healthy upstream service path. In this scenario, however, the distinguishing issue is NSSA external redistribution and the confirming observation is: The NSSA LSDB contains the type 7 prefix and another area receives the translated external advertisement.
D:Correct LSA synchronization or update flooding causes, then allow the SPF process to converge. This is a plausible configuration or operational fix 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 NSSA external redistribution and the confirming observation is: The NSSA LSDB contains the type 7 prefix and another area receives the translated external advertisement.
Question 10
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: A remote OSPF area must inject a branch-only external prefix but the access router is not allowed to flood ordinary type 5 LSAs within the area. Which operational control would best prevent a recurrence of this exact failure mode?
- Verify summary coverage and black-hole risk whenever component routes change.
- Test both the NSSA LSDB and remote external route installation after a redistribution change.
- Test loss of upstream connectivity separately from loss of the local OSPF adjacency.
- Monitor LSDB freshness and SPF processing during periods of churn.
Explanation
Correct Answer
B:Test both the NSSA LSDB and remote external route installation after a redistribution change. The control limits repetition of the described root condition: An NSSA can carry locally redistributed externals as type 7 LSAs, which an eligible ABR translates to type 5 outside the NSSA. During audits, confirm: The NSSA LSDB contains the type 7 prefix and another area receives the translated external advertisement.
Incorrect Answers
A: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 NSSA external redistribution and the confirming observation is: The NSSA LSDB contains the type 7 prefix and another area receives the translated external advertisement.
C:Test loss of upstream connectivity separately from loss of the local OSPF adjacency. This is a plausible preventive practice for a different OSPF condition, specifically OSPF ABR default-route validation. Receiving an OSPF default route only indicates a routing advertisement; it does not guarantee a healthy upstream service path. In this scenario, however, the distinguishing issue is NSSA external redistribution and the confirming observation is: The NSSA LSDB contains the type 7 prefix and another area receives the translated external advertisement.
D: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 NSSA external redistribution and the confirming observation is: The NSSA LSDB contains the type 7 prefix and another area receives the translated external advertisement.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests