The correct sequence is `git checkout new-feature` followed by `git merge main`, then resolving any conflicts. This is the proper way to merge main into a feature branch because it pulls Bob’s bug fixes directly into Alice’s working branch without disturbing the stable main branch. On the CompTIA ITF+ FC0-U61 exam, this scenario tests your understanding of branch management and the purpose of merging—specifically, that merging the target branch (main) into the source branch (feature) is the safe, standard workflow for incorporating upstream changes. A common trap is confusing this with merging the feature into main, which would introduce unfinished code into production. Another pitfall is attempting a rebase with a force push, which rewrites history and can disrupt the team. Remember the memory tip: “Merge the stable into the unstable”—always bring the main branch’s completed fixes into your feature branch, not the other way around.
FC0-U61 Software Development Concepts Practice Question
This FC0-U61 practice question tests your understanding of software development concepts. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A team of developers is collaborating on a mobile app using Git. One developer, Alice, is working on a new feature in a branch called "new-feature". Bob, another developer, has pushed several bug fixes to the main branch. Alice now wants to incorporate Bob's bug fixes into her feature branch. Which sequence of Git commands should Alice use to achieve this with minimal disruption?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
git checkout new-feature, git merge main, then resolve conflicts if any.
Merging the main branch into the feature branch (git checkout new-feature, git merge main) brings the fixes into Alice's branch. The opposite (merging feature into main) would add unfinished work to main. Rebasing with force push is dangerous. Creating a new branch doesn't bring in fixes.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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 fetch, git rebase new-feature onto origin/main, then force push.
Why it's wrong here
Rebasing rewrites history and force push can disrupt others; it's more advanced and risky.
✓
git checkout new-feature, git merge main, then resolve conflicts if any.
Why this is correct
This merges the latest main (with bug fixes) into the feature branch, keeping the work isolated.
Related concept
Read the scenario before looking for a memorised answer.
✗
git checkout -b new-feature, git push.
Why it's wrong here
This creates a new branch from the current branch, not incorporating the fixes.
✗
git checkout main, git pull, git merge new-feature, then push.
Why it's wrong here
This merges the feature branch into main, which is premature and could introduce incomplete code.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
Use explanations to understand the rule behind the answer.
TExam Day Tips
→Underline the problem statement mentally.
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the FC0-U61 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which FC0-U61 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
Software Development Concepts — This question tests Software Development Concepts — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: git checkout new-feature, git merge main, then resolve conflicts if any. — Merging the main branch into the feature branch (git checkout new-feature, git merge main) brings the fixes into Alice's branch. The opposite (merging feature into main) would add unfinished work to main. Rebasing with force push is dangerous. Creating a new branch doesn't bring in fixes.
What should I do if I get this FC0-U61 question wrong?
Identify which FC0-U61 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This FC0-U61 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-U61 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.