A team member wants to report a bug they found in the login feature. The team uses an agile planning tool for all their work. What is the most appropriate way for the team member to capture this bug?

Add a comment to an existing issue about the login feature, even if it is not related to the bug.

Send an email to the team lead describing the bug and ask them to create an issue.

Create a new issue with a clear title, a detailed description of the bug, and steps to reproduce it.

Create a new branch in the version control system and name it 'bug-login'.

A team uses a Kanban board and is reviewing their cumulative flow diagram (CFD). They notice that the distance between the 'In Progress' and 'Done' lines is widening over time. What is the most likely cause of this trend?

The WIP limit on the 'In Progress' column is too low, preventing the team from starting new work.

The team is completing work faster than new work is being added to the board.

Work is spending an increasing amount of time in the 'In Progress' column, indicating a bottleneck.

The team is not adding new work to the board, so the 'In Progress' line is flat.

What does a burndown chart primarily show?

The total amount of work completed over time

The amount of work remaining over time in a sprint

The velocity of the team across multiple sprints

The number of bugs found during a sprint

A support team uses a Kanban board to manage incoming tickets. They notice that the 'In Progress' column frequently has more than ten items, and team members are context-switching constantly, leading to delays. The team wants to improve their workflow. What is the most effective first step?

Create a new issue for each context switch to track the time lost, so the team can report on it in the next retrospective.

Increase the number of team members assigned to the 'In Progress' column to handle the higher volume of work.

Add more columns to the board to break down the 'In Progress' stage into smaller, more detailed steps.

Set a work-in-progress (WIP) limit on the 'In Progress' column and enforce it by having team members finish existing tasks before pulling new ones.

In GitLab, how can you link a merge request to an issue?

By including the issue number in the merge request description or using the 'Closes #123' syntax

By creating a new branch with the issue number in the name

By adding a comment to the issue with the merge request number

By assigning the issue to the merge request author

GitLabCertified Fundamentals Associate

Domain 6Objective 1

Apply Agile Planning Tools Across the Software Development Lifecycle GITLAB-CERTIFIED-GIT-ASSOCIATE Practice Questions (Page 2)

Part of the Agile Planning Tools domain, which makes up ~14% of our current practice bank.

32questions here

7free pages

10concepts

Questions 6–10

6application · medium
A team member wants to report a bug they found in the login feature. The team uses an agile planning tool for all their work. What is the most appropriate way for the team member to capture this bug?
Select an answer first
7expert · hard
A team uses a Kanban board and is reviewing their cumulative flow diagram (CFD). They notice that the distance between the 'In Progress' and 'Done' lines is widening over time. What is the most likely cause of this trend?
Select an answer first
8foundation · easy
What does a burndown chart primarily show?
Select an answer first
9application · medium
A support team uses a Kanban board to manage incoming tickets. They notice that the 'In Progress' column frequently has more than ten items, and team members are context-switching constantly, leading to delays. The team wants to improve their workflow. What is the most effective first step?
Select an answer first
10foundation · easy
In GitLab, how can you link a merge request to an issue?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to GITLAB-CERTIFIED-GIT-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-GIT-ASSOCIATE” is a trademark of its owner, used for identification only.