FC0-U71 Applications and Software Practice Question
A programmer is using a version control system. Which THREE are core Git concepts?
⚠ Common exam trap
FC0-U71 often tests the distinction between general programming concepts and Git-specific concepts — candidates may mistakenly select 'variable' or 'compilation' as Git concepts when they are not part of Git's version control model.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Repository
Option B (Repository) is correct because a Git repository is the core storage structure that holds all tracked files, history, and metadata in the .git directory. Option C (Branch) is correct because a branch is a movable pointer to a commit, enabling parallel lines of development in Git. Option D (Commit) is correct because a commit is Git's fundamental snapshot object that records a point-in-time state of the repository along with author, message, and parent references. Option A (Variable) is incorrect because variables are programming-language constructs, not Git concepts. Option E (Compilation) is incorrect because compilation is a build-process step performed by compilers, unrelated to Git's version control model.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Variable
Why it's wrong here
A variable is a named storage location within running program code; Git concepts concern repository state, such as commits, branches, tags and merges. It is tempting because variables appear in the same source files Git versions, but they belong to programming languages, not to Git's data model.
- ✓
Repository
Why this is correct
A repository is Git's core storage unit, holding the complete commit history, branches and tracked files for a project. It satisfies the version control constraint directly: every commit, merge and checkout operation acts on repository contents, making it one of the three fundamental Git concepts the question requires.
- ✓
Branch
Why this is correct
Branching creates an independent line of development from a commit, letting work diverge without affecting the main line. Git implements this as a lightweight movable pointer to a commit, satisfying the stem's requirement to identify core Git concepts alongside committing and merging.
- ✓
Commit
Why this is correct
A commit records a snapshot of staged changes, permanently capturing the project state at that point in the repository's history. This satisfies the stem's requirement for a core Git concept, since commits form the fundamental unit of version history that branching, merging and rollback operations all depend upon.
- ✗
Compilation
Why it's wrong here
Compilation converts source code into executable binaries; Git tracks snapshots of file content, not build artefacts. It is tempting because build pipelines often run alongside version control, and compiled outputs are sometimes committed, but compilation itself is a toolchain step, not a Git concept such as commit, branch or merge.
Go deeper
Related to this question
About these practice questions
Courseiva writes every FC0-U71 question from scratch — 988 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
This FC0-U71 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the FC0-U71 exam.