FC0-U71 Applications and Software Practice Question
A developer is using Git for version control. Which THREE actions are core Git operations? (Select THREE.)
⚠ Common exam trap
FC0-U71 often tests the distinction between version control operations and general development tasks, so candidates might mistakenly select 'debug' or 'compile' as Git operations because they are common developer activities.
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
✓
merge
Option A (merge) is a core Git operation because it combines changes from one branch into another, using the commit history and a three-way merge to integrate divergent lines of development. Option B (commit) is fundamental to Git, as it records a snapshot of the staged changes into the local repository, creating a new commit object with a unique SHA-1 hash. Option C (branch) is also a core Git operation, allowing the creation, listing, or deletion of branches, which are lightweight movable pointers to commits that enable parallel development. Options D (debug) and E (compile) are not Git operations; debugging and compiling are development tasks performed by debuggers and compilers, not by Git's version control commands.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
merge
Why this is correct
Merging combines divergent branch histories by integrating commits from one branch into another, preserving the commit graph through a merge commit or fast-forward. This satisfies the stem's requirement for a core Git operation, as branching and merging are fundamental to Git's distributed version-control model.
- ✓
commit
Why this is correct
Committing records the staged snapshot into the local repository's history, creating a new revision that Git can later diff, revert or branch from. It is a core Git operation because it advances the repository's commit graph, satisfying the stem's requirement for a fundamental version-control action.
- ✓
branch
Why this is correct
Branching creates a movable pointer to a commit, letting developers diverge work without copying files. Git's cheap branch pointers make this a core operation, satisfying the stem's requirement for a fundamental version-control action alongside commit and merge.
- ✗
debug
Why it's wrong here
Debugging is a general programming activity performed in an IDE or debugger, not a Git command for tracking changes, committing snapshots or merging branches. It is tempting because developers debug code stored in Git repositories, and it would be correct if the question asked about software development tasks rather than version control operations.
- ✗
compile
Why it's wrong here
Compilation transforms source code into executables via a compiler or build tool; Git tracks file versions and never compiles code. It is tempting because compiled artefacts are often committed to repositories, and it would be correct if the question asked which actions belong to a build pipeline rather than core Git operations.
Go deeper
Related to this question
About these practice questions
This FC0-U71 question is part of Courseiva's 988-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.