The city's cloud team uses infrastructure-as-code templates to deploy identical hardened network baselines for each department. Which security implication is most accurate?
Select an answer to reveal the explanation.
Short Explanation
Templates are a cookie cutter—great when the shape is secure, scary when the cutter is wrong. IaC gives you repeatable hardened networks, but one bad pattern stamps that flaw everywhere. Version control and review are part of keeping the cutter clean.
Full Explanation
Infrastructure as code enables repeatable, consistent deployment of hardened configurations, which is a security benefit for municipal environments that need uniform baselines. The corresponding risk is scaled misconfiguration: defects in a template propagate across every deployment. Treating IaC as error-proof, documentation-only, or something that should avoid version control ignores both the benefit and the blast-radius risk.