A software team is setting up a board for their sprint workflow. Their process is: 'To Do' → 'In Development' → 'In Review' → 'Done'. They have created the lists but notice that the board displays them in alphabetical order: 'Done', 'In Development', 'In Review', 'To Do'. This makes it hard to follow the flow of work. What should the team do to fix this?

Drag the lists on the board so they appear in the order: 'To Do', 'In Development', 'In Review', 'Done'.

Delete all lists and recreate them in the desired order.

Change the board's sort setting to 'Manual' in the board configuration.

Rename the lists with numeric prefixes, such as '1. To Do', '2. In Development', etc.

A team's board has lists 'To Do', 'In Progress', 'Done'. They want to automate the following: when an issue is moved to 'Done', it should be automatically closed. Which automation rule should they configure?

Trigger: 'Issue closed'; Action: 'Move issue to list: Done'.

Trigger: 'Issue assigned'; Action: 'Close issue'.

Trigger: 'Issue created'; Action: 'Move issue to list: Done'.

Trigger: 'Issue moved to Done'; Action: 'Close issue'.

A team's board has lists: 'New', 'In Progress', 'Done'. They want to rename 'New' to 'Backlog' to better match their terminology. What is the correct way to do this?

Edit the list name 'New' and change it to 'Backlog'.

Change the board's title to 'Backlog'.

Create a new list 'Backlog' and move all issues from 'New' to it, then delete 'New'.

Delete the 'New' list and create a new list 'Backlog'.

Which of the following is a valid way to create a new board list in GitLab?

From the issue tracker, drag an issue to a new column that appears automatically

From the group settings, import a list from a CSV file

From the project settings, click 'Add list' and enter a custom list name

From the board view, select 'Create list' and choose a label or assignee to base the list on

A team's board has lists 'To Do', 'Doing', 'Review', 'Done'. They have an automation rule that moves an issue to 'Review' when it is assigned. They now want to add a rule that moves an issue to 'Done' when it is closed. They are concerned about conflicts. What is the best way to handle this?

Create the new rule, but only apply it to issues in the 'Review' list.

Delete the existing rule and create a new rule that handles both assignment and closing.

Add the new rule with trigger 'Issue closed' and action 'Move issue to list: Done'. Both rules can coexist because they have different triggers.

Modify the existing rule to also move the issue to 'Done' when it is closed.

GitLabCertified Agile Portfolio Management Associate

Domain 3Objective 2

Set up Board Lists and Workflows GITLAB-CERTIFIED-AGILE-PROJECT-MANAGEMENT-ASSOCIATE Practice Questions (Page 3)

Part of the Visual Workflows with Boards domain, which makes up ~18% of our current practice bank.

16questions here

4free pages

4concepts

Questions 11–15

11application · medium
A software team is setting up a board for their sprint workflow. Their process is: 'To Do' → 'In Development' → 'In Review' → 'Done'. They have created the lists but notice that the board displays them in alphabetical order: 'Done', 'In Development', 'In Review', 'To Do'. This makes it hard to follow the flow of work. What should the team do to fix this?
Select an answer first
12application · medium
A team's board has lists 'To Do', 'In Progress', 'Done'. They want to automate the following: when an issue is moved to 'Done', it should be automatically closed. Which automation rule should they configure?
Select an answer first
13application · medium
A team's board has lists: 'New', 'In Progress', 'Done'. They want to rename 'New' to 'Backlog' to better match their terminology. What is the correct way to do this?
Select an answer first
14foundation · easy
Which of the following is a valid way to create a new board list in GitLab?
Select an answer first
15expert · medium
A team's board has lists 'To Do', 'Doing', 'Review', 'Done'. They have an automation rule that moves an issue to 'Review' when it is assigned. They now want to add a rule that moves an issue to 'Done' when it is closed. They are concerned about conflicts. What is the best way to handle this?
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.