Question 100
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: A dedicated Ethernet pair experiences unnecessary DR-related behavior even though there are only two routers and no shared third-party devices. 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.
- Audit OSPF interface timers during template deployment and route maintenance.
- Test external metric-type assumptions after an ASBR topology or cost change.
- Document OSPF network types for dedicated versus shared Ethernet circuits.
Explanation
Correct Answer
D:Document OSPF network types for dedicated versus shared Ethernet circuits. The control limits repetition of the described root condition: A point-to-point OSPF interface avoids broadcast DR/BDR election behavior when both sides use a consistent compatible type. During audits, confirm: The pair reaches Full without a broadcast-segment DR/BDR election under the point-to-point design.
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 point-to-point on Ethernet and the confirming observation is: The pair reaches Full without a broadcast-segment DR/BDR election under the point-to-point design.
B:Audit OSPF interface timers during template deployment and route maintenance. This is a plausible preventive practice for a different OSPF condition, specifically Hello/dead timer mismatch. Neighbors must agree on key OSPF Hello parameters, including timing intervals, to maintain adjacency. In this scenario, however, the distinguishing issue is OSPF point-to-point on Ethernet and the confirming observation is: The pair reaches Full without a broadcast-segment DR/BDR election under the point-to-point design.
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 point-to-point on Ethernet and the confirming observation is: The pair reaches Full without a broadcast-segment DR/BDR election under the point-to-point design.
Question 101
During an edge-to-core validation, an HPE Juniper Networking engineer investigates this situation: Two OSPF devices were cloned with identical router IDs and show unstable or confusing link-state information during a core replacement. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare router IDs and the origins of LSAs across the affected area.
- Check the transit area's type and the endpoints' shared nonbackbone-area participation.
- Inspect both peers' OSPF interface network type and resulting designated-router state.
- Compare the negotiated interface MTU and database description exchange counters on both ends.
Explanation
Correct Answer
A:Compare router IDs and the origins of LSAs across the affected area. This check examines the decisive condition for OSPF duplicate router identifier before any unrelated changes are made. The underlying mechanism is: Duplicate router IDs undermine unique identification of OSPF LSA originators and can corrupt stable topology interpretation. The confirming observation is: Each router originates LSAs under a distinct ID and the LSDB converges without conflicting self-originated data.
Incorrect Answers
B: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 OSPF duplicate router identifier and the confirming observation is: Each router originates LSAs under a distinct ID and the LSDB converges without conflicting self-originated data.
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 OSPF duplicate router identifier and the confirming observation is: Each router originates LSAs under a distinct ID and the LSDB converges without conflicting self-originated data.
D:Compare the negotiated interface MTU and database description exchange counters on both ends. This is a plausible diagnostic check for a different OSPF condition, specifically OSPF MTU adjacency ExStart. Inconsistent MTU handling can prevent successful OSPF database description exchange despite matching Hello parameters. In this scenario, however, the distinguishing issue is OSPF duplicate router identifier and the confirming observation is: Each router originates LSAs under a distinct ID and the LSDB converges without conflicting self-originated data.
Question 102
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: Two OSPF devices were cloned with identical router IDs and show unstable or confusing link-state information during a core replacement. 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.
- Duplicate router IDs undermine unique identification of OSPF LSA originators and can corrupt stable topology interpretation.
- A point-to-point OSPF interface avoids broadcast DR/BDR election behavior when both sides use a consistent compatible type.
- Inconsistent MTU handling can prevent successful OSPF database description exchange despite matching Hello parameters.
Explanation
Correct Answer
B:Duplicate router IDs undermine unique identification of OSPF LSA originators and can corrupt stable topology interpretation. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Each router originates LSAs under a distinct ID and the LSDB converges without conflicting self-originated data. The targeted correction is: Assign unique router IDs and restart or reset the affected protocol process in a controlled change.
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 OSPF duplicate router identifier and the confirming observation is: Each router originates LSAs under a distinct ID and the LSDB converges without conflicting self-originated data.
C: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 OSPF duplicate router identifier and the confirming observation is: Each router originates LSAs under a distinct ID and the LSDB converges without conflicting self-originated data.
D:Inconsistent MTU handling can prevent successful OSPF database description exchange despite matching Hello parameters. This is a plausible protocol explanation for a different OSPF condition, specifically OSPF MTU adjacency ExStart. Inconsistent MTU handling can prevent successful OSPF database description exchange despite matching Hello parameters. In this scenario, however, the distinguishing issue is OSPF duplicate router identifier and the confirming observation is: Each router originates LSAs under a distinct ID and the LSDB converges without conflicting self-originated data.
Question 103
During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: Two OSPF devices were cloned with identical router IDs and show unstable or confusing link-state information during a core replacement. 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.
- Each router originates LSAs under a distinct ID and the LSDB converges without conflicting self-originated data.
- Neighbor detail moves from ExStart to Full after MTU alignment without suppressing required checks.
Explanation
Correct Answer
C:Each router originates LSAs under a distinct ID and the LSDB converges without conflicting self-originated data. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Duplicate router IDs undermine unique identification of OSPF LSA originators and can corrupt stable topology interpretation.
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 OSPF duplicate router identifier and the confirming observation is: Each router originates LSAs under a distinct ID and the LSDB converges without conflicting self-originated data.
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 OSPF duplicate router identifier and the confirming observation is: Each router originates LSAs under a distinct ID and the LSDB converges without conflicting self-originated data.
D:Neighbor detail moves from ExStart to Full after MTU alignment without suppressing required checks. This is a plausible observed evidence for a different OSPF condition, specifically OSPF MTU adjacency ExStart. Inconsistent MTU handling can prevent successful OSPF database description exchange despite matching Hello parameters. In this scenario, however, the distinguishing issue is OSPF duplicate router identifier and the confirming observation is: Each router originates LSAs under a distinct ID and the LSDB converges without conflicting self-originated data.
Question 104
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: Two OSPF devices were cloned with identical router IDs and show unstable or confusing link-state information during a core replacement. Which response or focused corrective action best addresses this situation without changing unrelated components?
- 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.
- Correct MTU consistency across the adjacency and retain valid OSPF database synchronization.
- Assign unique router IDs and restart or reset the affected protocol process in a controlled change.
Explanation
Correct Answer
D:Assign unique router IDs and restart or reset the affected protocol process in a controlled change. The change addresses the root behavior described here: Duplicate router IDs undermine unique identification of OSPF LSA originators and can corrupt stable topology interpretation. Verify success with: Each router originates LSAs under a distinct ID and the LSDB converges without conflicting self-originated data.
Incorrect Answers
A: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 OSPF duplicate router identifier and the confirming observation is: Each router originates LSAs under a distinct ID and the LSDB converges without conflicting self-originated data.
B: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 OSPF duplicate router identifier and the confirming observation is: Each router originates LSAs under a distinct ID and the LSDB converges without conflicting self-originated data.
C:Correct MTU consistency across the adjacency and retain valid OSPF database synchronization. This is a plausible configuration or operational fix for a different OSPF condition, specifically OSPF MTU adjacency ExStart. Inconsistent MTU handling can prevent successful OSPF database description exchange despite matching Hello parameters. In this scenario, however, the distinguishing issue is OSPF duplicate router identifier and the confirming observation is: Each router originates LSAs under a distinct ID and the LSDB converges without conflicting self-originated data.
Question 105
During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: Two OSPF devices were cloned with identical router IDs and show unstable or confusing link-state information during a core replacement. Which operational control would best prevent a recurrence of this exact failure mode?
- Check router-ID uniqueness before bringing cloned routing instances online.
- Document virtual links as a temporary remediation with a planned backbone simplification.
- Document OSPF network types for dedicated versus shared Ethernet circuits.
- Include interface MTU parity and the neighbor Full state in standard link acceptance tests.
Explanation
Correct Answer
A:Check router-ID uniqueness before bringing cloned routing instances online. The control limits repetition of the described root condition: Duplicate router IDs undermine unique identification of OSPF LSA originators and can corrupt stable topology interpretation. During audits, confirm: Each router originates LSAs under a distinct ID and the LSDB converges without conflicting self-originated data.
Incorrect Answers
B: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 OSPF duplicate router identifier and the confirming observation is: Each router originates LSAs under a distinct ID and the LSDB converges without conflicting self-originated data.
C: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 OSPF duplicate router identifier and the confirming observation is: Each router originates LSAs under a distinct ID and the LSDB converges without conflicting self-originated data.
D:Include interface MTU parity and the neighbor Full state in standard link acceptance tests. This is a plausible preventive practice for a different OSPF condition, specifically OSPF MTU adjacency ExStart. Inconsistent MTU handling can prevent successful OSPF database description exchange despite matching Hello parameters. In this scenario, however, the distinguishing issue is OSPF duplicate router identifier and the confirming observation is: Each router originates LSAs under a distinct ID and the LSDB converges without conflicting self-originated data.
Question 106
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: A summarized OSPF route remains advertised from an ABR after the last valid component subnet was removed from the area. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Identify which LSA type carries the prefixes and whether they originate at an ASBR rather than an ABR.
- Inspect the ABR aggregate's contributing prefixes and current summary advertisement conditions.
- Inspect NSSA configuration and the presence and translation of type 7 LSAs at its ABR.
- Compare the local route-install decision with LSA propagation in neighboring link-state databases.
Explanation
Correct Answer
B:Inspect the ABR aggregate's contributing prefixes and current summary advertisement conditions. This check examines the decisive condition for Area border prefix withdrawal before any unrelated changes are made. The underlying mechanism is: Summary advertisement must reflect actual reachable components and implementation rules to avoid attracting traffic to a missing site. The confirming observation is: Remote routing and ABR detail show the correct summary withdrawal or safe discard behavior after the component disappears.
Incorrect Answers
A:Identify which LSA type carries the prefixes and whether they originate at an ASBR rather than an ABR. This is a plausible diagnostic check for a different OSPF condition, specifically ASBR external aggregation. AS-external advertisements have a different summarization control point from interarea type 3 summaries. In this scenario, however, the distinguishing issue is Area border prefix withdrawal and the confirming observation is: Remote routing and ABR detail show the correct summary withdrawal or safe discard behavior after the component disappears.
C:Inspect NSSA configuration and the presence and translation of type 7 LSAs at its ABR. This is a plausible diagnostic check for a different OSPF condition, specifically NSSA external redistribution. An NSSA can carry locally redistributed externals as type 7 LSAs, which an eligible ABR translates to type 5 outside the NSSA. In this scenario, however, the distinguishing issue is Area border prefix withdrawal and the confirming observation is: Remote routing and ABR detail show the correct summary withdrawal or safe discard behavior after the component disappears.
D:Compare the local route-install decision with LSA propagation in neighboring link-state databases. This is a plausible diagnostic check for a different OSPF condition, specifically Inbound OSPF route filtering scope. A local routing-table import decision is not necessarily an LSA flooding filter in a link-state area. In this scenario, however, the distinguishing issue is Area border prefix withdrawal and the confirming observation is: Remote routing and ABR detail show the correct summary withdrawal or safe discard behavior after the component disappears.
Question 107
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: A summarized OSPF route remains advertised from an ABR after the last valid component subnet was removed from the area. Which routing or service mechanism best explains the reported behavior?
- AS-external advertisements have a different summarization control point from interarea type 3 summaries.
- An NSSA can carry locally redistributed externals as type 7 LSAs, which an eligible ABR translates to type 5 outside the NSSA.
- Summary advertisement must reflect actual reachable components and implementation rules to avoid attracting traffic to a missing site.
- A local routing-table import decision is not necessarily an LSA flooding filter in a link-state area.
Explanation
Correct Answer
C:Summary advertisement must reflect actual reachable components and implementation rules to avoid attracting traffic to a missing site. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Remote routing and ABR detail show the correct summary withdrawal or safe discard behavior after the component disappears. The targeted correction is: Correct aggregation and route-discard policy for the intended contributor-dependent reachability.
Incorrect Answers
A:AS-external advertisements have a different summarization control point from interarea type 3 summaries. This is a plausible protocol explanation for a different OSPF condition, specifically ASBR external aggregation. AS-external advertisements have a different summarization control point from interarea type 3 summaries. In this scenario, however, the distinguishing issue is Area border prefix withdrawal and the confirming observation is: Remote routing and ABR detail show the correct summary withdrawal or safe discard behavior after the component disappears.
B:An NSSA can carry locally redistributed externals as type 7 LSAs, which an eligible ABR translates to type 5 outside the NSSA. This is a plausible protocol explanation for a different OSPF condition, specifically NSSA external redistribution. An NSSA can carry locally redistributed externals as type 7 LSAs, which an eligible ABR translates to type 5 outside the NSSA. In this scenario, however, the distinguishing issue is Area border prefix withdrawal and the confirming observation is: Remote routing and ABR detail show the correct summary withdrawal or safe discard behavior after the component disappears.
D:A local routing-table import decision is not necessarily an LSA flooding filter in a link-state area. This is a plausible protocol explanation for a different OSPF condition, specifically Inbound OSPF route filtering scope. A local routing-table import decision is not necessarily an LSA flooding filter in a link-state area. In this scenario, however, the distinguishing issue is Area border prefix withdrawal and the confirming observation is: Remote routing and ABR detail show the correct summary withdrawal or safe discard behavior after the component disappears.
Question 108
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: A summarized OSPF route remains advertised from an ABR after the last valid component subnet was removed from the area. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The NSSA LSDB contains the type 7 prefix and another area receives the translated external advertisement.
- Neighbor LSDB inspection shows LSAs still flood even if local route installation differs.
- ABR neighbors and area 0 LSAs show a continuous interarea path after the design repair.
- Remote routing and ABR detail show the correct summary withdrawal or safe discard behavior after the component disappears.
Explanation
Correct Answer
D:Remote routing and ABR detail show the correct summary withdrawal or safe discard behavior after the component disappears. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Summary advertisement must reflect actual reachable components and implementation rules to avoid attracting traffic to a missing site.
Incorrect Answers
A:The NSSA LSDB contains the type 7 prefix and another area receives the translated external advertisement. This is a plausible observed evidence for a different OSPF condition, specifically NSSA external redistribution. An NSSA can carry locally redistributed externals as type 7 LSAs, which an eligible ABR translates to type 5 outside the NSSA. In this scenario, however, the distinguishing issue is Area border prefix withdrawal and the confirming observation is: Remote routing and ABR detail show the correct summary withdrawal or safe discard behavior after the component disappears.
B:Neighbor LSDB inspection shows LSAs still flood even if local route installation differs. This is a plausible observed evidence for a different OSPF condition, specifically Inbound OSPF route filtering scope. A local routing-table import decision is not necessarily an LSA flooding filter in a link-state area. In this scenario, however, the distinguishing issue is Area border prefix withdrawal and the confirming observation is: Remote routing and ABR detail show the correct summary withdrawal or safe discard behavior after the component disappears.
C:ABR neighbors and area 0 LSAs show a continuous interarea path after the design repair. This is a plausible observed evidence 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 Area border prefix withdrawal and the confirming observation is: Remote routing and ABR detail show the correct summary withdrawal or safe discard behavior after the component disappears.
Question 109
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: A summarized OSPF route remains advertised from an ABR after the last valid component subnet was removed from the area. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Correct aggregation and route-discard policy for the intended contributor-dependent reachability.
- Apply ASBR-appropriate external aggregation or controlled redistribution for the external prefix set.
- Configure the required area as NSSA and authorize controlled redistribution and type 7 translation.
- Place summarization or route-advertisement controls at appropriate area boundaries rather than assuming an ordinary local import policy changes flooding.
Explanation
Correct Answer
A:Correct aggregation and route-discard policy for the intended contributor-dependent reachability. The change addresses the root behavior described here: Summary advertisement must reflect actual reachable components and implementation rules to avoid attracting traffic to a missing site. Verify success with: Remote routing and ABR detail show the correct summary withdrawal or safe discard behavior after the component disappears.
Incorrect Answers
B:Apply ASBR-appropriate external aggregation or controlled redistribution for the external prefix set. This is a plausible configuration or operational fix for a different OSPF condition, specifically ASBR external aggregation. AS-external advertisements have a different summarization control point from interarea type 3 summaries. In this scenario, however, the distinguishing issue is Area border prefix withdrawal and the confirming observation is: Remote routing and ABR detail show the correct summary withdrawal or safe discard behavior after the component disappears.
C:Configure the required area as NSSA and authorize controlled redistribution and type 7 translation. This is a plausible configuration or operational fix for a different OSPF condition, specifically NSSA external redistribution. An NSSA can carry locally redistributed externals as type 7 LSAs, which an eligible ABR translates to type 5 outside the NSSA. In this scenario, however, the distinguishing issue is Area border prefix withdrawal and the confirming observation is: Remote routing and ABR detail show the correct summary withdrawal or safe discard behavior after the component disappears.
D:Place summarization or route-advertisement controls at appropriate area boundaries rather than assuming an ordinary local import policy changes flooding. This is a plausible configuration or operational fix for a different OSPF condition, specifically Inbound OSPF route filtering scope. A local routing-table import decision is not necessarily an LSA flooding filter in a link-state area. In this scenario, however, the distinguishing issue is Area border prefix withdrawal and the confirming observation is: Remote routing and ABR detail show the correct summary withdrawal or safe discard behavior after the component disappears.
Question 110
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: A summarized OSPF route remains advertised from an ABR after the last valid component subnet was removed from the area. Which operational control would best prevent a recurrence of this exact failure mode?
- Maintain an external-prefix inventory and validate reachable components before suppressing specifics.
- Include full component withdrawal in summary-routing regression tests.
- Test both the NSSA LSDB and remote external route installation after a redistribution change.
- Validate both forwarding routes and LSDB contents during policy design reviews.
Explanation
Correct Answer
B:Include full component withdrawal in summary-routing regression tests. The control limits repetition of the described root condition: Summary advertisement must reflect actual reachable components and implementation rules to avoid attracting traffic to a missing site. During audits, confirm: Remote routing and ABR detail show the correct summary withdrawal or safe discard behavior after the component disappears.
Incorrect Answers
A:Maintain an external-prefix inventory and validate reachable components before suppressing specifics. This is a plausible preventive practice for a different OSPF condition, specifically ASBR external aggregation. AS-external advertisements have a different summarization control point from interarea type 3 summaries. In this scenario, however, the distinguishing issue is Area border prefix withdrawal and the confirming observation is: Remote routing and ABR detail show the correct summary withdrawal or safe discard behavior after the component disappears.
C:Test both the NSSA LSDB and remote external route installation after a redistribution change. This is a plausible preventive practice for a different OSPF condition, specifically NSSA external redistribution. An NSSA can carry locally redistributed externals as type 7 LSAs, which an eligible ABR translates to type 5 outside the NSSA. In this scenario, however, the distinguishing issue is Area border prefix withdrawal and the confirming observation is: Remote routing and ABR detail show the correct summary withdrawal or safe discard behavior after the component disappears.
D:Validate both forwarding routes and LSDB contents during policy design reviews. This is a plausible preventive practice for a different OSPF condition, specifically Inbound OSPF route filtering scope. A local routing-table import decision is not necessarily an LSA flooding filter in a link-state area. In this scenario, however, the distinguishing issue is Area border prefix withdrawal and the confirming observation is: Remote routing and ABR detail show the correct summary withdrawal or safe discard behavior after the component disappears.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests