City IT wants reviewers to see how proposed Azure environment definitions changed over time before anything goes live. Which IaC benefit supports that need?
Select an answer to reveal the explanation.
Short Explanation
Treat infra definitions like source code: check them in, diff them, review them. That version-control habit is a big IaC win for city change control. It is not a free pass to delete the world overnight.
Full Explanation
Storing infrastructure definitions in version control enables history, peer review, and auditable change — a core benefit of infrastructure as code. Reviewers can compare proposed environment updates before deployment the same way they review application code. That discipline improves change control for municipal Azure estates. IaC does not eliminate subscriptions, replace Entra ID, or imply unattended mass deletion as its defining purpose.