Test Online Free Atlassian ACP-620 Exam Questions and Answers
Practice a live sample before buying full access. This page keeps the free ACP-620 question set organized by page so visitors and search engines can reach the canonical -questions.html URL directly.
Nash can view all issues but he is unable to rank the backlog in the Jira Software board.
Which permissions does Nash need to request to get the proper access? (Choose two.)
Answer: Explanation:
Since Nash can view the issues in the Jira project, he does not need to request the Browse Projects permission anymore.
To rank issues in the backlog section, Nash needs to have both the schedule and edit issues permission. Ranking backlog here means changing the issue's Due Date. You need both permissions to change the issues' Due Date.
Schedule issues grant the ability to view or edit an issue's due date.
Edit issues grant the ability to edit issues.
Manage sprints, Move Issues, and View Development Tools are not required.
View Development Tools to grant users in a software project to view development-related information on the issue, such as commits, reviews, and build information.
Question 2Selectable Answer
Razi has added and enabled the automation below. After Razi creates an issue, which of the following are true about the assignee of that issue? (Choose two.)
(Assume this automation is using the default priority, and all of the required permissions and labels exist.)
Questions and Answers PDF 12/40
Answer: Explanation:
An issue that matches the first rule will be assigned to Razi since Razi is the user that triggers the action.
The action here refers to creating the issue.
labels = Java OR priority > Medium will return any issues with a Java label or any issues that have high or highest priority. Therefore, issues with the highest priority will always match the first rule and ignore the second rule. Nina will not be the assignee.
Question 3Selectable Answer
Which of the following are true about the roadmap? (Choose four.)
Answer: Explanation:
Users can create new epics, new issues, and new comments from the roadmap dashboard.
Users can filter issues based on:
- Issue summary
- Assignee
- Status category
- Versions
- Label
- Issue type
Reference:
- Customize Your View on the Roadmap
- Create Epics on the Roadmap
If the below image is not visible, right-click the below image then click 'Open image in new tab'.
Question 4Selectable Answer
As a scrum master, Sarah needs access to manage a sprint and rank an issue.
According to this table, how many roles need to be assigned to Sarah?
Answer: Explanation:
To rank an issue, the user needs Schedule and Edit Issues permission. The role 'editors' is required.
To view an issue, the user needs Browse Projects permission. The role 'users' is required.
To manage sprints, the user needs Manage Sprints permission. The role 'leads' is required.
Therefore, Sarah needs 3 roles.
Administer Projects permission allows users to administer a project in Jira, which includes managing versions and components. Sarah does not need this permission.
Reference:
- Rank an issue
- Project permissions
Question 5Selectable Answer
Based on the below diagram, which statements are true? (Choose three.)
Answer: Explanation:
On July 21st, there are:
- 5 issues in 'To Do'
- 5 issues in 'In Progress'
- 5 issues in 'Done'
- 10 issues in 'Done'
Reference: View and understand the cumulative flow diagram
Question 6Selectable Answer
Which of the following are the best scenarios to use Components more than Custom Field? (Choose two.)
Answer: Explanation:
Components:
Users should use components when they want to auto-assign an issue to a specific user. An issue can have more than one component. Project administrators have the proper access to manage the project component. Since components only belong to a Jira project, users cannot share the component globally with other Jira projects.
Custom fields:
Users should use custom fields if they want the field to be used globally. The custom field has a few field types that can only accept a single value. Jira administrators have global permission to manage the custom field.
Question 7Selectable Answer
Sarah's team has 10 completed issues in the current active sprint.
As a Jira administrator, what is the minimum permission Sarah needs to complete the sprint?
Answer: Explanation:
To complete a sprint, users must be a Jira Administrator. Non-administrator users need Manage Sprints permission to manage the sprint. Since the user is a Jira administrator, Manage Sprints permission is not required.
Browse Projects is the required permission to view the issues.
Move Issues permission is for moving issues to another project, which is not required in managing the sprint. Transition Issues grants users the ability to transition issues' status, which is not required in managing the sprint.
When completing a sprint, users need Edit and Schedule Issues permission if there are incomplete issues. The incomplete issues need to be moved to the backlog or to the next sprint. If all issues are completed, these two permissions are not required.
Reference:
- Complete a sprint
- Project permissions
- Permissions for company-managed projects
Without the Manage Sprints permission. (Non-admin)
Without the Edit Issues permission if there are incomplete issues.
Without the Schedule Issues permission if there are incomplete issues.
Question 8Selectable Answer
contain one or more rules defined by users. If automation will not execute the tasks. do not match with the rules,
Answer: Explanation:
Users can specify conditions that must be met for their rule to continue running. For example, their rule will only escalate an issue if it is a high priority.
If a condition fails, no actions following it will be performed. The exception is with the If/else block condition.
Not all rules need to have conditions. Conditions can be placed anywhere in the rule chain.
Automation rules are made up of three parts:
- Triggers (When)
- Conditions (If/Else-if/Else)
- Actions (Then)
Reference:
- What are automation rules?
- Automation conditions
Question 9Selectable Answer
Sarah is working on a financial project that involves sensitive information which should not be openly available to any users. She wants to create a new team-managed project for her assignment.
Suggest the best access level for Sarah's project.
Note:
- Company-managed projects are formerly known as classic projects.
- Team-managed projects are formerly known as next-gen projects.
Answer: Explanation:
Since Sarah's project contains sensitive information, she should use private level access for her project. By using this access level, Sarah can control who can have access to manage issues in her project.
These are the three access levels in team-managed Jira projects:
Open - Anyone with access to the site can search, view, create, or edit this project's issues.
Limited - Anyone with access to the site can search, view, and comment on this project's issues. Only people added to the project can create and edit its issues.
Private - Only admins and people added to the project can search, view, create, or edit its issues.
Question 10Selectable Answer
Razi works on multiple Jira projects. Although he can confirm the status properly mapped to the board column, he claims that a few issues are still missing from the Scrum board.
Which of the following are the possible root causes? (Choose three.)
Answer: Explanation:
View Development Tools permission is not related with hidden issues. This permission allows users to view the development panel, which displays information from Bitbucket, GitHub, Fisheye, Crucible, and Bamboo.
Board Sub-Filter only exists in the Kanban Board. This user is using a Scrum board.
These are the possible reasons why issues would be missing from the Jira board:
- The JQL from Board Filter or Sub-Filter excludes some issues.
- Users selected Quick Filter that filtered out some of the issues.
- Users do not have the Browse Projects permission to view the issues.
- Some issues have Issue Level Security.
- Some issues are mapped to the Unmapped Statuses column.
Question 11Selectable Answer
Which of the following are true about a Jira project? (Choose two.)
Note:
- Company-managed projects are formerly known as classic projects.
- Team-managed projects are formerly known as next-gen projects.
Answer: Explanation:
Company-managed project:
By default, these groups below have the 'Administer Jira' global permission.
- System-administrators
- Atlassian-addons-admin
- Site-admins
- Administrators
- Jira-administrators
Users in these groups can create and administer projects, issue types, fields, workflows, and schemes for all company-managed Jira projects. They can also perform most administration tasks, except: managing users, importing data, and editing system email settings.
'Create Projects' permission does not exist in Jira.
Team-managed project:
All licensed users can create a team-managed Jira project, even non-admins. If you are a Jira admin and you want to restrict this, you'll need to remove the 'Create team-managed projects' permission.
Reference: Get started with team-managed projects
Question 12Selectable Answer
Jira automation helps users to automate repetitive manual works and focus more on the team's productivity.
Which of the following are true about Jira automation? (Choose three.)
Answer: Explanation:
One automation can be applied globally. Users can control this using Scope. Scope will determine which projects will apply this automation and can only be edited from the global administration settings.
Scope has 4 options:
- A single project.
- A selection of multiple projects.
- All projects in your Jira instance.
- All projects of a specified project type, e.g. all Software projects. You can create your own automation to trigger other automations. By default, the actor field is the 'Automation for Jira' user.
The automation owner has the option to disable the notification using the 'Notify on error' option.
Reference: Edit the details of the rule
Question 13Selectable Answer
shows the actual and estimated amount of work to be done in a sprint. The horizontal x-axis indicates time, and the vertical y-axis indicates cards (issues).
Answer: Explanation:
A Burndown Chart shows the actual and estimated amount of work to be done in a sprint. The horizontal x-axis in a Burndown Chart indicates time, and the vertical y-axis indicates cards (issues).
You should use a Burndown Chart to track the total work remaining, and to project the likelihood of achieving the sprint's goal. By tracking the remaining work throughout the iteration, a team can manage its progress, and respond to trends accordingly. For example, if the Burndown Chart shows that the team is unlikely to reach the sprint goal, then the team can take the necessary actions to stay on track.
Reference: View and understand the burndown chart
Question 14Selectable Answer
Which of the following is true about Quick Filters?
Answer: Explanation:
Quick Filters will add a new JQL to the existing main JQL filters of your Kanban or Scrum board.
Only My Issues and Recently Updated are the default filters, and both can be edited.
Jira administrator, project administrator, and board administrator can manage the Jira board.
Reference: Configure Quick Filters
Question 15Selectable Answer
Which of the following are false about the roadmap? (Choose three.)
Answer: Explanation:
View Settings is a collection of settings that allow users to adjust their personal view of the roadmap. The settings only apply to individual users. Users can change their view at any time.
Schedule Bars for child issues are currently available for scrum teams only.
Epic Display Options allow users to use the dropdown to select which epics to display. The current options are All, Incomplete, or Complete.
Users can adjust the color of an epic directly on the roadmap. Simply right-click the epic and choose a fresh color.
The epic bar has a default duration according to how users view their timeline. The default durations are weeks, months, or quarters.
