FC0-U71 Software Development Concepts Practice Question
A team of developers is working on a large project with multiple features. They use a version control system. One developer creates a new branch to develop a feature, while other developers continue working on the main branch. After completing the feature, the developer wants to combine the changes from the feature branch back into the main branch. What version control operation should be performed?
⚠ Common exam trap
The CompTIA ITF+ exam often tests the distinction between a 'pull request' (a request to merge) and the actual 'merge' operation, leading candidates to confuse the collaborative workflow step with the underlying version control command.
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
The correct operation is 'Merge' (D), which combines the changes from the feature branch into the main branch. In Git, merging integrates the commit history of two branches, preserving the feature's work while incorporating it into the target branch. This is the standard workflow for bringing a completed feature back into the main line of development.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Pull request
Why it's wrong here
A pull request is a review-and-approval workflow wrapper around integration, not the integration operation itself; it does not combine the branches. It is tempting because pull requests commonly trigger merges on hosted platforms, and would be correct when the team requires peer review before changes reach main.
- ✗
Fork
Why it's wrong here
Forking duplicates an entire repository into a separate copy under another account or namespace; it does not merge a feature branch into main. It is tempting because forks also isolate feature work, and would be correct when contributing to a project where you lack write access to the upstream repository.
- ✗
Commit
Why it's wrong here
Commit records staged changes into the current branch's history; it does not integrate one branch's commits into another. It is tempting because committing is the prerequisite step before any integration, and would be the correct operation when saving the developer's completed feature work locally on the feature branch.
- ✓
Merge
Why this is correct
Merge integrates the feature branch's commits into the main branch, combining divergent histories while preserving both lines of development. This is the operation that reunites the completed feature work with the mainline, satisfying the stem's requirement to combine changes.
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 →
Same concept, more angles
6 more ways this is tested on FC0-U71
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A developer is using Git and wants to integrate changes from a feature branch into the main branch. Which Git operation should be performed?
hard- A.Branch
- B.Commit
- C.Clone
- ✓ D.Merge
Why D: The 'git merge' command integrates changes from one branch into another, typically merging a feature branch into the main branch. It combines the commit histories and creates a merge commit if necessary, preserving the context of both branches.
Variation 2. A developer is working on a collaborative software project and uses Git for version control. The developer creates a new feature on a separate branch. After completing the feature, what is the typical next step to integrate the changes into the main branch?
hard- A.Commit the changes directly to the main branch
- B.Delete the feature branch without merging
- ✓ C.Merge the feature branch into the main branch
- D.Push the branch to the remote repository
Why C: After completing work on a feature branch, the typical next step is to merge the feature branch into the main branch to integrate the changes. This is the standard Git workflow: create a branch, commit changes, then merge back into the mainline (often via a pull request). Merging combines the histories and brings the feature into the main branch.
Variation 3. In Git, which action creates a snapshot of changes in the repository?
hard- A.Merge
- ✓ B.Commit
- C.Push
- D.Branch
Why B: In Git, a commit creates a snapshot of the staged changes in the repository, recording the state of the tracked files along with a message, author, and timestamp. Each commit is identified by a SHA-1 (or SHA-256) hash and forms a node in the repository's history graph. This is the fundamental operation that captures changes into version control.
Variation 4. A software developer is working on a team project and uses Git for version control. The developer has made changes to the code and wants to save a snapshot of the current state of the project locally. Which Git command should they use?
hard- A.git pull
- B.git branch
- ✓ C.git commit
- D.git push
Why C: The `git commit` command records the staged changes in the local repository, creating a permanent snapshot of the project's current state. It captures a point-in-time version of the code along with a commit message, allowing the developer to track history and revert if needed. Unlike remote operations, `git commit` works entirely locally, which matches the requirement to save a snapshot locally.
Variation 5. A developer creates a new branch in a version control system to work on a new feature. After completing the feature, the developer wants to combine the changes from the feature branch back into the main branch. What is this process called?
easy- A.Committing
- B.Forking
- C.Branching
- ✓ D.Merging
Why D: Merging is the process of combining changes from one branch into another — here, taking the completed feature branch and integrating its commits into the main branch. Git performs this via git merge, which either fast-forwards or creates a merge commit.
Variation 6. Two developers have edited the same file and created different versions. To integrate their changes, which Git operation should they perform?
hard- A.git pull
- ✓ B.git merge
- C.git rebase
- D.git commit
Why B: The git merge command is used to integrate changes from one branch into another, combining the histories of both branches. When two developers have edited the same file in different branches, merging brings their changes together into a single branch, resolving any conflicts. This is the standard operation for integrating divergent work.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.