A cloud engineer finishes a local Terraform tweak for a parks subnet and wants a durable snapshot in repository history before sharing. What should they create?
Select an answer to reveal the explanation.
Short Explanation
A commit is a labeled snapshot: ‘here’s the parks subnet tweak’ with a message you can find later. Untracked scratch files and silent applies vanish from history. Commit first, then share—future you will say thanks.
Full Explanation
A commit captures a point-in-time snapshot of tracked files with metadata such as author and message. That snapshot is the atomic unit of source-control history before pushes, reviews, or merges. Applying infrastructure changes without commits, or leaving work untracked, removes the audit trail DevOps practices expect.