Question 60
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: An access area sends hundreds of individual internal prefixes across the ABR even though the operator intended one stable site summary. 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 both the NSSA LSDB and remote external route installation after a redistribution change.
- Verify summary coverage and black-hole risk whenever component routes change.
Explanation
Correct Answer
D:Verify summary coverage and black-hole risk whenever component routes change. The control limits repetition of the described root condition: Interarea aggregation is performed by a suitable ABR; setting an unrelated import filter does not itself produce the expected summary. During audits, confirm: Remote areas see the aggregate summary and no unwanted individual component advertisements under the defined policy.
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 Route summarization at ABR and the confirming observation is: Remote areas see the aggregate summary and no unwanted individual component advertisements under the defined policy.
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 Route summarization at ABR and the confirming observation is: Remote areas see the aggregate summary and no unwanted individual component advertisements under the defined policy.
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 Route summarization at ABR and the confirming observation is: Remote areas see the aggregate summary and no unwanted individual component advertisements under the defined policy.
Question 61
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: A routing team summarizes an OSPF access area but still sees a large collection of external redistributed routes originating from one ASBR. 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 backbone reachability and actual upstream service path behind the advertised default.
- Inspect LSA sequence numbers, age and LSDB synchronization before adjusting interface bandwidth.
- Inspect the ABR's area range configuration and the origin of interarea summary LSAs.
Explanation
Correct Answer
A:Identify which LSA type carries the prefixes and whether they originate at an ASBR rather than an ABR. This check examines the decisive condition for ASBR external aggregation before any unrelated changes are made. The underlying mechanism is: AS-external advertisements have a different summarization control point from interarea type 3 summaries. The confirming observation is: External summary behavior and routing-policy evidence show the intended external aggregate without an unrelated area-range effect.
Incorrect Answers
B: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 ASBR external aggregation and the confirming observation is: External summary behavior and routing-policy evidence show the intended external aggregate without an unrelated area-range effect.
C: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 ASBR external aggregation and the confirming observation is: External summary behavior and routing-policy evidence show the intended external aggregate without an unrelated area-range effect.
D: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 ASBR external aggregation and the confirming observation is: External summary behavior and routing-policy evidence show the intended external aggregate without an unrelated area-range effect.
Question 62
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: A routing team summarizes an OSPF access area but still sees a large collection of external redistributed routes originating from one ASBR. Which routing or service mechanism best explains the reported behavior?
- Receiving an OSPF default route only indicates a routing advertisement; it does not guarantee a healthy upstream service path.
- AS-external advertisements have a different summarization control point from interarea type 3 summaries.
- Link-state routes depend on consistent current LSAs and completed SPF processing, not solely on neighbor Full status.
- Interarea aggregation is performed by a suitable ABR; setting an unrelated import filter does not itself produce the expected summary.
Explanation
Correct Answer
B:AS-external advertisements have a different summarization control point from interarea type 3 summaries. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: External summary behavior and routing-policy evidence show the intended external aggregate without an unrelated area-range effect. The targeted correction is: Apply ASBR-appropriate external aggregation or controlled redistribution for the external prefix set.
Incorrect Answers
A: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 ASBR external aggregation and the confirming observation is: External summary behavior and routing-policy evidence show the intended external aggregate without an unrelated area-range effect.
C: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 ASBR external aggregation and the confirming observation is: External summary behavior and routing-policy evidence show the intended external aggregate without an unrelated area-range effect.
D: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 ASBR external aggregation and the confirming observation is: External summary behavior and routing-policy evidence show the intended external aggregate without an unrelated area-range effect.
Question 63
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: A routing team summarizes an OSPF access area but still sees a large collection of external redistributed routes originating from one ASBR. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- 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.
- External summary behavior and routing-policy evidence show the intended external aggregate without an unrelated area-range effect.
- The area retains a default summary and no longer carries the unwanted individual interarea summaries.
Explanation
Correct Answer
C:External summary behavior and routing-policy evidence show the intended external aggregate without an unrelated area-range effect. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: AS-external advertisements have a different summarization control point from interarea type 3 summaries.
Incorrect Answers
A: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 ASBR external aggregation and the confirming observation is: External summary behavior and routing-policy evidence show the intended external aggregate without an unrelated area-range effect.
B: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 ASBR external aggregation and the confirming observation is: External summary behavior and routing-policy evidence show the intended external aggregate without an unrelated area-range effect.
D:The area retains a default summary and no longer carries the unwanted individual interarea summaries. This is a plausible observed evidence for a different OSPF condition, specifically Totally stubby interarea suppression. A normal stub excludes type 5 externals but still allows type 3 interarea summaries, whereas a totally stubby design suppresses nondefault type 3s. In this scenario, however, the distinguishing issue is ASBR external aggregation and the confirming observation is: External summary behavior and routing-policy evidence show the intended external aggregate without an unrelated area-range effect.
Question 64
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: A routing team summarizes an OSPF access area but still sees a large collection of external redistributed routes originating from one ASBR. Which response or focused corrective action best addresses this situation without changing unrelated components?
- 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.
- Configure the ABR area range with a prefix that genuinely covers the intended internal networks.
- Apply ASBR-appropriate external aggregation or controlled redistribution for the external prefix set.
Explanation
Correct Answer
D:Apply ASBR-appropriate external aggregation or controlled redistribution for the external prefix set. The change addresses the root behavior described here: AS-external advertisements have a different summarization control point from interarea type 3 summaries. Verify success with: External summary behavior and routing-policy evidence show the intended external aggregate without an unrelated area-range effect.
Incorrect Answers
A: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 ASBR external aggregation and the confirming observation is: External summary behavior and routing-policy evidence show the intended external aggregate without an unrelated area-range effect.
B: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 ASBR external aggregation and the confirming observation is: External summary behavior and routing-policy evidence show the intended external aggregate without an unrelated area-range effect.
C: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 ASBR external aggregation and the confirming observation is: External summary behavior and routing-policy evidence show the intended external aggregate without an unrelated area-range effect.
Question 65
During a core-routing migration rehearsal, an HPE Juniper Networking engineer investigates this situation: A routing team summarizes an OSPF access area but still sees a large collection of external redistributed routes originating from one ASBR. 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.
- Test loss of upstream connectivity separately from loss of the local OSPF adjacency.
- Monitor LSDB freshness and SPF processing during periods of churn.
- Verify summary coverage and black-hole risk whenever component routes change.
Explanation
Correct Answer
A:Maintain an external-prefix inventory and validate reachable components before suppressing specifics. The control limits repetition of the described root condition: AS-external advertisements have a different summarization control point from interarea type 3 summaries. During audits, confirm: External summary behavior and routing-policy evidence show the intended external aggregate without an unrelated area-range effect.
Incorrect Answers
B: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 ASBR external aggregation and the confirming observation is: External summary behavior and routing-policy evidence show the intended external aggregate without an unrelated area-range effect.
C: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 ASBR external aggregation and the confirming observation is: External summary behavior and routing-policy evidence show the intended external aggregate without an unrelated area-range effect.
D: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 ASBR external aggregation and the confirming observation is: External summary behavior and routing-policy evidence show the intended external aggregate without an unrelated area-range effect.
Question 66
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: IPv4 OSPFv2 adjacency is healthy, but IPv6 prefixes are absent after adding IPv6 to an access interface. 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 OSPFv3 participation and IPv6 link-local neighbor formation instead of assuming OSPFv2 carries IPv6.
- Compare the interface area ID on both neighbors and inspect received OSPF Hello fields.
- Inspect the ABR's area range configuration and the origin of interarea summary LSAs.
Explanation
Correct Answer
B:Inspect OSPFv3 participation and IPv6 link-local neighbor formation instead of assuming OSPFv2 carries IPv6. This check examines the decisive condition for OSPFv3 address-family enablement before any unrelated changes are made. The underlying mechanism is: OSPFv2 and OSPFv3 have different address-family and protocol mechanics, so an OSPFv2 neighbor alone proves nothing about IPv6 routing. The confirming observation is: An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table.
Incorrect Answers
A:Compare the area's stub configuration and its LSA types with the missing external destinations. This is a plausible diagnostic check 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 OSPFv3 address-family enablement and the confirming observation is: An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table.
C:Compare the interface area ID on both neighbors and inspect received OSPF Hello fields. This is a plausible diagnostic check for a different OSPF condition, specifically Area ID mismatch. An OSPF adjacency requires consistent area identity on the shared link. In this scenario, however, the distinguishing issue is OSPFv3 address-family enablement and the confirming observation is: An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table.
D: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 OSPFv3 address-family enablement and the confirming observation is: An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table.
Question 67
During an edge-to-core validation, an HPE Juniper Networking engineer investigates this situation: IPv4 OSPFv2 adjacency is healthy, but IPv6 prefixes are absent after adding IPv6 to an access interface. Which routing or service mechanism best explains the reported behavior?
- A stub area excludes AS-external type 5 LSAs and relies on ABR-supplied reachability rather than importing individual external routes.
- An OSPF adjacency requires consistent area identity on the shared link.
- OSPFv2 and OSPFv3 have different address-family and protocol mechanics, so an OSPFv2 neighbor alone proves nothing about IPv6 routing.
- Interarea aggregation is performed by a suitable ABR; setting an unrelated import filter does not itself produce the expected summary.
Explanation
Correct Answer
C:OSPFv2 and OSPFv3 have different address-family and protocol mechanics, so an OSPFv2 neighbor alone proves nothing about IPv6 routing. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table. The targeted correction is: Configure and verify the intended OSPFv3 IPv6 operation on both peers.
Incorrect Answers
A:A stub area excludes AS-external type 5 LSAs and relies on ABR-supplied reachability rather than importing individual external routes. This is a plausible protocol explanation 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 OSPFv3 address-family enablement and the confirming observation is: An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table.
B:An OSPF adjacency requires consistent area identity on the shared link. This is a plausible protocol explanation for a different OSPF condition, specifically Area ID mismatch. An OSPF adjacency requires consistent area identity on the shared link. In this scenario, however, the distinguishing issue is OSPFv3 address-family enablement and the confirming observation is: An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table.
D: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 OSPFv3 address-family enablement and the confirming observation is: An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table.
Question 68
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: IPv4 OSPFv2 adjacency is healthy, but IPv6 prefixes are absent after adding IPv6 to an access interface. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The local LSDB lacks type 5 LSAs while an ABR-provided default can still be installed.
- The pair reports the same area ID and progresses through the normal neighbor state sequence to Full.
- Remote areas see the aggregate summary and no unwanted individual component advertisements under the defined policy.
- An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table.
Explanation
Correct Answer
D:An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: OSPFv2 and OSPFv3 have different address-family and protocol mechanics, so an OSPFv2 neighbor alone proves nothing about IPv6 routing.
Incorrect Answers
A:The local LSDB lacks type 5 LSAs while an ABR-provided default can still be installed. This is a plausible observed evidence 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 OSPFv3 address-family enablement and the confirming observation is: An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table.
B:The pair reports the same area ID and progresses through the normal neighbor state sequence to Full. This is a plausible observed evidence for a different OSPF condition, specifically Area ID mismatch. An OSPF adjacency requires consistent area identity on the shared link. In this scenario, however, the distinguishing issue is OSPFv3 address-family enablement and the confirming observation is: An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table.
C: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 OSPFv3 address-family enablement and the confirming observation is: An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table.
Question 69
During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: IPv4 OSPFv2 adjacency is healthy, but IPv6 prefixes are absent after adding IPv6 to an access interface. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Configure and verify the intended OSPFv3 IPv6 operation on both peers.
- Configure the ABR area range with a prefix that genuinely covers the intended internal networks.
- Use a normal area if individual external LSAs are required, or explicitly design default-route reachability through the ABR.
- Assign both link interfaces to the intended common area without moving unrelated interfaces.
Explanation
Correct Answer
A:Configure and verify the intended OSPFv3 IPv6 operation on both peers. The change addresses the root behavior described here: OSPFv2 and OSPFv3 have different address-family and protocol mechanics, so an OSPFv2 neighbor alone proves nothing about IPv6 routing. Verify success with: An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table.
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 OSPFv3 address-family enablement and the confirming observation is: An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table.
C:Use a normal area if individual external LSAs are required, or explicitly design default-route reachability through the ABR. This is a plausible configuration or operational fix 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 OSPFv3 address-family enablement and the confirming observation is: An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table.
D:Assign both link interfaces to the intended common area without moving unrelated interfaces. This is a plausible configuration or operational fix for a different OSPF condition, specifically Area ID mismatch. An OSPF adjacency requires consistent area identity on the shared link. In this scenario, however, the distinguishing issue is OSPFv3 address-family enablement and the confirming observation is: An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table.
Question 70
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: IPv4 OSPFv2 adjacency is healthy, but IPv6 prefixes are absent after adding IPv6 to an access interface. Which operational control would best prevent a recurrence of this exact failure mode?
- Verify summary coverage and black-hole risk whenever component routes change.
- Track IPv4 and IPv6 adjacencies and RIB entries as separate acceptance checks.
- Record permitted LSA types and verify the default route before converting an area to stub.
- Validate area IDs for both link endpoints in change prechecks.
Explanation
Correct Answer
B:Track IPv4 and IPv6 adjacencies and RIB entries as separate acceptance checks. The control limits repetition of the described root condition: OSPFv2 and OSPFv3 have different address-family and protocol mechanics, so an OSPFv2 neighbor alone proves nothing about IPv6 routing. During audits, confirm: An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table.
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 OSPFv3 address-family enablement and the confirming observation is: An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table.
C: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 OSPFv3 address-family enablement and the confirming observation is: An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table.
D:Validate area IDs for both link endpoints in change prechecks. This is a plausible preventive practice for a different OSPF condition, specifically Area ID mismatch. An OSPF adjacency requires consistent area identity on the shared link. In this scenario, however, the distinguishing issue is OSPFv3 address-family enablement and the confirming observation is: An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests