Gitflow vs Trunk-Based Development Quiz

1. In Gitflow, when is a release branch created?

When a feature is completed

When preparing a new production release

For every bug fix

After each sprint ends

2. What is the key difference between Gitflow and trunk-based development in terms of branch complexity?

Gitflow uses fewer branches

Trunk-based uses fewer, shorter-lived branches

Both use identical branch structures

Trunk-based requires more branches

3. Which approach better supports rapid iteration and continuous deployment?

Gitflow with strict release schedules

Trunk-based development with short-lived branches

Multiple permanent feature branches

Manual branch management without CI/CD

4. True or False: Trunk-based development requires developers to commit directly to main without feature branches.

True

False

Submit

6. Which branching strategy minimizes the risk of merge conflicts?

Gitflow with long-lived branches

Trunk-based with frequent small merges

Multiple main branches

Feature branches lasting several months

Submit

8. What is the naming convention for feature branches in Gitflow?

Feature/feature-name

Feat-feature-name

Feature_name

F/feature-name

9. True or False: Gitflow is better suited for projects with scheduled release dates.

True

False

10. Which practice is essential in trunk-based development to keep the main branch stable?

Long code review periods

Automated testing and continuous integration

Delaying feature merges until release time

Manual testing before every commit

11. What is the primary goal of trunk-based development?

Keep a single main branch where all developers integrate frequently

Maintain separate branches for each feature indefinitely

Use release branches as the primary integration point

Create a new branch for each bug fix and never merge

12. What is the primary benefit of trunk-based development for CI/CD pipelines?

Easier to manage multiple release versions

Simpler, more frequent integration and deployment

Better isolation of experimental features

Reduced need for automated testing

13. In Gitflow, which branch represents production-ready code?

Develop

Master/Main

Release

Feature

14. True or False: Trunk-based development requires feature flags to hide incomplete features.

True

False

15. Which Gitflow branch is created from a release branch for emergency fixes?

Feature branch

Develop branch

Hotfix branch

Master branch

16. What is the main disadvantage of long-lived feature branches?

They reduce code quality

They increase merge conflicts and integration risks

They prevent code reviews

They slow down feature development

17. In trunk-based development, how long should a feature branch typically exist?

Several weeks or months

A few days or less

One release cycle

Until the next major version

18. What is a 'hotfix' branch in Gitflow used for?

Developing new features in isolation

Addressing critical production bugs quickly

Staging code before release

Testing experimental changes safely

19. Which branching strategy is most compatible with continuous deployment?

Gitflow with long-lived release branches

Trunk-based development with short-lived feature branches

Git-flow with monthly release cycles

Feature branching without any trunk

20. In Gitflow, what is the purpose of the 'develop' branch?

Serves as the stable production-ready code

Integrates feature branches and serves as a staging area

Holds only hotfix changes for critical production issues

Stores archived versions of old releases

AutoOps+ Branching Strategies Gitflow and Trunk Based Quiz

1. In Gitflow, when is a release branch created?

2.

What first name or nickname would you like us to use?

2. What is the key difference between Gitflow and trunk-based development in terms of branch complexity?

3. Which approach better supports rapid iteration and continuous deployment?

4. True or False: Trunk-based development requires developers to commit directly to main without feature branches.

5. In Gitflow, a ____ branch is used to prepare for a production release.

6. Which branching strategy minimizes the risk of merge conflicts?

7. In trunk-based development, incomplete features are hidden using ____.

8. What is the naming convention for feature branches in Gitflow?

9. True or False: Gitflow is better suited for projects with scheduled release dates.

10. Which practice is essential in trunk-based development to keep the main branch stable?

11. What is the primary goal of trunk-based development?

12. What is the primary benefit of trunk-based development for CI/CD pipelines?

13. In Gitflow, which branch represents production-ready code?

14. True or False: Trunk-based development requires feature flags to hide incomplete features.

15. Which Gitflow branch is created from a release branch for emergency fixes?

16. What is the main disadvantage of long-lived feature branches?

17. In trunk-based development, how long should a feature branch typically exist?

18. What is a 'hotfix' branch in Gitflow used for?

19. Which branching strategy is most compatible with continuous deployment?

20. In Gitflow, what is the purpose of the 'develop' branch?