A county platform team stores Terraform templates and application code and must prove who changed a production module and when. Which source-control capability primarily provides that history?
Select an answer to reveal the explanation.
Short Explanation
Source control is the city’s black box recorder for code and IaC. Commits stamp who touched what and when, so ‘who changed that module?’ is a git log, not a scavenger hunt through chat. Skip the live-only server edits—history lives in the repo.
Full Explanation
Version management in source control systems retains an auditable history of changes, including author identity, timestamps, and diffs. Municipal infrastructure-as-code and application repositories rely on that history for accountability, rollback, and change review. Informal screenshots, unstructured email digests, or unreplicated live edits do not provide reliable version provenance.