FC0-U71 Applications and Software Practice Question
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?
⚠ Common exam trap
FC0-U71 often tests the misconception that pushing a branch to a remote repository integrates it into main — candidates pick 'push' instead of 'merge,' but pushing only publishes the branch.
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 feature branch into the main branch
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.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Commit the changes directly to the main branch
Why it's wrong here
Committing straight to main bypasses the merge step, so the feature branch's history never integrates through review. Direct commits suit trivial hotfixes on solo repositories, whereas collaborative workflows merge the completed branch into main via pull request.
- ✗
Delete the feature branch without merging
Why it's wrong here
Deleting the branch discards the commits, so the feature never reaches main. Branch deletion is correct only after a successful merge, or when abandoning experimental work entirely; here the completed feature must first be merged.
- ✓
Merge the feature branch into the main branch
Why this is correct
Git integrates completed branch work by merging the feature branch into the main branch, combining the divergent commit histories. This satisfies the stem's scenario of a finished feature being brought back into the mainline after development on a separate branch.
- ✗
Push the branch to the remote repository
Why it's wrong here
Pushing publishes the branch to the remote but leaves main unchanged; integration still requires a merge or pull request. Pushing is the right step for sharing work-in-progress or backing up a branch, not for incorporating finished changes into main.
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.