Atlassian ACP-610 Exam Questions Instant Access

Question 1

Analyze the component configuration of a project as shown.

Dave creates an issue and wants to use the auto-assignment feature of Jir

a. Which statement is definitely correct?

AIf UX is selected, the issue will be assigned to admin.

BIf Login and Signoff are selected, the issue will be assigned to Project admin.

CIf Signoff is selected, the issue will be assigned to Project admin.

DIf Test is selected, the issue will be assigned to Project lead.

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.

Question 2

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.)

AAdded a fix version on a committed story.

BEstimated a story in the backlog.

CDragged on estimated story from the backlog to the sprint.

DModified the estimate value on a committed story.

EAdded another 5ub-task to a committed story.

FLogged work on several committed stories.

Answer : C, D

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

Question 3

Gen prioritizes and triages support requests as soon as they come in. She now wants to use drag-and-drop to:

* quickly assign and transition them to in Progress

* instantly associate them with Epics

Which board view will meet these requirements?

AScrum backlog

BKanban board

CKanban backlog

DActive sprints

Answer : B

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]

Question 4

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.

AIdentify the reason.

BThe filter should be in DESC order.

CStories are missing from the query.

DRanking is disabled.

EThe query should only have one project.

EThe active sprint has not yet been completed.

Answer : D

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

Question 5

Analyze the Epic Report shown.

Identify why the epic completion date is hard to predict.

AMost stories aren't estimated until the end of the epic

BThe configured Working Days for the board are unrealistic.

CThe team is using issue count for their estimation statistic.

DThe team adds new stories throughout the epic.

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

Question 6

You need to assign team members to view code commits in the DEV project. An excerpt of the DEV permission scheme is shown.

Which two project roles must they be granted? (Choose two.)

AUsers

BAdministrators

CDevelopers

DSprinters

EManagers

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.

Question 7

Your company recently created an internal IT project to track hardware requests. View the project configuration below: Project: Hardware request Project lead: Allen Frank Default Assignee: Project lead

To test the triaging process you create the first issue in the project and select the Macbook 13" component. You don t update the assignee field and leave it to the default value of Automatic.

Based on the current configuration, which value will the assignee field show after creating the test issue?

AAllen Frank

BMac Taylor

CAutomatic

DLouise Lin

EUnaligned

Answer : B

Based on the current configuration, the assignee field will show Mac Taylor after creating the test issue. This is because the Macbook 13' component has Mac Taylor as the component lead and the component/s field has been configured to override the project's default assignee when using a certain component.Therefore, when creating an issue with the Macbook 13' component, the assignee field will automatically be set to Mac Taylor, regardless of the default assignee of the project or the value of the assignee field before creating the issue34Reference:

3: What are components? | Jira Software Cloud | Atlassian Support

4: How to enable and edit component/s , affects Version/s and fix version ...

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