Copado Certified Practice Exam

What happens to feature branches when user stories are deployed to the production environment?

1. Feature branches are deleted.

2. New feature branches are created.

3. Feature branches are reused from previous commits.

4. Feature branches are archived.

The correct answer is: Feature branches are reused from previous commits.

The concept of feature branches in a deployment pipeline is fundamental to managing code changes in a collaborative environment. When user stories are deployed to the production environment, the common practice is to ensure that the feature branches related to those user stories are also managed accordingly. The correct understanding in this context is that feature branches are typically merged into the main branch (often referred to as 'develop' or 'main'). Once the features associated with those branches are deployed, it is common practice to delete feature branches to maintain a clean repository. This prevents clutter and helps streamline future development efforts. The notion that feature branches would simply be reused from previous commits implies that they can continuously serve as a foundation for new development, which isn't the usual case following deployment. Feature branches are generally intended for specific tasks or user stories and are intended to be short-lived. After a successful deployment, those branches that served their purpose would typically be deleted rather than reused, as this supports a clean and organized version control strategy. New feature branches are created as new user stories or tasks come up, but this does not suggest any reuse of old branches in the same context. Archiving feature branches is not a standard operating procedure in many development workflows. Once merged and deployed, the focus shifts to new development