A water utility wants a maintainable NetDevOps loop that combines s…

Question

A water utility wants a maintainable NetDevOps loop that combines structured encoding, local on-box reaction, and controller APIs for fleet changes. Which integrated approach best fits?

Accepted Answer

Use YANG/JSON encoding for automation payloads, EEM for local fast events, and controller APIs for reviewed fleet-wide changes in a staged pipeline — Think of the water network like a plant control loop: clean data formats in the pipes, a local trip for the pump that must stop now, and a central desk for citywide setpoints. YANG/JSON, EEM, and controller APIs each cover one part. Email-only or EEM-only leaves the loop broken.

Answer

Rely only on unstructured email instructions to NOC staff with no APIs or encoding standards

Answer

Put every civic change exclusively in on-box EEM with no controller or source control

Answer

Disable encoding validation, EEM, and controllers to keep operations purely manual

A water utility wants a maintainable NetDevOps loop that combines structured encoding, local on-box reaction, and controller APIs for fleet changes. Which integrated approach best fits?

Short Explanation

Full Explanation