Question 30
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: On a shared Ethernet access segment, the router intended as the OSPF designated router never wins the election after all adjacencies settle. Which operational control would best prevent a recurrence of this exact failure mode?
- Document OSPF network types for dedicated versus shared Ethernet circuits.
- Review DR/BDR state after topology changes and avoid unnecessary adjacency resets.
- Test loss of upstream connectivity separately from loss of the local OSPF adjacency.
- Maintain an external-prefix inventory and validate reachable components before suppressing specifics.
Explanation
Correct Answer
B:Review DR/BDR state after topology changes and avoid unnecessary adjacency resets. The control limits repetition of the described root condition: DR election on broadcast networks considers eligible interface priority and uses router ID for priority ties; priority zero makes a router ineligible. During audits, confirm: The intended device shows a higher eligible priority and is elected after an appropriate election event.
Incorrect Answers
A: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 Broadcast DR election priority and the confirming observation is: The intended device shows a higher eligible priority and is elected after an appropriate election event.
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 Broadcast DR election priority and the confirming observation is: The intended device shows a higher eligible priority and is elected after an appropriate election event.
D: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 Broadcast DR election priority and the confirming observation is: The intended device shows a higher eligible priority and is elected after an appropriate election event.
Question 31
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: Two Junos neighbors exchange Hello packets but repeatedly remain in ExStart or Exchange after one link changed its configured MTU. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare the received Hello and dead intervals on both ends of the same segment.
- Inspect current DR, BDR and adjacency state rather than restarting every node.
- Compare the negotiated interface MTU and database description exchange counters on both ends.
- Inspect OSPFv3 participation and IPv6 link-local neighbor formation instead of assuming OSPFv2 carries IPv6.
Explanation
Correct Answer
C:Compare the negotiated interface MTU and database description exchange counters on both ends. This check examines the decisive condition for OSPF MTU adjacency ExStart before any unrelated changes are made. The underlying mechanism is: Inconsistent MTU handling can prevent successful OSPF database description exchange despite matching Hello parameters. The confirming observation is: Neighbor detail moves from ExStart to Full after MTU alignment without suppressing required checks.
Incorrect Answers
A:Compare the received Hello and dead intervals on both ends of the same segment. This is a plausible diagnostic check 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 MTU adjacency ExStart and the confirming observation is: Neighbor detail moves from ExStart to Full after MTU alignment without suppressing required checks.
B:Inspect current DR, BDR and adjacency state rather than restarting every node. This is a plausible diagnostic check for a different OSPF condition, specifically DR BDR transition on LAN. OSPF uses an elected backup designated router to support a controlled transition on broadcast segments. In this scenario, however, the distinguishing issue is OSPF MTU adjacency ExStart and the confirming observation is: Neighbor detail moves from ExStart to Full after MTU alignment without suppressing required checks.
D:Inspect OSPFv3 participation and IPv6 link-local neighbor formation instead of assuming OSPFv2 carries IPv6. This is a plausible diagnostic check for a different OSPF condition, specifically OSPFv3 address-family enablement. OSPFv2 and OSPFv3 have different address-family and protocol mechanics, so an OSPFv2 neighbor alone proves nothing about IPv6 routing. In this scenario, however, the distinguishing issue is OSPF MTU adjacency ExStart and the confirming observation is: Neighbor detail moves from ExStart to Full after MTU alignment without suppressing required checks.
Question 32
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: Two Junos neighbors exchange Hello packets but repeatedly remain in ExStart or Exchange after one link changed its configured MTU. Which routing or service mechanism best explains the reported behavior?
- Neighbors must agree on key OSPF Hello parameters, including timing intervals, to maintain adjacency.
- OSPF uses an elected backup designated router to support a controlled transition on broadcast segments.
- OSPFv2 and OSPFv3 have different address-family and protocol mechanics, so an OSPFv2 neighbor alone proves nothing about IPv6 routing.
- Inconsistent MTU handling can prevent successful OSPF database description exchange despite matching Hello parameters.
Explanation
Correct Answer
D:Inconsistent MTU handling can prevent successful OSPF database description exchange despite matching Hello parameters. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Neighbor detail moves from ExStart to Full after MTU alignment without suppressing required checks. The targeted correction is: Correct MTU consistency across the adjacency and retain valid OSPF database synchronization.
Incorrect Answers
A:Neighbors must agree on key OSPF Hello parameters, including timing intervals, to maintain adjacency. This is a plausible protocol explanation 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 MTU adjacency ExStart and the confirming observation is: Neighbor detail moves from ExStart to Full after MTU alignment without suppressing required checks.
B:OSPF uses an elected backup designated router to support a controlled transition on broadcast segments. This is a plausible protocol explanation for a different OSPF condition, specifically DR BDR transition on LAN. OSPF uses an elected backup designated router to support a controlled transition on broadcast segments. In this scenario, however, the distinguishing issue is OSPF MTU adjacency ExStart and the confirming observation is: Neighbor detail moves from ExStart to Full after MTU alignment without suppressing required checks.
C:OSPFv2 and OSPFv3 have different address-family and protocol mechanics, so an OSPFv2 neighbor alone proves nothing about IPv6 routing. This is a plausible protocol explanation for a different OSPF condition, specifically OSPFv3 address-family enablement. OSPFv2 and OSPFv3 have different address-family and protocol mechanics, so an OSPFv2 neighbor alone proves nothing about IPv6 routing. In this scenario, however, the distinguishing issue is OSPF MTU adjacency ExStart and the confirming observation is: Neighbor detail moves from ExStart to Full after MTU alignment without suppressing required checks.
Question 33
During an edge-to-core validation, an HPE Juniper Networking engineer investigates this situation: Two Junos neighbors exchange Hello packets but repeatedly remain in ExStart or Exchange after one link changed its configured MTU. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Neighbor detail moves from ExStart to Full after MTU alignment without suppressing required checks.
- The Hello parameter mismatch is absent and the neighbor remains stable across several dead intervals.
- The former BDR assumes DR responsibility and eligible neighbors reach the expected Full state without widespread clearing.
- An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table.
Explanation
Correct Answer
A:Neighbor detail moves from ExStart to Full after MTU alignment without suppressing required checks. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Inconsistent MTU handling can prevent successful OSPF database description exchange despite matching Hello parameters.
Incorrect Answers
B:The Hello parameter mismatch is absent and the neighbor remains stable across several dead intervals. This is a plausible observed evidence 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 MTU adjacency ExStart and the confirming observation is: Neighbor detail moves from ExStart to Full after MTU alignment without suppressing required checks.
C:The former BDR assumes DR responsibility and eligible neighbors reach the expected Full state without widespread clearing. This is a plausible observed evidence for a different OSPF condition, specifically DR BDR transition on LAN. OSPF uses an elected backup designated router to support a controlled transition on broadcast segments. In this scenario, however, the distinguishing issue is OSPF MTU adjacency ExStart and the confirming observation is: Neighbor detail moves from ExStart to Full after MTU alignment without suppressing required checks.
D:An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table. This is a plausible observed evidence for a different OSPF condition, specifically OSPFv3 address-family enablement. OSPFv2 and OSPFv3 have different address-family and protocol mechanics, so an OSPFv2 neighbor alone proves nothing about IPv6 routing. In this scenario, however, the distinguishing issue is OSPF MTU adjacency ExStart and the confirming observation is: Neighbor detail moves from ExStart to Full after MTU alignment without suppressing required checks.
Question 34
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: Two Junos neighbors exchange Hello packets but repeatedly remain in ExStart or Exchange after one link changed its configured MTU. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Align Hello and dead timer values on the adjacency while keeping the network's planned convergence budget.
- Correct MTU consistency across the adjacency and retain valid OSPF database synchronization.
- Restore a stable DR/BDR election and avoid unnecessary protocol restarts.
- Configure and verify the intended OSPFv3 IPv6 operation on both peers.
Explanation
Correct Answer
B:Correct MTU consistency across the adjacency and retain valid OSPF database synchronization. The change addresses the root behavior described here: Inconsistent MTU handling can prevent successful OSPF database description exchange despite matching Hello parameters. Verify success with: Neighbor detail moves from ExStart to Full after MTU alignment without suppressing required checks.
Incorrect Answers
A:Align Hello and dead timer values on the adjacency while keeping the network's planned convergence budget. This is a plausible configuration or operational fix 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 MTU adjacency ExStart and the confirming observation is: Neighbor detail moves from ExStart to Full after MTU alignment without suppressing required checks.
C:Restore a stable DR/BDR election and avoid unnecessary protocol restarts. This is a plausible configuration or operational fix for a different OSPF condition, specifically DR BDR transition on LAN. OSPF uses an elected backup designated router to support a controlled transition on broadcast segments. In this scenario, however, the distinguishing issue is OSPF MTU adjacency ExStart and the confirming observation is: Neighbor detail moves from ExStart to Full after MTU alignment without suppressing required checks.
D:Configure and verify the intended OSPFv3 IPv6 operation on both peers. This is a plausible configuration or operational fix for a different OSPF condition, specifically OSPFv3 address-family enablement. OSPFv2 and OSPFv3 have different address-family and protocol mechanics, so an OSPFv2 neighbor alone proves nothing about IPv6 routing. In this scenario, however, the distinguishing issue is OSPF MTU adjacency ExStart and the confirming observation is: Neighbor detail moves from ExStart to Full after MTU alignment without suppressing required checks.
Question 35
During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: Two Junos neighbors exchange Hello packets but repeatedly remain in ExStart or Exchange after one link changed its configured MTU. Which operational control would best prevent a recurrence of this exact failure mode?
- Audit OSPF interface timers during template deployment and route maintenance.
- Test DR failure in maintenance windows and record preferred backup priorities.
- Include interface MTU parity and the neighbor Full state in standard link acceptance tests.
- Track IPv4 and IPv6 adjacencies and RIB entries as separate acceptance checks.
Explanation
Correct Answer
C:Include interface MTU parity and the neighbor Full state in standard link acceptance tests. The control limits repetition of the described root condition: Inconsistent MTU handling can prevent successful OSPF database description exchange despite matching Hello parameters. During audits, confirm: Neighbor detail moves from ExStart to Full after MTU alignment without suppressing required checks.
Incorrect Answers
A: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 MTU adjacency ExStart and the confirming observation is: Neighbor detail moves from ExStart to Full after MTU alignment without suppressing required checks.
B:Test DR failure in maintenance windows and record preferred backup priorities. This is a plausible preventive practice for a different OSPF condition, specifically DR BDR transition on LAN. OSPF uses an elected backup designated router to support a controlled transition on broadcast segments. In this scenario, however, the distinguishing issue is OSPF MTU adjacency ExStart and the confirming observation is: Neighbor detail moves from ExStart to Full after MTU alignment without suppressing required checks.
D:Track IPv4 and IPv6 adjacencies and RIB entries as separate acceptance checks. This is a plausible preventive practice for a different OSPF condition, specifically OSPFv3 address-family enablement. OSPFv2 and OSPFv3 have different address-family and protocol mechanics, so an OSPFv2 neighbor alone proves nothing about IPv6 routing. In this scenario, however, the distinguishing issue is OSPF MTU adjacency ExStart and the confirming observation is: Neighbor detail moves from ExStart to Full after MTU alignment without suppressing required checks.
Question 36
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: An OSPF router on a peering VLAN shows a neighbor repeatedly disappearing even though both interfaces have stable link state and IP connectivity. 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 external route types and compare the internal cost to each advertising ASBR.
- Compare the negotiated interface MTU and database description exchange counters on both ends.
- Compare the received Hello and dead intervals on both ends of the same segment.
Explanation
Correct Answer
D:Compare the received Hello and dead intervals on both ends of the same segment. This check examines the decisive condition for Hello/dead timer mismatch before any unrelated changes are made. The underlying mechanism is: Neighbors must agree on key OSPF Hello parameters, including timing intervals, to maintain adjacency. The confirming observation is: The Hello parameter mismatch is absent and the neighbor remains stable across several dead intervals.
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 Hello/dead timer mismatch and the confirming observation is: The Hello parameter mismatch is absent and the neighbor remains stable across several dead intervals.
B:Inspect external route types and compare the internal cost to each advertising ASBR. This is a plausible diagnostic check for a different OSPF condition, specifically External E1 versus E2 selection. An external E2 metric primarily represents the advertised external cost, whereas E1 accounts for internal cost toward the ASBR plus external cost. In this scenario, however, the distinguishing issue is Hello/dead timer mismatch and the confirming observation is: The Hello parameter mismatch is absent and the neighbor remains stable across several dead intervals.
C: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 Hello/dead timer mismatch and the confirming observation is: The Hello parameter mismatch is absent and the neighbor remains stable across several dead intervals.
Question 37
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: An OSPF router on a peering VLAN shows a neighbor repeatedly disappearing even though both interfaces have stable link state and IP connectivity. Which routing or service mechanism best explains the reported behavior?
- Neighbors must agree on key OSPF Hello parameters, including timing intervals, to maintain adjacency.
- An external E2 metric primarily represents the advertised external cost, whereas E1 accounts for internal cost toward the ASBR plus external cost.
- Interarea aggregation is performed by a suitable ABR; setting an unrelated import filter does not itself produce the expected summary.
- Inconsistent MTU handling can prevent successful OSPF database description exchange despite matching Hello parameters.
Explanation
Correct Answer
A:Neighbors must agree on key OSPF Hello parameters, including timing intervals, to maintain adjacency. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The Hello parameter mismatch is absent and the neighbor remains stable across several dead intervals. The targeted correction is: Align Hello and dead timer values on the adjacency while keeping the network's planned convergence budget.
Incorrect Answers
B:An external E2 metric primarily represents the advertised external cost, whereas E1 accounts for internal cost toward the ASBR plus external cost. This is a plausible protocol explanation for a different OSPF condition, specifically External E1 versus E2 selection. An external E2 metric primarily represents the advertised external cost, whereas E1 accounts for internal cost toward the ASBR plus external cost. In this scenario, however, the distinguishing issue is Hello/dead timer mismatch and the confirming observation is: The Hello parameter mismatch is absent and the neighbor remains stable across several dead intervals.
C: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 Hello/dead timer mismatch and the confirming observation is: The Hello parameter mismatch is absent and the neighbor remains stable across several dead intervals.
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 Hello/dead timer mismatch and the confirming observation is: The Hello parameter mismatch is absent and the neighbor remains stable across several dead intervals.
Question 38
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: An OSPF router on a peering VLAN shows a neighbor repeatedly disappearing even though both interfaces have stable link state and IP connectivity. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The calculated path ranking changes as predicted when an E1 policy considers internal cost to each exit.
- The Hello parameter mismatch is absent and the neighbor remains stable across several dead intervals.
- Remote areas see the aggregate summary and no unwanted individual component advertisements under the defined policy.
- Neighbor detail moves from ExStart to Full after MTU alignment without suppressing required checks.
Explanation
Correct Answer
B:The Hello parameter mismatch is absent and the neighbor remains stable across several dead intervals. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Neighbors must agree on key OSPF Hello parameters, including timing intervals, to maintain adjacency.
Incorrect Answers
A:The calculated path ranking changes as predicted when an E1 policy considers internal cost to each exit. This is a plausible observed evidence for a different OSPF condition, specifically External E1 versus E2 selection. An external E2 metric primarily represents the advertised external cost, whereas E1 accounts for internal cost toward the ASBR plus external cost. In this scenario, however, the distinguishing issue is Hello/dead timer mismatch and the confirming observation is: The Hello parameter mismatch is absent and the neighbor remains stable across several dead intervals.
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 Hello/dead timer mismatch and the confirming observation is: The Hello parameter mismatch is absent and the neighbor remains stable across several dead intervals.
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 Hello/dead timer mismatch and the confirming observation is: The Hello parameter mismatch is absent and the neighbor remains stable across several dead intervals.
Question 39
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: An OSPF router on a peering VLAN shows a neighbor repeatedly disappearing even though both interfaces have stable link state and IP connectivity. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Use an E1 policy when internal path cost to an external exit must influence the selection.
- Configure the ABR area range with a prefix that genuinely covers the intended internal networks.
- Align Hello and dead timer values on the adjacency while keeping the network's planned convergence budget.
- Correct MTU consistency across the adjacency and retain valid OSPF database synchronization.
Explanation
Correct Answer
C:Align Hello and dead timer values on the adjacency while keeping the network's planned convergence budget. The change addresses the root behavior described here: Neighbors must agree on key OSPF Hello parameters, including timing intervals, to maintain adjacency. Verify success with: The Hello parameter mismatch is absent and the neighbor remains stable across several dead intervals.
Incorrect Answers
A:Use an E1 policy when internal path cost to an external exit must influence the selection. This is a plausible configuration or operational fix for a different OSPF condition, specifically External E1 versus E2 selection. An external E2 metric primarily represents the advertised external cost, whereas E1 accounts for internal cost toward the ASBR plus external cost. In this scenario, however, the distinguishing issue is Hello/dead timer mismatch and the confirming observation is: The Hello parameter mismatch is absent and the neighbor remains stable across several dead intervals.
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 Hello/dead timer mismatch and the confirming observation is: The Hello parameter mismatch is absent and the neighbor remains stable across several dead intervals.
D: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 Hello/dead timer mismatch and the confirming observation is: The Hello parameter mismatch is absent and the neighbor remains stable across several dead intervals.
Question 40
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: An OSPF router on a peering VLAN shows a neighbor repeatedly disappearing even though both interfaces have stable link state and IP connectivity. Which operational control would best prevent a recurrence of this exact failure mode?
- Test external metric-type assumptions after an ASBR topology or cost change.
- Verify summary coverage and black-hole risk whenever component routes change.
- Include interface MTU parity and the neighbor Full state in standard link acceptance tests.
- Audit OSPF interface timers during template deployment and route maintenance.
Explanation
Correct Answer
D:Audit OSPF interface timers during template deployment and route maintenance. The control limits repetition of the described root condition: Neighbors must agree on key OSPF Hello parameters, including timing intervals, to maintain adjacency. During audits, confirm: The Hello parameter mismatch is absent and the neighbor remains stable across several dead intervals.
Incorrect Answers
A: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 Hello/dead timer mismatch and the confirming observation is: The Hello parameter mismatch is absent and the neighbor remains stable across several dead intervals.
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 Hello/dead timer mismatch and the confirming observation is: The Hello parameter mismatch is absent and the neighbor remains stable across several dead intervals.
C: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 Hello/dead timer mismatch and the confirming observation is: The Hello parameter mismatch is absent and the neighbor remains stable across several dead intervals.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests