- +254-717-828-927
- [email protected]
The ATLASSIAN ACP-120 Practice Exam feature is the handiest format available for our customers. The customers can give unlimited tests and even track the mistakes and marks of their previous given tests from history so that they can overcome their mistakes. The ACP-120 Exam can be customized which means that the students can settle the time and Jira Cloud Administrator according to their needs and solve the test on time.
The ACP-120 exam covers a range of topics related to Jira Cloud administration, including user management, project configuration, issue tracking, and reporting. ACP-120 exam is designed to test the candidate's ability to configure and manage Jira Cloud instances to meet specific business requirements. ACP-120 Exam also tests the candidate's ability to identify and troubleshoot common issues that may arise in Jira Cloud instances.
Generally speaking, passing the exam is what the candidates wish. Our ACP-120 exam braindumps can help you pass the exam just one time. And in this way, your effort and time spend on the practicing will be rewarded. ACP-120 training materials offer you free update for one year, so that you can know the latest information for the exam timely. In addition, ACP-120 Exam Dumps cover most of the knowledge point for the exam, and you can pass the exam as well as improve your ability in the process of learning. Online and offline chat service is available for ACP-120 learning materials, if you have any questions for ACP-120 exam dumps, you can have a chat with us.
ATLASSIAN ACP-120 Certification Exam is intended for Jira Cloud administrators who want to demonstrate their expertise in managing Jira instances on the cloud. ACP-120 exam covers a range of topics, including Jira administration basics, user management, project configuration, custom fields and workflows, issue types, and permissions. ACP-120 exam is designed to test the ability of administrators to troubleshoot and solve common issues that arise in Jira Cloud instances.
The Atlassian ACP-120 (Jira Cloud Administrator) Certification Exam is a valuable certification for professionals who work with Jira Cloud on a daily basis. It demonstrates the candidate's expertise in administering and managing Jira Cloud instances and validates their skills in implementing best practices for improving the performance and stability of Jira Cloud. Jira Cloud Administrator certification can help professionals enhance their career prospects, gain recognition in the industry, and differentiate themselves from peers.
NEW QUESTION # 76
Which action requires that users have the "Administer Projects" permission?
Answer: C
Explanation:
TheAdminister Projectspermission in Jira Software Cloud grants users the ability to manage project settings, such as components, versions, and roles. Among the listed actions,modifying component leads(Option C) requires theAdminister Projectspermission, as it involves updating project-specific configurations.
* Explanation of the Correct Answer (Option C):
* Modifying component leads involves changing the user assigned as the lead for acomponent in Project settings > Components. This action requires theAdminister Projectspermission, as it is a project administration task.
* Exact Extract from Documentation:
Administer Projects permission
TheAdminister Projectspermission allows users to manage project settings, including:
* Creating, editing, or deleting components and their leads.
* Updating project details, roles, and permissions.
* Configuring notification schemes, issue security, and other project-level settings.To modify component leads:
* Go toProject settings > Components.
* Edit the component and update the lead.Note: Only users withAdminister Projects permission can perform this action.(Source: Atlassian Support Documentation, "Manage components in Jira Cloud")
* Why This Fits: Modifying component leads is a project administration task that directly requires theAdminister Projectspermission, making Option C the correct choice.
* Why Other Options Are Incorrect:
* Reopen bugs (Option A):
* Reopening bugs involves transitioning an issue back to an open status, which requires the Transition Issuespermission and possiblyEdit Issuespermission, depending on the workflow. It does not requireAdminister Projects.
* Extract from Documentation:
Transition Issues permission
Allows users to move issues through workflow transitions, such as reopening a bug. This does not require Administer Projects.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Assign issues to themselves (Option B):
* Assigning issues to oneself requires theAssignable Userpermission (to be eligible as an assignee) and theAssign Issuespermission (to change the assignee). These are not administrative tasks.
* Extract from Documentation:
Assign Issues permission
Allows users to assign issues to other users or themselves, provided they have theAssignable Userpermission.
This does not requireAdminister Projects.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Edit due dates (Option D):
* Editing due dates requires theEdit Issuespermission, as it involves modifying an issue's Due Datefield. This is not an administrative task.
* Extract from Documentation:
Edit Issues permission
Allows users to modify issue fields, such as Due Date, Summary, or Description. This does not require Administer Projects.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Set fix versions (Option E):
* Setting fix versions requires theEdit Issuespermission to modify theFix Versionsfield. In some cases, theResolve Issuespermission may also be needed if the field is restricted to resolution workflows, butAdminister Projectsis not required.
* Extract from Documentation:
Edit Issues permission
Allows users to update fields like Fix Versions. TheAdminister Projectspermission is required to manage versions, not set them on issues.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Additional Notes:
* TheAdminister Projectspermission is typically granted to project administrators or leads via the project's permission scheme. It is checked inProject settings > Permissions.
* Other actions listed (A, B, D, E) are issue-level operations that do not require administrative privileges.
:
Atlassian Support Documentation:Manage components in Jira Cloud
Atlassian Support Documentation:Manage permissions in Jira Cloud
NEW QUESTION # 77
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?
Answer: E
NEW QUESTION # 78
On the Bulk Operation screen, Taylor is unable to choose the Delete Issues bulk action. What does Taylor definitely need?
Answer: E
Explanation:
The inability to choose theDelete Issuesbulk action on the Bulk Operation screen indicates that Taylor lacks the necessary permission to delete issues in the project. TheDelete Issuespermission, which is a project-level permission defined in the project's permission scheme, is required for this action. Therefore, Taylor definitely needsproject permissions(Option D).
* Explanation of the Correct Answer (Option D):
* TheDelete Issuespermission allows users to delete issues, including via bulk operations. This permission is granted through the project's permission scheme and is specific to the project containing the issues. If Taylor cannot select theDelete Issuesbulk action, she lacks this permission for the project.
* Exact Extract from Documentation:
Delete Issues permission
TheDelete Issuespermission allows users to delete issues, either individually or via bulk operations. This permission is granted via the project's permission scheme.
To perform bulk operations:
* Run a filter to select issues.
* On the Bulk Operation screen, choose an action (e.g., Delete Issues).Note: Users must have the relevant permission (e.g.,Delete Issues) for allselected issues to see the action in the bulk operation wizard.To check permissions:
* Go toProject settings > Permissions.
* Verify which users, groups, or roles have theDelete Issuespermission.(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Why This Fits: TheDelete Issuespermission is a project-level permission, and granting it to Taylor will enable her to choose theDelete Issuesbulk action, makingproject permissions (Option D) the correct answer.
* Why Other Options Are Incorrect:
* Organization admin privileges (Option A):
* Organization admins manage Atlassian organization settings, such as user access and billing. They do not directly control project-level permissions likeDelete Issues.
* Extract from Documentation:
Organization admins manage user access and organization settings. Project-specific actions, like deleting issues, are controlled by project permissions.
(Source: Atlassian Support Documentation, "Manage your Atlassian organization")
* Jira administration privileges (Option B):
* Jira administrators manage global settings, such as schemes and user management. While they can modify permission schemes, theDelete Issuespermission is project-specific and does not require Jira admin privileges to grant or use.
* Extract from Documentation:
Jira administrators can modify permission schemes, but theDelete Issuespermission is applied at the project level and does not require admin privileges to use.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Global permissions (Option C):
* Global permissions (e.g.,Administer Jira,Create Projects) control system-wide actions, not project-specific actions like deleting issues. TheDelete Issuespermission is project- level, not global.
* Extract from Documentation:
Global permissions control system-wide actions, such as administering Jira or sharing filters. Project permissions, likeDelete Issues, are specific to projects.
(Source: Atlassian Support Documentation, "Manage global permissions")
* Project administration privileges (Option E):
* Project administration privileges (via theAdminister Projectspermission) allow users to manage project settings, such as components and permission schemes. However, deleting issues is an issue-level action that requires theDelete Issuespermission, not administrative privileges.
* Extract from Documentation:
TheAdminister Projectspermission allows managing project settings. Deleting issues requires theDelete Issuespermission, which is separate.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Additional Notes:
* To resolve the issue, check Taylor's permissions inProject settings > Permissionsand ensure she has theDelete Issuespermission, either directly, via a group, or via a project role.
* If the issues in the bulk operation span multiple projects, Taylor needs theDelete Issues permission for all relevant projects.
:
Atlassian Support Documentation:Manage permissions in Jira Cloud
Atlassian Support Documentation:Manage your Atlassian organization
Atlassian Support Documentation:Manage global permissions
NEW QUESTION # 79
You renamed a status in the workflow of a team-managed project. Which statement is true?
Answer: C
Explanation:
Renaming a status in a team-managed project's workflow affects only that project's workflow, as statuses in team-managed projects are project-specific. The primary impact is thatsaved filters that reference the status must be updated(Option D), as JQL queries in filters use status names and will no longer return correct results if the status name changes.
* Explanation of the Correct Answer (Option D):
* In Jira, saved filters often use JQL queries that reference status names (e.g., status = "In Progress"). If a status is renamed in a team-managed project's workflow (e.g., from "In Progress" to "Active"), any filters referencing the old status name will no longer include issues in the renamed status. These filters must be updated to use the new status name.
* Exact Extract from Documentation:
Manage statuses in team-managed projects
Statuses in team-managed projects are project-specific and edited inProject settings > Workflow. Renaming a status changes its name for that project's issues.
Impact: JQL queries in filters, boards, or dashboards that reference the status name (e.g., status = "In Progress") will no longer match issues in the renamed status. Update these queries to use the new status name.
(Source: Atlassian Support Documentation, "Configure workflows in team-managed projects")
* Why This Fits: Renaming a status affects JQL-based filters that explicitly reference the status, requiring updates to reflect the new name, making Option D the correct answer.
* Why Other Options Are Incorrect:
* The status will be renamed in all team-managed workflows (Option A):
* Statuses in team-managed projects are project-specific, not shared across projects.
Renaming a status in one project's workflow does not affect other team-managed projects.
* Extract from Documentation:
Each team-managed project has its own workflow and statuses, independent of other projects. Changes to a status in one project do not affect others.
(Source: Atlassian Support Documentation, "Configure workflows in team-managed projects")
* Workflow rules that reference the status must be updated (Option B):
* Workflow rules in team-managed projects (e.g., transition restrictions, fieldupdates) reference statuses by their internal IDs or context, not their display names. Renaming a status does not break these rules, so they do not need updating.
* Extract from Documentation:
Workflow rules in team-managed projects are tied to status IDs, not names. Renaming a status does not require updating rules.
(Source: Atlassian Support Documentation, "Configure workflows in team-managed projects")
* Transitions coming into that status must be updated (Option C):
* Transitions in a workflow reference statuses by their internal IDs or context, not their display names. Renaming a status does not affect the transitions pointing to it, so no updates are needed.
* Extract from Documentation:
Transitions are linked to statuses by internal IDs. Renaming a Bedrock status does not affect transition configurations.
(Source: Atlassian Support Documentation, "Configure workflows in team-managed projects")
* The status will be renamed on the Status page in Jira administration (Option E):
* TheStatus pagein Jira administration (Settings > Issues > Statuses) manages global statuses used in company-managed projects. Team-managed project statuses are project- specific and do not appear on or affect the global Status page.
* Extract from Documentation:
Statuses in team-managed projects are project-specific and not listed inSettings > Issues > Statuses, which is for company-managed projects.
(Source: Atlassian Support Documentation, "Manage statuses in Jira Cloud")
* Additional Notes:
* Renaming a status in a team-managed project is done inProject settings > Workflowand requires project admin privileges.
* To minimize filter issues, use status IDs in JQL queries (e.g., status = 10001), but this is less common than using names.
:
Atlassian Support Documentation:Configure workflows in team-managed projects Atlassian Support Documentation:Manage statuses in Jira Cloud Atlassian Support Documentation:Manage filters in Jira Cloud
NEW QUESTION # 80
You want to restore a Cloud instance with another Jira Cloud backup. Which is not a valid option?
Answer: D
Explanation:
Restoring a Jira Cloud instance with a backup involves importing data, users, and media from thebackup file.
Valid options include importing data, merging or overwriting users, and importing media. However, importing apps(Option B) is not a valid option, as apps are not included in Jira Cloud backups and must be reinstalled separately.
* Explanation of the Correct Answer (Option B):
* Jira Cloud backups include issues, configurations, users, and media (e.g., attachments) but do not include installed apps or their data. Restoring a backup does not involve importing apps, as apps must be reinstalled from the Atlassian Marketplace and configured separately.
* Exact Extract from Documentation:
Restore Jira Cloud from a backup
A Jira Cloud backup includes:
* Issues and their history.
* Configurations (e.g., workflows, schemes).
* Users and groups.
* Media (e.g., attachments).When restoring:
* Import data: Restore issues and configurations.
* Merge with existing Cloud users: Add users from the backup without overwriting existing users.
* Overwrite existing Cloud users: Replace existing users with those from the backup.
* Import media: Restore attachments and other media.Note: Apps and their data are not included in backups. Reinstall apps from the Atlassian Marketplace after restoring.(Source:
Atlassian Support Documentation, "Restore your Jira Cloud site from a backup")
* Why This Fits:Importing appsis not a valid option for restoring a Jira Cloud backup, as apps are excluded from backups, making Option B the correct answer.
* Why Other Options Are Incorrect:
* Import data (Option A):
* Importing data is a valid option, as it restores issues, configurations, and other Jira data from the backup.
* Extract from Documentation:
Import data to restore issues, projects, and configurations from a Jira Cloud backup.
(Source: Atlassian Support Documentation, "Restore your Jira Cloud site from a backup")
* Merge with existing Cloud users (Option C):
* Merging users is a valid option, allowing users from the backup to be added to the existing Cloud instance without overwriting current users.
* Extract from Documentation:
ChooseMerge with existing Cloud usersto add users from the backup while preserving existing user accounts.
(Source: Atlassian Support Documentation, "Restore your Jira Cloud site from a backup")
* Overwrite existing Cloud users (Option D):
* Overwriting users is a valid option, replacing existing users with those from the backup.
* Extract from Documentation:
ChooseOverwrite existing Cloud usersto replace current users with those from the backup.
(Source: Atlassian Support Documentation, "Restore your Jira Cloud site from a backup")
* Import media (Option E):
* Importing media is a valid option, restoring attachments and other media files from the backup.
* Extract from Documentation:
Import media to restore attachments and other files included in the backup.
(Source: Atlassian Support Documentation, "Restore your Jira Cloud site from a backup")
* Additional Notes:
* Restoring a Jira Cloud backup requiresJira administratorororganization adminprivileges and is done viaSettings > System > Restore.
* After restoring, apps must be reinstalled, and their data may need to be reimported if the app supports it.
:
Atlassian Support Documentation:Restore your Jira Cloud site from a backup Atlassian Support Documentation:Manage apps in Jira Cloud
NEW QUESTION # 81
......
Reliable ACP-120 Exam Question: https://www.pdfvce.com/ATLASSIAN/ACP-120-exam-pdf-dumps.html
© Dynamic Technologies. All rights reserved.
