hardMultiple Choice
FC0-U71 Practice Question: Two developers have edited the same file and…
Two developers have edited the same file and created different versions. To integrate their changes, which Git operation should they perform?
⚠ Common exam trap
FC0-U71 often tests the distinction between merge and rebase, with candidates incorrectly choosing rebase for integration when merge is the standard operation for combining divergent branches.
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 merge
The git merge command is used to integrate changes from one branch into another, combining the histories of both branches. When two developers have edited the same file in different branches, merging brings their changes together into a single branch, resolving any conflicts. This is the standard operation for integrating divergent work.
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 pull
Why it's wrong here
git pull fetches and merges remote commits into the local branch; it cannot reconcile two divergent local edits to one file. It is tempting because pull does perform a merge, but that merge joins remote history, not two developers' conflicting working copies — git merge (or a rebase) integrates their branches.
- ✓
git merge
Why this is correct
git merge integrates divergent branches by combining the two developers' commits into a unified history, resolving changes to the same file. It reconciles their separate versions, whereas operations like clone or commit alone cannot join parallel lines of work.
- ✗
git rebase
Why it's wrong here
git rebase rewrites commit history by replaying one branch's commits onto another, which does not merge two divergent versions of the same file into a combined result. It is tempting for producing linear history, and it would be correct when the requirement is tidying local commits before sharing rather than integrating parallel edits.
- ✗
git commit
Why it's wrong here
git commit records the current staging area as a new snapshot in the local repository; it neither compares nor combines another developer's version. It is tempting because committing is the routine step after editing, and it would be correct when the requirement is saving local work before any integration with a remote branch occurs.
Visual reference
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 →
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.