Courseiva

FC0-U71 Applications and Software Practice Question

A developer is using Git and wants to integrate changes from a feature branch into the main branch. Which Git operation should be performed?

⚠ Common exam trap

The trap is confusing merge with other Git operations like rebase or pull; candidates might think 'commit' integrates changes, but commit only saves local changes, not branch integration.

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

✓

Merge

The 'git merge' command integrates changes from one branch into another, typically merging a feature branch into the main branch. It combines the commit histories and creates a merge commit if necessary, preserving the context of both branches.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Branch

    Why it's wrong here

    Branch creates a separate line of development; it does not move or merge commits between branches. It is tempting because feature work happens on branches, but the correct use is isolating work before integration, not combining it into main.

  • ✗

    Commit

    Why it's wrong here

    Commit records staged changes into the current branch's history; it does not combine divergent branch histories. It is tempting because it is the routine save step, but its correct use is capturing a snapshot on one branch, not integrating a feature branch into main.

  • ✗

    Clone

    Why it's wrong here

    Clone copies a remote repository locally, including its history; it does not reconcile two branches within an existing repository. It is tempting because it is how developers obtain code, but its correct use is initial setup or duplicating a repo, not merging feature work into main.

  • ✓

    Merge

    Why this is correct

    Merging replays the feature branch's commits onto the main branch and creates a merge commit that preserves both histories, satisfying the requirement to integrate completed feature work. Unlike rebasing, it does not rewrite existing commits, so shared branch history stays intact for collaborators.

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 →

How Courseiva writes practice questions · Editorial policy

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.