Which setting is used for the dampening period when configuring an on-change publication for YANG-push versus OpenConfig?
Click on the arrows to vote for the correct answer
A. B. C. D.C.
https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/prog/configuration/1612/b_1612_programmability_cg/model_driven_telemetry.htmlYANG-Push and OpenConfig are two methods for publishing updates to network devices. Both methods allow network operators to subscribe to changes in device configurations and receive updates in real-time.
When configuring an on-change publication for YANG-Push and OpenConfig, network operators can set a dampening period to prevent flooding the network with updates. The dampening period is a timer that starts when a configuration change occurs. During this period, any additional changes to the same configuration object are ignored.
The answer to the question is A. null. This means that there is no dampening period.
In YANG-Push, the dampening period is not supported, so the only option is to set the dampening period to null. In OpenConfig, the dampening period can be set to a specific value, such as -1 (infinite), 0 (disabled), or a positive integer value that represents the number of seconds to wait before allowing another update.
Setting the dampening period to null for YANG-Push means that all changes to the configuration object will be sent immediately to the subscriber, without any delay. This can result in a higher frequency of updates, but also provides more immediate feedback to the subscriber about changes in the network.
In summary, when configuring an on-change publication for YANG-push, the dampening period is set to null, while in OpenConfig, it can be set to a specific value such as -1, 0, or a positive integer value representing the number of seconds to wait.