Question 210
While checking a production data center change, the team finds: Two Nexus routed neighbors stop forming OSPF adjacencies during key rotation because their configured keychain accept and send lifetimes do not overlap. What technical condition most directly accounts for the failure?
Explanation
Correct Answer
The technical cause is The OSPF authentication peers are using mismatched active key IDs or validity intervals. The appropriate response is: Coordinate the supported authentication keychain parameters and overlapping key transition periods. Confirm successful repair: The intended OSPF adjacency remains authenticated across the key-rotation window with old keys retired safely.
Incorrect Answers
Fibre Channel port security does not restrict fabric logins to the designated authorized WWPN identities. “Configure supported MDS port-security bindings for the intended server initiator and affected VSAN” would address that alternative cause, not the condition in this question: the OSPF authentication peers are using mismatched active key IDs or validity intervals.
“Configure supported MACsec policy and secure key agreement on both authorized switch endpoints” responds to this separate finding: link-layer encryption is not enabled or negotiated for the intended MACsec-protected connection. This question instead needs “Coordinate the supported authentication keychain parameters and overlapping key transition periods”, so the alternative does not meet the stated condition.
The centralized AAA server returns a role mapping that lacks the specific least-privilege authorization needed for monitoring. “Correct the authorized TACACS command or role mapping without granting full switch administrator permissions” applies to that separate problem. The observed case is two Nexus routed neighbors stop forming OSPF adjacencies during key rotation because their configured keychain accept and send lifetimes do not overlap; choosing this alternative would address the wrong failure mode.