Hotspot Question You company uses a Git source-code repository. You plan to implement Gitflow as a workflow strategy. You need to identify which branch types are used for production code and preproduc

Question

Exhibit

Answer Area

• Production code:Master
  MasterFeatureDevelop
• Preproduction code:Develop
  MasterFeatureDevelop

Explanation

This question tests knowledge of the Gitflow branching workflow strategy, specifically which branch types serve production and preproduction environments.

Approach. In Gitflow, the 'main' (or 'master') branch holds production-ready code - it always reflects the current production state and is only updated via merge from release or hotfix branches. The 'develop' branch serves as the preproduction integration branch where all feature branches are merged and tested before being promoted to a release; it represents the latest delivered development changes for the next release. Therefore: Production code → main branch; Preproduction code → develop branch.

Concept tested. Gitflow branching strategy: understanding the roles of 'main' (production) and 'develop' (preproduction/integration) branches, as well as supporting branches like feature, release, and hotfix branches that feed into them.

Reference. Vincent Driessen's original Gitflow model (nvie.com/posts/a-successful-git-branching-model/) and Microsoft Azure DevOps documentation on branching strategies.

No community discussion yet for this question.