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

Questions 21–23

1. 21foundation · easy

   In GitLab, what is the primary purpose of labels in issue lifecycle management?

   • ATo categorize and track issues by attributes such as status, priority, or team
   • BTo store confidential information about an issue that only maintainers can view
   • CTo permanently lock an issue so it cannot be edited or closed
   • DTo automatically assign issues to specific users based on their workload
   Reveal Solution Discussion Select an answer first
2. 22expert · hard

   A group has a set of group-level labels. A project maintainer wants to change the color of one of these group-level labels to better match their project's theme. What is the most accurate statement about their ability to do this?

   • AThe project maintainer can edit the group-level label, and the change will be applied to all projects in the group.
   • BThe project maintainer cannot edit the group-level label because they do not have the required permission at the group level.
   • CThe project maintainer can edit the group-level label, but the change will only affect the label within their project.
   • DThe project maintainer can create a new project-level label with the same name and a different color to override the group-level label.
   Reveal Solution Discussion Select an answer first
3. 23application · medium

   A team is using a Kanban-style board to manage their work. They have a 'To Do' list and a 'Doing' list. They want to visually indicate on the board which issues are blocked and need attention. What is the most effective way to achieve this?

   • AMove the blocked issues to a separate list called 'Blocked'.
   • BChange the color of the issue card manually.
   • CAdd a comment to the issue saying 'blocked'.
   • DCreate a 'blocked' label and apply it to the relevant issues.
   Reveal Solution Discussion Select an answer first