← All topics
Quiz: Branching Strategies: questions with answers
15 questions, each with the answer and a short explanation.
Take the timed quiz + get a certificate →- Q1. In Git Flow, which branch holds only released code?
- Q2. In Git Flow, a hotfix branch must be merged into which branches?
- Q3. How many long-lived branches does GitHub Flow use?
- Q4. In trunk-based development, how is a three-week feature handled?
- Q5. What does this print? (code)
- Q6. Which strategy fits best for a mobile app that ships numbered versions and must patch the old version while building the next one?
- Q7. Why does git merge --no-ff release/1.4.0 matter in Git Flow?
- Q8. What is the main risk of long-lived feature branches?
- Q9. Which is a branch protection rule on GitHub?
- Q10. For a student portfolio website deployed on every merge, which strategy is the most sensible default?
- Q11. In Git Flow, which branch does a new feature branch start from?
- Q12. In Git Flow, what kind of work is allowed on a release branch?
- Q13. In GitHub Flow, what usually happens right after a pull request is merged into main?
- Q14. Why do teams name branches like feature/SK-142-upi-refunds?
- Q15. Which practice does trunk-based development depend on most?