Atlassian ACP-610 Managing Jira Projects for Data Center and Server Certification Exam Practice Test

Answer : C

The component configuration of the project shows that each component has a different default assignee. The default assignee is the user who will be automatically assigned to an issue when that component is selected.

The image shows that the default assignee for the Signoff component is Project admin. Therefore, if Dave creates an issue and selects Signoff as the component, the issue will be assigned to Project admin.

The other options are not correct because:

If UX is selected, the issue will not be assigned to admin, but to Unassigned. The image shows that the default assignee for the UX component is Unassigned, which means that no user will be automatically assigned to an issue with that component.

If Login and Signoff are selected, the issue will not be assigned to Project admin, but to Project lead. The image shows that the default assignee for multiple components is Project lead, which means that if more than one component is selected, the issue will be assigned to Project lead.

If Test is selected, the issue will not be assigned to Project lead, but to Unassigned. The image shows that the default assignee for the Test component is Unassigned, which means that no user will be automatically assigned to an issue with that component.

Answer : A

The team can use the Release link to remove issues as needed from the Done column. This will create a version in the project that contains all the issues that were removed, and the team can use the version report to see the details of each clean-up. Excluding issues in Done status from the board filter or via a sub-filter will not remove them from the Done column, but only hide them from view. Excluding issues where Resolution != EMPTY from the board filter will also hide issues from other columns that have a resolution set, which is not desired.Reference:[Releasing a version], [Managing Jira Projects Data Center and Server: Certification Bundle]

Answer : B, C

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.

Answer : D

The only field that can definitely be set by all project team members is Labels. Labels are a system field that can be edited by any user who has the Edit Issues permission in the project, regardless of the screen configuration. The other fields may or may not be editable by the project team members, depending on how they are configured in the screen scheme, field configuration scheme, and permission scheme of the project. For example, Attachment requires both the Edit Issues permission and the Create Attachments permission, Assignee requires both the Edit Issues permission and the Assignable User permission, Fix Version/s requires both the Edit Issues permission and the Resolve Issues permission, and Issue Type requires both the Edit Issues permission and a compatible issue type scheme. For more information on how to configure fields in Jira, seeConfiguring fields and screens.Reference:Configuring fields and screens

Answer : A

An epic burndown chart shows the progress towards completing an epic over time. It is useful for tracking how much work is left to be done and predicting when it will be completed. The epic burndown chart is based on the estimation statistic that is configured for the board (either story points or issue count) and shows the total amount of work remaining in the epic at the end of each sprint. You can use this chart to estimate how many additional sprints will be needed to complete an epic.Reference:: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-epic-burndown-chart/

Answer : D

The epic completion date is hard to predict because the team adds new stories throughout the epic. This means that the scope of the epic is not fixed and can change over time. The Epic Report shows the progress of an epic by comparing the estimated amount of work to the completed work. The report also shows a projected completion date based on the team's average velocity. However, if the team keeps adding new stories to the epic, the estimated amount of work will increase and the projected completion date will be pushed further. This makes it difficult to plan and deliver the epic within a certain timeframe.Reference:Managing Jira Projects Data Center and Server: Certification Bundle, Epic Report

Answer : D

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]