Question 39 of 1,000
Software Development and DesignhardMultiple ChoiceObjective-mapped

200-901 Software Development and Design Practice Question

This 200-901 practice question tests your understanding of software development and design. 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 developer is using Git for version control. After creating a new feature branch 'feature-login' from 'main', they make several commits. Meanwhile, another developer has merged changes into 'main'. The developer wants to incorporate the latest main changes into 'feature-login' without creating a merge commit. Which Git command should they use?

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 pull --rebase origin main

Option C is correct because `git pull --rebase origin main` fetches the latest changes from the remote `main` branch and then rebases the current `feature-login` branch onto those changes. This incorporates the new commits from `main` without creating a merge commit, resulting in a linear history. The `--rebase` flag ensures that the developer's commits are replayed on top of the updated `main`, avoiding the extra merge commit that `git merge` would create.

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 rebase main

    Why it's wrong here

    Missing fetch; need to fetch latest main first. But the command itself is correct if main is up-to-date, but typically you'd fetch first.

  • git merge main

    Why it's wrong here

    Merge creates a merge commit, which is not desired here.

  • git pull --rebase origin main

    Why this is correct

    This fetches and rebases the current branch onto main, incorporating changes without a merge commit.

    Related concept

    Read the scenario before looking for a memorised answer.

  • git checkout main && git pull && git checkout feature-login && git merge main

    Why it's wrong here

    This creates a merge commit.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Cisco often tests the distinction between `git merge` and `git rebase` in the context of avoiding merge commits, and the trap here is that candidates may choose `git rebase main` (Option A) without realizing it does not fetch remote changes, or they may choose `git merge main` (Option B) thinking it can be done without a merge commit, which is incorrect.

Trap categories for this question

  • Command / output trap

    Missing fetch; need to fetch latest main first. But the command itself is correct if main is up-to-date, but typically you'd fetch first.

Detailed technical explanation

How to think about this question

Under the hood, `git pull --rebase` performs a `git fetch` followed by `git rebase FETCH_HEAD`. This replays the local commits from `feature-login` onto the tip of the remote `main`, effectively rewriting the branch history. In a real-world scenario, this is commonly used in feature branches to keep a clean, linear history before merging into `main`, especially in workflows that enforce a linear commit history (e.g., using `git rebase` before a fast-forward merge). A subtle behavior is that rebasing rewrites commit hashes, which can cause issues if the branch is shared with other developers; in such cases, `git merge` might be preferred despite the merge commit.

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 200-901 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 200-901 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 200-901 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 200-901 question test?

Software Development and Design — This question tests Software Development and Design — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: git pull --rebase origin main — Option C is correct because `git pull --rebase origin main` fetches the latest changes from the remote `main` branch and then rebases the current `feature-login` branch onto those changes. This incorporates the new commits from `main` without creating a merge commit, resulting in a linear history. The `--rebase` flag ensures that the developer's commits are replayed on top of the updated `main`, avoiding the extra merge commit that `git merge` would create.

What should I do if I get this 200-901 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: Jul 4, 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 200-901 practice question is part of Courseiva's free Cisco 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 200-901 exam.