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

Questions 1–5

1. 1foundation · easy

   A team no longer uses the 'QA Testing' stage and wants to remove it from their board. What is the correct way to do this in GitLab?

   • AArchive the list to hide it from the board
   • BRename the list to 'QA Testing' and leave it empty
   • CDelete the list from the board settings
   • DChange the list's label to 'None' to make it disappear
   Reveal Solution Discussion Select an answer first
2. 2foundation · easy

   What is the purpose of automation rules on a GitLab board?

   • ATo automatically delete issues that have been in a list for too long
   • BTo automatically move issues between lists based on defined triggers or actions
   • CTo automatically create new lists when the board becomes too crowded
   • DTo automatically assign issues to the first available team member
   Reveal Solution Discussion Select an answer first
4. 3expert · medium

   A team's board has lists 'Backlog', 'Ready', 'Doing', 'Done'. They want to rename 'Ready' to 'Ready for Review' and also want to ensure that the order of the lists remains 'Backlog', 'Ready for Review', 'Doing', 'Done'. What is the correct approach?

   • ADelete the 'Ready' list and create a new list 'Ready for Review' in the same position.
   • BRename the list and then recreate the board to ensure the order is correct.
   • CRename the list and then drag it to the correct position if it moves.
   • DRename the list 'Ready' to 'Ready for Review'. The list will stay in its current position in the board's list order.
   Reveal Solution Discussion Select an answer first
5. 4foundation · easy

   In a GitLab board, what is the primary purpose of a board list?

   • ATo filter issues by assignee so each team member sees their own work
   • BTo store a backlog of issues that are not yet assigned to any milestone
   • CTo represent a workflow stage, such as To Do, Doing, or Done, and group issues that belong to that stage
   • DTo define the labels that can be applied to issues in the project
   Reveal Solution Discussion Select an answer first
6. 5application · medium

   A small startup's board currently has lists: 'Backlog', 'In Progress', 'Blocked', 'Done'. They realize that 'Blocked' is not a separate stage but a state that an 'In Progress' item can be in. They want to simplify the board to reflect only true workflow stages. What is the best approach?

   • ARemove the 'Blocked' list and use a 'blocked' label on issues in the 'In Progress' list to indicate the state.
   • BMerge 'Blocked' and 'Done' into a single list called 'Finished'.
   • CKeep the 'Blocked' list and add a 'Blocked' label to issues in it.
   • DRename 'Blocked' to 'Waiting' and keep it as a stage.
   Reveal Solution Discussion Select an answer first