Correct Answer: BC

Two project roles that must be granted to view code commits in the DEV project are:

Developers

Administrators

According to the image you sent, the View Development Tools permission determines which users can see development information from tools such as Bitbucket, GitHub, FishEye, and Crucible. This permission is granted to the Project role

(Developers) and the Project role (Administrators) in the DEV permission scheme. Therefore, users who are assigned to these roles will be able to view code commits in the DEV project.

The other options are not correct because:

Users do not have the View Development Tools permission in the DEV permission scheme, so they cannot see code commits in the DEV project. Sprinters do not have the View Development Tools permission in the DEV permission scheme,

so they cannot see code commits in the DEV project. Managers do not have the View Development Tools permission in the DEV permission scheme, so they cannot see code commits in the DEV project.

Correct Answer: C

The Cumulative Flow Diagram is the report that provides the information that the head of customer service wants. The Cumulative Flow Diagram is a tool that visualizes the quantity and distribution of work items along different stages of a process. The report shows how many work items are in each stage at any given time, and how they flow from one stage to another. The report can help identify potential bottlenecks in the support workflow by showing where work items accumulate or stagnate over time. For example, if the report shows a sudden increase or a wide band of work items in the "Waiting for Customer" stage, it may indicate that the customers are not responding quickly enough or that the support team is not following up effectively. The report can also help monitor the overall progress and performance of the support teams by showing the total number of work items created, resolved, and remaining over time. References: Managing Jira Projects Data Center and Server: Certification Bundle, Cumulative Flow Diagram

Correct Answer: E

The Velocity Chart is the best report to compare work committed and work completed in sprints over time. It shows the average amount of work that a team can complete in a sprint, based on the historical data of previous sprints. It also

shows how much work was planned and how much was actually completed in each sprint. By looking at the Velocity Chart, a team can see if they are overestimating or underestimating their capacity, and adjust their planning accordingly.

Therefore, option E is correct. References: Velocity Chart, Managing Jira Projects Data Center and Server:

Certification Bundle

Correct Answer: C

This JQL query is always correct because it uses the duedate field, which is a date picker that stores a date value without a time component, and the startOfDay() function, which returns the start of the current day (i.e., midnight). This query will return all issues that have a due date before today and are assigned to either Adam or Eve. The other queries are either incorrect or unreliable because they use different fields or functions that may not work as expected. For example, the due field is a date time picker that stores both a date and a time value, and the currentLogin() function returns the date and time of the current user's last login, which may vary depending on the user and their timezone. References: : https:// support.atlassian.com/jira-software- cloud/docs/advanced-search-reference-jql-fields/#Advancedsearchingfieldsreference- DuedateDuedate https://support.atlassian.com/jira-software-cloud/docs/advanced-search- reference-jql-functions/ #Advancedsearchingfunctionsreference-startOfDaystartOfDay

Correct Answer: D

A Sprint Report is the best report to provide a list of all issues included in a particular sprint. A Sprint Report shows the scope, status, and completion date of each sprint. It also displays a breakdown of the completed, incomplete, and added issues in the sprint. The release manager can easily view the list of incomplete issues in the Issue Navigator by clicking on the View in Issue Navigator link at the bottom of the report. A Sprint Report also helps to track the team's performance and identify any scope changes during the sprint. References: Managing Jira Projects Data Center and Server: Certification Bundle, [Sprint Report | Jira Software Cloud]

Correct Answer: BE

A project screen is a screen that is used to display or edit issue fields in a project. A project administrator can modify his project screen if it meets the following prerequisites: The screen is not shared with other projects or issue types. The screen does not use the default system fields. The screen scheme and the issue type screen scheme are not shared with other projects or issue types. If these conditions are met, the project administrator can perform the following actions on his project screen: Create a new tab Rename a tab Remove a tab Add an existing field Remove a field Reorder fields The project administrator cannot create a new field, set a default value for a field, or make a field required. These actions require Jira administration permissions. References: : https://support.atlassian.com/jira-software- cloud/ docs/configure-field-layouts-in-the-issue-view/ https://support.atlassian.com/jira-software-cloud/docs/what-are-issue-fields/

Correct Answer: C

Jon needs Move Issues and Create Issues permissions to move an issue from project A to project B. Move Issues permission allows him to initiate the move operation, while Create Issues permission allows him to create the issue in the destination project. Transition Issues permission is not relevant for moving issues, as it only affects workflow transitions. Administer Projects permission is not required for moving issues, unless the issue type or workflow needs to be changed during the move. Assign Issues permission is not required for moving issues, unless the assignee needs to be changed during the move. References: [Moving an issue], [Managing Jira Projects Data Center and Server: Certification Bundle]

Correct Answer: B

Based on the report shown, which is a Velocity Chart, the only statement that is definitely true about the team's performance is that they sometimes commit more work than they can complete in an iteration. This can be seen by comparing the green bars (completed work) and the gray bars (estimated work) in each sprint. For example, in Sprint 4, the team committed 10 story points but only completed 8 story points. The other statements are not necessarily true based on the report alone. For example, the team may be estimating their work accurately, but facing other challenges or impediments that prevent them from completing their work on time. Or, the team may not be committing unestimated work to an iteration, but rather re-estimating some issues during the sprint. Or, scope change may not be affecting the team's ability to complete work on time, but rather reflecting changes in priorities or requirements. Or, the team may be using sprint duration consistently, but varying the amount of work they commit to each sprint based on their capacity or velocity. For more information on how to interpret and use the Velocity Chart, see Velocity Chart. References: Velocity Chart

Correct Answer: E

Correct Answer: BE

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. References: Configuring filters, Configuring quick filters