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

Questions 11–15

1. 11foundation · easy

   When creating a new milestone in GitLab, which three fields are available to define the milestone?

   • AName, owner, and start date
   • BTitle, labels, and weight
   • CName, description, and assignee
   • DTitle, description, and due date
   Reveal Solution Discussion Select an answer first
2. 12foundation · easy

   If a burndown chart shows a line that is consistently above the ideal trend line, what does this indicate?

   • AThe team has added scope to the sprint
   • BThe team is completing work faster than planned
   • CThe team is working on the wrong tasks
   • DThe team is behind schedule
   Reveal Solution Discussion Select an answer first
4. 13expert · hard

   A team is using a burndown chart for a sprint. The chart shows a flat line for the first three days, then a steep downward slope for the next two days. What is the most likely explanation?

   • AThe burndown chart is based on issue count, so it does not reflect actual effort.
   • BThe team was blocked at the start of the sprint and then resolved the blocker, completing work rapidly.
   • CThe team was working on a large issue that was closed on day five.
   • DThe team added new issues at the start, then closed them all at once.
   Reveal Solution Discussion Select an answer first
5. 14foundation · easy

   What is a common use of a burndown chart during a sprint?

   • ATo assign tasks to team members
   • BTo review code quality
   • CTo calculate team velocity for the next sprint
   • DTo monitor daily progress and identify if the team will finish on time
   Reveal Solution Discussion Select an answer first
6. 15expert · hard

   A project manager is using a burndown chart to monitor a sprint. The chart shows a sudden upward spike in remaining work on day 5. The team confirms they did not add any new issues. What is the most likely cause of the spike?

   • AThe team closed a merge request, which increased the remaining work.
   • BThe milestone due date was extended, causing the chart to reset.
   • CAn existing issue was reopened, increasing the remaining work count.
   • DThe burndown chart was recalculated with a different weight system.
   Reveal Solution Discussion Select an answer first