FC0-U71 Applications and Software Practice Question
A software development team is using a version control system to manage their codebase. They want to create an isolated copy of the main codebase to develop a new feature without affecting the main line of development. Which Git operation should they use?
⚠ Common exam trap
A common mix-up: candidates confuse branching with cloning; cloning creates a separate repository copy, while branching creates an isolated line within the same repository.
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
✓
git branch
git branch is the correct operation because it creates a new branch, which is an isolated line of development. This allows the team to work on the feature without affecting the main branch. git commit records changes, git merge combines branches, and git clone copies a repository. Only branching provides the required isolation for feature 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.
- ✓
git branch
Why this is correct
git branch creates a new branch, which is an independent line of development. This allows the team to work on a new feature in isolation without impacting the main branch. Changes made on the branch can later be merged back. This is the standard Git operation for isolating feature work and aligns perfectly with the scenario.
- ✗
git merge
Why it's wrong here
git merge integrates changes from one branch into another. It is used after feature development is complete to combine the isolated work back into the main line. Using merge before creating a separate branch would not provide isolation; it would combine changes directly. Thus, it is not the operation to initiate isolated development.
- ✗
git commit
Why it's wrong here
git commit records changes to the local repository, creating a snapshot of the current staging area. It does not create an isolated copy of the codebase for feature development. Committing directly to the main branch would affect the main line of development, which is exactly what the team wants to avoid. Therefore, this operation does not meet the requirement.
- ✗
git clone
Why it's wrong here
git clone creates a copy of an existing repository, typically from a remote location. While it produces a separate working copy, it is not used for creating a feature branch within the same repository. Cloning is for obtaining a repository for the first time or creating a separate copy, not for isolating feature work in the same project. It would not provide the branch-based isolation needed.
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.