[Oct-2025] Pass ACP-120 Exam in First Attempt Updated ACP-120 Exam Questions
Jira Administrator Dumps ACP-120 Exam for Full Questions - Exam Study Guide
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.
NEW QUESTION # 21
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 IN (Jira,Trelb, ^Jim Align.) AND * &iodate >. startOrMonth(1) AND &iodate <= endOrMonth(1)
- B. Application IN (Jira, Trelb, ^Jim Align-) AND * (duedate>= startOrMonth(1) OR duedate <= endOrMonth(1))
- C. Application = ^Jim^ OR Application = OR * Application = ^Jim Align^ AND duedate startOrMonth(1) OR duedate <= endOrMonth(1)
- D. (Application =^Jire^ OR Application = ^Trelb. OR Application = ^Jim Align-) AND duedate startOrMonth(1m) AND duedate <= endOrMonth(,m)
- E. Application IN (Jira,Trelb,Jira Align) AND * (duedate>= startOrMonth(1M) AND duedate<= endOrMonth(1M))
Answer: E
NEW QUESTION # 22
Your user directories are configured as shown:
The Active Directory administrators have just started the process of copying all the users from the old Company B directory to Company A directory. During this process, the group membership is being changed to allow for more fine-grained security control.
A large number of migrated users complain that they do not have the correct new group memberships.
Which configuration change should you perform?
- A. Disable the Company A directory.
- B. Synchronize the Company A directory.
- C. Disable the Company B directory.
- D. Reorder the directories so the Jira Internal Directory is listed first.
- E. Reorder the directories so Company A is before Company B.
- F. Enable the Crowd user directory.
Answer: B
NEW QUESTION # 23
Your Jira support project has allowed anonymous customers to create issues through an incoming mail handler for some time.
In order to enhance efficiency, your project manager has inquired about the possibility of allowing anonymous users to also create issues using Jira instead of the mail handler, but without allowing further access or need of a license.
Which two actions will let you meet the requirement? (Choose two.)
- A. Create an issue security scheme with a default level allowing only licensed Jira users to access issues.
- B. Ensure that the Reporter is not required in the project's field configuration scheme.
- C. Add Group Anyone to the Browse Projects permission in the project's permission scheme.
- D. Ensure that the Jira mode in the general configuration has been set to Public.
- E. Add Group Anyone to the Create Issues permission in the project's permission scheme.
Answer: C,D
NEW QUESTION # 24
A project is using the Approval workflow shown.
The project lead has communicated the following change requests:
- It should be possible to transition issues into the Awaiting Approval status from any other status apart from the Approved status.
- Different transition screens will be needed for each transition into the Awaiting Approval status.
How do you configure the workflow to satisfy these requirements?
- A. - Create a transition from the Open to the Awaiting Approval status.
- Reuse the existing transition screen from the Request approval transition. - B. - Create a transition from the Open to the Awaiting Approval status.
- Create appropriate transition screens and associate them with the individual transitions into the Awaiting Approval status. - C. - Create a global transition to the Awaiting Approval status.
- Create an appropriate transition screen and associate it with the global transition. - D. - Create a global transition to the Awaiting Approval status.
- Create multiple appropriate transition screens and associate it with the global transition. - E. - Reuse the Request approval transition between the Open and Awaiting Approval status.
- Create an appropriate transition screen and associate it with the transition.
Answer: C
NEW QUESTION # 25
You created a new "Create a new issue or add a comment to an existing issue" mail handler. What two fields have specific settings in the handler? (Choose two.)
- A. Custom Field
- B. Epic Link
- C. Priority
- D. Watchers
- E. Reporter
Answer: C,E
Explanation:
The question pertains to configuring a"Create a new issue or add a comment to an existing issue" mail handlerin Jira Software Cloud. Mail handlers process incoming emails to create issues or add comments, and certain fields can be specifically configured to control how the handler behaves. According to Jira Cloud documentation, the two fields with specific settings in this type of mail handler areReporterandPriority.
* Explanation of the Correct Answers:
* Reporter (Option C):
* TheReporterfield specifies the user who is set as the reporter of the issue created by the mail handler. In the mail handler configuration, you can define whether the reporter is set to a default user, derived from the email's "From" address (if the email address matches a Jira user), or another specified user.
* Exact Extract from Documentation:
Configuring an email handler
When setting up a mail handler like "Create a new issue or add a comment to an existing issue," you can configure the following settings:
* Reporter: Specify the user who will be set as the reporter for new issues. Options include:
* The user associated with the email's "From" address (if they have a Jira account).
* A default user (e.g., a project lead or a specific user account).
* If no valid user is found, the handler can be configured to reject the email or use a fallback user.This setting ensures that the issue is attributed to the correct user as the reporter.(Source: Atlassian Support Documentation, "Configure email handlers in Jira Cloud")
* Why This Fits: The Reporter field is a critical setting in the mail handler, as it determines who is recorded as creating the issue, which affects permissions, notifications, and reporting.
* Priority (Option D):
* ThePriorityfield allows you to set a default priority for issues created by the mail handler if the email does not explicitly specify a priority. This ensures that new issues have a consistent priority unless overridden by the email content.
* Exact Extract from Documentation:
Field settings for mail handlers
For the "Create a new issue or add a comment to an existing issue" handler, you can specify default values for certain fields, including:
* Priority: Set a default priority for new issues (e.g., Medium, High). If the email contains a specific priority value (e.g., via a keyword or mapping), it can override the default.These settings allow you to control the behavior of issue creation and ensure consistency in field values.(Source: Atlassian Support Documentation, "Configure email handlers in Jira Cloud")
* Why This Fits: The Priority field is explicitly configurable in the mail handler to ensure that new issues are assigned an appropriate priority, making it one of the two fields with specific settings.
* Why Other Options Are Incorrect:
* Epic Link (Option A):
* TheEpic Linkfield is not specifically configurable in the mail handler settings. While you can map email content to fields like Epic Link using advanced configurations (e.g., regex or scripting in Automation), it is not a standard field with specific settings in the mail handler configuration interface.
* Extract from Documentation:
Mail handlers allow mapping of email content to standard fields like Summary, Description, or Priority.
Advanced field mappings, such as Epic Link, require custom automation rules or third-party apps.
(Source: Atlassian Support Documentation, "Automate email processing with Jira Automation")
* Custom Field (Option B):
* While custom fields can sometimes be populated via email content (e.g., through regex or automation), the mail handler's standard configuration does not provide specific settings for custom fields. The handler focuses on system fields like Reporter and Priority.
* Extract from Documentation:
Custom fields are not directly supported in the default mail handler settings. To populate custom fields, you may need to use Jira Automation or a third-party mail handler app.
(Source: Atlassian Support Documentation, "Configure email handlers in Jira Cloud")
* Watchers (Option E):
* TheWatchersfield is not a configurable setting in the mail handler. You cannot specify default watchers or automatically add watchers based on email content in the standard mail handler configuration. Watchers are typically managed manually or via automation rules.
* Extract from Documentation:
Watchers are not a configurable field in mail handlers. To add watchers automatically, use JiraAutomation or a workflow post function.
(Source: Atlassian Support Documentation, "Configure notifications and watchers")
* Additional Notes:
* The"Create a new issue or add a comment to an existing issue" mail handleris one of several mail handler types in Jira Cloud. Its configuration focuses on ensuring that issues are created with the correct metadata (e.g., Reporter, Priority) and that comments are added to existing issues based on issue keys in the email subject.
* Configuring the Reporter and Priority fields ensures that issues created via email align with project workflows and notification schemes.
:
Atlassian Support Documentation:Configure email handlers in Jira Cloud
Atlassian Support Documentation:Automate email processing with Jira Automation Atlassian Support Documentation:Configure notifications and watchers
NEW QUESTION # 26
Two users have access to the same filter and see the same issues in a company-managed project. One of them can perform a bulk operation to watch issues in the filter, but the other user cannot. What should you investigate?
- A. Project roles
- B. Project permissions
- C. Default user preferences
- D. Groups
- E. Product access
Answer: B
Explanation:
The scenario describes two users who can view the same issues in a filter (indicating they have theBrowse Projectspermission), but only one can perform a bulk operation towatchissues. The ability to watch issues is controlled by theView Issue WatchersandManage Watcher Listpermissions in the project's permission scheme. Therefore, you should investigateproject permissions(Option A).
* Explanation of the Correct Answer (Option A):
* Performing a bulk operation to watch issues requires theManage Watcher Listpermission, which allows users to add themselves or others as watchers to an issue. Since both users can see the issues (via the filter), they likely have theBrowse Projectspermission, but the user who cannot perform the bulk operation may lack theManage Watcher Listpermission.
* Exact Extract from Documentation:
Manage Watcher List permission
TheManage Watcher Listpermission allows users to add or remove watchers from an issue, including via bulk operations. This permission is granted via the project's permission scheme.
Note: To view the watcher list, users also need theView Issue Watcherspermission. Both permissions are required to perform actions like bulk watching issues.
To check permissions:
* Go toProject settings > Permissions.
* Review theManage Watcher ListandView Issue Watcherspermissions to see which users, groups, or roles have them.(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Why This Fits: The difference in the users' ability to perform the bulk watch operation is most likely due to a difference in theirManage Watcher Listpermission, which is defined in the project's permission scheme. Investigating project permissions will reveal whether the second user lacks this permission.
* Why Other Options Are Incorrect:
* Product access (Option B):
* Product access determines whether users can use Jira Software. Both users can view the filter and issues, indicating they have product access. Product access does not control specific permissions like managing watchers.
* Extract from Documentation:
Manage product access
Product access grants users the ability to use Jira products. Specific actions, like managing watchers, are controlled by project or global permissions, not product access.
(Source: Atlassian Support Documentation, "Manage product access")
* Groups (Option C):
* Groups may be used in permission schemes to grant permissions, but the root cause is the permission itself, not the group membership. Investigating groups might be a secondary step after checking project permissions, butproject permissionsis the more direct answer.
* Extract from Documentation:
Groups are used in permission schemes to grant permissions to multiple users. To determine why a user lacks a permission, check the permission scheme first, then verify group membership if relevant.
(Source: Atlassian Support Documentation, "Manage groups")
* Default user preferences (Option D):
* Default user preferences (e.g., notification settings) control whether a user receives notifications for watched issues, not their ability to watch issues.The issue is about performing a bulk operation, not receiving notifications.
* Extract from Documentation:
Manage user preferences
Users can manage their notification preferences inPersonal settings > Email notifications. These settings affect notification delivery, not the ability to perform actions like watching issues.
(Source: Atlassian Support Documentation, "Manage your Jira notification emails")
* Project roles (Option E):
* Project roles are used in permission schemes to grant permissions. Like groups, roles are a means to assign permissions, but the issue lies in the permission itself (Manage Watcher List). Investigating project permissions directly addresses the root cause.
* Extract from Documentation:
Project roles are used in permission schemes to grant permissions likeManage Watcher List. Check the permission scheme to identify the root cause of permission differences.
(Source: Atlassian Support Documentation, "Manage project roles")
* Additional Notes:
* Both users can see the filter and issues, so they likely have theBrowse Projectspermission. The difference in their ability to perform the bulk watch operation points to theManage Watcher List permission, which should be checked inProject settings > Permissions.
* If the permission is granted to a group or role, verify the users' membership in those groups or roles as a follow-up step.
:
Atlassian Support Documentation:Manage permissions in Jira Cloud
Atlassian Support Documentation:Manage product access
Atlassian Support Documentation:Manage groups
Atlassian Support Documentation:Manage your Jira notification emails
Atlassian Support Documentation:Manage project roles
NEW QUESTION # 27
Alana has set up a new incoming mail handler to create issues or add a comment to an existing issue.
All new issues should be unassigned to triage them individually. You have not set up any components.
Sometimes issues are being randomly assigned to various users upon creation.
Which configuration can cause the observed behavior? (Choose one)
- A. An Update Issue Field workflow post function
- B. An Assign to Lead Developer workflow post function
- C. The CC Assignee setting of the mail handler
- D. The Default Assignee project setting
Answer: D
NEW QUESTION # 28
A dashboard displays an Issue Statistics gadget as shown.
The dashboard owner wants to change the order of the statuses shown in the gadget to appear as follows.
1. To Do
2. In Progress
3. Ready For QA
4. Blocked
5. Rejected
6. Done
Which action will permanently arrange the statuses into the required order?
- A. Change the category of the statuses.
- B. Change the Sort Direction option in the gadget to Ascending.
- C. Reorder the statues on the Status administration page.
- D. Change the gadget Sort By field to Total.
- E. Add numbers to the status names to allow them to be sorted in numerical order.
Answer: E
Explanation:
Reference: https://community.atlassian.com/t5/Jira-questions/How-to-change-order-of-statuses-in-a-Two- Dimension-filter/qaq-p/320423
NEW QUESTION # 29
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 existing users to send invitations to anyone
- C. Enable Jira Software and Confluence invite links
- D. Approve any domain
- E. Approve your organization domain only
Answer: D
NEW QUESTION # 30
One of your teams has noticed a spelling mistake in the name of an issue type.
What should you do before correcting the name of the issue type?
- A. Warn users that dashboard gadgets that refer to the issue type in their configuration will need to be updated with the corrected name.
- B. Warn users that saved filters using the issue type will not be able to find the issue type after the change.
- C. Update the issue type schemes to refer to the new name.
- D. Update the workflow schemes for the issue type to use the new name.
Answer: C
Explanation:
Reference: https://confluence.atlassian.com/adminjiracloud/adding-editing-and-deleting-an-issue-type-scheme-844500754.html
NEW QUESTION # 31
Critical production bugs in a Jira Software project are hidden with an issue security scheme that has a single security level.
Only project administrators are listed in the security level and granted the Set Issue Security permission.
A new requirement states that a few other Jira Core users, who have Browse Projects permission, should be able to see the hidden issues. These users will vary per issue and be selected from across various groups.
What needs to be added to the security level?
- A. Group
- B. Application access
- C. User custom field value
- D. Group custom field value
- E. Project role
- F. Single Users
Answer: E
Explanation:
Reference: https://confluence.atlassian.com/adminjiracloud/configuring-issue-level-security-776636711.html
NEW QUESTION # 32
Carlos describes his problem in the classic HR project
* He cannot attach files to issues of Request issue type when they are in the Approved status
* He can attach files to issues of Request issue type in any other status
* He can attach files to every other issue issue type in every status
He asks for your help in determining the root cause Select the root cause (Choose one)
- A. There is a workflow condition configured
- B. He does not have the correct project permission
- C. The Attachment field is missing on the screen used by the Request issue type
- D. He is not a member of a security level
- E. There is a workflow step property configured
Answer: E
NEW QUESTION # 33
You are prompted to perform a re-index after you have made configuration changes to a very large Jira instance.
Which reason would justify re-indexing only a project instead of a full re-index of the instance?
- A. Time tracking was modified for the project.
- B. Only custom fields used by the project were modified.
- C. Only project users would be affected by the re-index.
- D. Workflow changes were limited to the project's unique workflow.
Answer: B
Explanation:
Reference: https://confluence.atlassian.com/adminjiraserver079/search-indexing-950288998.html
NEW QUESTION # 34
You renamed a status in the workflow of a team-managed project. Which statement is true?
- A. The status will be renamed in all team-managed workflows.
- B. The status will be renamed on the Status page in Jira administration.
- C. Workflow rules that reference the status must be updated.
- D. Transitions coming into that status must be updated.
- E. Saved filters that reference the status must be updated.
Answer: E
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 # 35
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. Henry is missing the Assignable User project permission in the Jira project
- B. Henry is missing the Browse Projects project permission in the Jira project
- C. The Issue Assigned event does not list the current assignee as a recipient in the projects notification scheme
- D. Henry adjusted his personal email notification preference to not notify him when he is the assignee of an issue
- E. The Issue Updated event does not list the current assignee as a recipient in the project's notification scheme
Answer: C,E
NEW QUESTION # 36
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 both issue types, the Assignee field should be hidden when creating but not when viewing an issue.
- B. For the Fire issue type, the Description field should have a default value of "Termination".
- C. For the Hire issue type, the field description for the Due Date field should read "First day of work".
- D. For both issue types, the Resolution should be set once the issues are being resolved.
- E. For both issue types, the Employee Name custom field must be required upon creation and must never be blank.
- F. For the Fire issue type, the default value for the Priority field should be Blocker.
Answer: A,D
NEW QUESTION # 37
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. Radio buttons
- C. Checkboxes
- D. Paragraph
Answer: B,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 # 38
Your site contains the following:
* Alpha filter: Public
* Beta filter: Private
* Omega dashboard: PublicThe system setting 'Allow users to share dashboards and filters with the public' is currently set to ON. You change that setting to OFF. What is the impact of this change?
- A. You cannot set Viewers to Private on Alpha filter.
- B. You cannot set Viewers to Public on Beta filter.
- C. Users who are not logged in cannot see Alpha filter.
- D. Users who are not logged in cannot see Omega dashboard.
Answer: C,D
NEW QUESTION # 39
You want to introduce Jira to your small non-profit organization.
Since you are unsure of the optimal deployment option you have gathered some requirements:
- You need to manage a team of up to 15 employees.
- You need to be able to track a backlog of staff action items.
- You want to easily visualize the progress of ongoing work.
The solution must require minimal administration since your organization only has a part-time IT volunteer.
What solution is most appropriate for your organization?
- A. Jira Service Desk Data Center
- B. Jira Core Server
- C. Jira Software Data Center
- D. Jira Service Desk Cloud
Answer: D
NEW QUESTION # 40
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. Global permissions
- C. Project permissions
- D. Product access
- E. Security levels
Answer: C
NEW QUESTION # 41
......
The Atlassian ACP-120 exam is a web-based, proctored exam that consists of 70 multiple-choice questions. ACP-120 exam is timed for 180 minutes, and the passing score is 65%. ACP-120 exam is conducted in English and is available to candidates worldwide.
Authentic Best resources for ACP-120 Online Practice Exam: https://www.dumpsfree.com/ACP-120-valid-exam.html
Get the superior quality ACP-120 Dumps with explanations waiting just for you, get it now: https://drive.google.com/open?id=1aGudVD7SRwjiXbTvGtbiaJvi9dniYBfd