ExamGecko
Home / Atlassian / ACP-610 / List of questions
Ask Question

Atlassian ACP-610 Practice Test - Questions Answers, Page 2

List of questions

Question 11

Report
Export
Collapse

Your team often accepts new requests from outside groups during an active sprint. You want to see if such frequent scope change mid-sprint is causing bottlenecks. Which report provides the needed insight?

Control Chart
Control Chart
Burndown Chart
Burndown Chart
Average Age Chart
Average Age Chart
Velocity Chart
Velocity Chart
Cumulative Flow Diagram
Cumulative Flow Diagram
Suggested answer: E

Explanation:

The Cumulative Flow Diagram is the report that provides the needed insight to see if frequent scope change mid-sprint is causing bottlenecks. The Cumulative Flow Diagram shows the quantity and distribution of work items along different stages of a process over time. The report can help identify potential bottlenecks in the 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 ''In Progress'' stage, it may indicate that the team is overloaded with work or facing some blockers. If the team often accepts new requests from outside groups during an active sprint, the report can show how this affects the flow of work and the completion of the sprint goal.Reference:Managing Jira Projects Data Center and Server: Certification Bundle,Cumulative Flow Diagram

Atlassian ACP-610 image Question 11 explanation 18213 09162024190126000000

asked 16/09/2024
Bright Ngobeni
40 questions

Question 12

Report
Export
Collapse

You need to find all issues that were not competed in some past sprint, and that are now part of an active sprint. Identify two functions that you need to use in your JQL query. (Choose two.)

closedSprints()
closedSprints()
futures prints()
futures prints()
completed()
completed()
remaming()
remaming()
openSprints()
openSprints()
Suggested answer: A, E

Explanation:

The two functions that are needed to use in the JQL query to find all issues that were not completed in some past sprint, and that are now part of an active sprint are closedSprints() and openSprints(). The closedSprints() function returns all issues that are assigned to a completed sprint. The openSprints() function returns all issues that are assigned to an incomplete sprint. By combining these two functions with the NOT operator, we can filter out the issues that belong to both a completed sprint and an incomplete sprint, and only get the issues that were not completed in some past sprint, and that are now part of an active sprint. For example, the JQL query could be:

project = XYZ AND issuekey NOT IN (closedSprints() AND openSprints())

This query will return all issues in project XYZ that are not in both a closed sprint and an open sprint, meaning they are either in a closed sprint only or an open sprint only. Since we are looking for issues that are now part of an active sprint, we can assume they are in an open sprint only.Reference:Advanced search reference - JQL functions,Modifying closedSprints() to return previous two Sprints,JQL - Explanation of what closedSprints() does

asked 16/09/2024
RYAN UBANA
39 questions

Question 13

Report
Export
Collapse

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?

project in (BERT, ERNIE) AND type in (standardlssueTypesG, Epic)
project in (BERT, ERNIE) AND type in (standardlssueTypesG, Epic)
project in (BERT. ERNIE) AND issuetype - Epic AND type not in subTasklssueTypesO
project in (BERT. ERNIE) AND issuetype - Epic AND type not in subTasklssueTypesO
(project = BERT AND type not in subTasklssueTypesO) OR (project = ERNIE AND issuetype Epic)
(project = BERT AND type not in subTasklssueTypesO) OR (project = ERNIE AND issuetype Epic)
project = BERT OR (project - ERNIE AND type = Epic)
project = BERT OR (project - ERNIE AND type = Epic)
(project - BERT AND type in standardlssueTypes(J) OR (project - ERNIE AND issuetype -Epic)
(project - BERT AND type in standardlssueTypes(J) OR (project - ERNIE AND issuetype -Epic)
Suggested answer: 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

asked 16/09/2024
Jason Siemens
36 questions

Question 14

Report
Export
Collapse

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?

* Create a quick filter * Add: NOT labels='daily_business_
* Create a quick filter * Add: NOT labels='daily_business_
* Update the board sub-filter * Add; AND NOT labels = daily business
* Update the board sub-filter * Add; AND NOT labels = daily business
* Update the board filter * Add: AND labels NOT IN (daily.business, EMPTY:
* Update the board filter * Add: AND labels NOT IN (daily.business, EMPTY:
* Update the board filter * Add: AND (labels != daily, business OR labels IS EMF
* Update the board filter * Add: AND (labels != daily, business OR labels IS EMF
Suggested answer: 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

asked 16/09/2024
John Ordonez
30 questions

Question 15

Report
Export
Collapse

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?

The sprint was completed early.
The sprint was completed early.
An epic with a story point estimate was completed during the sprint.
An epic with a story point estimate was completed during the sprint.
Someone increased the story point value on an issue mid-sprint.
Someone increased the story point value on an issue mid-sprint.
A sub-task was in an unmapped status at the start of the sprint.
A sub-task was in an unmapped status at the start of the sprint.
A new sub-task was created drying the sprint
A new sub-task was created drying the sprint
Suggested answer: 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

asked 16/09/2024
James Morris
35 questions

Question 16

Report
Export
Collapse

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?

Scrum backlog
Scrum backlog
Kanban board
Kanban board
Kanban backlog
Kanban backlog
Active sprints
Active sprints
Suggested answer: B

Explanation:

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]

asked 16/09/2024
lakshmi potla
30 questions

Question 17

Report
Export
Collapse

The release manager is requesting a list of all issues included in a particular sprint. Which report will provide this information?

Control Chart
Control Chart
Release Burndown
Release Burndown
Version Report
Version Report
Sprint Report
Sprint Report
Average Age Report
Average Age Report
Suggested answer: D

Explanation:

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.Reference:Managing Jira Projects Data Center and Server: Certification Bundle, [Sprint Report | Jira Software Cloud]

asked 16/09/2024
doaa elshazly
47 questions

Question 18

Report
Export
Collapse

Your team failed to meet their last sprint commitment and you want to investigate further. You need an agile report that:

* shows you a list of the incomplete issues in the sprint

* allows you to quickly view that list in the Issue Navigator

Which report meets this need?

Burndown Chart
Burndown Chart
Control Chart
Control Chart
Cumulative Flow Diagram
Cumulative Flow Diagram
Sprint Report
Sprint Report
Velocity Chart
Velocity Chart
Suggested answer: D

Explanation:

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]

asked 16/09/2024
test testsers
39 questions

Question 19

Report
Export
Collapse

Analyze the Epic Report shown.

Atlassian ACP-610 image Question 19 18221 09162024190126000000

Identify why the epic completion date is hard to predict.

Most stories aren't estimated until the end of the epic
Most stories aren't estimated until the end of the epic
The configured Working Days for the board are unrealistic.
The configured Working Days for the board are unrealistic.
The team is using issue count for their estimation statistic.
The team is using issue count for their estimation statistic.
The team adds new stories throughout the epic.
The team adds new stories throughout the epic.
Suggested answer: D

Explanation:

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

asked 16/09/2024
Junwei Li
41 questions

Question 20

Report
Export
Collapse

A project was created with a shared configuration. Which two configurations were shared? (Choose two.

component lead assignments
component lead assignments
versions
versions
transition screens
transition screens
project role membership
project role membership
project permissions
project permissions
Suggested answer: 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

asked 16/09/2024
Andre Passos
35 questions
Total 75 questions
Go to page: of 8
Search

Related questions