NEW 2025 Certification Sample Questions ACP-120 Dumps & Practice Exam
ACP-120 Deluxe Study Guide with Online Test Engine
NEW QUESTION # 46
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. Users who are not logged in cannot see Omega dashboard.
- B. You cannot set Viewers to Private on Alpha filter.
- C. Users who are not logged in cannot see Alpha filter.
- D. You cannot set Viewers to Public on Beta filter.
Answer: A,C
NEW QUESTION # 47
Many projects share the same permission scheme and workflow scheme.
The requirements in those projects are:
- Only Translators should be able to use the Translation workflow transition.
- The same team of Translators work across all the projects.
How should Translators be configured to meet these requirements?
- A. As single users
- B. As a Group custom field
- C. As a group
- D. As a User custom field
- E. As a project role
Answer: E
Explanation:
Reference: https://confluence.atlassian.com/adminjiracloud/configuring-projects-776636280.html
NEW QUESTION # 48
One of the HR managers created a filter and shared the subscription with members of the hr- managers group. The filter contains the following valid JQL query:
Manager = currentUser() AND Manager in membersOf("hr-managers")
Which issues will be included in the subscription?
- A. Only issues where the user who created the filter is listed in the Manager field.
- B. Only issues where the recipient of the email is listed in the Manager field.
- C. All issues where the user listed in the Manager field is a member of the hr-managers group.
- D. All issues that are assigned to any member of the hr-managers group.
- E. Only issues where the group hr-managers is listed in the Manager field.
Answer: C
NEW QUESTION # 49
Jan asked you to create a new Select List custom field called Department for his project MCAS. You created the field in the morning. In the afternoon, Jan notes that his Jira dashboard is not showing the field correctly. He asks to help him troubleshoot.
View the Exhibit to see Jan's entire dashboard.
- The first gadget shows 26 issues in the project by Status.
- The second gadget shows that there are three issues that have the new Department field set.
- The last gadget shows "No Data Available". The filter query for that gadget is "project=MCAS and Department is empty."
Why does Jan's gadget say "No Data Available"?
- A. There is issue security on the issues.
- B. The JQL query for the filter is not valid.
- C. Jan does not have the proper Browse permissions.
- D. You created the field Department but did not re-index the MCAS project.
- E. The field is marked Optional in the Field Configuration.
- F. The field context on the Department field was not set to allow empty values.
Answer: F
NEW QUESTION # 50
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 adjusted his personal email notification preference to not notify him when he is the assignee of an issue
- B. The Issue Assigned event does not list the current assignee as a recipient in the projects notification scheme
- C. Henry is missing the Browse Projects 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 Assignable User project permission in the Jira project
Answer: A,B
NEW QUESTION # 51
The HR team approaches you with new requirements they want you to implement:
- Allow users to send requests into Jira by emailing "[email protected]."
- Have those emails automatically turned into "Holiday Requests" in the HR project.
You have already set up an Incoming Mail Server and a mail handler to "Create a new issue or add a comment to an existing issue." Which three additional options can you set with this mail configuration? (Choose three.)
- A. Set default Reporter.
- B. Set Assignee and Watchers.
- C. Create new Jira users based on the From address.
- D. Set Environment.
- E. Set a custom field.
Answer: A,D,E
NEW QUESTION # 52
The operations team currently uses the OPS project to track their tasks. They have a new requirement to begin handling change requests.
Inspect the partial summary of the current OPS project configuration:
Which two requirements would require creating a new project? (Choose two.)
- A. Change requests will have a different workflow.
- B. Change requests will notify different people for all system events.
- C. Change requests will have different component leads.
- D. Change requests will not use versions.
- E. Change requests will require the Due Date field to be populated.
Answer: B,E
NEW QUESTION # 53
Martin has Create Attachments permission in a software project, but he cannot attach anything to issues in Approved status.
What is the problem?
- A. The Attachment field is missing from the screen for that issue type.
- B. There is a workflow condition configured.
- C. He does not have the correct project permission.
- D. There is a workflow step property configured.
- E. He is not a member of a security level.
Answer: C
Explanation:
Reference: https://confluence.atlassian.com/adminjiracloud/configuring-file-attachments-818578880.html
NEW QUESTION # 54
You renamed a value in the Resolution field from Done to Finished. What might need to be updated as a result?
- A. Workflow post functions
- B. Issues in team-managed projects
- C. Issue Statistics gadgets
- D. Issue detail view
- E. Saved filters
Answer: E
Explanation:
Renaming a value in theResolutionfield (fromDonetoFinished) changes its display name globally in Jira Software Cloud. This can impact configurations or features that reference the resolution value by name, particularly in JQL queries. The element most likely to need updating issaved filters(Option B), as they often use JQL queries that include resolution values.
* Explanation of the Correct Answer (Option B):
* Saved filtersoften use JQL queries that reference resolution values (e.g., resolution = Done). If theResolutionfield value is renamed fromDonetoFinished, any filters using resolution = Done will no longer match issues with the renamed resolution (Finished), as the old value is no longer valid. These filters must be updated to use resolution = Finished to continue returning the correct issues.
* Exact Extract from Documentation:
Manage resolutions in Jira Cloud
Resolutions are global values used in theResolutionfield to indicate an issue's resolution state.
Impact of renaming a resolution:
* JQL queries in filters, boards, or gadgets referencing the resolution name (e.g., resolution = Done) will no longer match issues if the value is renamed (e.g., to Finished).To update:
* Go toIssues > Manage filters.
* Edit filters to use the new resolution name (e.g., resolution = Finished).Note: Renaming a resolution affects all projects and requires updating JQL-based configurations.(Source:
Atlassian Support Documentation, "Manage resolutions in Jira Cloud")
* Why This Fits: Renaming a resolution value impactssaved filtersthat use JQL queries referencing the old value, requiring updates to maintain functionality, making Option B the correct answer.
* Why Other Options Are Incorrect:
* Workflow post functions (Option A):
* Workflow post functionscan set theResolutionfield (e.g.,Set Issue ResolutiontoDone).
These post functions typically use the resolution's internal ID, not its display name, so renamingDonetoFinisheddoes not require changes to post functions.
* Extract from Documentation:
Post functions reference resolution IDs, not names. Renaming a resolution does not affect workflow configurations.
(Source: Atlassian Support Documentation, "Configure advanced work item workflows")
* Issue detail view (Option C):
* Theissue detail viewdisplays theResolutionfield value as configured. RenamingDoneto Finishedupdates the display automatically without requiring manual changes to the issue detail view or its configuration (e.g.,issue layout).
* Extract from Documentation:
The issue detail view reflects the current resolution name automatically. No changes are needed after renaming a resolution.
(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud")
* Issue Statistics gadgets (Option D):
* Issue Statistics gadgets(e.g., on dashboards) can display data based on fields like Resolution. While gadgets may reference resolution values in their configuration, they typically use resolution IDs or dynamically update to reflect the renamed value. The impact is less direct than with saved filters, which rely on explicit JQL queries.
* Extract from Documentation:
Gadgets like Issue Statistics use field values or IDs. Renaming a resolution may not require gadget updates unless JQL queries are explicitly used.
(Source: Atlassian Support Documentation, "Manage dashboards in Jira Cloud")
* Issues in team-managed projects (Option E):
* Resolutionsare global and apply to both company-managed and team-managed projects.
RenamingDonetoFinishedupdates the value for all issues, including those in team- managed projects, without requiring changes to the issues themselves. The change is reflected automatically.
* Extract from Documentation:
Resolutions are global and apply to all projects. Renaming a resolution updates its display for all issues without requiring issue-level changes.
(Source: Atlassian Support Documentation, "Manage resolutions in Jira Cloud")
* Additional Notes:
* Renaming a resolution is done inSettings > Issues > Resolutionsand requiresJira administrator privileges.
* Other JQL-based features (e.g., automation rules, boards) may also be impacted if they reference the resolution name, butsaved filtersare the most commonly affected.
* To minimize impacts, use resolution IDs in JQL queries (e.g., resolution = 10000), though this is less common.
:
Atlassian Support Documentation:Manage resolutions in Jira Cloud
Atlassian Support Documentation:Configure advanced work item workflows
Atlassian Support Documentation:Configure issue layouts in Jira Cloud
Atlassian Support Documentation:Manage dashboards in Jira Cloud
NEW QUESTION # 55
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. Only custom fields used by the project were modified.
- B. Workflow changes were limited to the project's unique workflow.
- C. Time tracking was modified for the project.
- D. Only project users would be affected by the re-index.
Answer: A
Explanation:
Reference: https://confluence.atlassian.com/adminjiraserver079/search-indexing-950288998.html
NEW QUESTION # 56
Which time tracking configuration can be controlled on a global basis for all projects in Jira?
- A. which users or groups have the ability to log work on issues
- B. the default time unit on estimates when users don't explicitly specify one
- C. whether time tracking fields are available on standard versus sub-task issue types
- D. whether Original Estimate is required when creating issues
- E. which users have the ability to edit or delete their own or other users' worklogs
Answer: B
Explanation:
Reference: https://www.softwaretestinghelp.com/jira-time-tracking/
NEW QUESTION # 57
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. Ensure that the Reporter is not required in the project's field configuration scheme.
- B. Create an issue security scheme with a default level allowing only licensed Jira users to access issues.
- C. Ensure that the Jira mode in the general configuration has been set to Public.
- D. Add Group Anyone to the Create Issues permission in the project's permission scheme.
- E. Add Group Anyone to the Browse Projects permission in the project's permission scheme.
Answer: C,E
NEW QUESTION # 58
A team in your company requests a new Jira project that fulfills the following requirements:
* Ability to work on issues in weekly iterations
* Allows the project administrators to create their own fields
The project should fulfill these requirements right after creation without the need to enable additional features.
Which project should you create?
- A. Team-managed project with Scrum template
- B. Company-managed project with Scrum template
- C. Team-managed project with Canban template
- D. A company-managed project with Kanban template
Answer: B
NEW QUESTION # 59
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 the Reporter can close bugs.
- B. Rule to clear the Assignee when closing.
- C. Rule to reopen Sub-tasks when reopening Stories.
- D. Rule to clear the Description when reopening.
- E. Rule to ensure only Peter can approve Stories.
Answer: C
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 # 60
You need to create a filter that shows only issues that were created during the last calendar month. Identify the correct JQL query.
- A. created changed during (startOfMonth(), endOfMonth())
- B. createdDate >= startOfMonth(-1) OR createdDate <= endOfMonth(-1)
- C. createdDate >= startOfMonth(-1m) AND createdDate <= endOfMonth(-1m)
- D. created >= startOfMonth(-1) AND created <= endOfMonth(-1)
Answer: C
Explanation:
To create a filter that shows issues created during the last calendar month, the JQL query must use the createdDatefield with thestartOfMonth(-1m)andendOfMonth(-1m)functions to define the time range. The correct query iscreatedDate >= startOfMonth(-1m) AND createdDate <= endOfMonth(-1m)(Option D).
* Explanation of the Correct Answer (Option D):
* ThecreatedDatefield represents the date an issue was created. ThestartOfMonth(-1m)function returns the first day of the previous month (e.g., April 1, 2025, for May 2025), andendOfMonth (-1m)returns the last day of the previous month (e.g., April 30, 2025). The querycreatedDate >= startOfMonth(-1m) AND createdDate <= endOfMonth(-1m)selects issues created within this range, covering the entire last calendar month.
* Exact Extract from Documentation:
Search for issues using JQL
ThecreatedDatefield (orcreatedalias) stores the creation date of an issue. Use date functions like startOfMonth()andendOfMonth()to define time ranges.
Examples:
* createdDate >= startOfMonth(-1m) AND createdDate <= endOfMonth(-1m) returns issues created in the previous calendar month.
* Use-1mto indicate one month ago.Note: Ensure date fields use>=and<=for inclusive ranges.
(Source: Atlassian Support Documentation, "Search for issues using JQL")
* Why This Fits: The query in Option D correctly usescreatedDate,startOfMonth(-1m), and endOfMonth(-1m)withANDto define the last calendar month, making it the correct answer.
* Why Other Options Are Incorrect:
* created changed during (startOfMonth(), endOfMonth()) (Option A):
* Thechanged duringoperator is used for fields that track changes (e.g., status, assignee), not for static fields likecreated. Additionally,startOfMonth()andendOfMonth()without-1 mrefer to the current month, not the last month.
* Extract from Documentation:
Thechanged duringoperator is invalid for thecreatedfield. Use>=and<=for date comparisons.
(Source: Atlassian Support Documentation, "Advanced searching - operators reference")
* createdDate >= startOfMonth(-1) OR createdDate <= endOfMonth(-1) (Option B):
* TheORoperator creates a logical error, selecting issues created after the start of the previous monthorbefore the end of the previous month, which includes almost all issues.
Additionally,-1is ambiguous and typically invalid without a unit (e.g.,-1mfor one month).
The correct operator isANDto define a range.
* Extract from Documentation:
UseANDto define a date range (e.g., createdDate >= startOfMonth(-1m) AND createdDate <= endOfMonth(-1 m)).ORcreates an overly broad range.
(Source: Atlassian Support Documentation, "Advanced searching - operators reference")
* created >= startOfMonth(-1) AND created <= endOfMonth(-1) (Option C):
* The-1syntax without a unit (e.g.,-1m) is ambiguous and typically invalid in JQL. The correct syntax uses-1mto indicate one month ago. Additionally, whilecreatedis an alias for createdDate, the incorrect time unit makes this query invalid.
* Extract from Documentation:
Date functions require units likemfor months (e.g.,startOfMonth(-1m)). Without a unit, the query is invalid.
(Source: Atlassian Support Documentation, "Advanced searching - functions reference")
* Additional Notes:
* The filter can be created inIssues > Search for issues, saved as a filter, and shared if needed.
* Thecreatedalias can be used instead ofcreatedDate, butcreatedDateis more explicit and matches the options.
* Ensure the Jira instance's timezone aligns with the expected month range.
:
Atlassian Support Documentation:Search for issues using JQL
Atlassian Support Documentation:Advanced searching - operators reference Atlassian Support Documentation:Advanced searching - functions reference
NEW QUESTION # 61
Billie needs to perform various restricted tasks in the system. You must decide whether to grant her site admin or organization admin privileges.
Identify two reasons why you must make her an organization admin (Choose two)
- A. Billie needs to make changes to user's profiles
- B. Billie needs to remove users from the site
- C. Billie needs to enable other users to be site or product admins
- D. Billie needs to log in as other users for troubleshooting user accounts
- E. Billie needs to enable other users to be organization admins
Answer: B,E
NEW QUESTION # 62
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. Summary
- B. Project, Issue Type
- C. Summary, Issue Type
- D. Project
- E. Project, Summary
Answer: A
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 # 63
You performed the following steps:
* Created a new filter with the JQL query project IN projectsWhereUserHasRole("Sales")
* Created a filter subscription for the filter and set the recipients to the Sales group.
Leila is a member of the Sales group. Which issues will Leila receive in her subscription?
- A. Issues from projects where Leila is in the Sales group
- B. Issues from projects where Leila is in the Sales role
- C. Issues assigned to anyone in the Sales role
- D. Issues assigned to anyone in the Sales group
Answer: B
Explanation:
The JQL query project IN projectsWhereUserHasRole("Sales") filters for issues in projects wherethe user running the query has theSalesproject role. Since Leila is a member of theSales groupand receives the filter subscription, the issues she receives are those from projects whereLeila is in the Sales role(Option A).
* Explanation of the Correct Answer (Option A):
* The JQL functionprojectsWhereUserHasRole("Sales")returns a list of projects where the user executing the query is a member of theSalesproject role. The query project IN projectsWhereUserHasRole("Sales") selects all issues from those projects.
* Leila, as a member of theSales group, receives the filter subscription. When the subscription runs for Leila, the JQL query is evaluated in her context, meaning it returns issues from projects where Leilahas theSalesproject role.
* Exact Extract from Documentation:
Advanced searching - functions reference
TheprojectsWhereUserHasRole("role")function returns projects where the user running the query is a member of the specified project role.
Example:
* project IN projectsWhereUserHasRole("Sales") returns issues from projects where the user has theSalesproject role.Note: For filter subscriptions, the query is executed in the context of each recipient, so results depend on the recipient's role membership.(Source: Atlassian Support Documentation, "Advanced searching - functions reference")
* Why This Fits: The filter subscription runs the JQL query for Leila, returning issues from projects whereLeila is in the Sales role, making Option A the correct answer.
* Why Other Options Are Incorrect:
* Issues assigned to anyone in the Sales group (Option B):
* The JQL query does not filter byassigneeor group membership. It only selects issues based on the projects where the user has theSalesrole, regardless of who the issues are assigned to.
* Extract from Documentation:
To filter by assignee, use assignee in membersOf("group"). TheprojectsWhereUserHasRolefunction filters by project, not assignee.
(Source: Atlassian Support Documentation, "Advanced searching - fields reference")
* Issues from projects where Leila is in the Sales group (Option C):
* The query usesprojectsWhereUserHasRole("Sales"), which checks for theSalesproject role, not a group. Project roles and groups are distinct, and the query does not reference group membership.
* Extract from Documentation:
Project roles are project-specific and distinct from groups. UseprojectsWhereUserHasRolefor roles, not membersOffor groups.
(Source: Atlassian Support Documentation, "Advanced searching - functions reference")
* Issues assigned to anyone in the Sales role (Option D):
* The query does not filter byassigneeor role membership of the assignee. It selects issues from projects where the user (Leila) has theSalesrole, not issues assigned to users in that role.
* Extract from Documentation:
To filter by assignees in a role, additional JQL or scripting is needed.projectsWhereUserHasRoleonly filters by project.
(Source: Atlassian Support Documentation, "Advanced searching - fields reference")
* Additional Notes:
* TheSalesproject role must exist in the relevant projects, and Leila must be added to it inProject settings > Peoplefor those projects.
* The subscription sends emails to theSales group, and each recipient (like Leila) seesissues based on their own role membership in the JQL query's context.
* Leila must haveBrowse Projectspermission for the projects returned by the query to see the issues.
:
Atlassian Support Documentation:Advanced searching - functions reference Atlassian Support Documentation:Advanced searching - fields reference Atlassian Support Documentation:Manage filters in Jira Cloud
NEW QUESTION # 64
In his personal settings, Bob has the setting "Email notifications for issue activity set to "Don't send me email notifications".
Identify two reasons why Bob continues to receive some email notifications from Jira (Choose two)
- A. Bob has been subscribed to several filters
- B. Bob has the Watch your issues setting enabled
- C. Bob was sent an email via the Send email feature in Jira
- D. Bob was added as a watcher of an issue
- E. Bob is mentioned directly in a comment
Answer: A,C
NEW QUESTION # 65
......
ACP-120 dumps review - Professional Quiz Study Materials: https://www.exam4labs.com/ACP-120-practice-torrent.html
ACP-120 Test Prep Training Practice Exam Questions Practice Tests: https://drive.google.com/open?id=15uQVetaHZSEOs47TZtC4WOYLl11Bjue6