Use Milestones and Burndown Charts GITLAB-CERTIFIED-AGILE-PROJECT-MANAGEMENT-ASSOCIATE Practice Questions (Page 4)

Questions 16–20

1. 16foundation · easy

   In GitLab, how do you associate an issue with a milestone?

   • ABy setting the milestone field on the issue
   • BBy creating a label with the same name as the milestone
   • CBy linking the issue in the milestone description
   • DBy adding the milestone name to the issue title
   Reveal Solution Discussion Select an answer first
2. 17application · medium

   A project manager is reviewing the milestone progress page and sees that the percentage of completed issues is 60%, but the burndown chart shows a flat line for the last three days. What does this combination most likely indicate?

   • AThe milestone is on track because 60% of the work is already complete.
   • BThe burndown chart is broken because it should always show a downward slope.
   • CThe milestone has too many issues assigned, causing the chart to be inaccurate.
   • DThe team is not completing work at the expected rate, and the burndown chart is not showing any recent progress.
   Reveal Solution Discussion Select an answer first
4. 18foundation · easy

   Which of the following is a required field when creating a milestone in GitLab?

   • ADue date
   • BAssignee
   • CDescription
   • DTitle
   Reveal Solution Discussion Select an answer first
5. 19application · medium

   A project manager is using a burndown chart to monitor a sprint. The chart shows that the remaining work line is consistently below the ideal line. What does this indicate about the team's velocity?

   • AThe team is completing work faster than planned.
   • BThe burndown chart is inaccurate because the line cannot be below the ideal line.
   • CThe team is behind schedule because they have less work remaining.
   • DThe team is exactly on track because the line is below the ideal.
   Reveal Solution Discussion Select an answer first
6. 20expert · hard

   A team is using a milestone to track a sprint. The burndown chart shows that the remaining work line is consistently above the ideal line, but the team reports they are working at full capacity. What is the most likely explanation?

   • AThe team is not closing issues because they are waiting for code review.
   • BThe burndown chart is showing the total number of issues, not the remaining work.
   • CThe milestone has too many issues assigned, causing the chart to be inaccurate.
   • DThe team underestimated the effort required for the issues, so the burndown chart is not reflecting the actual workload.
   Reveal Solution Discussion Select an answer first