• Home
  • Blogs
  • ACP-120 Dumps To Pass Jira Administrator Exam in One Day (Updated 77 Questions) [Q11-Q30]

ACP-120 Dumps To Pass Jira Administrator Exam in One Day (Updated 77 Questions) [Q11-Q30]

Share

ACP-120 Dumps To Pass Jira Administrator Exam in One Day (Updated 77 Questions)

ACP-120 Exam Brain Dumps - Study Notes and Theory


ATLASSIAN ACP-120 (Jira Cloud Administrator) Exam is designed to test the skills and knowledge of individuals who are responsible for administering Jira Cloud, a popular project management software. ACP-120 exam is designed to assess the candidate's ability to configure and maintain Jira Cloud, as well as their understanding of various Jira Cloud features.

 

NEW QUESTION # 11
Two projects were created as follows:
* OPS1: Created from the Procurement project template.
* OPS2: Created from the Process Control project template.You need to create project OPS3. You want it to have the same components as OPS1 but the same schemes as OPS2. How should OPS3 be created?

  • A. With a shared configuration with OPS2 from the Procurement project template
  • B. With a shared configuration with OPS1 from the Process Control project template

Answer: A

Explanation:
Requirements for OPS3:
* Same Components as OPS1:Components are configurationswithina project, not typically part of the shared scheme setup during creation.
* Same Schemes as OPS2:Schemes (Workflow Scheme, Issue Type Scheme, Screen Schemes, Field Configuration Scheme, Permission Scheme, etc.) define the core configuration and behavior of a project.
How Project Creation Options Work:
* Creating from a Template:Sets up a project with anew setof schemes and configurations based on the chosen template. The new project doesnotinitially share schemes with any other project.
* Creating with Shared Configuration:When you create a project and choose "Share settings with an existing project" (e.g., share with OPS2), the new project (OPS3) uses theexact same scheme objectsas the existing project (OPS2). Changes to these schemes will affect both projects. This is the mechanism to ensure OPS3 has the same schemes as OPS2.
Analyzing the Options:
* with a shared configuration with OPS1 from the Process Control project template
* Shared configuration with OPS1: This would give OPS3 the sameschemesas OPS1. This contradicts Requirement 2 (needs schemes from OPS2).
* from the Process Control project template: Choosing a template is generally an alternative to sharing configuration. If you share configuration, the template choice is irrelevant for the schemes. This part makes the option confusing, but the core action (sharing with OPS1) is incorrect based on the scheme requirement.
* with a shared configuration with OPS2 from the Procurement project template
* Shared configuration with OPS2: This would give OPS3 the sameschemesas OPS2. Thissatisfies Requirement 2.
* from the Procurement project template: As above, the template choice is confusing when sharing configuration. However, the critical action (sharing schemes with OPS2) aligns with the requirement.
Addressing the Component Requirement:
Neither "creating from a template" nor "creating with shared configuration" will automatically copy the Componentsfrom OPS1 to OPS3. Components need to be set up manually within the OPS3 project after it has been created.
Conclusion:
To meet the requirement of having the sameschemesas OPS2, youmustcreate OPS3 using the "Share settings with an existing project" option and select OPS2. Option B correctly specifies sharing the configuration with OPS2.
The mention of the template in Option B is likely extraneous or indicates a slightly flawed understanding in the question's options, but the core part "shared configuration with OPS2" is thecorrect action to satisfy the scheme requirement. The component requirement must be handled separately after project creation.
Therefore, the correct approach described in the options is:
with a shared configuration with OPS2 from the Procurement project template


NEW QUESTION # 12
Peter is building a workflow in his team-managed project. He can add several rules to his workflow except for one rule. Identify that rule.

  • A. Rule to ensure only Peter can approve Stories.
  • B. Rule to clear the Description when reopening.
  • C. Rule to clear the Assignee when closing.
  • D. Rule to reopen Sub-tasks when reopening Stories.
  • E. Rule to ensure only the Reporter can close bugs.

Answer: D

Explanation:
In team-managed projects, workflows are simplified and configured withinProject settings > Workflow.
Users (typically project admins) can add rules to transitions, such as clearing fields, restricting transitions, or setting field values. However, team-managed workflows do not support complex automation-like rules, such as automatically reopening Sub-tasks when a Story is reopened, as this requires interacting with related issues (Sub-tasks), which is not supported out-of-box in team-managed workflow rules.
* Explanation of the Correct Answer (Option B):
* The rule toreopen Sub-tasks when reopening Storiesrequires a workflow rule to detect the transition of a Story to an open status and then automatically transition its Sub-tasks to an open status. Team-managed workflows do not support rules that affect related issues (e.g., Sub-tasks) during a transition. This functionality requires Jira automation or a company-managed project workflow with custom post functions, which are not available in team-managed projects.
* Exact Extract from Documentation:
Configure workflows in team-managed projects
Team-managed projects use simplified workflows that allow adding rules to transitions, such as:
* Restricting transitions to specific users or roles.
* Setting or clearing field values (e.g., Assignee, Description).
* Requiring fields to be filled.Rules are limited to the issue being transitioned and cannot affect related issues (e.g., Sub-tasks, Epics). To automate actions on related issues, use Jira automation rules.Note: Team-managed workflows are project-specific and edited inProject settings > Workflow.(Source: Atlassian Support Documentation, "Configure workflows in team-managed projects")
* Why This Fits: The rule to reopen Sub-tasks requires interacting with related issues (Sub-tasks), which is beyond the capabilities of team-managed workflow rules, making Option B the correct answer.
* Why Other Options Are Incorrect:
* Rule to clear the Assignee when closing (Option A):
* Team-managed workflows support rules to clear fields during a transition. A rule can be added to the transition to theClosedstatus to clear theAssigneefield.
* Extract from Documentation:
You can add a rule to a transition to clear a field, such as Assignee, when moving to a status like Closed.
(Source: Atlassian Support Documentation, "Configure workflows in team-managed projects")
* Rule to ensure only Peter can approve Stories (Option C):
* Team-managed workflows allow restricting transitions to specific users or roles. A rule can be added to the transition to anApprovedstatus to allow only Peter to perform it.
* Extract from Documentation:
Add a rule to restrict a transition to a specific user (e.g., Peter) or role, ensuring only they can move issues to a status like Approved.
(Source: Atlassian Support Documentation, "Configure workflows in team-managed projects")
* Rule to clear the Description when reopening (Option D):
* Team-managed workflows support clearing fields during transitions. A rule can be added to the transition to anOpenstatus to clear theDescriptionfield.
* Extract from Documentation:
Rules can clear fields like Description during a transition, such as when reopening an issue.
(Source: Atlassian Support Documentation, "Configure workflows in team-managed projects")
* Rule to ensure only the Reporter can close bugs (Option E):
* Team-managed workflows allow restricting transitions to specific users, including the Reporter. A rule can be added to the transition to theClosedstatus for bugs to allow only the Reporter to perform it.
* Extract from Documentation:
Restrict a transition to the Reporter to ensure only they can move issues to a status like Closed.
(Source: Atlassian Support Documentation, "Configure workflows in team-managed projects")
* Additional Notes:
* Team-managed workflows are designed for simplicity, with rules limited to the issue being transitioned. Complex logic, such as affecting Sub-tasks (Option B), requires Jira automation rules, which are separate from workflow rules.
* Peter, as a project admin in a team-managed project, can edit the workflow inProject settings > Workflow.
:
Atlassian Support Documentation:Configure workflows in team-managed projects Atlassian Support Documentation:Automate your Jira Cloud instance


NEW QUESTION # 13
You are designing a complex new workflow. Two of the requirements are listed below:
1. Any user should be able to trigger the Put On Hold transition from any status in the workflow.
2. Only users with the Close Issues permission should be able to Close the issue at any point in the flow.
Based only on these requirements, which two workflow elements should you use? (Choose two.)

  • A. Global Transitions
  • B. Triggers
  • C. Conditions
  • D. Validators
  • E. Common Transitions

Answer: B,C

Explanation:
Reference: https://confluence.atlassian.com/adminjiracloud/working-with-workflows-776636540.html


NEW QUESTION # 14
Your company will migrate to Jira. You plan to import with a CSV file.
Which fields are required as CSV columns for your import?

  • A. Project
  • B. Project, Issue Type
  • C. Summary, Issue Type
  • D. Project, Summary
  • E. Summary

Answer: E

Explanation:
Explanation: Each CSV file must possess a heading row with a Summary column Reference:
https://confluence.atlassian.com/adminjiraserver/importing-data-from-csv-938847533.html


NEW QUESTION # 15
Your Jira instance has a Select List custom field named Application, which lists all the Atlassian offerings. You need to write a JQL query that shows all issues due within the next month for Jira, Trelb, and Jira Align applications.
Which query will satisfy the requirement?

  • A. (Application =^Jire^ OR Application = ^Trelb. OR Application = ^Jim Align-) AND duedate startOrMonth(1m) AND duedate <= endOrMonth(,m)
  • B. Application IN (Jira,Trelb,Jira Align) AND * (duedate>= startOrMonth(1M) AND duedate<= endOrMonth(1M))
  • C. Application = ^Jim^ OR Application = OR * Application = ^Jim Align^ AND duedate startOrMonth(1) OR duedate <= endOrMonth(1)
  • D. Application IN (Jira,Trelb, ^Jim Align.) AND * &iodate >. startOrMonth(1) AND &iodate <= endOrMonth(1)
  • E. Application IN (Jira, Trelb, ^Jim Align-) AND * (duedate>= startOrMonth(1) OR duedate <= endOrMonth(1))

Answer: B


NEW QUESTION # 16
You have two issue types in your HR project: Hire and Fire.
Which two requirements can be met through changes only to field configurations? (Choose two.)

  • A. For the Hire issue type, the field description for the Due Date field should read "First day of work".
  • B. For the Fire issue type, the Description field should have a default value of "Termination".
  • C. For the Fire issue type, the default value for the Priority field should be Blocker.
  • D. For both issue types, the Assignee field should be hidden when creating but not when viewing an issue.
  • E. For both issue types, the Resolution should be set once the issues are being resolved.
  • F. For both issue types, the Employee Name custom field must be required upon creation and must never be blank.

Answer: D,E


NEW QUESTION # 17
A team complains that many of their issues are in the Closed status, but do not have a resolution set, which causes problems with reporting. The project uses a single workflow.
You want to set the resolution to Done on all existing issues in the Closed status.
Which combination of workflow elements and a bulk operation will achieve this?

  • A. - A temporary transition and a screen
    - An Edit Issues bulk operation
  • B. - A screen and a custom field
    - An Edit Issues bulk operation
  • C. - A temporary transition and a post function
    - A Transition Issues bulk operation
  • D. - A temporary transition and a trigger
    - An Edit Issues bulk operation
  • E. - A screen and the Resolution field
    - A Move Issues bulk operation

Answer: D


NEW QUESTION # 18
Gary is no longer receiving notifications when his colleagues modify issues that he is watching. You already verified that watchers should be notified. Which personal setting did Gary update?

  • A. Notifications for relevant issues
  • B. You make changes to the issue
  • C. Watch your issues
  • D. Email notifications format

Answer: A

Explanation:
The scenario indicates that Gary is no longer receiving notifications for issues he is watching, despite the notification scheme being correctly configured to notify watchers. This suggests that Gary has modified a personal setting that controls whether he receives notifications for watched issues. Based on Jira Software Cloud documentation, the relevant personal setting is "Notifications for relevant issues" (Option D).
Explanation of the Correct Answer (Option D):
In Jira Cloud, users can control their notification preferences through their personal settings in the user profile. The setting "Notifications for relevant issues" determines whether a user receives email notifications for events they are associated with, such as being a watcher of an issue.
If Gary disabled this setting (i.e., turned off notifications for relevant issues), he would stop receiving notifications for issues he is watching, even if the project's notification scheme is configured to notify watchers.
Exact Extract from Documentation:
Manage your Jira notification emails
You can choose whether you want to receive email notifications about activity in your Jira products. For example, you can choose to receive emails when you're added as a watcher to an issue, or when an issue you' re working on is updated.
To manage your notification preferences:
From your Jira site, select your profile picture in the top right and select Personal settings.
Under Email notifications, select whether you'd like to receive notifications for relevant issue activity.
On: Receive emails for issue activity you're associated with, like when you're a watcher, assignee,or reporter.
Off: Don't receive emails for issue activity, even if you're associated with the issue.
Note: This setting doesn't affect emails about your account, like password resets. To manage those, update your Atlassian account preferences.
(Source: Atlassian Support Documentation, "Manage your Jira notification emails") Why This Fits: The documentation explicitly states that turning off the "Notifications for relevant issues" setting prevents a user from receiving emails for issue activity they are associated with, including as a watcher. Since Gary is no longer receiving notifications for watched issues, this is the most likely setting he updated.
Why Other Options Are Incorrect:
Watch your issues (Option A):
This option refers to a setting that automatically adds a user as a watcher to issues they create or are assigned to. However, the question states that Gary is already watching the issues (since he was receiving notifications previously), so this setting is not relevant. Disabling this setting would only prevent Gary from being automatically added as a watcher to new issues, not stop notifications for issues he is already watching.
Extract from Documentation:
Watching issues
You can watch an issue to receive email notifications whenever it's updated. By default, you may automatically watch issues you create or are assigned to, depending on your notification settings.
To change your auto-watch settings:
Select your profile picture and then select Settings.
Under Jira settings, select whether to automatically watch issues you create or are assigned to.
(Source: Atlassian Support Documentation, "Watch issues and manage your watchlist") You make changes to the issue (Option B):
This option is not a standard personal setting in Jira Cloud. There is no user-level setting that specifically toggles notifications based on whether the user themselves makes changes to an issue. Notifications are controlled by the notification scheme and the user's email notification preferences, not by a setting tied to the user's own changes.
Email notifications format (Option C):
This setting allows users to choose the format of email notifications (e.g., HTML or text). Changing this setting affects how notifications are displayed, not whether they are sent. Therefore, it would not cause Gary to stop receiving notifications entirely.
Extract from Documentation:
Email format
You can choose whether notifications are sent in HTML or text format. This is managed in your Atlassian account settings, under email preferences.
(Source: Atlassian Support Documentation, "Manage your Atlassian account") Additional Notes:
The question specifies that the notification scheme is correctly configured to notify watchers, so the issue lies with Gary's personal settings, not the project or system configuration.
The "Notifications for relevant issues" setting is a global toggle that affects all notifications for issue activity a user is associated with, making it the most direct cause of Gary's issue.
References:
Atlassian Support Documentation: Manage your Jira notification emails
Atlassian Support Documentation: Watch issues and manage your watchlist Atlassian Support Documentation: Manage your Atlassian account


NEW QUESTION # 19
Henry was recently assigned multiple issues in a classic software project. He has not received any email notifications about the assignment of these issues but he received notifications about other changes to issues from this and other projects.
Identify two possible reasons (Choose two)

  • A. The Issue Assigned event does not list the current assignee as a recipient in the projects notification scheme
  • B. Henry adjusted his personal email notification preference to not notify him when he is the assignee of an issue
  • C. Henry is missing the Assignable User project permission in the Jira project
  • D. The Issue Updated event does not list the current assignee as a recipient in the project's notification scheme
  • E. Henry is missing the Browse Projects project permission in the Jira project

Answer: A,B


NEW QUESTION # 20
Your business owners have told you to use roles as much as possible in Jira because it allows them to do things that groups cannot do.
When considering this, you need to be aware of those actions in Jira that require the use of groups rather than roles.
Identify two actions in Jira that require the use of groups. (Choose two.)

  • A. defining Issue Security levels
  • B. granting system administrative rights
  • C. granting Project Administration rights
  • D. allowing users to use transitions in all the workflows
  • E. controlling who can perform Bulk Change in a project
  • F. granting permissions to teams coming from Active Directory

Answer: A,C

Explanation:
Reference: https://confluence.atlassian.com/adminjiracloud/managing-project-roles-776636382.html


NEW QUESTION # 21
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. Email notifications will be sent during the bulk operation.
  • B. Filter subscriptions based on the filter will stop sending emails.
  • C. The saved filter will display no issues.
  • D. Christian will be added as a watcher on all the edited issues.

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 # 22
The marketing team has asked you to embed the trigger tab of an issue collector on several internal web pages and change its size, color, and text. They also want the ability to track which webpage finally generated the underlying feedback issue. You are not familiar with advanced issue collector configuration.
Which type of developer should you contact for assistance?

  • A. Groovy
  • B. Velocity
  • C. JavaScript
  • D. Python
  • E. SQL

Answer: C

Explanation:
Reference: https://confluence.atlassian.com/adminjiracloud/using-the-issue-collector-776636529.html


NEW QUESTION # 23
In your company-managed project, you are in the process of releasing a version that contains unresolved issues. You opt to ignore these issues and proceed to release the version. What happens to the unresolved issues?

  • A. They are moved to the top of the backlog.
  • B. They are moved to the next version.
  • C. They are transitioned to Done.
  • D. They are left unresolved.

Answer: D

Explanation:
When releasing a version in a company-managed project that contains unresolved issues, you can choose to ignore these issues and proceed with the release. The unresolved issuesare left unresolved(Option C), meaning they retain their current status and resolution state without being automatically moved or transitioned.
* Explanation of the Correct Answer (Option C):
* In Jira, releasing a version marks it as complete and updates theRelease DateandReleasedstatus for the version. If unresolved issues (issues without a resolution, e.g., not in a Done status) are included, you can choose to ignore them during the release process. Ignoring unresolved issues means they remain in their current state-unresolved, with no changes to their status, resolution, or version association. They are not automatically moved to another version, transitioned, or reordered in the backlog.
* Exact Extract from Documentation:
Release a version in company-managed projects
When releasing a version:
* You can choose to ignore unresolved issues (issues without a resolution).
* Ignored unresolved issues: Remain in their current status and resolution state, with no automatic changes.To release:
* Go toProject settings > Releases.
* Select the version and clickRelease.
* Choose to ignore unresolved issues if prompted.Note: Unresolved issues are not moved to another version or transitioned unless explicitly configured.(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")
* Why This Fits: Ignoring unresolved issues during a version release leaves them unchanged in their current unresolved state, making Option C the correct answer.
* Why Other Options Are Incorrect:
* They are moved to the next version (Option A):
* Moving unresolved issues to the next version is an option during the release process, but it is not the default or required action when choosing toignoreunresolved issues. Ignoring them explicitly avoids moving them to another version.
* Extract from Documentation:
When releasing, you can move unresolved issues to another version or leave them unchanged. Ignoring unresolved issues keeps them in their current version.
(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")
* They are transitioned to Done (Option B):
* Transitioning issues toDone(or setting a resolution) requires a workflow transition and is not automatic when releasing a version. Ignoring unresolved issues means no status or resolution changes occur.
* Extract from Documentation:
Releasing a version does not transition issues or set resolutions unless explicitly configured via a workflow post function.
(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")
* They are moved to the top of the backlog (Option D):
* Releasing a version does not affect the backlog order or automatically reorder issues. The backlog is managed separately, and ignoring unresolved issues leaves them in their current position.
* Extract from Documentation:
Releasing a version does not modify the backlog order. Unresolved issues remain in their current position unless manually reordered.
(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")
* Additional Notes:
* Releasing a version requiresproject adminprivileges and is done inProject settings > Releases.
* If you choose to move unresolved issues to another version instead of ignoring them, Option A would apply, but the question specifiesignoringthe issues.
* Unresolved issues may still be associated with the released version unless manually updated.
:
Atlassian Support Documentation:Manage versions in company-managed projects


NEW QUESTION # 24
What is the impact of changing the name of a project?

  • A. Jira will need to be reindexed.
  • B. The project key will also change.
  • C. Issue filters may need to be updated.
  • D. The old name can no longer be reused.
  • E. The URL for issues will change.

Answer: C

Explanation:
Changing the name of a project in Jira Software Cloud affects how the project is displayed and referenced in certain contexts, but it does not have significant system-wide impacts like reindexing or changing URLs. The primary impact is thatissue filters may need to be updated(Option E), as filters often reference the project name.
* Explanation of the Correct Answer (Option E):
* In Jira, issue filters (created using JQL, Jira Query Language) can include the project name to scope the search (e.g., project = "Old Project Name"). If the project name changes, any filters that explicitly reference the old project name will no longer return the correct results and must be updated to use the new project name.
* Exact Extract from Documentation:
Change a project's name
To change the name of a project:
* Go toProject settings > Details.
* Update theNamefield and save changes.Impact: Changing the project name does not affect the project key, issue keys, or URLs. However, JQL queries, filters, or dashboards that reference the project by name (e.g., project = "Old Name") may need to be updated to reflect the new name.Note: Use the project key in JQL queries to avoid issues with name changes, as the key remains constant.(Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")
* Why This Fits: The documentation explicitly states that changing a project's name impacts JQL- based filters and dashboards that reference the project name, making Option E the correct choice.
* Why Other Options Are Incorrect:
* Jira will need to be reindexed (Option A):
* Changing a project name is a metadata update that does not affect the search index.
Reindexing is required for changes like modifying field configurations or schemes, but not for renaming a project.
* Extract from Documentation:
Reindexing is required when you make changes to field configurations, schemes, or indexing settings.
Changing a project's name or key does not trigger a reindex.
(Source: Atlassian Support Documentation, "Reindex Jira Cloud")
* The URL for issues will change (Option B):
* Issue URLs in Jira are based on the project key and issue key (e.g., https://<site>.atlassian.
net/browse/KEY-123), not the project name. Changing the project name does not affect URLs.
* Extract from Documentation:
Issue URLs are constructed using the project key and issue key, which remain unchanged when the project name is updated.
(Source: Atlassian Support Documentation, "Manage projects in Jira Cloud")
* The old name can no longer be reused (Option C):
* There is no restriction in Jira preventing the reuse of a previous project name. Project names are not required to be unique, and the old name can be reused for another project or reverted if needed.
* Extract from Documentation:
Project names can be reused across projects, as they are not required to be unique. The project key, however, must be unique.
(Source: Atlassian Support Documentation, "Create and configure projects")
* The project key will also change (Option D):
* The project key is a separate attribute from the project name and remains unchanged when the name is updated. Changing the project key is a distinct operation that requires admin permissions and affects issue keys and URLs.
* Extract from Documentation:
The project key is a unique identifier for the project and does not change when you update theproject name.
To change the project key, use theChange project keyoption, which updates all issue keys and URLs.
(Source: Atlassian Support Documentation, "Edit a project key")
* Additional Notes:
* To minimize the impact of project name changes, it's recommended to use the project key in JQL queries (e.g., project = KEY) instead of the project name, as the key is immutable unless explicitly changed.
* Changing the project name requires project admin permissions and is done inProject settings > Details.
:
Atlassian Support Documentation:Manage project settings in Jira Cloud
Atlassian Support Documentation:Create and configure projects
Atlassian Support Documentation:Reindex Jira Cloud
Atlassian Support Documentation:Edit a project key


NEW QUESTION # 25
You are the site and organization admin of a Jira Software and Confluence instance.
You are the only administrator and you don't have any Trusted users.
Users currently cannot send invitations to anyone. You need to control the number of licenses used.
Therefore, you want to either invite individual users or approve individual user requests.
Which site access setting will meet this requirement? (Choose one)

  • A. Don't approve any domain
  • B. Enable Jira Software and Confluence invite links
  • C. Enable existing users to send invitations to anyone
  • D. Approve any domain
  • E. Approve your organization domain only

Answer: A


NEW QUESTION # 26
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 is not in a group or project role.
  • B. The other level is marked as the default.
  • C. The other level is configured for different issue types.
  • D. Andre does not have Edit Issues permission.
  • E. Andre does not have Set Issue Security permission.

Answer: E

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 # 27
DEV and ENG projects share the same permission scheme. Users of both projects also work in a single board that shows both DEV and ENG issues.
However some users cannot move issues across the board or move issues between the two projects. Identify the configuration related to this problem. (Choose one)

  • A. Board permissions
  • B. Security levels
  • C. Project permissions
  • D. Global permissions
  • E. Product access

Answer: B


NEW QUESTION # 28
You want to use a bulk operation to move issues between two company-managed projects that use different field configurations. Which field will definitely be updated?

  • A. Resolved Date
  • B. Custom fields
  • C. Assignee
  • D. Status
  • E. Components

Answer: D

Explanation:
When moving issues between two company-managed projects with different field configurations using a bulk operation, certain fields may need to be updated due to differences in workflows, field configurations, or project-specific settings. The field that willdefinitelybe updated isStatus(Option E), as issues must be mapped to a valid status in the target project's workflow.
* Explanation of the Correct Answer (Option E):
* Each company-managed project can have its ownworkflow scheme, which assigns workflows to issue types. When moving issues between projects, the source project's workflow may have different statuses than the target project's workflow. During a bulk move, you must map the current status of each issue to a valid status in the target project's workflow, as the source status may not exist in the target workflow. This status mapping is a mandatory step in the bulk move process, ensuring thatStatusis always updated.
* Exact Extract from Documentation:
Move issues between projects
When moving issues to a different project in Jira Cloud, you must map the issue's status to a valid status in the target project's workflow.
To move issues:
* Select issues and chooseBulk change>Move issues.
* Choose the target project and issue type.
* Map the source status to a target status for each issue type.Note: Status mapping is required because projects may use different workflows with distinct statuses.(Source: Atlassian Support Documentation, "Move issues in Jira Cloud")
* Why This Fits: The bulk move operation always requires mapping theStatusfield to a valid status in the target project's workflow, makingStatusthe field that will definitely be updated.
* Why Other Options Are Incorrect:
* Assignee (Option A):
* TheAssigneefield is not necessarily updated during a move. If the assignee is a valid user in the target project and has theAssignable Userpermission, the assignee remains unchanged. Only if the assignee is invalid (e.g., lacks permissions) might you need to update it, but this is not guaranteed.
* Extract from Documentation:
TheAssigneefield is preserved during a move unless the user is not assignable in the target project, in which case you may be prompted to choose a new assignee.
(Source: Atlassian Support Documentation, "Move issues in Jira Cloud")
* Custom fields (Option B):
* Custom fieldsmay need to be updated if the target project's field configuration requires values for fields that were not required in the source project. However, this is not guaranteed, as it depends on the specific field configurations. If the custom fields are optional or have compatible values, no update is needed.
* Extract from Documentation:
Custom fields may require updates if the target project's field configuration mandates values not required in the source project. This is not always necessary.
(Source: Atlassian Support Documentation, "Move issues in Jira Cloud")
* Resolved Date (Option C):
* TheResolved Date(orResolution Date) is a read-only system field set automatically when an issue'sResolutionis set (e.g., via a workflow transition). It is not directly updated during a move unless the status mapping triggers a resolution change, which is not guaranteed.
* Extract from Documentation:
TheResolution Dateis set by workflow transitions, not directly by moving issues. It remains unchanged unless the move alters the resolution.
(Source: Atlassian Support Documentation, "Configure advanced work item workflows")
* Components (Option D):
* Componentsare project-specific, and the target project may have different components.
During a move, you may need to map or clear components if the source components do not exist in the target project. However, this is not guaranteed, as components may be compatible or optional.
* Extract from Documentation:
Components may need to be mapped or cleared if the target project has different components, but this is not always required.
(Source: Atlassian Support Documentation, "Move issues in Jira Cloud")
* Additional Notes:
* The bulk move operation is performed viaIssues > Search for issues > Bulk change > Move issues, requiring theMove Issuespermission.
* The mandatory status mapping ensures compliance with the target project's workflow, making Statusthe only field always updated.
* Other fields (e.g.,Assignee,Custom fields) may be updated depending on configurations, but only Statusis certain.
:
Atlassian Support Documentation:Move issues in Jira Cloud
Atlassian Support Documentation:Configure advanced work item workflows


NEW QUESTION # 29
A team is complaining that their Jira project is slow to use. You are able to replicate the slow behavior by viewing and trying to edit one of their issues.
Which logging option will help you or a system administrator to diagnose the problem?

  • A. Enable profiling globally, so the logs can be inspected for anomalies when viewing the issue.
  • B. Configure Jira to record and log the JavaScript execution from the browser console.
  • C. Set the logging to DEBUG level on all packages causing activity for that issue.
  • D. Use the Log Analyzer to get more information about the issue view process.

Answer: A

Explanation:
Reference: https://www.elastic.co/guide/en/kibana/current/xpack-logs-analysis.html


NEW QUESTION # 30
......


The ACP-120 exam is a multiple-choice exam and is delivered online. ACP-120 exam consists of 60 questions, and candidates have 180 minutes to complete the exam. The passing score for the exam is 65%, and candidates who pass the exam will receive a certificate that validates their skills and knowledge in Jira Cloud administration. Overall, the ACP-120 exam is an excellent way for professionals to validate their Jira Cloud administration skills and demonstrate their expertise in this area.

 

ACP-120 Dumps PDF - Want To Pass ACP-120 Fast: https://ucertify.examprepaway.com/ATLASSIAN/braindumps.ACP-120.ete.file.html

Related Blogs

more
ATLASSIAN ACP-120 Certification Practice Exam