Question 500
An NSR configuration fails commit after an operator adds graceful restart on the same device. What observable result most directly verifies the intended configuration?
Explanation
Correct Answer
This is the model-intended best choice because conflicting local GR and NSR configuration must be resolved before activation. The targeted correction is to remove the incompatible local mode and validate the supported HA configuration. Validate it by observing that the corrected candidate commits and the Routing Engine synchronization check passes.
Incorrect Answers
That result would be useful for a different failure, namely: An Ethernet service must retain bridge state during Routing Engine failover but only Layer 3 HA settings are considered. The current case specifically calls for: Remove the incompatible local mode and validate the supported HA configuration. The required observed result is: The corrected candidate commits and the Routing Engine synchronization check passes.
This response would target a different source scenario: One LAG member fails silently and the service loses capacity even though the logical interface remains active. It cannot establish the current acceptance requirement, which is: The corrected candidate commits and the Routing Engine synchronization check passes. The relevant action is: Remove the incompatible local mode and validate the supported HA configuration.
The alternative addresses a router sends OSPF Hello packets but remains stuck because the subnet mask differs across neighbors on a broadcast link, not the present root cause. Here the selected correction must reflect conflicting local GR and NSR configuration must be resolved before activation. Test for: The corrected candidate commits and the Routing Engine synchronization check passes.