ATLASSIAN ACP-120 Exam Prep Guide: Prep guide for the ACP-120 Exam
2026 New Preparation Guide of ATLASSIAN ACP-120 Exam
NEW QUESTION # 11
Alana has set up a new incoming mail handler to create issues or add a comment to an existing issue.
All new issues should be unassigned to triage them individually. You have not set up any components.
Sometimes issues are being randomly assigned to various users upon creation.
Which configuration can cause the observed behavior? (Choose one)
- A. An Assign to Lead Developer workflow post function
- B. The Default Assignee project setting
- C. The CC Assignee setting of the mail handler
- D. An Update Issue Field workflow post function
Answer: B
NEW QUESTION # 12
George is the project lead of several projects. Now, he needs to create projects but should not have Jira administrator privileges. What does George need?
- A. Product role
- B. Project role
- C. Project permission
- D. Global permission
- E. Product access
Answer: D
NEW QUESTION # 13
No one should be allowed to edit issues in a particular workflow status of a company-managedproject. Which element must be configured?
- A. Condition
- B. Trigger
- C. Status Property
- D. Post function
Answer: C
Explanation:
Okay, let's analyze this question again with the revised options.
The requirement is to preventanyonefromeditingan issue when it resides in aspecific workflow status.
As established previously:
* Conditions (A):Control whether atransitionout of or into a status can occur. They check criteriabeforea transition starts. They don't prevent editingwhilean issue is sitting in a status.
* Post Functions (Implied by B & C):Actions that executeaftera transition is successfully completed (e.
g., updating a field, sending a notification). They don't affect editability within the status itself.
* Triggers (D):Automatically initiate a workflow transition based on external events (like code commits). Not relevant to editing permissions within a status.
The correct way to achieve this in Jira is by setting aStatus Property:
* Navigate to Workflow configuration.
* Select the relevant status.
* Go to its 'Properties'.
* Add a property: jira.issue.editable with the value false.
NEW QUESTION # 14
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. Andre does not have Edit Issues permission.
- B. Andre is not in a group or project role.
- C. The other level is marked as the default.
- D. Andre does not have Set Issue Security permission.
- E. The other level is configured for different issue types.
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 # 15
You are setting up Jira Software Cloud for an organization of 250 employees. Product access is already configured to grant new users access to Jira Software by default You now need to configure site access so that it meets these 3 conditions
1. Minimum administration overhead is required
2. Access is granted to the entire organization at the same time
3. Access is restricted only to your organization
Which solution meets these requirements? (Choose one)
- A. Create an invite link and share it with all current and future employees
- B. Add all your company's domains as approved domains
- C. Approve any domain in the site access settings
- D. Set the global mode to public and enable CAPTCHA on sign up
- E. Enable existing users to send invitations to all current and future employees
Answer: B
NEW QUESTION # 16
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 a site administrator
- B. As a member of the administrators group
- C. As a trusted user
- D. As a member of the jira-administrators and confluence-administrators group
- E. As an organization administrator
Answer: E
NEW QUESTION # 17
Which statement is true about changing a project's key?
- A. Unshared project schemes will be automatically renamed to reflect the new project key.
- B. Internal Jira links referencing an old key will continue to work.
- C. Users have to update issue filters referencing the old project key.
- D. The old project key can be reused for a new project.
- E. External links to issues in that project need to be updated to match the new project key.
Answer: B
Explanation:
Reference: https://confluence.atlassian.com/adminjiraserver075/editing-a-project-key-935
NEW QUESTION # 18
Gary complains that he is not getting any notifications when issues are updated.
According to the notification helper, he should receive notifications for all issues he is watching. His coworkers confirm they receive those notifications and they regularly update issues that he is watching.
Which update to Gary's personal settings must have occurred (Choose one)
- A. The setting You're watching the issue was disabled
- B. The setting Email notifications format was changed
- C. The setting You make changes to the issue was disabled
- D. The setting Watch your issues was disabled
Answer: D
NEW QUESTION # 19
You are setting up a new Jira instance and three new projects with shared configuration. There are many managers at the company and you need to structure their permissions accordingly.
Which requirement can only be met with a Managers project role?
- A. Different managers need to delete issues in different projects.
- B. Any manager should be able to view the development tools in any project.
- C. Managers need to be able to create shared dashboards.
- D. Only managers who are project leads can see the restricted security level in their own projects.
- E. Only some managers must be selectable from a custom field, depending on the project.
Answer: D
NEW QUESTION # 20
version in a company-managed project:
* Move all issues in version 1.1 to version 1.2.
* Remove version 1.1 as an available option from the Fix Versions system field.
Which two operations will both meet the requirements? (Choose two.)
- A. Merge
- B. Delete
- C. Build and release
- D. Archive
Answer: A,D
Explanation:
The question involves managing versions in a company-managed project in Jira Software Cloud. Maia wants to move all issues from version 1.1 to version 1.2 and remove version 1.1 as an available option in theFix Versionsfield. The two operations that meet both requirements areArchiveandMerge.
* Explanation of the Correct Answers:
* Archive (Option B):
* Archiving a version removes it from theFix Versionsfield as an available option for new issues, while preserving the version's association with existing issues. Additionally, archiving allows you to move issues to another version (e.g., version 1.2) during the process, meeting both requirements.
* Exact Extract from Documentation:
Archive a version
Archiving a version removes it from the list of available versions in fields like Fix Versions, so it can't be selected for new issues. You can also move issues to another version during the archiving process.
To archive a version:
* Go to your project'sReleasespage.
* Find the version (e.g., version 1.1) and selectArchive.
* Optionally, choose to move issues to another version (e.g., version 1.2).Archived versions are still visible in reports and issue details but are no longer selectable in fields.Note: You need project admin permissions to archive versions.(Source:
Atlassian Support Documentation, "Manage versions in company-managed projects")
* Why This Fits: Archiving version 1.1 removes it from the Fix Versions field, preventing it from being selected for new issues, and allows Maia to move all issues to version 1.2 during the archiving process, fulfilling both requirements.
* Merge (Option D):
* Merging a version moves all issues from one version (e.g., version 1.1) to another (e.g., version 1.2) and deletes the source version, effectively removing it from the Fix Versions field. This meets both requirements, as it reassigns issues and eliminates version 1.1 as an available option.
* Exact Extract from Documentation:
Merge versions
Merging versions allows you to combine two versions by moving all issues from one version to another. The source version is deleted after the merge.
To merge versions:
* Go to your project'sReleasespage.
* Find the version to merge (e.g., version 1.1) and selectMerge.
* Choose the target version (e.g., version 1.2) to move issues to.After merging, the source version (version 1.1) is removed from the Fix Versions field and is no longer available for selection.Note: Merging is permanent and cannot be undone, so ensure the target version is correct.(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")
* Why This Fits: Merging version 1.1 into version 1.2 moves all issues to version 1.2 and deletes version 1.1, ensuring it is no longer an option in the Fix Versions field, thus meeting both requirements.
* Why Other Options Are Incorrect:
* Delete (Option A):
* Deleting a version removes it from the Fix Versions field, but it also removes the version from all issues associated with it without reassigning them to another version. This does not meet the requirement to move issues to version 1.2.
* Extract from Documentation:
Delete a version
Deleting a version removes it from the project and clears it from the Fix Versions field of all associated issues. Issues are not reassigned to another version automatically.
Note: Use caution, as this action cannot be undone, and issues lose their version association.
(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")
* Build and release (Option C):
* Building and releasing a version marks it as complete and moves unresolved issues to another version, but it does not remove the version from the Fix Versions field. Released versions remain selectable unless archived or deleted.
* Extract from Documentation:
Release a version
Releasing a version marks it as complete and optionally moves unresolved issues to another version. The released version remains available in the Fix Versions field unless archived.
(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")
* Additional Notes:
* BothArchiveandMergeare suitable, but they have different implications:
* Archiving preserves version 1.1 in reports and issue histories, making it ideal if historical data needs to be retained.
* Merging permanently deletes version 1.1, which may be preferred if the version is no longer relevant.
* The operations require project admin permissions in a company-managed project, and the Releasespage is accessed viaProject Settings > Releases.
:
Atlassian Support Documentation:Manage versions in company-managed projects Atlassian Support Documentation:Configure releases and versions
NEW QUESTION # 21
You are a site administrator.
You have created an account fo rAshley
You need to log in as Ashley to ensure his permissions are set correctly Identify why you are unable to log in as Ashley (Choose one)
- A. Ashley has not accessed your site yet
- B. Ashley does not have a managed account
- C. You are not an organization admin
- D. Ashley has the role of site admin
Answer: B
NEW QUESTION # 22
Jon is a new Jira user. He reports that adding comments to Jira isn't working as expected. When he attempts to @mention a user, no list of available users is provided. Because he does not know everyone's username, he is unable to target comments to specific users.
What is the cause of this problem?
- A. The field configuration for the Comment field is not set to Autocomplete Renderer.
- B. Jon does not have the View Users project permission.
- C. Jon does not have the Browse Users global permission.
- D. Jon does not have the correct field security permission for the Comment field.
Answer: A
Explanation:
Reference: https://community.atlassian.com/t5/Jira-questions/Can-t-Mention-other-users/qaq-p/5238
NEW QUESTION # 23
One of your teams has noticed a spelling mistake in the name of an issue type.
What should you do before correcting the name of the issue type?
- A. Update the workflow schemes for the issue type to use the new name.
- B. Update the issue type schemes to refer to the new name.
- C. Warn users that saved filters using the issue type will not be able to find the issue type after the change.
- D. Warn users that dashboard gadgets that refer to the issue type in their configuration will need to be updated with the corrected name.
Answer: B
Explanation:
Reference: https://confluence.atlassian.com/adminjiracloud/adding-editing-and-deleting-an-issue-type-scheme-844500754.html
NEW QUESTION # 24
A team of technical writers works in the WRITE project. The project uses a single, shared workflow.
To better match the team's way of working they request a workflow change: The initial status of their project's workflow should be changed from Open to Awaiting Inspiration.
- You navigate to the Workflows section of the administration, update the Name of the status in the workflow designer and publish your change.
What are two implications of this change? (Choose two.)
- A. Filters and Gadgets that referred to the Open status by name will be broken.
- B. The workflow scheme for the WRITE project will need to be published before the change takes effect.
- C. The Open Status will be changed to Awaiting Inspiration in all workflows using that status.
- D. Transitions to the Awaiting Inspiration status will fail until the post functions for those transitions are updated.
- E. Awaiting Inspiration will be created as a new Status in Jira.
Answer: B,E
NEW QUESTION # 25
You are a site admin for your company.
Which function can you NOT perform? (Choose one)
- A. Manage users and groups
- B. Configure products in your Atlassian Cloud site(s)
- C. Deactivate a Cloud site
- D. Enable Single Sign On for your Atlassian Cloud site(s)
- E. Enable invite links for your products
Answer: C
NEW QUESTION # 26
Carlos describes his problem in the classic HR project
* He cannot attach files to issues of Request issue type when they are in the Approved status
* He can attach files to issues of Request issue type in any other status
* He can attach files to every other issue issue type in every status
He asks for your help in determining the root cause Select the root cause (Choose one)
- A. There is a workflow step property configured
- B. He does not have the correct project permission
- C. He is not a member of a security level
- D. There is a workflow condition configured
- E. The Attachment field is missing on the screen used by the Request issue type
Answer: A
NEW QUESTION # 27
Two users have access to the same filter and see the same issues in a company-managed project. One of them can perform a bulk operation to watch issues in the filter, but the other user cannot. What should you investigate?
- A. Groups
- B. Default user preferences
- C. Project roles
- D. Project permissions
- E. Product access
Answer: D
Explanation:
The scenario describes two users who can view the same issues in a filter (indicating they have theBrowse Projectspermission), but only one can perform a bulk operation towatchissues. The ability to watch issues is controlled by theView Issue WatchersandManage Watcher Listpermissions in the project's permission scheme. Therefore, you should investigateproject permissions(Option A).
* Explanation of the Correct Answer (Option A):
* Performing a bulk operation to watch issues requires theManage Watcher Listpermission, which allows users to add themselves or others as watchers to an issue. Since both users can see the issues (via the filter), they likely have theBrowse Projectspermission, but the user who cannot perform the bulk operation may lack theManage Watcher Listpermission.
* Exact Extract from Documentation:
Manage Watcher List permission
TheManage Watcher Listpermission allows users to add or remove watchers from an issue, including via bulk operations. This permission is granted via the project's permission scheme.
Note: To view the watcher list, users also need theView Issue Watcherspermission. Both permissions are required to perform actions like bulk watching issues.
To check permissions:
* Go toProject settings > Permissions.
* Review theManage Watcher ListandView Issue Watcherspermissions to see which users, groups, or roles have them.(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Why This Fits: The difference in the users' ability to perform the bulk watch operation is most likely due to a difference in theirManage Watcher Listpermission, which is defined in the project's permission scheme. Investigating project permissions will reveal whether the second user lacks this permission.
* Why Other Options Are Incorrect:
* Product access (Option B):
* Product access determines whether users can use Jira Software. Both users can view the filter and issues, indicating they have product access. Product access does not control specific permissions like managing watchers.
* Extract from Documentation:
Manage product access
Product access grants users the ability to use Jira products. Specific actions, like managing watchers, are controlled by project or global permissions, not product access.
(Source: Atlassian Support Documentation, "Manage product access")
* Groups (Option C):
* Groups may be used in permission schemes to grant permissions, but the root cause is the permission itself, not the group membership. Investigating groups might be a secondary step after checking project permissions, butproject permissionsis the more direct answer.
* Extract from Documentation:
Groups are used in permission schemes to grant permissions to multiple users. To determine why a user lacks a permission, check the permission scheme first, then verify group membership if relevant.
(Source: Atlassian Support Documentation, "Manage groups")
* Default user preferences (Option D):
* Default user preferences (e.g., notification settings) control whether a user receives notifications for watched issues, not their ability to watch issues.The issue is about performing a bulk operation, not receiving notifications.
* Extract from Documentation:
Manage user preferences
Users can manage their notification preferences inPersonal settings > Email notifications. These settings affect notification delivery, not the ability to perform actions like watching issues.
(Source: Atlassian Support Documentation, "Manage your Jira notification emails")
* Project roles (Option E):
* Project roles are used in permission schemes to grant permissions. Like groups, roles are a means to assign permissions, but the issue lies in the permission itself (Manage Watcher List). Investigating project permissions directly addresses the root cause.
* Extract from Documentation:
Project roles are used in permission schemes to grant permissions likeManage Watcher List. Check the permission scheme to identify the root cause of permission differences.
(Source: Atlassian Support Documentation, "Manage project roles")
* Additional Notes:
* Both users can see the filter and issues, so they likely have theBrowse Projectspermission. The difference in their ability to perform the bulk watch operation points to theManage Watcher List permission, which should be checked inProject settings > Permissions.
* If the permission is granted to a group or role, verify the users' membership in those groups or roles as a follow-up step.
:
Atlassian Support Documentation:Manage permissions in Jira Cloud
Atlassian Support Documentation:Manage product access
Atlassian Support Documentation:Manage groups
Atlassian Support Documentation:Manage your Jira notification emails
Atlassian Support Documentation:Manage project roles
NEW QUESTION # 28
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. Manage Sprints
- B. Edit Issues
- C. Move Issues
- D. Work On Issues
- E. Schedule Issues
- F. Assignable User
Answer: B,E
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 # 29
The configuration details of an SMTP Mail Server of a Jira instance are shown below.
The configuration hasn't been changed in the last 24 months.
Currently emails are no longer being sent and the failed notifications can be seen in the Mail Error Queue.
What is the likely cause of the failure?
- A. The user jira has no valid Jira license.
- B. The SMTP password has expired.
- C. Email volume has increased and the Timeout is too low.
- D. The database and/or server disk is full.
- E. The Jira license has expired.
Answer: E
NEW QUESTION # 30
A team in your company requests a new Jira project that fulfills the following requirements:
* Ability to work on issues in weekly iterations
* Allows the project administrators to create their own fields
The project should fulfill these requirements right after creation without the need to enable additional features.
Which project should you create?
- A. Company-managed project with Scrum template
- B. Team-managed project with Scrum template
- C. A company-managed project with Kanban template
- D. Team-managed project with Canban template
Answer: A
NEW QUESTION # 31
......
Latest Questions ACP-120 Guide to Prepare Free Practice Tests: https://www.dumpstorrent.com/ACP-120-exam-dumps-torrent.html
ACP-120 Practice Exam - 77 Unique Questions: https://drive.google.com/open?id=1JpOoo9-u28rJGFOSx0463aDuoF0MTz7n