The TestValid ATLASSIAN ACP-120 exam questions are designed and verified by experienced and qualified Jira Cloud Administrator (ACP-120) exam trainers. They have verified all ATLASSIAN ACP-120 exam questions one by one and ensured the top standard of TestValid ATLASSIAN ACP-120 Practice Test questions. So you do not need to worry about the ACP-120 exam preparation just download TestValid ATLASSIAN ACP-120 latest dumps and start preparing today.
ATLASSIAN ACP-120 (Jira Cloud Administrator) Exam is an important certification for professionals who work with Jira Cloud. It demonstrates that the candidate has the skills and knowledge necessary to effectively manage Jira Cloud instances and ensure that they are optimized for their organization's needs. By earning this certification, professionals can enhance their career prospects and demonstrate their value to potential employers.
The ACP-120 Certification Exam is a valuable credential for Jira Cloud Administrators who want to demonstrate their expertise in managing Jira Cloud instances. ACP-120 exam tests candidates on a range of topics related to Jira Cloud configuration and management. Candidates who pass the exam can demonstrate their ability to manage projects effectively using Jira Cloud.
As the leader in the market for over ten years, our ACP-120 practice engine owns a lot of the advantages. Our ACP-120 study guide is featured less time input, high passing rate, three versions, reasonable price, excellent service and so on. All your worries can be wiped out because our ACP-120 learning quiz is designed for you. We hope that that you can try our free trials before making decisions.
NEW QUESTION # 50
You inherited a mature Jira instance with hundreds of projects and associated schemes. You are trying to optimize the administration of the instance.
You need to create a new project and determine which schemes to apply.
Select the two best approaches. (Choose two.)
Answer: A,C
NEW QUESTION # 51
Currently, several groups and project robs are listed in every system event of the DEV Notification Scheme and should remain that way. A new requirement states that when DEV issues move from the status Open to status Assigned, only Project Rob (Managers) should be notified. DEV project does not share any of its schemes.
Identify the event that needs to be configured.
Answer: B
NEW QUESTION # 52
In a company-managed project, a limited set of users should be notified when issues transition to Pending status, and the project admin must be able to manage the list of users. What two items must be configured?
(Choose two.)
Answer: A,C
Explanation:
To address the requirement of notifying a limited set of users when issues transition to a "Pending" status in a company-managed project, and allowing the project admin to manage the list of users, two key configurations are necessary: aproject roleand acustom event. Below is the detailed explanation based on official Jira Software Cloud documentation.
* Project Role (Option A):
* Purpose: Project roles allow project administrators to define and manage a group of users who can be assigned specific permissions or notification responsibilities within a project. This is critical for the requirement that the project admin must manage the list of users to be notified.
* How It Works: In Jira, project roles (e.g., "Developers," "Administrators," or a custom role like
"Pending Status Notifiers") are created and managed at the project level. The project admin can add or remove users from these roles without needing global admin permissions, which aligns with the requirement for the project admin to manage the user list.
* Configuration Steps:
* Navigate toProject Settings > Peoplein the company-managed project.
* Create a new project role or use an existing one (e.g., "Pending Notifiers").
* Add users to this role as needed. The project admin can update this list at any time.
* In the notification scheme, associate the project role with the custom event (explained below) to ensure that users in this role receive notifications when the event is triggered.
* Why This Is Necessary: Using a project role ensures scalability and flexibility. Instead of hardcoding individual users or groups in the notification scheme, a project role allows the admin to dynamically manage who receives notifications without modifying the underlying configuration.
* Custom Event (Option C):
* Purpose: A custom event is required to trigger notifications specifically for thetransition to the
"Pending" status. Jira's notification system relies on events to determine when and to whom notifications are sent. By creating a custom event, you can link it to the specific workflow transition (e.g., moving to "Pending") and configure the notification scheme to notify the project role.
* How It Works: In Jira, events are fired during workflow transitions via post functions. A custom event (e.g., "Issue Moved to Pending") can be created and associated with the transition to the
"Pending" status. The notification scheme is then configured to send notifications to the designated project role when this event occurs.
* Configuration Steps:
* Navigate toSettings > System > Events(requires Jira admin permissions).
* Create a new custom event, such as "Issue Moved to Pending," with a description and an appropriate notification template (e.g., "Issue Updated").
* In the workflow used by the project, edit the transition to the "Pending" status:
* Add a post function to the transition, such as"Fire a Generic Event"or a custom event, and select the custom event ("Issue Moved to Pending").
* Update the project'snotification scheme(found inProject Settings > Notificationsor Settings > Issues > Notification Schemes):
* Map the custom event to the project role (e.g., "Pending Notifiers") to ensure that users in this role receive notifications when the event is fired.
* Why This Is Necessary: A custom event is essential because Jira's default events (e.g., "Issue Updated," "Issue Created") may not be specific enough to target only the "Pending" status transition. A custom event ensures that notifications are sent only when the issue transitions to
"Pending," meeting the requirement for targeted notifications.
* Why Other Options Are Incorrect:
* Workflow Condition (Option B):
* A workflow condition controls whether a user can execute a transition (e.g., restricting who can move an issue to "Pending"). It does not influence notifications or manage lists of users to be notified. Therefore, it is irrelevant to the requirement of notifying users and allowing the project admin to manage the user list.
* Workflow Validator (Option D):
* A workflow validator checks whether certain criteria are met before allowing a transition to proceed (e.g., ensuring a field is filled). Like conditions, validators do not handle notifications or user management for notifications, making this option incorrect.
* Group (Option E):
* While groups can be used in notification schemes to define who receives notifications, they are managed by Jira admins at the global level (viaSettings > User Management > Groups ), not by project admins. The requirement specifies that theproject adminmust manage the list of users, which is not feasible with groups since project admins lack permission to edit global groups. Project roles, however, can be managed by project admins, making them the correct choice over groups.
* Additional Notes:
* The configuration assumes a company-managed project, as team-managed projects have simpler permission and notification settings that do not support custom events or complex workflow configurations to the same extent.
* If the project admin lacks permission to edit workflows or notification schemes (which require Jira admin access), they would need to collaborate with a Jira admin to set up the custom event and initial notification scheme. However, once configured, the project admin can manage the project role's membership independently.
* The use of a custom event ensures that notifications are specific to the "Pending" status transition, avoiding unnecessary notifications for other transitions or actions.
NEW QUESTION # 53
You are using a bulk operation to move a few stories from a company-managed project to a team-managed project. What will happen to the stories?
Answer: A
Explanation:
When moving stories from a company-managed project to a team-managed project using a bulk operation, certain issue attributes are preserved, while others may change or be lost due to differences in project configurations. The definite outcome is thattheir comments will remain the same(Option A), as comments are retained during issue moves.
* Explanation of the Correct Answer (Option A):
* Commentsare part of an issue's data and are preserved when moving issues between projects, whether from a company-managed to a team-managed project or vice versa. The bulk move operation retains all comments attached to the stories, ensuring they remain visible in the target team-managed project.
* Exact Extract from Documentation:
Move issues in Jira Cloud
When moving issues between projects:
* Comments: All comments are retained, including their content, author, and timestamps.To move issues:
* Select issues and chooseBulk change>Move issues.
* Choose the target project and issue type.
* Map fields and statuses as needed.Note: Comments are preserved regardless of the source or target project type (company-managed or team-managed).(Source: Atlassian Support Documentation, "Move issues in Jira Cloud")
* Why This Fits: The bulk move operation ensures that comments are transferred with the stories, makingtheir comments will remain the samea definite outcome.
* Why Other Options Are Incorrect:
* Their keys will remain the same (Option B):
* Issuekeys(e.g., PROJ-123) are project-specific, consisting of the project key and an issue number. When moving issues to a different project (from a company-managed to a team- managed project), the issues are assigned new keys based on the target project's key (e.g., NEWPROJ-456). The original keys do not remain the same.
* Extract from Documentation:
When moving issues to a different project, the issue keys change to reflect the target project's key. The original key is preserved in the issue history as a reference.
(Source: Atlassian Support Documentation, "Move issues in Jira Cloud")
* Their issue links will be lost (Option C):
* Issue links(e.g., "blocks," "is related to") are generally preserved during a move, provided the linked issues remain accessible in the target project and the link types are supported.
While there could be rare cases where links to restricted issues are affected, it is not a definite outcome that links will be lost.
* Extract from Documentation:
Issue links are retained during a move unless the linked issues are inaccessible in the target project due to permissions or restrictions.
(Source: Atlassian Support Documentation, "Move issues in Jira Cloud")
* Their issue history will be lost (Option D):
* Theissue history(e.g., status changes, field updates) is preserved during a move. The history is transferred to the target project, maintaining a record of all changes, including those from the source project.
* Extract from Documentation:
The issue history, including all changes and updates, is retained when moving issues between projects.
(Source: Atlassian Support Documentation, "Move issues in Jira Cloud")
* Additional Notes:
* Steps for the bulk move:
* Run a filter to select the stories inIssues > Search for issues.
* ChooseBulk change > Move issues.
* Select the team-managed project and map statuses or fields as needed.
* The operation requires theMove Issuespermission in the source project andCreate Issues permission in the target project.
* Other attributes (e.g.,status,custom fields) may need mapping due to differences between company-managed and team-managed projects, but comments are always preserved.
:
Atlassian Support Documentation:Move issues in Jira Cloud
NEW QUESTION # 54
You must add a new issue type to an existing company-managed project. Identify the configuration item that is definitely not impacted.
Answer: B
Explanation:
Adding a new issue type to a company-managed project requires updating configurations that map issue types to various settings (e.g., screens, workflows, fields). The configuration item that isdefinitely not impactedis theissue security scheme(Option C), as it controls issue visibility and is not directly tied to issue types.
* Explanation of the Correct Answer (Option C):
* Anissue security schemedefines security levels that restrict which users can view issues in a project, based on criteria like users, groups, or roles. It is applied at the project level and is not specific to issue types. Adding a new issue type does not require changes to the issue security scheme, as security levels apply to all issues in the project regardless of their type.
* Exact Extract from Documentation:
Configure issue security schemes
Issue security schemes define security levels to control who can view issues in a project.
Impact of issue types:
* Security levels are applied to all issues in a project, regardless of issue type.
* Adding a new issue type does not affect the issue security scheme.To check:
* Go toProject settings > Issue security.
* Review the security levels and their criteria.Note: Issue security is independent of issue type configurations.(Source: Atlassian Support Documentation, "Configure issue security schemes")
* Why This Fits: Theissue security schemeis not impacted by adding a new issue type, as it operates at the project level and does not depend on issue type configurations, making Option C the correct answer.
* Why Other Options Are Incorrect:
* Issue layout (Option A):
* Theissue layoutdefines which fields are displayed or hidden in the issue view for each issue type. Adding a new issue type may require configuring a new issue layout to specify field visibility for that type, impacting this configuration.
* Extract from Documentation:
Issue layouts are configured per issue type inProject settings > Issue layout. Adding a new issue type may require a new layout configuration.
(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud")
* Issue type screen scheme (Option B):
* Theissue type screen schememaps screens to issue types for operations (Create, Edit, View). Adding a new issue type requires assigning a screen to it in the scheme, impacting this configuration.
* Extract from Documentation:
Adding a new issue type requires updating the issue type screen scheme to assign screens for the new type.
(Source: Atlassian Support Documentation, "Configure screen schemes in Jira Cloud")
* Workflow scheme (Option D):
* Theworkflow schememaps workflows to issue types. Adding a new issue type requires assigning a workflow to it in the scheme, impacting this configuration.
* Extract from Documentation:
Adding a new issue type requires updating the workflow scheme to assign a workflow for the new type.
(Source: Atlassian Support Documentation, "Configure workflow schemes")
* Field configuration scheme (Option E):
* Thefield configuration schememaps field configurations to issue types, defining field behavior (required, optional, hidden). Adding a new issue type may require assigning a field configuration to it, impacting this configuration.
* Extract from Documentation:
Adding a new issue type may require updating the field configuration scheme to assign a configuration for the new type.
(Source: Atlassian Support Documentation, "Configure field settings")
* Additional Notes:
* Steps to add a new issue type:
* Add the issue type to the project's issue type scheme inProject settings > Issue types.
* Update theissue type screen scheme,workflow scheme, andfield configuration schemeto include the new issue type.
* Configure theissue layoutfor the new issue type if needed.
* These changes requireJira administratorprivileges for schemes andproject adminprivileges for issue layout.
* Theissue security schemeremains unaffected, as it applies to all issues in the project.
:
Atlassian Support Documentation:Configure issue security schemes
Atlassian Support Documentation:Configure issue layouts in Jira Cloud
Atlassian Support Documentation:Configure screen schemes in Jira Cloud
Atlassian Support Documentation:Configure workflow schemes
Atlassian Support Documentation:Configure field settings
NEW QUESTION # 55
......
We take responses from thousands of experts globally while updating the ACP-120 content of preparation material. Their feedback and reviews of successful applicants enable us to make our ATLASSIAN ACP-120 dumps material comprehensive for exam preparation purposes. This way we bring dependable and latest exam product which is enough to pass the ATLASSIAN ACP-120 certification test on the very first take.
Accurate ACP-120 Test: https://www.testvalid.com/ACP-120-exam-collection.html