ATLASSIAN certification ACP-120 exam targeted exercises

The content system of ACP-120 exam simulation is constructed by experts. After-sales service of our study materials is also provided by professionals. If you encounter some problems when using our ACP-120 study materials, you can also get them at any time. After you choose ACP-120 Preparation questions, professional services will enable you to use it in the way that suits you best, truly making the best use of it, and bringing you the best learning results.

ATLASSIAN ACP-120 (Jira Cloud Administrator) Exam is an online exam that consists of 60 multiple-choice questions. Candidates have 90 minutes to complete the exam, and a passing score of 65% or higher is required to earn certification. ACP-120 Exam covers a wide range of topics related to Jira Cloud administration, including user management, project management, issue management, and system administration.

>> ACP-120 Valid Braindumps Ebook <<

100% Pass ATLASSIAN - ACP-120 - Jira Cloud Administrator –The Best Valid Braindumps Ebook

As soon as you enter the learning interface of our system and start practicing our ATLASSIAN ACP-120 learning materials on our Windows software, you will find small buttons on the interface. These buttons show answers, and you can choose to hide answers during your learning of our ATLASSIAN ACP-120 Exam Quiz so as not to interfere with your learning process.

ATLASSIAN Jira Cloud Administrator Sample Questions (Q36-Q41):

NEW QUESTION # 36
Below are the requirements for two new fields to be used in a company-managed project:
* Allow a single option from a dropdown list of options.
* Allow bold and underlined text.
Identify the two field types you need to use. (Choose two.)

A. Short text
B. Checkboxes
C. Radio buttons
D. Paragraph

Answer: C,D

Explanation:
To meet the requirements for two new fields in a company-managed project, one field must allow selecting a single option from a dropdown list, and the other must allow bold and underlined text.The appropriate field types areRadio buttons(Option C) for the dropdown list andParagraph(Option B) for bold and underlined text.
* Explanation of the Correct Answers:
* Radio buttons (Option C):
* The requirement toallow a single option from a dropdown list of optionsis met by a Radio buttonscustom field. This field type presents a list of predefined options in a radio button format, allowing users to select exactly one option, similar to a dropdown list. In Jira, radio buttons are often used interchangeably withSelect List (single choice)for single- selection lists, and both fulfill the requirement.
* Exact Extract from Documentation:
Custom field types
TheRadio buttonsfield type allows users to select one option from a predefined list, presented as radio buttons.
To create:
* Go toSettings > Issues > Custom fields.
* Create a new field and selectRadio buttons.
* Define the list of options.Note: Radio buttons are similar toSelect List (single choice) and are used for single-selection dropdown-like functionality.(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")
* Why This Fits: TheRadio buttonsfield type provides a single-selection list, meeting the requirement for a dropdown list of options.
* Paragraph (Option B):
* The requirement toallow bold and underlined textis met by aParagraphcustom field (also known asText Field (multi-line)). This field type supports rich text input, including formatting options like bold and underlined text, using a WYSIWYG editor or wiki-style markup.
* Exact Extract from Documentation:
Custom field types
TheParagraph(orText Field (multi-line)) field type allows users to enter multiple lines of text with rich text formatting, including bold, underline, and other styles.
To create:
* Go toSettings > Issues > Custom fields.
* Create a new field and selectParagraph.Note: The rich text editor supports formatting like bold and underline, or users can use wiki-style markup (e.g.,bold, underline).(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")
* Why This Fits: TheParagraphfield supports rich text formatting, including bold and underlined text, meeting the second requirement.
* Why Other Options Are Incorrect:
* Short text (Option A):
* AShort text(orText Field (single line)) custom field allows single-line text input but does not support rich text formatting like bold or underlined text. It is unsuitable for the second requirement and does not provide a dropdown list for the first requirement.
* Extract from Documentation:
TheShort textfield type is for single-line plain text and does not support rich text formatting like bold or underline.
(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")
* Checkboxes (Option D):
* ACheckboxescustom field allows users to select multiple options from a predefined list.
The first requirement specifies asingle option, making checkboxes unsuitable, as they are designed for multiple selections.
* Extract from Documentation:
TheCheckboxesfield type allows multiple selections from a list. For single-selection lists, useRadio buttonsor Select List (single choice).
(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")
* Additional Notes:
* Steps to configure:
* Create aRadio buttonscustom field inSettings > Issues > Custom fields, name it appropriately, and define the options.
* Create aParagraphcustom field inSettings > Issues > Custom fieldsfor rich text input.
* Add both fields to the project's screens (Project settings > Screens).
* Configuring custom fields requiresJira administratorprivileges.
* TheRadio buttonsfield may display as a dropdown-like list in some interfaces, aligning with the requirement.
:
Atlassian Support Documentation:Manage custom fields in Jira Cloud
Atlassian Support Documentation:Configure screens in Jira Cloud

NEW QUESTION # 37
version in a company-managed project:
* Move all issues in version 1.1 to version 1.2.
* Remove version 1.1 as an available option from the Fix Versions system field.
Which two operations will both meet the requirements? (Choose two.)

A. Build and release
B. Delete
C. Merge
D. Archive

Answer: C,D

Explanation:
The question involves managing versions in a company-managed project in Jira Software Cloud. Maia wants to move all issues from version 1.1 to version 1.2 and remove version 1.1 as an available option in theFix Versionsfield. The two operations that meet both requirements areArchiveandMerge.
* Explanation of the Correct Answers:
* Archive (Option B):
* Archiving a version removes it from theFix Versionsfield as an available option for new issues, while preserving the version's association with existing issues. Additionally, archiving allows you to move issues to another version (e.g., version 1.2) during the process, meeting both requirements.
* Exact Extract from Documentation:
Archive a version
Archiving a version removes it from the list of available versions in fields like Fix Versions, so it can't be selected for new issues. You can also move issues to another version during the archiving process.
To archive a version:
* Go to your project'sReleasespage.
* Find the version (e.g., version 1.1) and selectArchive.
* Optionally, choose to move issues to another version (e.g., version 1.2).Archived versions are still visible in reports and issue details but are no longer selectable in fields.Note: You need project admin permissions to archive versions.(Source:
Atlassian Support Documentation, "Manage versions in company-managed projects")
* Why This Fits: Archiving version 1.1 removes it from the Fix Versions field, preventing it from being selected for new issues, and allows Maia to move all issues to version 1.2 during the archiving process, fulfilling both requirements.
* Merge (Option D):
* Merging a version moves all issues from one version (e.g., version 1.1) to another (e.g., version 1.2) and deletes the source version, effectively removing it from the Fix Versions field. This meets both requirements, as it reassigns issues and eliminates version 1.1 as an available option.
* Exact Extract from Documentation:
Merge versions
Merging versions allows you to combine two versions by moving all issues from one version to another. The source version is deleted after the merge.
To merge versions:
* Go to your project'sReleasespage.
* Find the version to merge (e.g., version 1.1) and selectMerge.
* Choose the target version (e.g., version 1.2) to move issues to.After merging, the source version (version 1.1) is removed from the Fix Versions field and is no longer available for selection.Note: Merging is permanent and cannot be undone, so ensure the target version is correct.(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")
* Why This Fits: Merging version 1.1 into version 1.2 moves all issues to version 1.2 and deletes version 1.1, ensuring it is no longer an option in the Fix Versions field, thus meeting both requirements.
* Why Other Options Are Incorrect:
* Delete (Option A):
* Deleting a version removes it from the Fix Versions field, but it also removes the version from all issues associated with it without reassigning them to another version. This does not meet the requirement to move issues to version 1.2.
* Extract from Documentation:
Delete a version
Deleting a version removes it from the project and clears it from the Fix Versions field of all associated issues. Issues are not reassigned to another version automatically.
Note: Use caution, as this action cannot be undone, and issues lose their version association.
(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")
* Build and release (Option C):
* Building and releasing a version marks it as complete and moves unresolved issues to another version, but it does not remove the version from the Fix Versions field. Released versions remain selectable unless archived or deleted.
* Extract from Documentation:
Release a version
Releasing a version marks it as complete and optionally moves unresolved issues to another version. The released version remains available in the Fix Versions field unless archived.
(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")
* Additional Notes:
* BothArchiveandMergeare suitable, but they have different implications:
* Archiving preserves version 1.1 in reports and issue histories, making it ideal if historical data needs to be retained.
* Merging permanently deletes version 1.1, which may be preferred if the version is no longer relevant.
* The operations require project admin permissions in a company-managed project, and the Releasespage is accessed viaProject Settings > Releases.
:
Atlassian Support Documentation:Manage versions in company-managed projects Atlassian Support Documentation:Configure releases and versions

NEW QUESTION # 38
On the Bulk Operation screen, Taylor is unable to choose the Delete Issues bulk action. What does Taylor definitely need?

A. Project permissions
B. Project administration privileges
C. Global permissions
D. Jira administration privileges
E. Organization admin privileges

Answer: A

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 # 39
Which time tracking configuration can be controlled on a global basis for all projects in Jira?

A. which users have the ability to edit or delete their own or other users' worklogs
B. whether Original Estimate is required when creating issues
C. whether time tracking fields are available on standard versus sub-task issue types
D. which users or groups have the ability to log work on issues
E. the default time unit on estimates when users don't explicitly specify one

Answer: E

Explanation:
Reference: https://www.softwaretestinghelp.com/jira-time-tracking/

NEW QUESTION # 40
A medical clinic has decided to use Jira. Their project will allow patients to file medical complaints.
The requirements for the project are as follows:
- Members of the group (jira-patients) must be able to see only their own complaints.
- Members of the group (medical-board) must be able to see all complaints.
Based only on these two requirements, which two configurations used together will satisfy them?
(Choose two.)

A. In the permission scheme, add Reporter and Group (anonymous) to Browse Projects and Create Issues.
B. Implement an issue security scheme with two levels: (#1) Reporter and (#2) Group (medical-board).
C. Implement an issue security scheme with three levels: (#1) Group (jira-patients), (#2) Reporter, and (#3) Group (medical-board).
D. Implement an issue security scheme with one level: Reporter and Group (medical-board).
E. In the permission scheme, add Group (jira-patients) and Group (medical-board) to Browse Projects and Create Issues permissions.

Answer: B,E

NEW QUESTION # 41
......

There are some loopholes or systemic problems in the use of a product, which is why a lot of online products are maintained for a very late period. The ACP-120 test material is not exceptional also, in order to let the users to achieve the best product experience, if there is some learning platform system vulnerabilities or bugs, we will check the operation of the ACP-120 quiz guide in the first time, let the professional service personnel to help user to solve any problems. The Jira Cloud Administrator prepare torrent has many professionals, and they monitor the use of the user environment and the safety of the learning platform timely, for there are some problems with those still in the incubation period of strict control, thus to maintain the ACP-120 Quiz guide timely, let the user comfortable working in a better environment.

ACP-120 Valid Dump: https://www.dumpsking.com/ACP-120-testking-dumps.html

Sean Lee Sean Lee

Biography

ATLASSIAN certification ACP-120 exam targeted exercises

100% Pass ATLASSIAN - ACP-120 - Jira Cloud Administrator –The Best Valid Braindumps Ebook

ATLASSIAN Jira Cloud Administrator Sample Questions (Q36-Q41):

Archives