mediumMultiple Choice
FC0-U71 Practice Question: A development team is using version control for…
A development team is using version control for their project. They need to isolate a new feature from the main codebase until it is complete. Which version control operation should they perform?
⚠ Common exam trap
CompTIA often tests the misconception that 'commit' or 'push' can isolate work, but these operations only record or share changes; they do not create a separate development path, which is the core purpose of a 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
✓
Branch
Branching creates a separate line of development within a version control system (e.g., Git, Mercurial), allowing the team to work on a new feature in isolation without affecting the main codebase (often called 'main' or 'master'). Once the feature is complete and tested, the branch can be merged back. This directly addresses the requirement to isolate work until it is finished.
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 it's wrong here
Merging integrates completed work from one branch into another, so it cannot isolate an unfinished feature. The team needs to create a branch, which diverges the codebase until the feature is ready. Merge is correct once the feature is complete and ready to rejoin main.
- ✗
Commit
Why it's wrong here
Committing records staged changes into the current branch's history, leaving the work on the shared mainline rather than isolating it. It is tempting because committing is the correct operation when saving completed local changes before switching branches or pushing.
- ✓
Branch
Why this is correct
Branching creates an independent line of development from the main codebase, letting the team commit feature work in isolation without affecting stable code. Merging reintegrates it once complete. This directly satisfies the requirement to isolate an incomplete feature, unlike committing, tagging or cloning, which do not separate parallel workstreams.
- ✗
Push
Why it's wrong here
Pushing uploads local commits to a remote repository, propagating the feature to the shared mainline instead of isolating it. It is tempting because pushing is the correct operation when publishing a finished branch so teammates can access the committed work.
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
1 more way 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 working on a new feature and creates a copy of the main codebase to work in isolation. Later, this copy is merged back into the main branch. Which version control concept describes this copy?
medium- A.Merge
- ✓ B.Branch
- C.Commit
- D.Pull request
Why B: A branch is an independent line of development created from a point in the main codebase so a developer can work in isolation without affecting the main line. When the feature is complete, the branch is merged back into the main branch. This matches the scenario exactly: a copy of the codebase used for isolated work that is later integrated.
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.