Your company-managed kanban project has a total of six statuses in the workflows. Which statement
about the kanban board is true?
C
Explanation:
In a company-managed Kanban project, the board can have multiple In Progress statuses from
different workflows mapped to the same column. This allows teams to visually group similar types of
work even if the statuses come from different issue types or workflows. It provides flexibility without
requiring one column per status.
5 development teams need to work across 3 projects and plan their iterations in a single board.
Which board supports this?
D
Explanation:
A company-managed Scrum board can be configured to pull issues from multiple projects, enabling
cross-team planning and coordination. This makes it ideal for multiple development teams working
across several projects and planning their iterations in a single board.
You are the project administrator of two Scrum projects, MOBI and TIS.
Team members find it difficult to switch between both projects to work on separate sprints.
They need the ability to work on issues from both projects in a single sprint.
Identify two ways that you can satisfy this requirement. (Choose two.)
C, E
Explanation:
Create a new Scrum board that includes both MOBI and TIS issues: This allows the teams to plan and
manage sprints using a single board that pulls issues from both projects.
Change the TIS project board filter to include issues from MOBI project: Modifying the board filter to
include issues from both projects enables the board to support a shared sprint across MOBI and TIS.
Marcella can see TIS issues but not the TIS project board.
Identify the reason why.
A
Explanation:
If Marcella can see TIS issues but not the TIS project board, it's likely because the board filter is not
shared with her. Boards in Jira are based on filters, and if the filter isn’t shared with a user, the board
won’t be visible to them - even if they have access to the project and issues.
You shared a URL to the dashboard with Bobby but when he looks at it, the gadgets return errors that
state, "The filter configured for this gadget could not be retrieved."
What is the most likely problem with the filters?
C
Explanation:
The error "The filter configured for this gadget could not be retrieved" typically means that the filters
used in the dashboard gadgets are not shared with Bobby. Even if Bobby has access to the projects or
issues, he cannot see the results unless the filters themselves are explicitly shared with him.
Teams using Project A and B currently use their own respective Scrum boards.
They must now work together on the same products and issues and in the same sprints.
You created a new Scrum board based on this filter:
project in (A,B) ORDER BY Rank ASC
You must also check two settings to make sure the teams can access and use the new board.
Identify the two settings. (Choose two.)
E, F
Explanation:
Sharing on the board filter: The board filter must be shared with all users who need access to the
board; otherwise, they won't be able to view or use it.
Project permissions: Users must have the necessary permissions (such as Browse Projects and
Manage Sprints) on both Project A and Project B to view issues and manage sprints on the new
shared board.
Your team needs a new board that:
● only shows issues that are actively in progress
● allows a separate area to prioritize incoming work
● allows them to release issues from the Done column
Identify the correct solution to meet these requirements
E
Explanation:
A Kanban board with the backlog enabled meets all the requirements: it shows only in-progress
issues (via column configuration), provides a separate area to prioritize incoming work (the Kanban
backlog), and allows for releasing issues from the Done column (via version management or Kanban
releases).
A team needs a board that meets these requirements:
● All issues can be moved across the entire workflow on a single view of the board.
● Issues can be worked in a continuous flow without start and stop dates.
Which board configuration meets the requirements?
A
Explanation:
A Kanban board without backlog displays all issues on a single view and supports a continuous
workflow without start and stop dates. This setup is ideal for teams using a continuous delivery
process, allowing issues to move freely across the entire workflow.
Newly created issues start in the to Do column of your Kanban board. The column has grown too full.
Additionally, the team is unable to focus on the prioritized issues they should be working on.
Which configuration change will help alleviate both problems?
A
DEV is a company-managed Kanban project with many statuses.
Users should never see issues in Cancelled or Rejected status when viewing their project board.
You want to remove the issues from the board but still have them counted in project reports.
Identify the approach that satisfies this requirement.
B
Explanation:
Adding a board sub-filter to exclude the Cancelled and Rejected statuses removes those issues from
the board view while still including them in project-level reports. This approach hides them from the
board without deleting or modifying workflow data.
Your team switched to using story points for estimation in the last 2 months and their sprints are
2 weeks long.
Which chart can definitely help you determine the average effort that the team can deliver during
each sprint?
A
Explanation:
The Velocity Chart shows the amount of story points completed in each sprint, allowing you to
determine the average effort the team can deliver. It's specifically designed to track estimation units
like story points across completed sprints.
The team requests that you configure their Kanban board in such a way that they can:
● see just particular subsets of issues based on values in a radio button field
● see all issues grouped by the epic they belong to
● distinguish cards visually based on their priority
Select three board configurations that when combined together, will satisfy these requirements.
(Choose three.)
A, C, E
Explanation:
Card colors by priority: Visually distinguishes issue cards on the board based on their priority.
Swimlanes by epic: Groups all issues under their respective epics, helping the team see work
organized by feature or theme.
Quick filters based on radio button field: Allows team members to filter and view specific subsets of
issues depending on the selected radio button field value.
You manage two team-managed Scrum projects.
You want to create a single board that displays the progress of the active sprints in both projects and
their burndown.
Identify the correct board type to use.
C
Explanation:
A company-managed Scrum board can pull issues from multiple team-managed projects, allowing
you to view and track the progress of active sprints and display a combined burndown. Team-
managed boards are limited to a single project, so a company-managed board is required for cross-
project visibility.
You want to configure a Kanban board so that issues disappear from the Done column as soon as
they are dragged into it. But you need to see Done issues in reports.
How can you achieve this behavior?
E
Explanation:
Modifying the board sub-filter allows you to exclude Done issues from the board view after they are
moved to that status, while still keeping them in Jira and visible in reports. This way, they disappear
from the board immediately but remain part of historical and reporting data.
You are the project administrator for a team based in the Middle East.
You need to change the Standard Working Days configuration on the board: from Sunday to Thursday
instead of Monday to Friday.
What will be affected by this change?
E
Explanation:
Changing the Standard Working Days affects the Burndown Chart, as this chart relies on working days
to plot the ideal and actual burn of work during a sprint. Adjusting working days ensures the
burndown chart accurately reflects the team's actual schedule.