Atlassian ACP-610 Managing Jira Projects for Data Center and Server Online Training
Atlassian ACP-610 Online Training
The questions for ACP-610 were last updated at Nov 22,2024.
- Exam Code: ACP-610
- Exam Name: Managing Jira Projects for Data Center and Server
- Certification Provider: Atlassian
- Latest update: Nov 22,2024
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
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.
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)
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
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