easyMultiple Select
200-901 Practice Question: Which TWO of the following are essential steps in…
Which TWO of the following are essential steps in a typical Git workflow when collaborating on a feature branch? (Choose two.)
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 branch into master
Option E (Create a branch) is essential because a feature branch isolates new work from the mainline, allowing commits to be made without affecting master until the work is ready. Option B (Merge the branch into master) is essential because the completed feature must be integrated back into the mainline so other collaborators can build on it. Option A (Rebase onto master) is a valid but optional technique for updating or linearizing history, not a required step in every workflow. Option C (Delete the remote repository) is destructive and unrelated to normal collaboration. Option D (Stash changes before switching branches) is only a convenience when the working tree is dirty, not an essential step of the workflow.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Rebase onto master
Why it's wrong here
Rebasing onto master rewrites feature-branch commits and is optional, not essential; typical workflows merge or rebase depending on team policy. It is tempting because rebasing keeps history linear before a pull request, which some teams mandate, but the question asks for steps essential to any collaborative feature-branch workflow.
- ✓
Merge the branch into master
Why this is correct
Merging the feature branch into master integrates completed work into the mainline, satisfying the collaboration requirement that changes reach the shared repository. In a typical Git workflow, the branch's commits are combined via merge, making the feature available to all collaborators before the branch is deleted.
- ✗
Delete the remote repository
Why it's wrong here
Deleting the remote repository destroys shared history and other collaborators' work, so it is never part of a feature-branch workflow. It is tempting because cleaning up after a merged branch is normal, but that means deleting the branch, not the remote repository itself.
- ✗
Stash changes before switching branches
Why it's wrong here
Stashing is only needed when uncommitted changes would conflict with a checkout; committing or working cleanly achieves the same switch without it. It is tempting because stashing is a common convenience when moving between branches mid-task, but it is conditional rather than an essential workflow step.
- ✓
Create a branch
Why this is correct
Creating a branch isolates feature work from the main codebase, satisfying the stem's requirement for a feature branch workflow. This step establishes a separate line of development so collaborators commit changes without destabilising main until the work is reviewed and merged.
Go deeper
Related to this question
About these practice questions
One of 975 original 200-901 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.