A developer is working on a merge request that fixes a bug described in issue #42. The developer wants the merge request to automatically close the issue when the merge request is merged. What should the developer do?

Manually close issue #42 after the merge request is merged.

Add 'Closes #42' to the merge request description.

Add 'Related to #42' to the merge request description.

Add a comment on issue #42 saying the fix is in the merge request.

What is the purpose of associating an issue with a milestone in GitLab?

To assign the issue to a specific user

To categorize the issue by type

To automatically close the issue when the milestone is reached

To track progress toward a release or goal

A quality assurance team frequently files the same type of bug report. They want to standardize the information collected, including environment, steps to reproduce, and expected vs. actual behavior. What is the best way to achieve this in GitLab?

Create an issue template with predefined sections and use it when creating new issues.

Create a milestone for bug reports and assign all bug issues to it.

Create a label called 'Bug Report' and apply it to every new issue.

Create a new project for bug reports and use its issue tracker.

A support engineer notices that an issue's title is misleading and its description is outdated. The issue is assigned to a developer and has a 'Bug' label. What should the support engineer do to improve the issue's clarity without losing its history?

Add a comment with the correct information and leave the title and description unchanged.

Edit the title and description to reflect the current situation.

Change the label to 'Documentation' to indicate the issue needs updating.

Close the issue and create a new one with the correct title and description.

A team has a policy that every issue must have at least one assignee and a 'Needs Triage' label until it is reviewed. A new batch of 20 issues was just imported and none have assignees or labels. What is the most efficient way to apply the policy to all 20 issues?

Create a new milestone and assign all issues to it.

Use the issue board to drag each issue to a 'Needs Triage' list.

Edit each issue individually to assign a team member and apply the label.

Use bulk edit to assign a team member and apply the 'Needs Triage' label to all selected issues.

GitLabCertified Fundamentals Associate

Domain 3Objective 2

Manage Issues Through Their Lifecycle GITLAB-CERTIFIED-GIT-ASSOCIATE Practice Questions (Page 6)

Part of the Merge Requests and Issues domain, which makes up ~20% of our current practice bank.

41questions here

9free pages

15concepts

Questions 26–30

26application · medium
A developer is working on a merge request that fixes a bug described in issue #42. The developer wants the merge request to automatically close the issue when the merge request is merged. What should the developer do?
Select an answer first
27foundation · easy
What is the purpose of associating an issue with a milestone in GitLab?
Select an answer first
28application · medium
A quality assurance team frequently files the same type of bug report. They want to standardize the information collected, including environment, steps to reproduce, and expected vs. actual behavior. What is the best way to achieve this in GitLab?
Select an answer first
29application · medium
A support engineer notices that an issue's title is misleading and its description is outdated. The issue is assigned to a developer and has a 'Bug' label. What should the support engineer do to improve the issue's clarity without losing its history?
Select an answer first
30application · medium
A team has a policy that every issue must have at least one assignee and a 'Needs Triage' label until it is reviewed. A new batch of 20 issues was just imported and none have assignees or labels. What is the most efficient way to apply the policy to all 20 issues?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to GITLAB-CERTIFIED-GIT-ASSOCIATE

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by GitLab. “GITLAB-CERTIFIED-GIT-ASSOCIATE” is a trademark of its owner, used for identification only.