TALEND-CORE-DEVELOPER practice question 10 of 15

You are collaborating on a project with other developers using talend best practices. When should you use a tag?

Full set: 55 questions
Answer options
A: Capturing snapshot of a codebase that requires ongoing maintenance.
B: Fixing hugs or enhancements.
C: Denoting major or minor releases. Correct answer
D: Denoting a milestone in the lifecycle of a project Correct answer
Correct Answer:
C. Denoting major or minor releases.; D. Denoting a milestone in the lifecycle of a project
Explanation

In Talend-recommended Git workflows, tags are immutable pointers that label a specific commit, most often a release or other significant checkpoint. They are therefore applied to mark major/minor releases (C) and to record milestones in a project’s life-cycle (D). Snapshots that will continue to evolve or where bug-fixes are applied are handled with branches, not tags.

Why Incorrect

A. Ongoing maintenance requires a branch so that new commits can be added; a tag is read-only.
B. Bug fixes or enhancements are developed on feature or maintenance branches; a tag cannot be updated once created.

References

1. Talend Studio User Guide 8.0

“Collaborating with Git – Working with tags”

p. 604: “Tags are read-only references used mainly to mark release versions or other milestones.”

2. Talend Best Practices Guide for Collaborative Development 7.3

Sect. 4.2 “Branching

Tagging and Releasing”: “Branches are used for continuing work… Tags identify immutable milestones such as v1.0

v1.1.”

3. Talend Software Development Life Cycle (SDLC) Guidelines

Rev. 2022-05

p. 17: “Apply a tag when a version is declared GA or when an agreed milestone is reached; do not use tags for ongoing fixes.”

Scroll to Top