Which statement best describes version control and the roles of repositories, commits, branches, and merges in collaborative development?

Which statement best describes version control and the roles of repositories, commits, branches, and merges in collaborative development?

• A. Version control encrypts code and manages licensing.
• B. Version control tracks changes; repositories store history; commits save snapshots; branches enable parallel work; merges integrate changes.
• C. Version control only logs the most recent change.
• D. Version control replaces the need for backups.

Answer: (B)

Version control tracks changes to a project over time, enabling collaboration and safe evolution of code. A repository is the storage that holds the entire history of the project, including every version of every file. Each commit is like a saved snapshot that records what changed at a particular moment, so you can review history, revert to earlier states, or pinpoint when a specific change was made. Branches let you work on new features or fixes in isolation, so different developers can pursue parallel work without stepping on each other’s toes. Merges bring those parallel developments back together, integrating the changes from different branches into a common history and surface conflicts that need resolution. In collaborative development, these elements work together to keep work organized and recoverable: people create branches for separate tasks, make commits to capture progress, and merge when the work is ready to be combined, ensuring a cohesive final result. The other ideas—encrypting code or managing licenses, only logging the most recent change, or replacing backups—do not describe what version control actually does.

Version control tracks changes to a project over time, enabling collaboration and safe evolution of code. A repository is the storage that holds the entire history of the project, including every version of every file. Each commit is like a saved snapshot that records what changed at a particular moment, so you can review history, revert to earlier states, or pinpoint when a specific change was made. Branches let you work on new features or fixes in isolation, so different developers can pursue parallel work without stepping on each other’s toes. Merges bring those parallel developments back together, integrating the changes from different branches into a common history and surface conflicts that need resolution.

In collaborative development, these elements work together to keep work organized and recoverable: people create branches for separate tasks, make commits to capture progress, and merge when the work is ready to be combined, ensuring a cohesive final result. The other ideas—encrypting code or managing licenses, only logging the most recent change, or replacing backups—do not describe what version control actually does.