2025 Latest ACP-120 Version Pass Certify | Reliable Dumps ACP-120 Reviews: Jira Cloud Administrator

Our Jira Cloud Administrator (ACP-120) exam questions are being offered in three easy-to-use and compatible formats. This ACP-120 exam dumps formats offer a user-friendly interface and are compatible with all devices, operating systems, and browsers. The TopExamCollection Jira Cloud Administrator (ACP-120) PDF questions file contains real and valid ATLASSIAN ACP-120 exam questions that assist you in ACP-120 exam dumps preparation and boost the candidate's confidence to pass the challenging Jira Cloud Administrator (ACP-120) exam easily.

ATLASSIAN ACP-120 (Jira Cloud Administrator) Exam covers a wide range of topics, including Jira Cloud architecture, configuration, and administration. It also focuses on advanced topics such as user management, permissions, workflows, and automation. ACP-120 Exam consists of 60 multiple-choice questions that need to be completed within 180 minutes. The passing score for ACP-120 exam is 65%, which means an individual needs to answer 39 questions correctly out of 60.

>> Latest ACP-120 Version <<

Latest Latest ACP-120 Version - Find Shortcut to Pass ACP-120 Exam

We provide the ACP-120 study materials which are easy to be mastered, professional expert team and first-rate service to make you get an easy and efficient learning and preparation for the ACP-120 test. Our product’s price is affordable and we provide the wonderful service before and after the sale to let you have a good understanding of our ACP-120 Study Materials before your purchase, you had better to have a try on our free demos.

ATLASSIAN Jira Cloud Administrator Sample Questions (Q32-Q37):

NEW QUESTION # 32
You receive workflow configuration requirements for issues in the Closed status. They are as follows:
Users must NOT be able to edit issues in this status.
Jira administrators must be able to edit issues in this status.
Only users in the release-managers group should see the transition to the Re-opened status Which combination of two workflow configuration items should you use to meet these requirements?
(Choose two.)

A. Conditions
B. Properties
C. Triggers
D. Validators
E. Post functions

Answer: A,D

NEW QUESTION # 33
Your organization uses Jira Software and Confluence. Dave is a new employee who needs the following privileges
* Approve access requests
* Manage group memberships
* Update billing details
You need to give him enough but not too many privileges How should you configure Dave's user account? (Choose one)

A. As an organization administrator
B. As a site administrator
C. As a member of the jira-administrators and confluence-administrators group
D. As a trusted user
E. As a member of the administrators group

Answer: A

NEW QUESTION # 34
Your site contains the following:
* Alpha filter: Public
* Beta filter: Private
* Omega dashboard: PublicThe system setting 'Allow users to share dashboards and filters with the public' is currently set to ON. You change that setting to OFF. What is the impact of this change?

A. You cannot set Viewers to Private on Alpha filter.
B. Users who are not logged in cannot see Alpha filter.
C. Users who are not logged in cannot see Omega dashboard.
D. You cannot set Viewers to Public on Beta filter.

Answer: B,C

NEW QUESTION # 35
Boris is reviewing his assigned issues. He wants to move them from the backlog into a planned sprint so he can work on them. Which two permissions does he need? (Choose two.)

A. Work On Issues
B. Manage Sprints
C. Move Issues
D. Assignable User
E. Schedule Issues
F. Edit Issues

Answer: E,F

Explanation:
To move issues from the backlog to a planned sprint in a Jira Software Cloud project, Boris needs permissions to modify the issue's sprint field and edit the issue itself. The two permissions required areSchedule Issues (Option B) andEdit Issues(Option D).
* Explanation of the Correct Answers:
* Schedule Issues (Option B):
* TheSchedule Issuespermission allows a user to add issues to a sprint, remove issues from a sprint, or move issues between sprints. This permission is necessary to move issues from the backlog (which is not part of a sprint) into a planned sprint.
* Exact Extract from Documentation:
Schedule Issues permission
TheSchedule Issuespermission allows users to:
* Add issues to a sprint.
* Remove issues from a sprint.
* Move issues between sprints or to the backlog.This permission is required to manage the sprint field in issues, such as moving an issue from the backlog to a planned sprint.Note: This permission is granted via the project's permission scheme.(Source:
Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Why This Fits: Moving an issue to a planned sprint involves updating theSprintfield, which requires theSchedule Issuespermission.
* Edit Issues (Option D):
* TheEdit Issuespermission allows a user to modify issue fields, including theSprintfield.
Without this permission, Boris cannot edit the issue to set its sprint, even if he has the Schedule Issuespermission.
* Exact Extract from Documentation:
Edit Issues permission
TheEdit Issuespermission allows users to modify issue fields, such as Summary, Description, or Sprint. This permission is required to update an issue's details, including moving it to a sprint if combined with the Schedule Issuespermission.
Note: This permission is granted via the project's permission scheme.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Why This Fits: Editing theSprintfield to move an issue into a planned sprint requires the Edit Issuespermission, as it involves modifying the issue's metadata.
* Why Other Options Are Incorrect:
* Work On Issues (Option A):
* TheWork On Issuespermission allows users to log work on issues (e.g., record time spent). It is not related to moving issues to a sprint or editing issue fields.
* Extract from Documentation:
Work On Issues permission
Allows users to log work on issues using the time tracking feature. This does not include editing issue fields or managing sprints.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Move Issues (Option C):
* TheMove Issuespermission allows users to move issues between projects or change their issue type within the same project. Moving an issue to a sprint does not involve changing its project or issue type, so this permission is not required.
* Extract from Documentation:
Move Issues permission
Allows users to move issues to a different project or change their issue type. This is not required for moving issues to a sprint within the same project.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Manage Sprints (Option E):
* TheManage Sprintspermission allows users to create, start, complete, or delete sprints.
While this permission is necessary for managing the sprint itself, it is not required to move issues into a planned sprint, as Boris is not creating or modifying the sprint.
* Extract from Documentation:
Manage Sprints permission
Allows users to create, start, complete, or delete sprints. Moving issues to an existing sprint requires the Schedule IssuesandEdit Issuespermissions, notManage Sprints.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Assignable User (Option F):
* TheAssignable Userpermission allows a user to be assigned to issues (i.e., set as the Assignee). It does not affect the ability to move issues to a sprint.
* Extract from Documentation:
Assignable User permission
Allows users to be set as the assignee of an issue. This does not include editing other fields like the Sprint field.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Additional Notes:
* Boris likely already has theBrowse Projectspermission, as he can review his assigned issues. The Schedule IssuesandEdit Issuespermissions are specifically required for the action of moving issues to a sprint.
* These permissions are granted via the project's permission scheme, which can be checked in Project settings > Permissions.
:
Atlassian Support Documentation:Manage permissions in Jira Cloud
Atlassian Support Documentation:Manage sprints in company-managed projects

NEW QUESTION # 36
A company-managed project has issue-level security configured, with two security levels. However, Andre only sees one of them in the Security Level dropdown field. Identify a possible reason.

A. The other level is marked as the default.
B. The other level is configured for different issue types.
C. Andre does not have Edit Issues permission.
D. Andre does not have Set Issue Security permission.
E. Andre is not in a group or project role.

Answer: D

Explanation:
In a company-managed project with issue-level security configured, theSecurity Leveldropdown field allows users to set the security level for an issue, restricting who can view it. If Andre only sees one security level instead of both, the most likely reason is that he lacks theSet Issue Securitypermission (Option C), which is required to view and select security levels in the dropdown.
* Explanation of the Correct Answer (Option C):
* TheSet Issue Securitypermission allows users to set or change the security level of an issue.
Without this permission, a user may not see all available security levels in theSecurity Level dropdown, or the field may be hidden or restricted. If Andre lacks this permission, he might only see the default security level (if set) or no options at all, depending on the configuration.
* Exact Extract from Documentation:
Set Issue Security permission
TheSet Issue Securitypermission allows users to set or change the security level of an issue, which determines who can view it. Without this permission, users cannot modify theSecurity Levelfield or may only see a subset of available levels.
To check this permission:
* Go toProject settings > Permissions.
* Verify which users, groups, or roles have theSet Issue Securitypermission.Note: The visibility of security levels in the dropdown also depends on the user's membership in groups or roles defined in the security levels.(Source: Atlassian Support Documentation,
"Configure issue security schemes")
* Why This Fits: TheSet Issue Securitypermission is directly responsible for allowing users to interact with theSecurity Levelfield. If Andre lacks this permission, he may not see both security levels, making Option C a likely reason.
* Why Other Options Are Incorrect:
* The other level is configured for different issue types (Option A):
* Issue security levels are not tied to specific issue types; they apply to all issues in a project under the issue security scheme. The configuration of security levels is project-wide, so this is not a valid reason.
* Extract from Documentation:
Issue security levels apply to all issue types in a project using the same issue security scheme. They are not restricted by issue type.
(Source: Atlassian Support Documentation, "Configure issue security schemes")
* Andre is not in a group or project role (Option B):
* While security levels may restrict visibility based on groups or project roles, the question is about Andre's ability to see security levels in the dropdown, not about viewing issues. The Set Issue Securitypermission determines whether Andre can see and select levels, not his membership in groups or roles for visibility purposes.
* Extract from Documentation:
Security levels define who can view issues (e.g., users in a group or role). TheSet Issue Securitypermission controls who can set the level, not who can view the issue.
(Source: Atlassian Support Documentation, "Configure issue security schemes")
* The other level is marked as the default (Option D):
* Marking a security level as the default ensures it is automatically applied to new issues if no level is specified. However, this does not prevent other levels from appearing in the Security Leveldropdown for users with theSet Issue Securitypermission.
* Extract from Documentation:
The default security level is applied to new issues if no level is set. All available levels are shown in the Security Leveldropdown to users with theSet Issue Securitypermission.
(Source: Atlassian Support Documentation, "Configure issue security schemes")
* Andre does not have Edit Issues permission (Option E):
* TheEdit Issuespermission allows users to modify issue fields, but theSecurity Levelfield is specifically controlled by theSet Issue Securitypermission. A user can haveEdit Issues permission but still not see security levels if they lackSet Issue Security.
* Extract from Documentation:
TheSet Issue Securitypermission is separate fromEdit Issuesand specifically controls access to theSecurity Levelfield.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Additional Notes:
* Another possible reason (not listed) could be that Andre is not in the groups or roles defined for the second security level, limiting its visibility in the dropdown. However, theSet Issue Security permission is the most direct cause listed.
* To resolve the issue, check Andre's permissions inProject settings > Permissionsand ensure he hasSet Issue Security.
:
Atlassian Support Documentation:Configure issue security schemes
Atlassian Support Documentation:Manage permissions in Jira Cloud

NEW QUESTION # 37
......

TopExamCollection has been to make the greatest efforts to provide the best and most convenient service for our candidates. High speed and high efficiency are certainly the most important points. In today's society, high efficiency is hot topic everywhere. So we designed training materials which have hign efficiency for the majority of candidates. It allows candidates to grasp the knowledge quickly, and achieved excellent results in the exam. TopExamCollection's ATLASSIAN ACP-120 Exam Training materials can help you to save a lot of time and effort. You can also use the extra time and effort to earn more money.

Dumps ACP-120 Reviews: https://www.topexamcollection.com/ACP-120-vce-collection.html