[Q21-Q37] Ultimate Guide to Prepare ACP-120 with Accurate PDF Questions [May 26, 2026]

Ultimate Guide to Prepare ACP-120 with Accurate PDF Questions [May 26, 2026]

Pass ATLASSIAN With Actualtests4sure Exam Dumps

The ACP-120 exam is a cloud-based, multiple-choice exam that consists of 60 questions. ACP-120 exam covers various topics such as Jira Cloud architecture, user management, project configuration, issue types, workflows, and administration. ACP-120 exam is designed to test your understanding of the Jira Cloud platform and your ability to troubleshoot and resolve common issues that may arise during the administration process. Passing the ACP-120 exam validates your expertise in Jira Cloud administration and provides you with an industry-recognized certification that can enhance your career prospects.

ATLASSIAN ACP-120 (Jira Cloud Administrator) Certification Exam is an online, proctored exam that can be taken from anywhere in the world. ACP-120 exam consists of 65 multiple-choice questions that need to be answered within 2 hours. The passing score for the exam is 65%, and the certification is valid for two years. Jira Cloud Administrator certification is an excellent way for professionals to showcase their expertise in Jira Cloud administration and advance their careers in project management.

 

NEW QUESTION # 21
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 make changes to the issue was disabled
• B. The setting Watch your issues was disabled
• C. The setting Email notifications format was changed
• D. The setting You're watching the issue was disabled

Answer: D

NEW QUESTION # 22
You are prompted to perform a re-index after you have made configuration changes to a very large Jira instance.
Which reason would justify re-indexing only a project instead of a full re-index of the instance?

• A. Only project users would be affected by the re-index.
• B. Only custom fields used by the project were modified.
• C. Workflow changes were limited to the project's unique workflow.
• D. Time tracking was modified for the project.

Answer: B

Explanation:
Reference: https://confluence.atlassian.com/adminjiraserver079/search-indexing-950288998.html

NEW QUESTION # 23
No one should be allowed to edit issues in a particular workflow status of a company-managedproject. Which element must be configured?

• A. Trigger
• B. Condition
• C. Post function
• D. Status Property

Answer: D

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 # 24
Francis needs to manage product subscriptions and billing on his Jira site. What administrator privileges does Francis definitely need?

• A. Product admin role for Jira Software
• B. Administer Jira global permission
• C. Organization admin role
• D. Product admin role for Jira Administration

Answer: C

Explanation:
Managing product subscriptions and billing for a Jira site is a task handled at the Atlassian organization level, not within the Jira product itself. Theorganization admin roleis required to perform these actions, as it grants access to billing and subscription management.
* Explanation of the Correct Answer (Option A):
* Theorganization admin roleallows users to manage the Atlassian organization, including product subscriptions, billing, and user access across all products (e.g., Jira Software, Confluence). Francis needs this role to manage subscriptions and billing for the Jira site.
* Exact Extract from Documentation:
Organization admin role
Organization administrators manage the Atlassian organization, including:
* Managing product subscriptions and billing.
* Adding or removing users from the organization.
* Configuring organization-wide settings like security policies.To manage billing:
* Go toadmin.atlassian.com.
* SelectBillingto view and update subscription details.Note: Only organization admins can manage subscriptions and billing. Product admins or Jira admins cannot access these settings.(Source: Atlassian Support Documentation, "Manage your Atlassian organization")
* Why This Fits: Theorganization admin roleis the only role that grants access to billing and subscription management, making Option A the correct choice.
* Why Other Options Are Incorrect:
* Product admin role for Jira Software (Option B):
* Theproduct admin role for Jira Softwareallows users to manage user access and settings specific to Jira Software (e.g., adding users to the product). It does not include access to billing or subscription management, which is handled at the organization level.
* Extract from Documentation:
Product admins for Jira Software manage user access and product-specific settings but cannot manage subscriptions or billing.
(Source: Atlassian Support Documentation, "Manage product access")
* Administer Jira global permission (Option C):
* TheAdminister Jiraglobal permission (Jira administrator role) allows usersto manage Jira- specific settings, such as schemes, workflows, and user groups. It does not grant access to organization-level billing or subscription management.
* Extract from Documentation:
TheAdminister Jirapermission allows managing Jira settings, such as schemes and permissions, but does not include billing or subscription management, which is handled by organization admins.
(Source: Atlassian Support Documentation, "Manage global permissions")
* Product admin role for Jira Administration (Option D):
* There is no distinctproduct admin role for Jira Administrationin Jira Cloud. The term may be confused with theJira administratorrole or product admin role for Jira Software, neither of which grants billing access.
* Extract from Documentation:
Jira Cloud uses roles like Jira administrator and product admin for Jira Software. Billing and subscriptions are managed by organization admins, not product-specific roles.
(Source: Atlassian Support Documentation, "Manage your Atlassian organization")
* Additional Notes:
* Francis must accessadmin.atlassian.comto manage subscriptions and billing, which requires the organization admin role.
* Other roles (e.g., Jira administrator) may be involved in configuring Jira settings but are irrelevant for billing tasks.
:
Atlassian Support Documentation:Manage your Atlassian organization
Atlassian Support Documentation:Manage product access
Atlassian Support Documentation:Manage global permissions

NEW QUESTION # 25
Currently, the 'Affects Version/s' field is populated on issues in a particular company-managed project. Now, you want to hide it when viewing issues and to hide its values when viewing filter results. Where would you go to make the change?

• A. Issue detail view
• B. Custom field context
• C. Screen
• D. Field configuration
• E. Issue layout

Answer: E

Explanation:
To hide theAffects Version/sfield when viewing issues and in filter results in a company-managed project, you need to configure theissue layout(Option E). The issue layout determines which fields are displayed or hidden in the issue view and affects how fields appear in filter results.
* Explanation of the Correct Answer (Option E):
* Theissue layoutin a company-managed project controls the visibility and arrangement of fields in the issue view (when viewing an issue) and influences how fields are displayed in filter results (e.
g., in issue navigator or boards). To hide theAffects Version/sfield, you can move it to the Hidden fieldssection in the issue layout. This ensures the field is not shown in the issue view or filter results, even if it contains values.
* Exact Extract from Documentation:
Configure issue layouts in company-managed projects
Issue layouts define which fields are displayed, hidden, or placed in the context panel when viewing issues.
They also influence field visibility in filter results.
To hide a field:
* Go toProject settings > Issue layout.
* Select the issue type or screen to configure.
* Move the field (e.g., Affects Version/s) to theHidden fieldssection.Note: Hiding a field in the issue layout does not remove it from screens used for Create or Edit operations, but it prevents it from appearing in the issue view and filter results.(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud")
* Why This Fits: Theissue layoutdirectly controls field visibility in the issue viewand filter results, making it the correct place to hide theAffects Version/sfield, satisfying both requirements.
* Why Other Options Are Incorrect:
* Issue detail view (Option A):
* Theissue detail viewis part of the issue view interface and is not a configuration setting. It is affected by the issue layout but cannot be directly modified to hide fields.
* Extract from Documentation:
The issue detail view displays fields based on the issue layout configuration. To hide fields, configure the issue layout inProject settings > Issue layout.
(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud")
* Field configuration (Option B):
* Field configurationscontrol whether fields are required, optional, or hidden for specific issue types. Hiding a field in a field configuration removes it from all operations (Create, Edit, View), which would preventAffects Version/sfrom being populated at all. The requirement is to hide the field only when viewing and in filter results, not to remove it entirely, so field configuration is not suitable.
* Extract from Documentation:
Hiding a field in a field configuration removes it from all screens and operations. Use issue layouts to hide fields in the issue view and filter results.
(Source: Atlassian Support Documentation, "Configure field settings")
* Custom field context (Option C):
* Custom field contextsdefine the options and default values for a custom field across projects or issue types. TheAffects Version/sfield is a system field, not a custom field, and contexts do not control field visibility in the issue view or filter results.
* Extract from Documentation:
Custom field contexts apply to custom fields and manage options, not visibility. System fields likeAffects Version/sare not affected by contexts.
(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")
* Screen (Option D):
* Screensdetermine which fields appear during issue operations (Create, Edit, View).
RemovingAffects Version/sfrom a screen would affect Create or Edit operations, not just viewing, and would not specifically hide the field in filter results. The issue layout is the correct place for view-specific changes.
* Extract from Documentation:
Screens control fields for Create, Edit, and View operations. To hide fields in the issue view and filter results, use the issue layout.
(Source: Atlassian Support Documentation, "Configure screens in Jira Cloud")
* Additional Notes:
* Configuring the issue layout requiresproject adminprivileges and is done inProject settings > Issue layout.
* HidingAffects Version/sin the issue layout does not remove its values from the database; it only prevents display in the issue view and filter results.
* Ensure the field remains on relevant screens for Create/Edit if it needs to continue being populated.
:
Atlassian Support Documentation:Configure issue layouts in Jira Cloud
Atlassian Support Documentation:Configure field settings
Atlassian Support Documentation:Manage custom fields in Jira Cloud
Atlassian Support Documentation:Configure screens in Jira Cloud

NEW QUESTION # 26
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 Update Issue Field workflow post function
• B. An Assign to Lead Developer workflow post function
• C. The Default Assignee project setting
• D. The CC Assignee setting of the mail handler

Answer: C

NEW QUESTION # 27
Level custom field contains three options: Beginner, Intermediate, Advanced Pro. You need to find issues in any of the levels. Identify the correct JQL query.

• A. Level = Beginner OR Level = Intermediate OR Level = Advanced Pro
• B. Level ~ (Beginner, Intermediate, "Advanced Pro")
• C. Level IN (Beginner, Intermediate, "Advanced Pro")
• D. Level IN (Beginner, Intermediate OR Advanced Pro)

Answer: C

Explanation:
To find issues where theLevelcustom field (a single-select field) has any of the valuesBeginner,Intermediate
, orAdvanced Pro, the JQL query must use theINoperator to check for multiple values. The correct query is Level IN (Beginner, Intermediate, "Advanced Pro")(Option B), as it properly handles the multi-word value Advanced Prowith quotes.
* Explanation of the Correct Answer (Option B):
* TheLevelcustom field is a single-select field with three options:Beginner,Intermediate, and Advanced Pro. TheINoperator allows checking if a field's value matches any of a list of values.
For multi-word values likeAdvanced Pro, quotes are required to treat it as a single value.
* The queryLevel IN (Beginner, Intermediate, "Advanced Pro")searches for issues where the Levelfield is set toBeginner,Intermediate, orAdvanced Pro, covering all possible values.
* Exact Extract from Documentation:
Advanced searching - operators reference
TheINoperator checks if a field's value matches any of the specified values.
Example:
* Level IN (Beginner, Intermediate, "Advanced Pro") returns issues where theLevelfield is set toBeginner,Intermediate, orAdvanced Pro.Note: For values containing spaces (e.g., Advanced Pro), enclose the value in double quotes.(Source: Atlassian Support Documentation, "Advanced searching - operators reference")
* Why This Fits: TheINoperator with properly quoted values efficiently searches for all specified Leveloptions, making Option B the correct answer.
* Why Other Options Are Incorrect:
* Level = Beginner OR Level = Intermediate OR Level = Advanced Pro (Option A):
* This query is functionally correct but less efficient than usingIN. It requires multiple= operators and does not handle the multi-word valueAdvanced Procorrectly without quotes, potentially causing a syntax error.
* Extract from Documentation:
UseINfor concise queries with multiple values. MultipleORclauses are valid but less efficient and require quotes for multi-word values.
(Source: Atlassian Support Documentation, "Advanced searching - operators reference")
* Level ~ (Beginner, Intermediate, "Advanced Pro") (Option C):
* The~operator is used for partial text matching (e.g., wildcard searches) and is not valid for single-select fields likeLevel, which require exact value matching. This query is syntactically incorrect.
* Extract from Documentation:
The~operator is for text fields and partial matching, not for select fields. Use=orINfor exact value matching.
(Source: Atlassian Support Documentation, "Advanced searching - operators reference")
* Level IN (Beginner, Intermediate OR Advanced Pro) (Option D):
* This query is syntactically incorrect, as theINoperator requires a comma-separated list of values, not logical operators likeOR. Additionally,Advanced Proneeds quotes to be treated as a single value.
* Extract from Documentation:
TheINoperator requires a list of values (e.g., (value1, value2, "value3")). Logical operators likeORare not allowed insideIN.
(Source: Atlassian Support Documentation, "Advanced searching - operators reference")
* Additional Notes:
* TheLevelfield must be a single-select custom field with the exact options listed.Verify the field's configuration inSettings > Issues > Custom fields.
* The query can be tested inIssues > Search for issuesand saved as a filter.
* Ensure the user hasBrowse Projectspermission for the relevant projects.
:
Atlassian Support Documentation:Advanced searching - operators reference Atlassian Support Documentation:Search for issues using JQL

NEW QUESTION # 28
You need to find unresolved issues assigned to suspended users. Identify the correct JQL query.

• A. resolution is EMPTY AND assignee in inactiveUsers()
• B. resolution = EMPTY AND assignee not in membersOf("jira-software-users")
• C. statusCategory = Done AND assignee not in activeUsers()
• D. resolution = Unresolved AND assignee changed to inactive
• E. statusCategory != Done AND assignee not in organizationMembers()

Answer: A

Explanation:
To find unresolved issues assigned to suspended users in Jira Software Cloud, the JQL query must check for issues with no resolution (unresolved) and an assignee who is inactive (suspended). The correct query is resolution is EMPTY AND assignee in inactiveUsers()(Option A), as it uses the appropriate field ( resolution) and function (inactiveUsers()) to identify these issues.
* Explanation of the Correct Answer (Option A):
* Unresolved issues: In Jira, an issue is considered unresolved if itsresolutionfield is empty (i.e., not set to Resolved, Done, or similar). The JQL clauseresolution is EMPTYidentifies unresolved issues.
* Suspended users: Suspended users are those whose accounts are inactive (e.g., deactivated or removed from the organization). TheinactiveUsers()function returns all inactive users in the Jira instance. The clauseassignee in inactiveUsers()filters for issues assigned to these users.
* Combined query:resolution is EMPTY AND assignee in inactiveUsers()returns all unresolved issues assigned to inactive users.
* Exact Extract from Documentation:
Search for issues using JQL
* resolution is EMPTY: Finds issues with no resolution set (unresolved issues).
* assignee in inactiveUsers(): Finds issues assigned to users who are inactive (e.g., deactivated or suspended).Example:
* resolution is EMPTY AND assignee in inactiveUsers() returns unresolved issues assigned to inactive users.Note: TheinactiveUsers()function is specific to Jira Cloud and includes users who are no longer active in the instance.(Source: Atlassian Support Documentation,
"Advanced searching - functions reference")
* Why This Fits: The query correctly usesresolution is EMPTYfor unresolved issues and inactiveUsers()for suspended users, making Option A the correct answer.
* Why Other Options Are Incorrect:
* statusCategory != Done AND assignee not in organizationMembers() (Option B):
* statusCategory != Donechecks the status category (e.g., To Do, In Progress) but is less precise thanresolution is EMPTY, as some statuses in non-Done categories may still be resolved.assignee not in organizationMembers()is incorrect, asorganizationMembers() is not a valid JQL function in Jira Cloud, and it would not specifically target inactive users.
* Extract from Documentation:
statusCategory != Doneis broader thanresolution is EMPTYand may include resolved issues. No organizationMembers()function exists in JQL.
(Source: Atlassian Support Documentation, "Advanced searching - fields reference")
* resolution = Unresolved AND assignee changed to inactive (Option C):
* resolution = Unresolvedis incorrect, asUnresolvedis not a valid resolution value; use resolution is EMPTYinstead.assignee changed to inactiveis invalid, aschanged to inactiveis not a supported JQL operator for theassigneefield.
* Extract from Documentation:
Useresolution is EMPTYfor unresolved issues. Thechangedoperator does not supportinactiveas a value for assignee.
(Source: Atlassian Support Documentation, "Advanced searching - operators reference")
* statusCategory = Done AND assignee not in activeUsers() (Option D):
* statusCategory = Doneis the opposite of what is needed, as it selects resolved or completed issues, not unresolved ones.assignee not in activeUsers()might include inactive users but is less precise thaninactiveUsers(), and thestatusCategoryclause makes the query incorrect.
* Extract from Documentation:
statusCategory = Doneselects issues in completed statuses, not unresolved issues. UseinactiveUsers()for precise inactive user filtering.
(Source: Atlassian Support Documentation, "Advanced searching - fields reference")
* resolution = EMPTY AND assignee not in membersOf("jira-software-users") (Option E):
* resolution = EMPTYis correct, butassignee not in membersOf("jira-software-users")is incorrect, asjira-software-usersis a default group for active users with Jira Software access, not a reliable indicator of suspended users. This would exclude active users in the group, not specifically target inactive ones.
* Extract from Documentation:
ThemembersOf()function checks group membership, not user activity status. UseinactiveUsers()to find suspended or deactivated users.
(Source: Atlassian Support Documentation, "Advanced searching - functions reference")
* Additional Notes:
* The query can be tested inIssues > Search for issuesand saved as a filter if needed.
* inactiveUsers()is specific to Jira Cloud and includes users who are deactivated or removed from the organization.
* Ensure the user running the query hasBrowse Projectspermission for the relevantprojects.
:
Atlassian Support Documentation:Advanced searching - functions reference Atlassian Support Documentation:Advanced searching - fields reference Atlassian Support Documentation:Advanced searching - operators reference Atlassian Support Documentation:Search for issues using JQL

NEW QUESTION # 29
Which three statements are correct about deleting a user account (Choose three)

• A. Access to all products and administration functions will be lost
• B. Issues that were created by a deleted account will be deleted
• C. Accounts can only be deleted if they have no issues assigned
• D. Individual users can delete their unmanaged accounts
• E. Organization admins can delete managed accounts

Answer: A,D,E

NEW QUESTION # 30
An issue is showing the Time Tracking section as follows:

There is clearly an hour's difference between the Original and Remaining estimates. Identify two possible reasons Logged Time is showing as Not Specified. (Choose two.)

• A. You do not have view permission to see the logged work.
• B. The remaining estimate was adjusted without logging any effort.
• C. The work log would have exceeded the project's time allowance, so it cannot be counted.
• D. Time tracking was not enabled when the work was logged.
• E. The hour's work was logged via a REST call by the user.
• F. The original estimate was increased.

Answer: B,D

Explanation:
Reference: https://confluence.atlassian.com/adminjiraserver/configuring-time-tracking-938847808.html

NEW QUESTION # 31
Tom has asked you why the numbers returned by his searches are not right.
He shows you three JQL queries:

How can you fix this?

• A. Change the query to project = "Cake Baking" and fixVersion ~ 1.1.0.
• B. Change the query to project = "Cake Baking" and fixVersion not in (1.1.0).
• C. Identify the missing issues and change the permissions so that everyone can see them.
• D. Rename the versions so they do not contain periods.
• E. Change the query to project = "Cake Baking" and ( fixVersion is empty or fixVersion != 1.1.0 ).

Answer: C

NEW QUESTION # 32
In project ENG, components are configured as shown:

The Default Assignee for ENG is the Project Lead. You select all four components on a new issue and leave Assignee as Automatic. To whom will the issue be assigned?

• A. Project Lead
• B. User 3
• C. User 2
• D. User 1
• E. Unassigned
• F. User 4

Answer: A

Explanation:
In Jira Software Cloud, theAssigneefield for a new issue can be set toAutomatic, in which case Jira determines the assignee based on the project'sDefault Assigneesetting and any component-specificDefault Assigneesettings. The issue in the ENG project has all four components selected (Activation, Bin, Cart, Database), and the Assignee is left asAutomatic. The issue will be assigned to theProject Lead(Option E) due to the rules for handling multiple components with conflicting default assignees.
* Explanation of the Correct Answer (Option E):
* Project Default Assignee: The project ENG has itsDefault Assigneeset to theProject Lead, meaning that if no component-specific assignee is determined, the issue will be assigned to the Project Lead.
* Component Default Assignees:
* Activation: Default Assignee isComponent lead(User 1).
* Bin: Default Assignee isProject default(Project Lead).
* Cart: Default Assignee isComponent lead(User 3).
* Database: Default Assignee isUnassigned.
* Automatic Assignment Logic with Multiple Components: When an issue has multiple components selected, Jira evaluates theDefault Assigneefor each component:
* If all components have the same default assignee, that user is assigned.
* If components have different default assignees (or some are unassigned), Jira falls back to the project'sDefault Assignee(Project Lead in this case).
* In this scenario:
* Activationassigns to User 1.
* Binassigns to the Project Lead (via project default).
* Cartassigns to User 3.
* Databaseassigns to Unassigned.
* Since the components have conflicting default assignees (User 1, Project Lead, User 3, Unassigned), Jira cannot resolve to a single assignee and uses the project'sDefault Assignee, which is theProject Lead.
* Exact Extract from Documentation:
Configure default assignees
TheDefault Assigneefor a project or component determines who is assigned to new issues when theAssignee field is set toAutomatic.
Multiple components:
* If an issue has multiple components with different default assignees, Jira assigns the issue to the project'sDefault Assignee.To configure:
* Go toProject settings > Componentsto set component default assignees.
* Go toProject settings > Detailsto set the project'sDefault Assignee.Note: The project's Default Assigneeis used when component assignees conflict.(Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")
* Why This Fits: With conflicting default assignees across the four components, Jira assigns the issue to the project'sDefault Assignee, which is theProject Lead, making Option E the correct answer.
* Why Other Options Are Incorrect:
* User 1 (Option A):
* User 1 is the default assignee for theActivationcomponent (as the Component lead).
However, with multiple components selected and different assignees (User 1, Project Lead, User 3, Unassigned), Jira falls back to the project'sDefault Assignee(Project Lead), not User 1.
* Extract from Documentation:
If multiple components have different default assignees, the project'sDefault Assigneeis used, not a component-specific assignee.
(Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")
* User 2 (Option B):
* User 2 is the Component lead forBin, but the default assignee forBinis set toProject default(Project Lead), not the Component lead. Even if it were User 2, the conflicting assignees across components would result in the Project Lead being assigned.
* Extract from Documentation:
TheProject defaultsetting for a component assigns issues to the project'sDefault Assignee, not the Component lead.
(Source: Atlassian Support Documentation, "Manage components in Jira Cloud")
* User 3 (Option C):
* User 3 is the default assignee for theCartcomponent (as the Component lead). However, the conflicting assignees across components (User 1, Project Lead, User 3, Unassigned) result in the Project Lead being assigned, not User 3.
* Extract from Documentation:
Conflicting component assignees result in the project'sDefault Assigneebeing used.
(Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")
* User 4 (Option D):
* User 4 is the Component lead forDatabase, but the default assignee forDatabaseis Unassigned, not User 4. Even if it were User 4, the conflicting assignees would result in the Project Lead being assigned.
* Extract from Documentation:
TheUnassigneddefault assignee for a component does not override the project'sDefault Assigneein conflicts.
(Source: Atlassian Support Documentation, "Manage components in Jira Cloud")
* Unassigned (Option F):
* While theDatabasecomponent has a default assignee ofUnassigned, the presence of other components with different assignees (User 1, Project Lead, User 3) creates a conflict, and Jira assigns the issue to the Project Lead, notUnassigned.
* Extract from Documentation:
Unassignedas a default assignee is overridden by the project'sDefault Assigneein cases of conflict.
(Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")
* Additional Notes:
* TheDefault Assigneefor the project is set inProject settings > Details, and component-specific default assignees are set inProject settings > Components.
* The user creating the issue must have theAssign Issuespermission, and the Project Lead must have theAssignable Userpermission to be assigned.
* If only one component were selected (e.g., Activation), the issue would be assigned to User 1, but selecting all four components triggers the conflict resolution to the Project Lead.
:
Atlassian Support Documentation:Manage project settings in Jira Cloud
Atlassian Support Documentation:Manage components in Jira Cloud
Atlassian Support Documentation:Manage permissions in Jira Cloud

NEW QUESTION # 33
Christian has a saved filter showing bugs that have not been updated in the past two weeks. He plans to run a bulk operation to change the priority to Highest on all the issues in the filter. Identify one definite outcome of this action.

• A. Christian will be added as a watcher on all the edited issues.
• B. Email notifications will be sent during the bulk operation.
• C. The saved filter will display no issues.
• D. Filter subscriptions based on the filter will stop sending emails.

Answer: C

Explanation:
Christian's saved filter shows bugs that have not been updated in the past two weeks, likely using a JQL query like issuetype = Bug AND updated <= -2w. Running a bulk operation to change the priority toHigheston all issues in the filter will update the issues, affecting theirupdatedtimestamp. The definite outcome is thatthe saved filter will display no issues(Option A), as the issues will no longer meet the filter's criteria after being updated.
* Explanation of the Correct Answer (Option A):
* The saved filter likely uses a JQL query such as issuetype = Bug AND updated <= -2w, which returns bugs not updated in the past two weeks (i.e., updated timestamp is older than two weeks).
When Christian performs a bulk operation to change the priority toHighest, each issue'supdated timestamp is set to the current time, as any edit (including priority changes) updates this field.
After the operation, all issues in the filter will have a recentupdatedtimestamp (e.g., within the last few minutes), causing them to no longer satisfy the updated <= -2w condition. As a result, the filter will return no issues.
* Exact Extract from Documentation:
Bulk change issues
Bulk operations (e.g., changing priority) update issue fields and metadata, including theupdatedtimestamp.
Impact on filters:
* If a filter uses a condition like updated <= -2w, updating issues will change theirupdated timestamp, potentially excluding them from the filter.To perform a bulk change:
* Run a filter inIssues > Search for issues.
* SelectBulk changeand choose an action (e.g., Edit Issues).
* Update fields (e.g., Priority to Highest).Note: Bulk changes trigger theIssue Updatedevent, updating theupdatedfield.(Source: Atlassian Support Documentation, "Bulk change issues in Jira Cloud")
* Why This Fits: The bulk operation updates theupdatedtimestamp of all issues, causing them to no longer meet the filter's updated <= -2w condition, resulting in the filter displaying no issues, making Option A the definite outcome.
* Why Other Options Are Incorrect:
* Filter subscriptions based on the filter will stop sending emails (Option B):
* Filter subscriptions send emails based on the filter's results and schedule (e.g., daily, weekly). The bulk operation does not disable the subscription or change its configuration; it only affects the filter's results. If the filter returns no issues after the operation, the subscription will send an email with no results, but it will not stop sending emails entirely.
* Extract from Documentation:
Filter subscriptions send emails based on the filter's results and schedule. Empty results do not stop the subscription; they result in an empty email.
(Source: Atlassian Support Documentation, "Manage filters in Jira Cloud")
* Christian will be added as a watcher on all the edited issues (Option C):
* Adding a watcher during a bulk operation is not automatic. Users are not added as watchers unless explicitly included in the bulk operation (e.g., via anAdd Watcheraction, which is not part of changing priority). Christian's user settings or automation rules could theoretically add him as a watcher, but this is not a definite outcome of the priority change.
* Extract from Documentation:
Bulk operations do not automatically add the user as a watcher. Use theAdd Watcheraction in abulk operation to add watchers explicitly.
(Source: Atlassian Support Documentation, "Bulk change issues in Jira Cloud")
* Email notifications will be sent during the bulk operation (Option D):
* Email notifications for theIssue Updatedevent (triggered by the priority change) depend on the project'snotification schemeand the recipients configured for the event (e.g., watchers, assignee). Notifications are not guaranteed, as they may be disabled or limited to specific users. Thus, this is not a definite outcome.
* Extract from Documentation:
Bulk operations trigger theIssue Updatedevent, but notifications depend on the notification scheme and may not be sent if not configured.
(Source: Atlassian Support Documentation, "Configure notification schemes")
* Additional Notes:
* The bulk operation requires Christian to have theEdit Issuespermission for the issues in the filter.
* The filter's JQL query (e.g., issuetype = Bug AND updated <= -2w) can be verified inIssues > Manage filters.
* To avoid impacting the filter, Christian could modify the JQL to exclude recently updated issues or create a temporary filter for the bulk operation.
:
Atlassian Support Documentation:Bulk change issues in Jira Cloud
Atlassian Support Documentation:Manage filters in Jira Cloud
Atlassian Support Documentation:Configure notification schemes

NEW QUESTION # 34
Which statement is correct regarding Jira Cloud import and export features?

• A. Jira admins can create backup files.
• B. Project admins can import their own projects.
• C. Org admins can restore overwritten backups.
• D. Jira admins can import backup files.
• E. Project admins can create site backups.

Answer: A

Explanation:
Jira Cloud's import and export features allow administrators to back up, restore, or migrate data. The correct statement is thatJira admins can create backup files(Option A), as this is a supported function for Jira administrators.
* Explanation of the Correct Answer (Option A):
* Jira administrators have the ability to create backup files for a Jira Cloud site, which include issues, configurations, users, and media (e.g., attachments). These backups can be used for restoration or migration purposes.
* Exact Extract from Documentation:
Create a backup for Jira Cloud
Jira administrators can create backup files that include issues, configurations, users, and media.
To create a backup:
* Go toSettings > System > Backup manager.
* SelectCreate backup for cloud.
* Download the backup file when ready.Note: Requires Jira administrator permissions.
Backup files can be used for restoration or migration.(Source: Atlassian Support Documentation, "Back up Jira Cloud data")
* Why This Fits: The ability to create backup files is explicitly granted to Jira admins, making Option A the correct statement.
* Why Other Options Are Incorrect:
* Org admins can restore overwritten backups (Option B):
* Organization admins manage Atlassian organization settings (e.g., billing, user access) but do not have direct access to Jira-specific backup restoration. Restoring backups, including overwritten ones, is handled byJira administratorsorsupport requeststo Atlassian.
Overwritten backups cannot typically be restored without Atlassian intervention.
* Extract from Documentation:
Organization admins manage organization-level settings. Restoring backups, including overwritten ones, requires Jira administrator permissions or Atlassian support.
(Source: Atlassian Support Documentation, "Manage your Atlassian organization")
* Project admins can import their own projects (Option C):
* Project admins can manage project settings (e.g., permissions, issue types) but do not have permissions to import projects or data, as this is a system-level action reserved forJira administrators.
* Extract from Documentation:
Importing projects or data requires Jira administrator permissions. Project admins cannot perform imports.
(Source: Atlassian Support Documentation, "Import data to Jira Cloud")
* Project admins can create site backups (Option D):
* Creating site backups is a system-level action restricted toJira administrators. Project admins lack the permissions to create backups for the entire site or their projects.
* Extract from Documentation:
Only Jira administrators can create site backups inSettings > System > Backup manager. Project admins do not have this capability.
(Source: Atlassian Support Documentation, "Back up Jira Cloud data")
* Jira admins can import backup files (Option E):
* While Jira admins can initiate the import process for backup files, the actual import of full site backups typically requiresAtlassian supportor is performed through specific tools (e.
g.,Import Jira Cloudfeature). Partial imports (e.g., CSV, Trello) are supported, but full backup imports are not a standard Jira admin action without additional steps. This makes the statement less definitively correct compared to Option A.
* Extract from Documentation:
Importing full site backups often requires Atlassian support. Jira admins can import partial data (e.g., CSV, JSON) but not full backups directly.
(Source: Atlassian Support Documentation, "Restore your Jira Cloud site from a backup")
* Additional Notes:
* Creating a backup is a straightforward action for Jira admins inSettings > System > Backup manager.
* The backup process requiresJira administratorprivileges, not project admin or organization admin roles.
* Full backup imports or restoration of overwritten backups typically involve Atlassian support, limiting the scope of Jira admin actions.
:
Atlassian Support Documentation:Back up Jira Cloud data
Atlassian Support Documentation:Restore your Jira Cloud site from a backup Atlassian Support Documentation:Import data to Jira Cloud Atlassian Support Documentation:Manage your Atlassian organization

NEW QUESTION # 35
Your Jira has 25,000 active users across the globe using 100 projects with over a million issues.
Another administrator has made a change to a field configuration scheme and you now need to re-index Jira.
What would be the impact of rebuilding the index in the foreground?

• A. Database backups cannot be run until the re-indexing is complete.
• B. The configuration change will not be applied until re-indexing is complete.
• C. Searches using the field may show erroneous results.
• D. Issues will take longer to display during the re-index.
• E. All users will be locked out of Jira until re-indexing completes.

Answer: B

NEW QUESTION # 36
Some of your project owners would like to make their projects publicly accessible over the Internet.
These projects will not require login.
You could support this by allowing read-only anonymous access to the projects.
Which two additional factors should you take into consideration when setting this up? (Choose two.)

• A. Anonymous users could export all issues from Jira.
• B. Anonymous users could see other users' names.
• C. Internet search engines could index data.
• D. Spam bots could add comments.
• E. Anonymous users could find a full list of all your projects.
• F. Licensed users might accidentally comment anonymously rather than logging in first.

Answer: A,C

NEW QUESTION # 37
......

ATLASSIAN ACP-120 certification exam is an important certification for Jira Cloud administrators who want to demonstrate their expertise and advance their careers. ACP-120 exam covers a range of topics related to Jira Cloud administration and is recognized by many companies around the world. Individuals who pass the exam will receive a digital badge and a certificate from ATLASSIAN, which can be used to showcase their skills and knowledge in Jira Cloud administration.

 

Latest ACP-120 Exam Dumps - Valid and Updated Dumps: https://examtorrent.actualtests4sure.com/ACP-120-practice-quiz.html