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.
Dom has added and enabled the below automation.
Which of the following issues will trigger this automation? (Choose two.)
(Assume this automation is using the default actor and default priority)
Answer: Explanation:
Issues have to match both rules to trigger the action:
- Issues must be higher than a medium priority; High or Highest.
- Issues must be reported by Razi or Nick.
The creator of the issue is not necessarily the same person as the reporter of the issue.
Reference: Create and edit rules
Question 17Selectable Answer
Razi is the Jira administrator for the WINDOWS Jira project. He received a new request to create a new Jira project called LINUX, and both projects need to have the same configurations.
Razi created the LINUX Jira project using the shared configuration option to ensure both projects have the same configurations.
Assuming the WINDOWS project is already configured with all of the below configurations, which configurations does Razi have to update in the LINUX project manually? (Choose three.)
Answer: Explanation:
Jira will not copy the below configurations if users created a project using the shared configuration option.
These configurations are associated with a single Jira project and cannot be shared across other projects:
- Components
- Version
- Project role members
- Project avatar
- Project description
- Project URL (From Details page)
Question 18Selectable Answer
Nash is using Kanban boards for his development projects. There are too many issues in the 'Done' column in one of the boards. He only wants to see completed issues for the current week.
Which of the following is the best feature that he should use to achieve this?
Answer: Explanation:
Although Nash can achieve this by using the JQL filter, Kanban boards have a feature to hide completed issues older than certain weeks. Hide Completed Issues will allow users to hide completed issues older than 1 week, 2 weeks, or 4 weeks. (exists in Kanban boards only)
JQL search results from the Board Filter will apply to Jira boards and reports.
JQL search results from the Board Sub-Filter will apply to Jira boards only. (exists in Kanban board only)
Swimlanes is a row on the board that can be used to group issues. There are a few types of Swimlanes; Queries, Stories, Assignees, Epics, Projects, or None. If you choose None, no swimlanes will be displayed.
Quick Filters allow users to enable/disable multiple filters with a single click from their Jira board view. If users selected multiple filters, only issues that match selected filters will be displayed. For example, if users selected 'Java Component' and 'High Priority', the result will be issues that have critical issues with Java components only. Quick Filters JQL will not overwrite JQL in your Board Filter. Jira will apply the JQL on top of your existing JQL Board Filter.
Question 19Selectable Answer
Sarah needs to create a bar graph to show to her team on how long issues have been opened before they are able to resolve them.
Which report does Sarah need to create?
Answer: Explanation:
Resolution Time Report contains graph bars and a table showing the length of time taken to resolve a set of issues for a project/filter. This helps users identify trends and incidents which they can investigate further. If the below image is not visible, right-click the below image then click 'Open image in new tab'.
Single Level Group By Report shows a table of issues grouped by a particular field (including custom fields) for a filter. This helps users group search results by a field and see the overall status of each group. Average Age Report contains graph bars and a table showing the average number of days that issues were unresolved in a day over the past certain days.
Pie Chart Report shows a pie chart of issues for a project/filter grouped by a specified field. This helps users see the breakdown of a set of issues at a glance.
Time Tracking Report shows the original and current time estimates for issues in the current project. This can help users determine whether work is on track for those issues.
Time Since Issues Report allows users to choose a date field and project/filter, then maps the issues against the date that the field was set. This can help users track how many issues were created, updated, etc, over a period of time.
Question 20Selectable Answer
Atlassian only allows certain users to create Jira automation.
Which users can create Jira automation? (Choose two.)
Answer: Explanation:
Only these 2 users have access to create Jira automation:
Jira administrators - All Jira projects.
Project administrators - Project that the admin has access to.
Question 21Selectable Answer
Which of the following are true about issue types? (Choose three.)
Answer: Explanation:
Only Jira administrators can create a new issue type. The order of the issue type can be changed in the Issue Type Scheme. 'None' is one of the options as the default issue type.
Reference: Add, edit, and delete an issue type
Question 22Selectable Answer
Nick found that there are too many unresolved issues in his team's backlog.
Suggest a report that can help Nick generate a graphical report and a table of the total and average age of the unresolved issues.
Answer: Explanation:
Average Age Report contains graph bars and a table showing the average number of days that issues were unresolved in a day over the past certain days.
If the below image is not visible, right-click the below image then click 'Open image in new tab'.
Resolution Time Report contains graph bars and a table showing the length of time taken to resolve a set of issues for a project/filter. This helps users identify trends and incidents which they can investigate further.
Single Level Group By Report shows a table of issues grouped by a particular field (including custom fields) for a filter. This helps users group search results by a field and see the overall status of each group.
Pie Chart Report shows a pie chart of issues for a project/filter grouped by a specified field. This helps users see the breakdown of a set of issues at a glance.
Time Tracking Report shows the original and current time estimates for issues in the current project. This can help users determine whether work is on track for those issues.
Time Since Issues Report allows users to choose a date field and project/filter, then maps the issues against the date that the field was set. This can help users track how many issues were created, updated, etc, over a period of time.
Question 23Selectable Answer
Users created a new custom field called 'Position' that has two values:
- Manager
- Non-Manager.
They need a graphical report to group issues from Manager and Non-Manager, and then apply a saved filter.
Which report can they use to generate the relevant information?
Answer: Explanation:
Pie Chart Report shows a pie chart of issues for a project/filter grouped by a specified field. This helps users see the breakdown of a set of issues at a glance.
Note: If users need to group issues in a table, then users can use Single Level Group By Report. If users need group issues in a graphical report, then users can use Pie Chart Report.
Sample of Pie Chart Reports with 'Assignee' as its Statistic Type. Users can also change it to a custom field. Resolution Time Report contains graph bars and a table showing the length of time taken to resolve a set of issues for a project/filter. This helps users identify trends and incidents which they can investigate further.
Average Age Report contains graph bars and a table showing the average number of days that issues were unresolved in a day over the past certain days.
Single Level Group By Report shows a table of issues grouped by a particular field (including custom fields) for a filter. This helps users group search results by a field and see the overall status of each group.
Time Tracking Report shows the original and current time estimates for issues in the current project. This can help users determine whether work is on track for those issues.
Time Since Issues Report allows users to choose a date field and project/filter, then maps the issues against the date that the field was set. This can help users track how many issues were created, updated, etc, over a period of time.
Question 24Written Answer
Dom created an issue in Project A. Now he wants to move the issue to Project B.
According to the information below, which of the following fields will retain their values after moving the issue to Project B? (Choose two.)
Project A custom fields:
- Custom Field A - Text Field (single line)
- Custom Field B - Text Field (single line)
- Custom Field C - Version picker
Project B custom fields:
- Custom Field A - Text Field (single line)
- Custom Field C - Version picker
A. Custom Field A
B. Components
C. Fix Versions
D. Labels
E. Custom Field C
F. Custom Field B
Answer: A,D Explanation:
Component and version fields are project fields; not global fields. Therefore, those data will be permanently lost if users move issues between projects. This includes the Version Picker custom field. Other incompatible fields will also appear empty, even if users choose to retain their values.
In this example, only Labels and Custom Field A will retain their values:
- Labels' values are shared globally.
- Custom Field A is compatible with Project B. Thus, Jira will retain its value.
- Project B does not have Custom Field B. Thus, Jira will not retain its value.
- Custom Field C is a version picker. Jira will not retain the version's value.
Question 25Selectable Answer
As a scrum master, Razi wants to get a list of issues for the upcoming sprint.
Which of the below is the right JQL?
Answer: Explanation:
nextSprints() and reopenSprints() do not exist.
These are the only valid JQL for sprint:
- openSprints()
- closedSprints()
- futureSprints()
openSprints() is a valid JQL but openSprints() is to get a list of issues in the current active sprint.
Reference: Advanced search reference - JQL functions
Question 26Selectable Answer
Nina is the account manager from the Finance Department.
She is responsible to:
- Create a new Jira user
- Grant application access
- Manage the billing information.
Which Jira user type is suitable for Nina?
Answer: Explanation:
Site administrators:
- Usually someone that has the authority to manage the team's finances.
- Manage new users.
- Manage billing and subscriptions.
- Manage site settings.
Jira administrators:
- Usually someone that has good technical knowledge in Jira.
- Manage Jira plugins.
- Manage Jira global configurations (Global permissions, global settings, etc).
- Manage Jira schemes (Workflow, permissions, screens, notifications, etc).
Project administrators:
- Usually someone that is managing a specific Jira project.
- Manage project configurations (Roles, project details, etc).
Jira Software users:
- Users that are working on issues in the Jira Software project.
- Users' permissions are being managed by other administrators.
Question 27Selectable Answer
Nina's team plans to complete 10 issues in the sprint. However, there are 2 issues still unresolved.
As a project administrator, what is the minimum permission Nina needs to complete the current sprint? (Choose four.)
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 not a Jira administrator, Manage Sprints permission is required.
The user requires Edit Issues and Schedule Issues because there are 2 unresolved issues that need to be moved to the backlog or to the next sprint.
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.
Question 28Selectable Answer
Which of the following is not the default team-managed project role?
Note:
- Company-managed projects are formerly known as classic projects.
- Team-managed projects are formerly known as next-gen projects
Answer: Explanation:
Team-managed software projects come with three roles by default:
- Administrator
- Member
- Viewer
Administrator - Admins can do most things, such as: update settings, add other admins to the project, manage features, customize issue types, and add rules on the board. Admins need product access to Jira Software to get the full benefit of this role.
Member - Members are a part of the team. They can create issues, edit them, comment on them, move them into different statuses, and generally collaborate on the project's work. Members need product access to Jira Software to get the full benefit of this role.
Viewer - Viewers can search through and view issues in the project, but not much else. You can give any registered user on your Jira site this role without extra product access.
Question 29Selectable Answer
Based on the below diagram, which statement is true about issues on July 25th?
There are 6 issues in the 'To Do' status.
Answer: Explanation:
On July 25th, there are:
- 4 issues in 'To Do'
- 1 issue in 'In Progress'
- 6 issues in 'Done'
Question 30Selectable Answer
Sarah's Team is responsible for developing a web application for their client. The modules will be delivered to the client batch by batch every two weeks.
Which of the following Jira Software template is suitable for Sarah's Team?
