In version control, what is the copy of files and folders that a team can work on before merging?

In version control, what is the copy of files and folders that a team can work on before merging?

• A. Branch
• B. Clone
• C. Commit
• D. Browser Developer Tools

Answer: (A)

A branch creates a separate line of development from the main codebase, so the team can work on changes independently without affecting the stable version. Each feature or fix can live in its own branch, and when it’s ready, those changes can be merged back into the main branch after review and testing. This isolation enables parallel work and safer integration. Cloning copies the whole repository to another location, but it’s not about maintaining separate work streams within the same project. Committing records changes as a snapshot within a branch, not the mechanism that provides parallel work paths. Browser Developer Tools aren’t related to version control concepts at all.

A branch creates a separate line of development from the main codebase, so the team can work on changes independently without affecting the stable version. Each feature or fix can live in its own branch, and when it’s ready, those changes can be merged back into the main branch after review and testing. This isolation enables parallel work and safer integration.

Cloning copies the whole repository to another location, but it’s not about maintaining separate work streams within the same project. Committing records changes as a snapshot within a branch, not the mechanism that provides parallel work paths. Browser Developer Tools aren’t related to version control concepts at all.