A project was created with a shared configuration.
Which two configurations were shared? (Choose two.
- A . component lead assignments
- B . versions
- C . transition screens
- D . project role membership
- E . project permissions
C, E
Explanation:
When a project is created with a shared configuration, it inherits the configurations of an existing project. This includes the workflow, issue types, screens, fields, permissions, notifications, and schemes associated with them. However, the component lead assignments and versions are specific to each project and are not shared. Therefore, the correct answer is C and E.
Reference: Creating a project, Configuring projects
You are a project administrator of DEV. Omar is a Jira administrator.
Identify two project settings that Omar can update in DEV but you cannot. (Choose two.)
- A . Notification scheme
- B . Project shortcuts
- C . Key
- D . Description
- E . Name
- F . Versions
A, C
Explanation:
As a project administrator of DEV, you can update some project settings such as project shortcuts, description, name, and versions. However, you cannot update the notification scheme or the key of the project, as these are global settings that require Jira administrator permissions. Therefore, the correct answer is A and C.
Reference: Managing project permissions, Managing project notifications, Changing the project key
A Jira administrator just created a new project based on the "Task management" project template.
Which Jira feature is enabled in this project by default?
- A . Epic issue type
- B . ranking of standard issue types
- C . Issue analysis reports
- D . Release Hub
B
Explanation:
The “Task management” project template is designed for managing simple tasks and tracking progress. By default, this template enables ranking of standard issue types, which allows you to order issues by priority on a board. The other features mentioned in the options are not enabled by default in this template. Therefore, the correct answer is B.
Reference: Creating a project, Ranking an issue
The team requests that you update the name of your project.
What impact will this have on Jira?
- A . The URL for issues will change.
- B . The project key will change.
- C . Issue filters may need to be updated.
- D . Issue search will not find issues from that project until Jira is re indexed.
C
Explanation:
Updating the name of your project will not affect the URL for issues, as they are based on the project key, not the name. The project key will also remain unchanged unless you explicitly change it. Issue search will still find issues from that project regardless of the name change. However, issue filters may need to be updated if they use the project name as a criterion. Therefore, the correct answer is C.
Reference: Editing a project’s details, Changing the project key, Searching for issues using filters
You are moving an epic between projects that share an issue type scheme.
Which issues are moved along with the epic5
- A . all standard issues in the epic
- B . all standard and sub-task issues in the epic
- C . only Story issues in the epic
- D . all sub-tasks of the epic itself
- E . all issues linked to the epic through issue links
A
Explanation:
When you move an epic between projects that share an issue type scheme, all standard issues in the epic are moved along with it. This means that any issue type that is not a sub-task or an epic will be moved to the new project. Sub-task issues in the epic will not be moved unless their parent issues are also in the epic. Story issues in the epic will be moved only if they are standard issue types, not sub-tasks. Issues linked to the epic through issue links will not be moved as they are not part of the epic hierarchy. Therefore, the correct answer is A.
Reference: Moving an issue, Working with epics
Which statement is definitely true about sub-tasks being used on a Scrurn board?
- A . Sub-task estimations are rolled up and displayed as the Original Estimate on the parent card.
- B . Sub-tasks can only be created by board administrators
- C . Sub-tasks can be displayed as cards in the Active sprints view.
- D . Sub-tasks can be displayed as cards in the Backlog view.
- E . Sub-tasks will automatically get resolved when the parent is moved to the Done column.
C
Explanation:
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]
A project uses several issue Types that have different workflows.
Sam can only see some of the issues on the project’s Kanban board but sees all of them in the issue search.
Identify a possible reason.
- A . board permissions
- B . column mapping
- C . issue-level security
- D . workflow conditions
B
Explanation:
A possible reason why Sam can only see some of the issues on the project’s Kanban board but sees all of them in the issue search is that the column mapping of the board does not include all the statuses of the different workflows used by the issue types. Column mapping determines which statuses are mapped to which columns on a board, and only issues with mapped statuses are displayed on the board. If an issue type has a workflow with a status that is not mapped to any column, then it will not appear on the board. Board permissions, issue-level security, and workflow conditions do not affect the visibility of issues on a board, as they apply to both the board and the issue search. Therefore, the correct answer is B.
Reference: [Configuring columns], [Configuring workflows]
Your team uses a custom field of type Labels to track keywords associated with incoming requests. Issues can have multiple keywords, and new keywords can be added at any time. They want to see keywords displayed prominently when viewing all cards on a board.
Which configuration meets this need?
- A . card layout
- B . swimlanes
- C . card colours
- D . issue detail view
A
Explanation:
The best configuration to meet the team’s need of displaying keywords prominently when viewing all cards on a board is card layout. Card layout allows you to customize what fields are shown on each card on a board, and you can choose to show any custom field of type Labels on the cards. Swimlanes are used to group issues into horizontal lanes based on certain criteria, such as assignee, priority, or query, but they do not show labels on each card. Card colours are used to highlight issues based on certain attributes, such as issue type, priority, or query, but they do not show labels on each card either. Issue detail view is used to show more information about an issue when you select it on a board, but it does not affect how cards are displayed on the board. Therefore, the correct answer is A.
Reference: [Configuring card layout], [Configuring swimlanes], [Configuring card colours], [Using boards]
Sam and Jo are product managers responsible for two separate products. Each product has its own Jira project and a corresponding Scrum board.
Management requests an integration between the products. Sam and Jo decide to create all the integration-related issues in Sams project and label them integration".
Jo updated his Scrum board’s saved filter to include the relevant integration issues from Sam’s project.
Which statement is definitely true?
- A . All integration issues always appear on top of Jo’s backlog.
- B . Changes to the rank of integration issues on Jo’s board are reflected on Sam’s board.
- C . Jo is unable to rank integration issues created by Sam.
- D . Sam is unable to transition integration issues that were ranked by Jo.
- E . Integration issues can only be ranked on Sam’s board.
B
Explanation:
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 team currently uses a single project to track both features and tasks.
They will be adopting aqile practices, as follows:
• Features will be developed during three week iterations.
• Tasks will be handled based on priority and rank and released incrementally as needed.
they want to use agile boards with minimal disruption to their current configuration.
Which solution will meet their requirements?
- A . a Kanban board in the current project with separate swimlanes per issue type
- B . two Scrum boards for the current project, one for each issue type
- C . a Scrum board in the current project with two quick fillers to show each issue type separately
- D . a second project for tasks with a shared configuration and separate boards per project
- E . a Kanban board for tasks and a Scrum board for features in the current project
E
Explanation:
The solution that will meet the team’s requirements of using agile boards with minimal disruption to their current configuration is to use a Kanban board for tasks and a Scrum board for features in the current project. This way, they can use different agile methodologies for different issue types without creating a new project or changing their existing configuration. They can use a Kanban board for tasks to handle them based on priority and rank and release them incrementally as needed. They can use a Scrum board for features to develop them during three week iterations with sprints and backlogs.
The other solutions are either not feasible or not optimal for their needs. Therefore, the correct answer is E.
Reference: [Creating a board], [Using a Scrum board], [Using a Kanban board]
Your team is using a Scrum board and has many issues planned for future sprints.
You need to configure a secondary board that:
• excludes those planned issues from the board but not from the reports
• hides issues in real time when users select multiple conditions
Which two board configurations satisfy the requirements? (Choose two.)
- A . swimlanes
- B . board sub-filter
- C . board filter
- D . column constraint
- E . quick filters
B, E
Explanation:
To exclude the planned issues from the board but not from the reports, you need to use a board sub-filter. A board sub-filter is an additional JQL query that is applied to the board filter to further refine the issues displayed on the board. The sub-filter does not affect the reports, which are based on the board filter only. To hide issues in real time when users select multiple conditions, you need to use quick filters. Quick filters are buttons that allow users to dynamically change the view of the board by applying one or more JQL queries. Users can select or deselect quick filters to show or hide issues that match the criteria.
Reference: Configuring filters, Configuring quick filters
Quang can transition issues from Resolved to Done using the workflow button on issues in his project. However, he cannot drag then from Resolved to Done on the project’s Kanban board Identify a possible reason why.
- A . Quang lacks a project permission.
- B . Quang is not a board administrator.
- C . The statuses are mapped to the same column.
- D . The board has a sub-filter configured
C
Explanation:
If Quang can transition issues from Resolved to Done using the workflow button on issues in his project, but cannot drag them from Resolved to Done on the project’s Kanban board, a possible reason is that the statuses are mapped to the same column. The columns on a Kanban board represent the stages of work in a project. Each column can have one or more statuses mapped to it. To move an issue from one column to another, you need to drag and drop it to a column that has a different status mapped to it. If the statuses are mapped to the same column, you cannot move the issue by dragging it on the board, but you can still use the workflow button to change its status.
Reference: Configuring columns, Moving an issue
The MR manager is unsure whether she wants a Scrum or Kanban board for her project. Identify one difference between the boards.
- A . Only Kanban boards support column constraints.
- B . Only Scrum boards support a card layout for backlog view.
- C . Only Kanban boards can display Days in column
- D . Only Scrum boards have a sub filter
- E . Only Scrum boards support selecting an estimation method.
E
Explanation:
One difference between Scrum and Kanban boards is that only Scrum boards support selecting an estimation method. Estimation is a way of measuring how much work is required to complete an issue or a sprint. Scrum boards allow you to choose between story points, original time estimate, or issue count as estimation methods. Kanban boards do not have estimation methods, as they focus on managing the flow of work rather than planning sprints.
Reference: Configuring estimation and tracking, Estimating an issue
An issue was created with the following attributes:
• Issue type: Story
• Priority: Blocker
• Labels: Tools, DevOps
• Reporter: A.Grant
An excerpt of the board’s swimlane configuration is shown.
In which swimlane will the issue appear?
- A . Change requests
- B . Expedite
- C . Internal stories
- D . Everything Else
- E . Stories
B
Explanation:
The issue will appear in the Expedite swimlane, because it matches the query priority = Blocker. Swimlanes are used to group issues on the board based on a common attribute, such as assignee, epic, or a custom query. The board’s swimlane configuration shows that the first swimlane is Expedite, which has the query priority = Blocker. This means that any issue with a blocker priority will be placed in this swimlane, regardless of its other attributes. The other swimlanes have different queries that do not match the issue’s attributes, such as type, labels, or reporter. Therefore, the issue will not appear in those swimlanes. The last swimlane is Everything Else, which is the default swimlane for any issue that does not match any of the previous queries. However, since the issue matches the Expedite query, it will not fall into this swimlane either. Hence, the correct answer is B.
Reference: [Configuring swimlanes], [Using swimlanes]
Your Scrum board has the following filter query:
project in (ENG. DEV) and type in (Bug. Task) ORDER BY Priority ASC
You have the necessary permissions but you are unable to drag an issue into a future sprint in the backlog.
- A . Identify the reason.
- B . The filter should be in DESC order.
- C . Stories are missing from the query.
- D . Ranking is disabled.
- E . The query should only have one project.
- F . The active sprint has not yet been completed.
D
Explanation:
The reason why you are unable to drag an issue into a future sprint in the backlog is that ranking is disabled. Ranking is a feature that allows you to order issues based on their relative priority or importance. Ranking is enabled by adding “ORDER BY Rank ASC” or “ORDER BY Rank DESC” to your board filter query. Ranking is required for Scrum boards, as it determines the order of issues in your backlog and sprints. If ranking is disabled, you cannot drag and drop issues in your backlog or plan future sprints.
Reference: Ranking an issue, Configuring filters
You are viewing a board that displays stories across multiple projects. You want to see a grouping of stories without epics.
Which swimlane selection will achieve this?
- A . Query: epic is EMPTY
- B . Stories
- C . Query: Type = Epic
- D . Projects
- E . Epics
A
Explanation:
Swimlanes are a way of grouping issues on a board based on certain criteria, such as assignee, priority, query, or epics. If you want to see a grouping of stories without epics, you can use a query swimlane with the condition epic is EMPTY, which will show only issues that are not part of any epic. The other options will either show epics or not group stories at all. Therefore, the correct answer is A.
Reference: [Configuring swimlanes], [Advanced searching – fields reference]
You want to remove some epics from your personal Scrum board, without impacting any other boards. Identify the correct solution.
- A . Exclude them via a quick filter.
- B . Mark them as Done via the Epics panel
- C . Exclude them via the board filter
- D . Exclude them via the board sub filter.
- E . Transition them into an unmapped status.
You manage a Scrum project with two development teams.
Issues are associated with each team using a custom field called Jean.
Parallel sprints have been disabled.
Which setup will provide each team with an individual Burndown Chart?
- A . a single Scrum board with quick filters
- B . a single Scrum board using the Team field as the Estimation Statistic
- C . two Scrum boards using the Team field as the Estimation Statistic
- D . two Scrum boards using the Team field in their board filters
D
Explanation:
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]
You have all the necessary permissions to transition issues on your board. There are no conditions or validators. One column has two statuses mapped to it You want to drag an issue into that column.
Which statement is true?
- A . You cannot drop it into either status.
- B . You can drop it only into the bottom status.
- C . You can drop it only into the top status.
- D . You can drop it into either pop-up window.
- E . You can drop it into either status
The ‘’Open issues filter of your project shows bugs, along with epics and stones.
You then view the project’s Scrum board where you only see epics and stories but not bugs.
Which configuration is responsible for this behavior?
- A . board filter query
- B . issue type scheme
- C . board filter shares
- D . swim lanes
- E . board sub-filter
Your team works in a project that uses only one workflow, a simplified workflow.
The configuration of the corresponding Kanban board is shown:
Which statement is definitely true?
- A . Bugs can be dragged from "In Progress" to "In Test" on this board.
- B . All team members can transition issues from Backlog to In Test.
- C . Issues can be transitioned freely between all workflow statuses
- D . A resolution will be set once an issue is dragged to Done
A
Explanation:
The statement that is definitely true is that bugs can be dragged from “In Progress” to “In Test” on this board. This is because the board configuration shown in the image has two columns: “In Progress” and “Done”. The “In Progress” column has three statuses mapped to it: “To Do”, “In Progress”, and “In Test”. The “Done” column has one status mapped to it: “Done”. Therefore, issues can be moved from one status to another within the same column by dragging them on the board. However, issues cannot be moved from one column to another by dragging them on the board, as this would require a workflow transition that is not available in a simplified workflow. A simplified workflow is a default workflow that allows any user with the Edit Issues permission to add or remove statuses on the fly. To move an issue from one column to another, you need to use the workflow button on the issue detail view and select a transition that matches the status of the destination column.
Reference: Configuring columns, Using a simplified workflow
Your team uses Story Points for estimation and tracking.
You performed several actions in the active sprint.
Which two actions are reflected as scope change? (Choose two.)
- A . Added a fix version on a committed story.
- B . Estimated a story in the backlog.
- C . Dragged on estimated story from the backlog to the sprint.
- D . Modified the estimate value on a committed story.
- E . Added another 5ub-task to a committed story.
- F . Logged work on several committed stories.
C, D
Explanation:
The two actions that are reflected as scope change are dragging an estimated story from the backlog to the sprint and modifying the estimate value on a committed story. Scope change is a measure of how much work was added or removed from a sprint after it started. It is calculated by comparing the total story points committed at the start of the sprint and the total story points completed at the end of the sprint. If you add or remove issues from a sprint, or change their estimates, you are changing the scope of the sprint. The other actions mentioned in the question do not affect the scope of the sprint, as they do not change the amount of work planned or done in the sprint.
Reference: Viewing the Velocity Chart, Scope change
You want to create a new Scrum board with the following requirements:
• Show all issue types from project BERT but do not show sub-tasks in the backlog
• Show only epics from project ERNIE
• Do not show issues from any other projects
Which board filler query meets these requirements?
- A . project in (BERT, ERNIE) AND type in (standardlssueTypesG, Epic)
- B . project in (BERT. ERNIE) AND issuetype – Epic AND type not in subTasklssueTypesO
- C . (project = BERT AND type not in subTasklssueTypesO) OR (project = ERNIE AND issuetype Epic)
- D . project = BERT OR (project – ERNIE AND type = Epic)
- E . (project – BERT AND type in standardlssueTypes(J) OR (project – ERNIE AND issuetype -Epic)
C
Explanation:
The board filter query that meets these requirements is (project = BERT AND type not in subTasklssueTypesO) OR (project = ERNIE AND issuetype Epic). This query will show all issue types from project BERT except sub-tasks, as well as only epics from project ERNIE. It will not show issues from any other projects, as it uses the OR operator to combine two conditions that specify the project names. The other queries do not meet all the requirements, as they either include sub-tasks from project BERT, exclude epics from project ERNIE, or show issues from other projects.
Reference: Configuring filters, Advanced searching – fields reference
Some issues in your project have labels and others do not.
Some tasks in your project are identified by a distinct label: daily_business. You need to prevent these issues from being displayed on the team’s Scrum board.
Which solution meets this requirement?
- A . • Create a quick filter
• Add: NOT labels="daily_business_ - B . • Update the board sub-filter
• Add; AND NOT labels = daily business - C . • Update the board filter
• Add: AND labels NOT IN (daily.business, EMPTY: - D . • Update the board filter
• Add: AND (labels != daily, business OR labels IS EMF
D
Explanation:
The solution that meets this requirement is to update the board filter and add: AND (labels != daily.business OR labels IS EMPTY). This will exclude issues that have the label daily_business from the board filter, which determines which issues are displayed on the board. It will also include issues that have no labels at all, as some issues in your project may not have labels. The other solutions do not meet this requirement, as they either do not exclude issues with daily_business label, or exclude issues with no labels.
Reference: Configuring filters, Advanced searching – operators reference
You are reviewing the Velocity Chart for your team and notice that they completed more story points than they committed in their last sprint. You are definitely the only person who can add issues to sprints in your project.
How did your learn complete more story points than they committed?
- A . The sprint was completed early.
- B . An epic with a story point estimate was completed during the sprint.
- C . Someone increased the story point value on an issue mid-sprint.
- D . A sub-task was in an unmapped status at the start of the sprint.
- E . A new sub-task was created drying the sprint
C
Explanation:
The reason why your team completed more story points than they committed in their last sprint is that someone increased the story point value on an issue mid-sprint. This will increase the total story points completed at the end of the sprint, but not affect the total story points committed at the start of the sprint. Therefore, it will result in a positive scope change. The other reasons mentioned in the question do not explain why your team completed more story points than they committed, as they either do not affect story points at all, or affect both committed and completed story points equally.
Reference: Viewing the Velocity Chart, Scope change