Question 312 of 892
Process — Managing Technical AspectshardMultiple ChoiceObjective-mapped

Quick Answer

The correct answer is that the 'feature/login' branch was merged into main via a merge commit. This is accurate because the Git history exhibit displays a merge commit with two parent commits—one from the tip of main and one from the tip of the feature branch—indicating an explicit integration rather than a fast-forward merge. On the PMP exam, this tests your ability to read a Git commit graph and distinguish between merge commits and linear history, a common trap being that a merge commit always preserves the branch topology, whereas a fast-forward would show a straight line. For exam day, remember the memory tip: "Two parents, one merge; one parent, just a surge"—if a commit has two parents, it is a merge commit; if only one, it is a regular commit on a linear path.

PMP Process — Managing Technical Aspects Practice Question

This PMP practice question tests your understanding of process — managing technical aspects. 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.

Network Topology
$ git logonelinegraphRefer to the exhibit.```|/* 4e5f6a7 Initial commit

Refer to the exhibit. A project manager is reviewing the Git history of a project. Which statement accurately describes the state of the repository?

Question 1hardmultiple choice
Full question →
Network Topology
$ git logonelinegraphRefer to the exhibit.```|/* 4e5f6a7 Initial commit

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

The 'feature/login' branch was merged into main via a merge commit.

The exhibit shows a merge commit (e.g., 'Merge branch feature/login into main') with two parent commits, one from main and one from the tip of 'feature/login'. This indicates that the 'feature/login' branch was integrated into main via a merge commit, not a fast-forward merge. Therefore, option B is correct.

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.

  • The 'feature/login' branch is still active and contains unmerged commits.

    Why it's wrong here

    The branch has been merged; its commits are now in main.

  • The 'feature/login' branch was merged into main via a merge commit.

    Why this is correct

    The graph shows a merge commit on main from feature/login.

    Related concept

    Read the scenario before looking for a memorised answer.

  • The 'feature/login' branch has not been merged into main.

    Why it's wrong here

    The merge commit shows it has been merged.

  • The 'feature/login' branch is behind main by one commit.

    Why it's wrong here

    The branch is merged, so it is not behind; it is up-to-date.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates may confuse a merge commit with a fast-forward merge, assuming that any merge commit means the branch is still active or unmerged, when in fact the merge commit itself is the evidence of integration.

Trap categories for this question

  • Command / output trap

    The merge commit shows it has been merged.

Detailed technical explanation

How to think about this question

In Git, a merge commit is created when two divergent branches are combined using `git merge --no-ff` or when a fast-forward is not possible. The merge commit has two parent pointers: one to the previous tip of main and one to the tip of the merged branch. This preserves the branch history and is common in team workflows to track feature integration. Real-world scenarios often use merge commits to maintain a clear audit trail of when features were integrated.

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.

TExam Day Tips

  • 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 PMP 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 exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related PMP practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free PMP practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this PMP question test?

Process — Managing Technical Aspects — This question tests Process — Managing Technical Aspects — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: The 'feature/login' branch was merged into main via a merge commit. — The exhibit shows a merge commit (e.g., 'Merge branch feature/login into main') with two parent commits, one from main and one from the tip of 'feature/login'. This indicates that the 'feature/login' branch was integrated into main via a merge commit, not a fast-forward merge. Therefore, option B is correct.

What should I do if I get this PMP question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 11, 2026

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.

Loading comments…

Sign in to join the discussion.

This PMP practice question is part of Courseiva's free PMI 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 PMP exam.