Git organizes work into three areas locally. Which trio best describes these areas?

Git organizes work into three areas locally. Which trio best describes these areas?

• A. History, working directory, staging area
• B. Working directory, repository, history
• C. Working directory, staging area, history
• D. Working directory, cache, log

Answer: (C)

Git’s local workflow revolves around three zones: the working directory where you edit files, the staging area where you assemble changes for the next commit, and the repository that stores committed history. This trio—working directory, staging area, and history (in the repository)—best matches the way changes move from your edits to a recorded history: you modify files in the working directory, stage the intended changes in the staging area, and then commit to capture those changes in the repository, which preserves the project’s history. The other options mix in terms that aren’t part of the core three areas (like cache or log) or present the sequence in a way that doesn’t reflect the actual flow from editing to recording history.

Git’s local workflow revolves around three zones: the working directory where you edit files, the staging area where you assemble changes for the next commit, and the repository that stores committed history. This trio—working directory, staging area, and history (in the repository)—best matches the way changes move from your edits to a recorded history: you modify files in the working directory, stage the intended changes in the staging area, and then commit to capture those changes in the repository, which preserves the project’s history. The other options mix in terms that aren’t part of the core three areas (like cache or log) or present the sequence in a way that doesn’t reflect the actual flow from editing to recording history.