FC0-U71 Software Development Concepts Practice Question
A development team is choosing a version control workflow for a project with multiple contributors. They want to keep the main branch stable and allow each developer to work independently before changes are reviewed and integrated. Which THREE of the following are characteristics of a typical branch-based version control workflow? (Choose three.)
⚠ Common exam trap
The trap here is assuming that any use of version control automatically means branches are isolated repositories rather than lightweight lines of development that share history and merge back.
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
✓
Developers create separate branches to isolate work on features or fixes.
A branch-based workflow isolates work by letting developers create branches for features or fixes, supports parallel development without disturbing others, and integrates changes into main only after review. Direct commits to main and permanently unsynchronized repository copies do not fit this model because they either bypass review or prevent effective integration and collaboration.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Developers create separate branches to isolate work on features or fixes.
Why this is correct
In a branch-based workflow, each developer creates a branch from a shared baseline such as main. This isolates unfinished or experimental changes so they do not affect other contributors. When the work is ready, the branch can be reviewed and merged. This matches the team's goal of independent work while keeping the main branch stable and free from incomplete changes.
- ✗
Each developer maintains a completely separate copy of the repository that never syncs.
Why it's wrong here
A branch is not a separate disconnected repository. Branches share the same repository history and can be synchronized and merged. If each developer used a copy that never synced, integration would be difficult and conflicts would multiply. The scenario calls for independent work that is later integrated, which requires shared history, not permanently isolated repositories.
- ✓
Branches allow parallel development without immediately affecting other developers.
Why this is correct
By working on separate branches, developers can make commits and test changes without altering what others see on main or on their own branches. This parallelism increases throughput and reduces disruption. When the branch is ready, it is merged. This behavior directly supports the team's requirement for independent work before changes are reviewed and integrated.
- ✗
All developers commit directly to the main branch without review.
Why it's wrong here
Committing directly to main bypasses isolation and review, which conflicts with the stated goal of keeping main stable. Branch-based workflows exist precisely to avoid this. While some small teams may allow direct commits, the scenario describes multiple contributors who want independent work and review before integration, so this practice would undermine the intended stability and collaboration.
- ✓
Changes are merged back into the main branch after review.
Why this is correct
After a developer completes work on a branch, the changes are typically proposed for review and then merged into main. This integrates tested and approved work while preserving main as a stable integration point. The review step catches defects and ensures consistency, which directly supports the team's goal of keeping the main branch reliable for all contributors.
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.