FC0-U71 Software Development Concepts Practice Question
A software company is using version control for a project. A developer has completed work on a new feature in a separate branch and wants to merge it into the main branch. What TWO steps should typically occur before the merge is accepted?
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
✓
Update the feature branch with the latest main branch changes
Common version control best practices include code review via pull requests and ensuring the feature branch is up to date with the main branch to minimize conflicts.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Delete the feature branch immediately
Why it's wrong here
Deleting the branch immediately discards the feature's history before review, testing, or merge completion. Branches are removed only after the merge is accepted and verified. Tempting as tidy housekeeping, but premature deletion loses commits and blocks rollback.
- ✓
Update the feature branch with the latest main branch changes
Why this is correct
Rebasing or merging main into the feature branch resolves conflicts locally and verifies the feature still builds against current code. This satisfies the pre-merge requirement that integration issues surface before acceptance, rather than after the main branch is destabilised.
- ✗
Run unit tests only on the main branch
Why it's wrong here
Testing only main leaves the feature branch unverified, so defects merge untested; the stem expects tests to pass on the branch before acceptance. It tempts because main-branch regression suites are standard, but they run after merge, not as the pre-merge gate.
- ✓
Submit a pull request for code review
Why this is correct
A pull request triggers peer review, letting teammates inspect the diff, run automated checks and approve changes before integration. This satisfies the pre-merge gate requiring independent verification, catching defects that the author alone would miss.
- ✗
Commit changes directly to the main branch
Why it's wrong here
Committing straight to main bypasses the pull request and code review that gate a feature branch merge; the stem expects review then merge. It tempts because direct commits suit solo projects or hotfixes where no review policy applies, yet they skip the branch protection this workflow requires.
Go deeper
Related to this question
About these practice questions
One of 988 original FC0-U71 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
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.