A group owner wants to standardize the labels used across all projects in their group. They want to create a set of common labels like 'bug', 'feature', and 'documentation' that are available in every project. What is the most efficient way to do this?

Create the labels in each project individually.

Ask each project maintainer to create the labels in their own project.

Create the labels in one project and then export and import them to other projects.

Create the labels at the group level.

What type of insight can you gain from GitLab's label analytics?

The list of users who have applied a specific label to issues

The exact commit history of issues with a specific label

The total number of comments made on issues with a specific label

The average time issues spend with a specific label before being closed

Which of the following is a common use of labels in GitLab issue lifecycle management?

Marking an issue as 'Bug' to indicate its type

Defining the exact due date and time for an issue

Replacing the need for milestones in tracking releases

Storing the full conversation history of an issue

A project manager is reviewing the label analytics for their project. They notice that the chart for the 'bug' label shows a sharp increase in 'issues created' but a flat line for 'issues closed'. They want to understand if this is a recent trend or a long-term problem. What is the most appropriate next step?

Change the time range on the label analytics chart to a longer period, such as the last 12 months.

Export the list of 'bug' issues to a spreadsheet for manual analysis.

Check the issue board to see the current number of open 'bug' issues.

Immediately assign more developers to fix bugs.

Who can delete a project label in GitLab?

Only the user who created the label

Any user with the Reporter role

Only users with the Maintainer role or higher

GitLabCertified Agile Portfolio Management Associate

Domain 2Objective 1

Manage Issue Lifecycles with Labels GITLAB-CERTIFIED-AGILE-PROJECT-MANAGEMENT-ASSOCIATE Practice Questions (Page 4)

Part of the Issue Lifecycle Management domain, which makes up ~22% of our current practice bank.

23questions here

5free pages

7concepts

Questions 16–20

16application · medium
A group owner wants to standardize the labels used across all projects in their group. They want to create a set of common labels like 'bug', 'feature', and 'documentation' that are available in every project. What is the most efficient way to do this?
Select an answer first
17foundation · easy
What type of insight can you gain from GitLab's label analytics?
Select an answer first
18foundation · easy
Which of the following is a common use of labels in GitLab issue lifecycle management?
Select an answer first
19expert · hard
A project manager is reviewing the label analytics for their project. They notice that the chart for the 'bug' label shows a sharp increase in 'issues created' but a flat line for 'issues closed'. They want to understand if this is a recent trend or a long-term problem. What is the most appropriate next step?
Select an answer first
20foundation · easy
Who can delete a project label in GitLab?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to GITLAB-CERTIFIED-AGILE-PROJECT-MANAGEMENT-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-AGILE-PROJECT-MANAGEMENT-ASSOCIATE” is a trademark of its owner, used for identification only.