A stormwater bureau stores per-site variables in YAML and needs consistent IOS XE configs for dozens of pump-station routers. Which concept best describes generating those configs from the data?
Select an answer to reveal the explanation.
Short Explanation
Templating is the cookie cutter: YAML is the dough (site data), Jinja-like templates are the cutter shape, and each pump station gets a consistently shaped config. Hand-pasting fifty routers is how typos flood the storm drains.
Full Explanation
Jinja-style templating (common in Ansible and many network automation stacks) combines structured data—often YAML—with templates that expand variables, conditionals, and loops into device configuration text. That pattern scales municipal multi-site builds far better than manual paste-and-edit. EPC captures and routing redesigns do not generate per-site configs. Understanding templating over structured data is a core Domain 5 encoding/automation skill.