- A
Rebase-only
Why wrong: Not a branching strategy, just a workflow preference.
- B
Merge avoidance
Why wrong: Not a standard branching strategy.
- C
Feature branching
Each feature is developed in its own branch.
- D
Direct commit to main
Why wrong: Generally discouraged; not a strategy.
- E
GitFlow
A branching model with develop, feature, release, and hotfix branches.
Question 673 of 1,000
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.
Which TWO of the following are valid branching strategies in Git? (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
✓
Feature branching
Feature branching (C) is a valid Git branching strategy where each new feature is developed in its own branch, allowing isolated work without disrupting the main codebase. GitFlow (E) is another valid strategy that defines a strict branching model with master, develop, feature, release, and hotfix branches, commonly used for projects with scheduled releases.
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.
- ✗
Rebase-only
Why it's wrong here
Not a branching strategy, just a workflow preference.
- ✗
Merge avoidance
Why it's wrong here
Not a standard branching strategy.
- ✓
Feature branching
Why this is correct
Each feature is developed in its own branch.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Direct commit to main
Why it's wrong here
Generally discouraged; not a strategy.
- ✓
GitFlow
Why this is correct
A branching model with develop, feature, release, and hotfix branches.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the distinction between Git operations (like rebase or merge) and actual branching strategies, so candidates mistakenly select 'Rebase-only' or 'Merge avoidance' as strategies when they are merely workflow tactics.
Detailed technical explanation
How to think about this question
Feature branching isolates work by creating a branch from a stable base (e.g., main or develop), and GitFlow formalizes this with a develop branch for integration and release branches for staging. Under the hood, Git's branching model uses lightweight pointers to commits, making branch creation cheap and encouraging frequent branching. In real-world CI/CD pipelines, feature branches are merged via pull requests after automated tests pass, while GitFlow's release branches allow last-minute bug fixes without blocking ongoing feature development.
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.
- →
Software Development and Design — study guide chapter
Learn the concepts, then practise the questions
- →
Software Development and Design practice questions
Targeted practice on this topic area only
- →
All 200-901 questions
1,000 questions across all exam domains
- →
Cisco DevNet Associate 200-901 study guide
Full concept coverage aligned to exam objectives
- →
200-901 practice test guide
How to use practice tests most effectively before exam day
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.
Software Development and Design practice questions
Practise 200-901 questions linked to Software Development and Design.
Understanding and Using APIs practice questions
Practise 200-901 questions linked to Understanding and Using APIs.
Application Deployment and Security practice questions
Practise 200-901 questions linked to Application Deployment and Security.
Cisco Platforms and Development practice questions
Practise 200-901 questions linked to Cisco Platforms and Development.
Network Fundamentals practice questions
Practise 200-901 questions linked to Network Fundamentals.
Infrastructure and Automation practice questions
Practise 200-901 questions linked to Infrastructure and Automation.
200-901 fundamentals practice questions
Practise 200-901 questions linked to 200-901 fundamentals.
200-901 scenario practice questions
Practise 200-901 questions linked to 200-901 scenario.
200-901 troubleshooting practice questions
Practise 200-901 questions linked to 200-901 troubleshooting.
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: Feature branching — Feature branching (C) is a valid Git branching strategy where each new feature is developed in its own branch, allowing isolated work without disrupting the main codebase. GitFlow (E) is another valid strategy that defines a strict branching model with master, develop, feature, release, and hotfix branches, commonly used for projects with scheduled releases.
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 →
Last reviewed: Jul 4, 2026
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.
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.
Sign in to join the discussion.