A water utility must push a template-driven SD-WAN change across many pump sites and wants to avoid one-off SSH snowflake configs. Which approach best fits?
Select an answer to reveal the explanation.
Short Explanation
vManage templates are the utility’s master blueprint; the configuration APIs stamp that blueprint on every pump site. Hand-SSH snowflakes look fast until Monday’s audit asks which device still matches intent.
Full Explanation
SD-WAN operational practice prefers vManage configuration and template APIs (or GUI flows backed by the same model) so changes remain centralized, versioned, and consistent across sites. Raw per-device SSH creates drift that fights controller intent. Spreadsheet password processes and unmanaged configs fail auditability. Use controller configuration APIs rather than CLI snowflakes for template-related changes.