A project manager notices that the burndown chart for the current sprint shows a sudden increase in remaining work after several days of steady decline. What is the most likely cause?

The burndown chart is recalculated daily and always shows a spike mid-sprint.

The milestone due date was extended, causing the chart to reset.

New issues were added to the milestone during the sprint.

The team closed several issues at once, causing a spike.

A project manager is setting up a milestone for a new feature release. The team has a list of issues and merge requests that must be completed for the release. What is the correct sequence of actions?

Create the milestone, then assign the issues and merge requests to it.

Assign the issues and merge requests to a project, then create a milestone.

Create the issues and merge requests, then create a milestone and link them.

Create a burndown chart, then create a milestone and assign work.

A development team is using a milestone to track a two-week sprint. Midway through, they realize that several issues originally planned for the sprint are no longer needed, and a few new urgent issues have been added. What should the team do to keep the milestone progress accurate?

Update the milestone's due date to give the team more time, but keep the original issues.

Close the milestone and create a new one with the updated list of issues.

Remove the unneeded issues from the milestone and assign the new urgent issues to it.

Leave the milestone unchanged and create a new milestone for the new issues.

A team lead is creating a milestone for a product release. The release date is fixed, and the team needs to track progress against that date. Which milestone configuration is essential for this tracking?

Set a due date on the milestone.

Add a detailed description of the release goals.

Create a burndown chart for the milestone.

Assign the milestone to a specific project.

A team is using a milestone to track a sprint. The milestone progress page shows 80% of issues are completed, but the burndown chart shows that the remaining work line is still above the ideal line. What is the most likely explanation?

The remaining issues are large or high-effort, so the burndown chart reflects a higher remaining effort than the issue count suggests.

The milestone progress page is counting closed merge requests, not issues.

The burndown chart is showing data from a different milestone.

The team has closed issues but not merged the associated merge requests.

GitLabCertified Agile Portfolio Management Associate

Domain 5Objective 2

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

Part of the Team Velocity and Tracking domain, which makes up ~26% of our current practice bank.

22questions here

5free pages

5concepts

Questions 6–10

6application · medium
A project manager notices that the burndown chart for the current sprint shows a sudden increase in remaining work after several days of steady decline. What is the most likely cause?
Select an answer first
7application · medium
A project manager is setting up a milestone for a new feature release. The team has a list of issues and merge requests that must be completed for the release. What is the correct sequence of actions?
Select an answer first
8application · medium
A development team is using a milestone to track a two-week sprint. Midway through, they realize that several issues originally planned for the sprint are no longer needed, and a few new urgent issues have been added. What should the team do to keep the milestone progress accurate?
Select an answer first
9application · medium
A team lead is creating a milestone for a product release. The release date is fixed, and the team needs to track progress against that date. Which milestone configuration is essential for this tracking?
Select an answer first
10application · hard
A team is using a milestone to track a sprint. The milestone progress page shows 80% of issues are completed, but the burndown chart shows that the remaining work line is still above the ideal line. What is the most likely explanation?
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.