🎙 Free live masterclass · Sun, 29 Nov, 7:00 pm IST · Java Full Stack roadmap Register free →
Skills101
← 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 →
  1. Q1. In Git Flow, which branch holds only released code?
  2. Q2. In Git Flow, a hotfix branch must be merged into which branches?
  3. Q3. How many long-lived branches does GitHub Flow use?
  4. Q4. In trunk-based development, how is a three-week feature handled?
  5. Q5. What does this print? (code)
  6. Q6. Which strategy fits best for a mobile app that ships numbered versions and must patch the old version while building the next one?
  7. Q7. Why does git merge --no-ff release/1.4.0 matter in Git Flow?
  8. Q8. What is the main risk of long-lived feature branches?
  9. Q9. Which is a branch protection rule on GitHub?
  10. Q10. For a student portfolio website deployed on every merge, which strategy is the most sensible default?
  11. Q11. In Git Flow, which branch does a new feature branch start from?
  12. Q12. In Git Flow, what kind of work is allowed on a release branch?
  13. Q13. In GitHub Flow, what usually happens right after a pull request is merged into main?
  14. Q14. Why do teams name branches like feature/SK-142-upi-refunds?
  15. Q15. Which practice does trunk-based development depend on most?