Question 80
A data center implementation team investigates the following fault: A Nexus on-box Python remediation applet recreates the same VLAN and interface objects every run, producing repeated configuration changes even when state is already correct. Which corrective change best resolves this problem?
Explanation
Correct Answer
The root problem is that The script lacks an idempotent precheck to compare desired and current network device state. The selected change addresses it directly: Query existing NX-OS state before applying only the necessary authorized configuration differences. Verify the outcome: Repeated execution converges to the same desired configuration without unintended duplicate changes.
Incorrect Answers
This action concerns nx os eem syslog event trigger, where The embedded event manager event detector does not match the actual authorized BGP neighbor-down message. The reported failure instead stems from The script lacks an idempotent precheck to compare desired and current network device state.
This action concerns nx os scheduler job interval, where The NX-OS scheduler job timing is not aligned with the intended maintenance frequency. The corrective response here is “Query existing NX-OS state before applying only the necessary authorized configuration differences”; this alternative does not provide that response.
This action concerns nexus bash shell and guest shell isolation, where The deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment. The stem reports a Nexus on-box Python remediation applet recreates the same VLAN and interface objects every run, producing repeated configuration changes even when state is already correct; this control addresses a different failure condition.