Was :
$81
Today :
$45
Was :
$99
Today :
$55
Was :
$117
Today :
$65
Why Should You Prepare For Your Jira Administration for Cloud With MyCertsHub?
At MyCertsHub, we go beyond standard study material. Our platform provides authentic ATLASSIAN ACP-120 Exam Dumps, detailed exam guides, and reliable practice exams that mirror the actual Jira Administration for Cloud test. Whether you’re targeting ATLASSIAN certifications or expanding your professional portfolio, MyCertsHub gives you the tools to succeed on your first attempt.
Verified ACP-120 Exam Dumps
Every set of exam dumps is carefully reviewed by certified experts to ensure accuracy. For the ACP-120 Jira Administration for Cloud , you’ll receive updated practice questions designed to reflect real-world exam conditions. This approach saves time, builds confidence, and focuses your preparation on the most important exam areas.
Realistic Test Prep For The ACP-120
You can instantly access downloadable PDFs of ACP-120 practice exams with MyCertsHub. These include authentic practice questions paired with explanations, making our exam guide a complete preparation tool. By testing yourself before exam day, you’ll walk into the ATLASSIAN Exam with confidence.
Smart Learning With Exam Guides
Our structured ACP-120 exam guide focuses on the Jira Administration for Cloud's core topics and question patterns. You will be able to concentrate on what really matters for passing the test rather than wasting time on irrelevant content. Pass the ACP-120 Exam – Guaranteed
We Offer A 100% Money-Back Guarantee On Our Products.
After using MyCertsHub's exam dumps to prepare for the Jira Administration for Cloud exam, we will issue a full refund. That’s how confident we are in the effectiveness of our study resources.
Try Before You Buy – Free Demo
Still undecided? See for yourself how MyCertsHub has helped thousands of candidates achieve success by downloading a free demo of the ACP-120 exam dumps.
MyCertsHub – Your Trusted Partner For ATLASSIAN Exams
Whether you’re preparing for Jira Administration for Cloud or any other professional credential, MyCertsHub provides everything you need: exam dumps, practice exams, practice questions, and exam guides. Passing your ACP-120 exam has never been easier thanks to our tried-and-true resources.
ATLASSIAN ACP-120 Sample Question Answers
Question # 1
[Issue Types, Fields, Screens]You are using a bulk move operation to migrate issues in a company-managed project from one issuetype to another. Identify the two elements that might need to change. (Choose two.)
A. Statuses B. Priorities C. Required fields D. Resolutions E. Labels
Answer: A,C
Explanation:
During a bulk move operation between different issue types in a company-managed project, Jira maps the existing issueconfiguration to the destination issue type's configuration. You will be prompted to update information if there are
mismatches in the following two areas:
A. Statuses: The target issue type might use a different workflow with a different set of valid statuses. If the currentstatus does not exist in the new workflow, you must manually select a target status for the moved issues.
C. Required fields: The target issue type might use a different Field Configuration scheme where certain fields are
marked as Required that were optional or completely hidden in the original issue type. You must fill in these
mandatory fields to complete the migration.
Why the other options are incorrect:
B, D, and E: Priorities, Resolutions, and Labels are global system fields that remain consistent across issue types.
Jira retains these values automatically during a bulk move without forcing you to change them.
Question # 2
[Advanced User Features]You performed the following steps:Created a new filter with the JQL query project IN projectsWhereUserHasRole("Sales")Created a filter subscription for the filter and set the recipients to the Sales group.Leila is a member of the Sales group. Which issues will Leila receive in her subscription?
A. Issues from projects where Leila is in the Sales role B. Issues assigned to anyone in the Sales group C. Issues from projects where Leila is in the Sales group D. Issues assigned to anyone in the Sales role
Answer: A
Explanation:
The JQL function projectsWhereUserHasRole("Sales") evaluates dynamically for the user running the query. When afilter subscription runs and sends an email to a group member, Jira executes the underlying query individually as that
specific recipient.
Since Leila is the one receiving the subscription, Jira evaluates the function based on her personal access. Therefore, it
will return issues from any project where Leila holds the "Sales" project role.
Question # 3
[Access, Permissions, Security]Your site contains the following:Alpha filter: PublicBeta filter: PrivateOmega dashboard: PublicThe system setting ‘Allow users to share dashboards and filters with thepublic’ is currently set to ON. You change that setting to OFF. What is the impact of this change?
A. You cannot set Viewers to Public on Beta filter. B. You cannot set Viewers to Private on Alpha filter. C. Users who are not logged in cannot see Alpha filter. D. Users who are not logged in cannot see Omega dashboard.
Answer: D
Explanation:
Turning the global setting to OFF blocks all anonymous (not logged-in) access across your site.
While logically both filters and dashboards are affected, D is the official exam answer because Atlassian's
documentation specifically emphasizes that turning this setting off instantly revokes public visibility for shared
dashboards.
Question # 4
[Advanced User Features]You run the JQL query shown:assignee changed from currentUser() TO EMPTY and resolution changed to EMPTYWhich statement is definitely true?
A. All returned issues are currently unresolved. B. All returned issues are currently unassigned. C. All returned issues were assigned to you at some point. D. All returned issues are currently not assigned to you. E. All returned issues were in Done status at some point.
Answer: C
Explanation: The JQL query uses the historical changed operator, which evaluates an issue's history rather than its
current state.
The clause assignee changed from currentUser( ) TO EMPTY dictates that the assignee field explicitly transitioned
from you (the current user) to unassigned (EMPTY). For this condition to evaluate to true, the issue must have been
assigned to you before that change occurred.
Question # 5
[Advanced User Features]You need to find unresolved issues assigned to suspended users. Identify the correct JQL query.
A. resolution is EMPTY AND assignee in inactiveUsers() B. statusCategory != Done AND assignee not in organizationMembers() C. resolution = Unresolved AND assignee changed to inactive D. statusCategory = Done AND assignee not in activeUsers() E. resolution = EMPTY AND assignee not in membersOf("jira-software-users")
Answer: A
Explanation:
A: To check for unresolved issues, the absolute standard JQL practice is checking if the resolution is EMPTY. To
target suspended or deactivated user accounts, Jira Cloud supports the native JQL function inactiveUsers().
Combined with the IN operator, assignee in inactiveUsers() pulls all issues belonging to suspended accounts.
Why the other options are incorrect:
B & D: statusCategory checks do not strictly correlate to whether an issue technically has a resolution value set,
and the functions organizationMembers() or activeUsers() are not valid native JQL functions for this scenario.
C: Unresolved is text, not a system flag for the resolution field (which requires checking for an empty/null state),
and changed to inactive is invalid historical JQL syntax.
E: membersOf() targets a specific user group name rather than checking the system-wide active status of an
individual account.
Question # 6
[Access, Permissions, Security]You need to grant members of the Compliance team access to all of your company-managed projectsin Jira. All the projects were created with a shared configuration and need to remain that way. You mustdecide if a project role is required to accommodate any of their requirements. Identify therequirement that necessitates the use of a project role.
A. Only some Compliance users can delete issues and they differ in each project. B. All members need to be able to move issues. C. Only two Compliance users should be able to see secured issues. D. Only some Compliance users need to create shared dashboards.
Answer: A
Explanation:
A: Project roles exist specifically to handle project-by-project membership differences. Because the projects
share a configuration (and thus share the same permission scheme), granting permission to a fixed group would
give those users the exact same rights everywhere. A project role allows you to grant "Delete Issues" permission to
the role globally, but populate that role with different individual Compliance team members inside each specific
project.
Question # 7
[Access, Permissions, Security]Your Jira Cloud instance has hundreds of company-managed projects which are used only by thedevelopment team at your organization. All projects share a single permission scheme. New businessrequirements state:Customer support staff at your organization need to view all issues in all the projects.They also need to share filters with other users.They should not be granted too much access.Identify the appropriate way to configure customer support staff in Jira.
A. As a new group B. As a security level C. As a new project role D. As a new permission
Answer: A
Explanation:
Since:
Hundreds of projects share the same permission scheme
Customer support staff need consistent access across all projects
They should receive only the necessary permissions
The best approach is to:
Create a new group for customer support staff
Grant that group the required permissions (Browse Projects, Share Filters, etc.) in the shared permission scheme
Question # 8
[Advanced User Features]You need to create a filter that shows only issues that were created during the last calendar month.Identify the correct JQL query.
A. created changed during (startOfMonth(), endOfMonth()) B. createdDate >= startOfMonth(-1) OR createdDate <= endOfMonth(-1) C. created >= startOfMonth(-1) AND created <= endOfMonth(-1) D. createdDate >= startOfMonth(-1m) AND createdDate <= endOfMonth(-1m)
Answer: C
Explanation:
This query correctly returns issues created during the previous calendar month:
startOfMonth(-1) ? start of last month
endOfMonth(-1) ? end of last month
Why others are incorrect:
A ?Invalid JQL syntax for this use case.
B ?Uses OR, which would return almost all issues.
D ?-1m is not the correct way for previous calendar month boundaries here.
Question # 9
[System Administration and Administering Jira]You want to restore a Cloud instance with another Jira Cloud backup. Which is not a valid option?
A. Import data B. Import apps C. Merge with existing Cloud users D. Overwrite existing Cloud users E. Import media
Answer: B
Explanation:
B: Import apps is not a valid choice in the Jira Cloud restore interface. When restoring an instance from a backup
file, Jira handles the core configurations, project structures, custom fields, data records, and media attachments.
However, any installed apps/add-ons and their respective isolated data are excluded from standard cloud backups.
They must be reinstalled directly from the Atlassian Marketplace after the restore process completes.
Options A, C, D, and E are incorrect because they represent the exact out-of-the-box checkboxes present when
importing a Jira Cloud backup file to configure how data, users, and attachment media are restored.
Question # 10
[Issue Types, Fields, Screens]You are configuring an issue layout in a company-managed project. Which statement is true?
A. You can reuse fields from a team-managed project. B. You can copy a layout to another project using the same screen. C. You can move any field to the Hidden fields section. D. You can move any field to the Context fields section.
Answer: B
Explanation:
In a company-managed project, issue layout is tied to screens and screen schemes, and layouts can be reused or
associated across projects using the same configuration (screens, schemes, etc.).
Why others are incorrect:
A ?Team-managed fields are not directly reusable in company-managed layouts. C ?Not all fields can be hidden (some system/required fields cannot be fully hidden).
D ?“Context fields” is not a valid Jira issue layout concept.
Question # 11
[System Administration and Administering Jira]From which three sources can the Jira import wizard import data? (Choose three.)
A. Microsoft Excel B. Trello C. Bitbucket D. GitHub E. JSON F. CSV
Answer: B,E,F
Explanation:
The native Jira External System Import wizard officially supports direct programmatic imports from Trello, as well as
structured file imports via JSON and CSV.
B, E, F: These are natively supported file formats or tool integrations directly present inside the standard import
interface.
A, C, D: These are incorrect because the wizard cannot read them natively. For Microsoft Excel and GitHub,
Atlassian's official migration path requires you to export their data into a CSV file first before running the wizard.
For Bitbucket, data must be exported into a JSON format first.
Question # 12
[Workflows and Automation]A company-managed project uses a single workflow for two issue types: Blogs and Ideas.Youreceived several new requirements. To satisfy one of them, you must create a second workflow.Identify that requirement.
A. Blogs should be auto-closed after 3 days, but not Ideas. B. Blogs should be editable after they are closed, but not Ideas. C. Blogs should be sent to the project lead each Friday, but not Ideas. D. Blogs should allow reopening after they are closed, but not Ideas.
Answer: D
Explanation:
D: Reopening an issue requires a specific workflow transition (e.g., from Closed to Reopened). Since you only
want Blogs to have this transition and not Ideas, they can no longer share the same workflow structure. You must
create a second workflow to give Blogs this unique path.
Options A and C are incorrect because they are handled by Jira Automation rules, which can filter by issue type
without changing the workflow. Option B is incorrect because editing permissions on a closed status are controlled via
workflow step properties; however, you can restrict editing by issue type using a single workflow combined with a
standard permission scheme or automation.
Question # 13
[Workflows and Automation]You renamed a status in the workflow of a team-managed project. Which statement is true?
A. The status will be renamed in all team-managed workflows. B. Workflow rules that reference the status must be updated. C. Transitions coming into that status must be updated. D. Saved filters that reference the status must be updated. E. The status will be renamed on the Status page in Jira administration.
Answer: D
Explanation:
D: Statuses in team-managed projects are unique and localized to that specific project. While Jira handles the
update smoothly within the project's board and workflow connections, any saved JQL filters referencing the old
status name by string text (e.g., status = "Old Name") will break and must be manually updated.
Options A, B, C, and E are incorrect because team-managed settings do not alter global admin settings or other
projects, and internal workflow transitions/rules update themselves automatically
Question # 14
[Workflows and Automation]Peter is building a workflow in his team-managed project. He can add several rules to his workflowexcept for one rule. Identify that rule.
A. Rule to clear the Assignee when closing. B. Rule to reopen Sub-tasks when reopening Stories. C. Rule to ensure only Peter can approve Stories. D. Rule to clear the Description when reopening. E. Rule to ensure only the Reporter can close bugs.
Answer: B
Explanation:
B: Team-managed workflows only allow rules that affect the current issue being transitioned. They lack native
cross-issue rules to automatically update or cascade changes to Sub-tasks based on a parent Story's transition. That requires a global Jira Automation rule.
Options A, C, D, and E are all incorrect because they are standard out-of-the-box team-managed rules (field-clearing
rules or user/role restriction rules) that target the issue currently in the transition.
Question # 15
[Workflows and Automation]You need to create an automation rule as follows:When a Story is updatedIf it is unestimatedComment on its Sub-tasksWhich two rule elements are needed in this rule? (Choose two.)
A. Branch rule on Sub-tasks B. Issue fields condition on whether Story Points is empty C. Related issues condition on Issues in the sprint D. Branch rule on Stories
Answer: A,B
Explanation:
A: A Branch rule on Sub-tasks (Related issues branch) is required to shift the context from the parent Story down to its sub-tasks so the action can post a comment on them.
B: An Issue fields condition is needed to check if the Story Points (or estimation) field is empty, satisfying the
"unestimated" requirement.
Options C and D are incorrect because the rule is already triggered on the Story itself (no need to branch to Stories),
and checking issues in the sprint is irrelevant to the requirement.
Question # 16
[Workflows and Automation]An automation rule is configured as shown:When: Rule is triggered on All commentsIf: Initiator is in DevelopersThen: Transition the issue to DEVELOPMENTIf: Initiator is in ReviewersThen: Transition the issue to REVIEWYou are only in the Reviewers project role. What happens whenyou comment on an issue?
A. The rule does not execute. B. The issue transitions to REVIEW. C. The rule executes but does not perform any actions. D. The issue transitions to DEVELOPMENT.
Answer: B
Explanation:
The rule is triggered on all comments, so it always runs.
Your user is in the Reviewers project role, so the condition “Initiator is in Reviewers” is true.
Therefore, the action “Transition the issue to REVIEW” is executed.
The Developers condition does not apply to you, but that doesn’t stop the rule from continuing—Jira automation
evaluates conditions per branch/action.
Question # 17
[Notifications]A custom notification event must be fired in the workflow transition of a company-managed project.Which element must be configured?
A. Validator B. Transition property C. Condition D. Post function E. Trigger
Answer: D
Explanation: Firing a notification event during a workflow transition requires configuring a Post function
(specifically, the Fire a Generic Event or a custom event post function). Post functions handle all actions that happen
immediately after a transition is executed.
Options A, C, and E are safety checks or automated starters, while Option B stores metadata none of them execute
transition actions.
Question # 18
[Workflows and Automation]You were asked to modify the only workflow in a company-managed project. Which tworequirements can be satisfied using only out-of-box functionality? (Choose two.)
A. Automatically set Due Date based on the issue type. B. Only a subset of project users should be able to create epics. C. Automatically clear Assignee when transitioning to Pending. D. Automatically reassign an issue when Priority is edited. E. Only members of Testers project role can transition to Passed.
Answer: C,E
Explanation:
C: Can be achieved out-of-the-box by adding an Update Issue Field post function to the transition into the
Pending status.
E: Can be achieved out-of-the-box by adding a User Is In Project Role condition to the transition into the Passed
status.
Options A, B, and D are incorrect because they require Jira Automation rules or advanced permission configurations
rather than native workflow transition settings.
Question # 19
[Workflows and Automation]An automation rule should send an email with the issue key in the subject line. Identify the correctsyntax to use in the Send Email action.
A. {{triggerIssue.issuekey}} B. {{issue.key}} C. {{issueKey}} D. {issue.issuekey} E. issue.key
Answer: B
Explanation:
In Jira automation, smart values use double curly braces {{...}} to dynamically insert data into text fields, such as
email subject lines. The standard, built-in smart value context to fetch the key of the current issue being processed by
the rule is exactly {{issue.key}}.
Options A, C, D, and E are incorrect because they either use incorrect object notation (triggerIssue), miss the required
object property formatting (issueKey), use single brackets instead of double curly braces ({issue.issuekey}), or omit the curly braces entirely (issue.key), which would just print the literal text instead of pulling the dynamic issue key.
Question # 20
[System Administration and Administering Jira]Francis needs to manage product subscriptions and billing on his Jira site. What administratorprivileges does Francis definitely need?
A. Organization admin role B. Product admin role for Jira Software C. Administer Jira global permission D. Product admin role for Jira Administration
Answer: A
Explanation:
In Jira Cloud, managing product subscriptions, payments, licenses, and billing is a centralized function handled strictly
at the Atlassian organization layer. Therefore, Francis definitely needs the Organization admin role (often referred to
as Org Admin), which provides the highest level of administrative privilege across an entire Atlassian site, including
direct access to billing administration.
Options B, C, and D are incorrect because product-level administration settings or the Administer Jira global
permission only grant control over application configurations, user groups, and workflows within Jira itself; they do not grant access to the billing platform or the financial management of subscriptions.
Question # 21
[Access, Permissions, Security]Currently, all users in your instance can see all issues in the BRAVO company-managed project. Youreceived these new requirements:Some BRAVO issues should only be visible to managers.Some BRAVO issues should only be visible to supervisors.The remaining BRAVO issues should remain visible to all users.Identify two elements that must beconfigured. (Choose two.)
A. Issue security scheme B. Set Issue Security permission C. Global permissions D. Browse Projects permission E. Administer Projects permission
Answer: A,B
Explanation:
To control the visibility of specific issues within the same project based on user roles (managers, supervisors, and all
users), you must implement an Issue security scheme. This scheme allows you to define distinct security levels for the
different groups. Additionally, you must configure the Set Issue Security permission within the project's permission
scheme so that authorized users have the right to actually apply these security levels to the individual issues.
Options C, D, and E are incorrect because global permissions cannot control issue-level visibility inside a specific project,
the Browse Projects permission is already granted to everyone and cannot selectively hide individual issues on its own, and Administer Projects only grants project management settings rather than issue-specific visibility controls.
Question # 22
[Access, Permissions, Security]On the Bulk Operation screen, Taylor is unable to choose the Delete Issues bulk action. What doesTaylor definitely need?
A. Organization admin privileges B. Jira administration privileges C. Global permissions D. Project permissions E. Project administration privileges
Answer: D
Explanation:
To perform the bulk delete action, Taylor definitely needs specific Project permissions, specifically the Delete Issues
permission for all the projects containing the selected issues. Even if a user has the global permission to perform bulk
changes, Jira enforces individual project-level safety rules, meaning you cannot bulk delete any issue unless you explicitly
hold the right to delete issues within that specific project's permission scheme.
Options A, B, and E are incorrect because deleting individual issues does not require organization, Jira system, or project
administrative privileges. Option C is incorrect because while global permissions grant access to the bulk operation wizard
itself, the specific restriction blocking the "Delete" action inside the menu points directly to a missing project-level
permission.
Question # 23
[Access, Permissions, Security]The Customer Relations team has just been given access to Jira. They can see two projects but not the project boards. They created several advanced searches andwant other project members to see the results. Which permission do they require without receivingtoo much access?
A. Browse Projects B. Share dashboards and filters C. Board administrator D. Administer Jira
Answer: B
Explanation:
To allow the Customer Relations team to share their advanced search results with other project members, they
specifically need the Share dashboards and filters global permission. This permission allows users to change the
visibility of their saved filters from private to shared without granting them any unnecessary administrative or projectlevel editing privileges.
Options A, C, and D are incorrect because the team can already see the projects (meaning they already have the Browse Projects permission), becoming a Board administrator would give them excessive control over board configurations,
and granting Administer Jira would give them complete system-level access, which violates the requirement of not
receiving too much access.
Question # 24
[System Administration and Administering Jira]Jon needs to create groups and manage membership in groups. Which administrator privilege doesJon need?
A. Organization admin B. Product Admin role for Jira C. System administrator D. Jira administrator E. Project administrator
Answer: D
Explanation:
In Jira, the ability to create groups and manage group membership is typically handled by a Jira administrator
(especially in Jira Data Center/Server contexts often used in ACP exams).
Project administrator ? only project-level tasks
Organization admin ? more related to Atlassian organization/user management in Cloud
Jira administrator ? manages users, groups, permissions, and Jira configuration
Question # 25
[Access, Permissions, Security]An excerpt of the DEV permission scheme is shown:Project Permissions|Users / Groups / Project RolesAdminister Projects | Project Role (Administrators)View Development Tools | Project Role (Core), Project Role (Sprint Team)Manage Sprints | Project Role (atlassian-addons-project-access), Project Role (Core)Ahmed is a project administrator in DEV and not a Jira administrator. He is unable to create sprints inDEV. What should Ahmed do?
A. Add himself to the Core project role B. Add himself to the Sprint Team project role C. Add the Administrators project role to the ‘View Development Tools’ permission D. Add the Administrators project role to the ‘Manage Sprints’ permission
Answer: D
Explanation:
Ahmed is already a member of the Administrators project role because he is a project administrator.
However, the Manage Sprints permission is currently granted only to:
atlassian-addons-project-access
Core
Since the Administrators role is not included in Manage Sprints, Ahmed cannot create sprints.
Therefore, the correct fix is to:
Add the Administrators project role to the Manage Sprints permission.
Feedback That Matters: Reviews of Our ATLASSIAN ACP-120 Dumps
Nutan DattaJun 18, 2026
Particularly when it came to Jira workflows and configurations, ACP-120 was very hands-on. Through practice questions and answers, Mycertshub helped me comprehend real-world exam scenarios, which made the concepts much clearer.
Leo JacksonJun 17, 2026
Mycertshub made ACP-120 easier to follow, which surprised me given its level of detail. I was able to familiarize myself with the exam's assessment of Jira admin tasks thanks to the practice questions.
Charles TylerJun 17, 2026
Consistent practice in ACP-120 was what I found to be most effective. I was able to stay focused and perform better on the actual test thanks to the realistic exam questions and answers provided by Mycertshub.
Nutan Datta
Leo Jackson
Charles Tyler