The statement that is definitely true is that changes to the rank of integration issues on Jo’s board are

reflected on Sam’s board. This is because ranking is a global attribute that affects how issues are

ordered across projects and boards based on their relative priority. When Jo updates his Scrum

board’s saved filter to include integration issues from Sam’s project, he can rank them along with his

own issues on his board. These changes will also affect how these issues are ranked on Sam’s board,

as they share the same rank field value. The other statements are not necessarily true or false, as

they depend on other factors such as permissions, workflow configurations, or board settings.

Therefore, the correct answer is B. Reference: [Ranking an issue], [Configuring filters]

A Sprint Report is also the best report to meet this need. As explained above, a Sprint Report shows a

list of the incomplete issues in the sprint and allows you to quickly view that list in the Issue

Navigator. A Sprint Report can help you investigate why your team failed to meet their last sprint

commitment by showing you how many issues were added or removed during the sprint, how many

issues were completed or not completed, and how much work was carried over to the next

sprint. Reference: Managing Jira Projects Data Center and Server: Certification Bundle, [Sprint Report

| Jira Software Cloud]

A Kanban board is the best option for Gen to prioritize and triage support requests using drag-and- drop. A Kanban board allows Gen to quickly assign issues to herself or other team members by dragging them to the appropriate column. She can also transition issues to In Progress by moving them across the workflow. Additionally, she can instantly associate issues with Epics by dragging them to the Epic panel on the right side of the board. A Kanban board also provides a visual overview of the current status and progress of the support requests. Reference: Managing Jira Projects Data Center and Server: Certification Bundle, Configuring projects | Administering Jira applications Data Center and …, [Working with issues | Jira Software Cloud]

Sub-tasks are a type of issue that can be used to break down a parent issue into smaller and more

manageable pieces. Sub-tasks can be displayed as cards in the Active sprints view of a Scrum board,

which allows you to track their progress and status. However, sub-task estimations are not rolled up

and displayed on the parent card, as they use a different field than the parent issue. Sub-tasks can be

created by anyone who has the Create Issue permission in the project, not only by board

administrators. Sub-tasks cannot be displayed as cards in the Backlog view, as they are only visible

under their parent issues. Sub-tasks will not automatically get resolved when the parent is moved to

the Done column, as they have their own workflow transitions and conditions. Therefore, the correct

answer is C. Reference: [Working with sub-tasks], [Configuring columns]

If you manage a Scrum project with two development teams and want to provide each team with an

individual Burndown Chart, you can create two Scrum boards using the Team field in their board

filters. A Burndown Chart is a report that shows the amount of work remaining in a sprint, based on

the issues that are included in the board filter. By using the Team field in the board filter, you can

ensure that each board only shows the issues that belong to a specific team, and thus generate a

separate Burndown Chart for each team. The other options will either show a combined Burndown

Chart for both teams or not use the Team field at all. Therefore, the correct answer is D. Reference:

[Creating a board], [Configuring filters], [Viewing the Burndown Chart]