What is the primary purpose of issue dependencies in GitLab?

To group issues into a milestone for release planning

To automatically assign issues to team members based on workload

To define a relationship where one issue must be completed before another can proceed

To link issues to a specific Git branch for version control

A team had Issue #55 'blocking' Issue #56. During a sprint review, the team realizes that #56 can proceed independently and the dependency is no longer valid. The team wants to remove the relationship without deleting either issue. What is the correct action?

Reassign Issue #56 to a different assignee

Edit Issue #55 and remove the 'blocks' link to #56

Change the milestone of Issue #56

A developer is reviewing the board and sees that Issue #501 has an icon indicating it is blocked. The developer wants to know which issue is blocking #501. Where should the developer look?

Open Issue #501 and check the linked issues section

A team is using GitLab to manage a data migration. The data cleansing (Issue #401) must be completed before the data import (Issue #402). The team has already created a dependency where #401 blocks #402. After a review, they decide that the import can start with a subset of clean data, so the dependency is no longer strict. What should the team do?

Reverse the dependency so #402 blocks #401

Remove the dependency between #401 and #402

Add a comment to #402 explaining the change

What is the correct way to change an existing dependency from 'blocks' to 'is blocked by' in GitLab?

Edit the relationship type in the 'Linked issues' section of the sidebar

Create a new issue and link it with the opposite relationship

Change the issue's due date to reflect the new dependency

Use the issue board to swap the order of the two issues

GitLabCertified Agile Portfolio Management Associate

Domain 2Objective 2

Configure Issue Dependencies GITLAB-CERTIFIED-AGILE-PROJECT-MANAGEMENT-ASSOCIATE Practice Questions (Page 1)

Part of the Issue Lifecycle Management domain, which makes up ~22% of our current practice bank.

19questions here

4free pages

4concepts

Questions 1–5

1foundation · easy
What is the primary purpose of issue dependencies in GitLab?
Select an answer first
2application · easy
A team had Issue #55 'blocking' Issue #56. During a sprint review, the team realizes that #56 can proceed independently and the dependency is no longer valid. The team wants to remove the relationship without deleting either issue. What is the correct action?
Select an answer first
3application · easy
A developer is reviewing the board and sees that Issue #501 has an icon indicating it is blocked. The developer wants to know which issue is blocking #501. Where should the developer look?
Select an answer first
4application · medium
A team is using GitLab to manage a data migration. The data cleansing (Issue #401) must be completed before the data import (Issue #402). The team has already created a dependency where #401 blocks #402. After a review, they decide that the import can start with a subset of clean data, so the dependency is no longer strict. What should the team do?
Select an answer first
5foundation · easy
What is the correct way to change an existing dependency from 'blocks' to 'is blocked by' in GitLab?
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.