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

Questions 1–5

1. 1application · medium

   A product team uses a single GitLab project for both internal tooling and customer-facing features. They want to distinguish 'bug' reports from 'feature' requests on the issue board, and they also want to see only customer-reported issues in a separate filtered view. The team lead creates a 'bug' label and a 'feature' label. What is the most efficient way to achieve the filtered view for customer-reported issues?

   • ACreate a 'customer-reported' label, apply it along with the 'bug' or 'feature' label to relevant issues, and filter the board by the 'customer-reported' label.
   • BUse the issue search bar to search for 'customer' in the title of each issue.
   • CApply only the 'customer-reported' label and remove the 'bug' or 'feature' label from those issues.
   • DCreate a separate project for customer-reported issues and move all such issues there.
   Reveal Solution Discussion Select an answer first
2. 2application · medium

   A user with the 'Guest' role in a project wants to apply a 'bug' label to an issue they are viewing. What is the most likely outcome?

   • AThey will be able to apply the label, but the change will be pending approval from a maintainer.
   • BThey will be able to apply the label, as 'Guest' is the minimum role required to apply labels.
   • CThey will be able to apply the label, but only if they are also a member of the group.
   • DThey will not be able to apply the label because they lack the required permission.
   Reveal Solution Discussion Select an answer first
4. 3application · medium

   A development manager wants to understand how the team's workload has shifted over the last quarter. They have been diligently labeling issues with 'bug', 'feature', and 'maintenance' labels. They want to see a visual breakdown of how many issues were created with each label over time. What should the manager use?

   • AA custom report generated from the API by manually counting issues.
   • BThe repository analytics page.
   • CThe issue board with a filter for each label.
   • DThe label analytics page for the project or group.
   Reveal Solution Discussion Select an answer first
5. 4application · medium

   A support team manages a high volume of issues. They want to prioritize their work by first addressing issues labeled 'Critical', then 'High', and finally 'Medium'. They currently use a standard issue board. What is the most effective way to set up their board to reflect this priority order?

   • ACreate three separate boards, one for each priority label.
   • BFilter the board by each label one at a time and manually reorder the issues.
   • CUse the issue list view and sort by the label name alphabetically.
   • DCreate a priority label list on the board with the labels ordered as 'Critical', 'High', 'Medium'.
   Reveal Solution Discussion Select an answer first
6. 5foundation · easy

   Which of the following actions is an example of using labels to track an issue's lifecycle stage?

   • AChanging the issue's assignee from one developer to another
   • BAdding the 'In Review' label to an issue after its code is submitted for review
   • CIncreasing the issue's weight from 3 to 5
   • DAdding a comment that says 'This issue is now in review'
   Reveal Solution Discussion Select an answer first