Question 630
At the Silverstream data center, EIGRP hellos pass across the transit link, yet R-SIL-PE1 never forms a neighbor with R-RIV-PE2; the peers use different EIGRP AS numbers. Which continuing operational control is most directly relevant to preventing this problem?
Explanation
Correct Answer
At the Silverstream data center, this continuing check directly limits recurrence of the observed failure. Compare AS identifiers across both ends during adjacency provisioning. The underlying problem is: EIGRP peers in different AS configurations will not establish the intended neighbor relationship.
Incorrect Answers
This would manage a different failure pattern. The adjacency rejects peer packets because their authentication settings do not agree. It is not the most direct recurring check for eigrp as mismatch at the Silverstream data center.
That safeguard protects against eigrp variance traffic sharing, not the concrete risk described at the Silverstream data center. EIGRP peers in different AS configurations will not establish the intended neighbor relationship.
This is useful for another concern: Monitor topology-table feasibility after bandwidth or delay changes affect route metrics. It does not continuously test eigrp as mismatch at the Silverstream data center.