CertsOut ATLASSIAN-ACP-120

ATLASSIAN ACP-120

Jira Administration for Cloud Version: Demo [ Total Questions: 10]

Web: www.certsout.com Email: support@certsout.com

IMPORTANT NOTICE Feedback We have developed quality product and state-of-art service to ensure our customers interest. If you have any suggestions, please feel free to contact us at feedback@certsout.com

Support If you have any questions about our product, please provide the following items: exam code screenshot of the question login id/email please contact us at support@certsout.com and our technical experts will provide support within 24 hours.

Copyright The product of each order has its own encryption code, so you should use it independently. Any unauthorized changes will inflict legal punishment. We reserve the right of final explanation for this statement.

Certs Exam

ATLASSIAN - ACP-120

Category Breakdown Category Number of Questions Advanced User Features 4 Issue Types, Fields, Screens 3 Workflows and Automation 2 System Administration and Administering Jira 1 TOTAL 10 Question #:1 - [Advanced User Features] Level custom field contains three options: Beginner, Intermediate, Advanced Pro. You need to find issues in any of the levels. Identify the correct JQL query.

A. Level = Beginner OR Level = Intermediate OR Level = Advanced Pro B. Level IN (Beginner, Intermediate, "Advanced Pro") C. Level ~ (Beginner, Intermediate, "Advanced Pro") D. Level IN (Beginner, Intermediate OR Advanced Pro) Answer: B

Explanation To find issues where theLevelcustom field (a single-select field) has any of the valuesBeginner,Intermediate , orAdvanced Pro, the JQL query must use theINoperator to check for multiple values. The correct query is Level IN (Beginner, Intermediate, "Advanced Pro")(Option B), as it properly handles the multi-word value Advanced Prowith quotes.

Explanation of the Correct Answer (Option B): TheLevelcustom field is a single-select field with three options:Beginner,Intermediate, and Advanced Pro. TheINoperator allows checking if a field’s value matches any of a list of values.

For multi-word values likeAdvanced Pro, quotes are required to treat it as a single value.

The queryLevel IN (Beginner, Intermediate, "Advanced Pro")searches for issues where the Levelfield is set toBeginner,Intermediate, orAdvanced Pro, covering all possible values.

Exact Extract from Documentation: Advanced searching - operators reference TheINoperator checks if a field’s value matches any of the specified values.

Example:

Pass with Valid Exam Questions Pool

1 of 26

Certs Exam

ATLASSIAN - ACP-120

Level IN (Beginner, Intermediate, "Advanced Pro") returns issues where theLevelfield is set toBeginner,Intermediate, orAdvanced Pro.Note: For values containing spaces (e.g., Advanced Pro), enclose the value in double quotes.(Source: Atlassian Support Documentation, "Advanced searching - operators reference") Why This Fits: TheINoperator with properly quoted values efficiently searches for all specified Leveloptions, making Option B the correct answer.

Why Other Options Are Incorrect: Level = Beginner OR Level = Intermediate OR Level = Advanced Pro (Option A): This query is functionally correct but less efficient than usingIN. It requires multiple= operators and does not handle the multi-word valueAdvanced Procorrectly without quotes, potentially causing a syntax error.

Extract from Documentation: UseINfor concise queries with multiple values. MultipleORclauses are valid but less efficient and require quotes for multi-word values.

(Source: Atlassian Support Documentation, "Advanced searching - operators reference") Level ~ (Beginner, Intermediate, "Advanced Pro") (Option C): The~operator is used for partial text matching (e.g., wildcard searches) and is not valid for single-select fields likeLevel, which require exact value matching. This query is syntactically incorrect.

Extract from Documentation: The~operator is for text fields and partial matching, not for select fields. Use=orINfor exact value matching.

(Source: Atlassian Support Documentation, "Advanced searching - operators reference") Level IN (Beginner, Intermediate OR Advanced Pro) (Option D): This query is syntactically incorrect, as theINoperator requires a comma-separated list of values, not logical operators likeOR. Additionally,Advanced Proneeds quotes to be treated as a single value.

Extract from Documentation: TheINoperator requires a list of values (e.g., (value1, value2, "value3")). Logical operators likeORare not allowed insideIN. (Source: Atlassian Support Documentation, "Advanced searching - operators reference")

Pass with Valid Exam Questions Pool

2 of 26

Certs Exam

ATLASSIAN - ACP-120

Additional Notes: TheLevelfield must be a single-select custom field with the exact options listed.Verify the field’s configuration inSettings > Issues > Custom fields.

The query can be tested inIssues > Search for issuesand saved as a filter.

Ensure the user hasBrowse Projectspermission for the relevant projects. : Atlassian Support Documentation:Advanced searching - operators reference Atlassian Support Documentation:Search for issues using JQL Question #:2 - [Issue Types, Fields, Screens] 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. Saved filters C. Issue detail view D. Issue Statistics gadgets E. Issues in team-managed projects Answer: B

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:

Pass with Valid Exam Questions Pool

3 of 26

Certs Exam

ATLASSIAN - ACP-120

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):

Pass with Valid Exam Questions Pool

4 of 26

Certs Exam

ATLASSIAN - ACP-120

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 teammanaged 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 Question #:3 - [Workflows and Automation] Pass with Valid Exam Questions Pool

5 of 26

Certs Exam

ATLASSIAN - ACP-120

An automation rule should send an email with the issue key in the subject line. Identify the correct syntax to use in the Send Email action.

A. {{triggerIssue.issuekey}} B. {{issue.key}} C. {{issueKey}} D. {issue.issuekey} E. issue.key Answer: B

Explanation In Jira Software Cloud, automation rules usesmart valuesto reference issue fields, such as the issue key, in actions like sending emails. The correct syntax for referencing the issue key in theSend Emailaction’s subject line is{{issue.key}}(Option B).

Explanation of the Correct Answer (Option B): The{{issue.key}}smart value retrieves the issue key (e.g., PROJ-123) of the issue that triggers or is processed by the automation rule. This can be used in the subject line of theSend Emailaction to include the issue key dynamically.

Exact Extract from Documentation: Use smart values in automation rules Smart values allow you to access issue fields and other data in automation actions. To reference the issue key: Use{{issue.key}}to insert the issue key (e.g., PROJ-123) in fields like email subjects or bodies.Examples: Email subject: Issue {{issue.key}} Updated Output: Issue PROJ-123 UpdatedNote: Smart values are enclosed in double curly braces ({{}}). Use dotnotation to access fields (e.g., {{issue.key}}, {{issue.summary}}).(Source: Atlassian Support Documentation, "Use smart values in Jira automation") Why This Fits: The{{issue.key}}syntax is the standard way to reference the issue key in Jira automation, making it the correct choice for theSend Emailaction’s subject line.

Why Other Options Are Incorrect: {{triggerIssue.issuekey}} (Option A):

Pass with Valid Exam Questions Pool

6 of 26

Certs Exam

ATLASSIAN - ACP-120 The{{triggerIssue}}smart value refers to the issue that triggers the rule, but the field iskey, notissuekey. The correct syntax is{{triggerIssue.key}}, not{{triggerIssue.issuekey}}.

Additionally,{{issue.key}}is sufficient for most rules unless specifically targeting the trigger issue in a branched rule.

Extract from Documentation:

Use{{triggerIssue.key}}to reference the key of the issue that triggers the rule.{{issue.key}}is used for the current issue in the rule’s context.

(Source: Atlassian Support Documentation, "Use smart values in Jira automation") {{issueKey}} (Option C): Smart values require dot notation for field access (e.g.,{{issue.key}}).{{issueKey}}is not a valid smart value, as it does not reference a specific field.

Extract from Documentation: Smart values must reference valid fields using dot notation (e.g., {{issue.key}}, {{issue.summary}}). Single variables like {{issueKey}} are not supported.

(Source: Atlassian Support Documentation, "Use smart values in Jira automation") {issue.issuekey} (Option D): The syntax uses single curly braces andissuekeyinstead ofkey, which is incorrect. Smart values require double curly braces ({{}}) and the correct field name (key).

Extract from Documentation: Smart values use double curly braces ({{}}) and standard field names (e.g., {{issue.key}}). Incorrect formats like {issue.issuekey} will not work.

(Source: Atlassian Support Documentation, "Use smart values in Jira automation") issue.key (Option E): Without curly braces,issue.keyis treated as plain text, not a smart value. It will not resolve to the issue key and will appear literally in the email subject.

Extract from Documentation: Smart values must be enclosed in {{}} to be evaluated. Plain text like issue.key will not resolve to a field value.

(Source: Atlassian Support Documentation, "Use smart values in Jira automation") Additional Notes:

Pass with Valid Exam Questions Pool

7 of 26

Certs Exam

ATLASSIAN - ACP-120 TheSend Emailaction in Jira automation allows smart values in the subject and body to dynamically include issue data.

If the rule involves branching or multiple issues,{{issue.key}}refers to the current issue in the rule’s context, while{{triggerIssue.key}}refers to the triggering issue. For a simple email rule, {{issue.key}}is typically sufficient.

: Atlassian Support Documentation:Use smart values in Jira automation Atlassian Support Documentation:Automate your Jira Cloud instance Question #:4 - [Workflows and Automation] An automation rule is configured as shown: When: Rule is triggered on All comments If: Initiator is in Developers Then: Transition the issue to DEVELOPMENT If: Initiator is in Reviewers Then: Transition the issue to REVIEWYou are only in the Reviewers project role. What happens when you comment on an issue?

A. The rule does not execute.

B. The issue transitions to REVIEW. C. The rule executes but does not perform any actions.

D. The issue transitions to DEVELOPMENT. Answer: B

Explanation The automation rule is triggered when any comment is added to an issue and checks the initiator’s project role to determine the action. Since you are only in theReviewersproject role, commenting on an issue will trigger the rule, and the issue will transition toREVIEWbased on the rule’s logic.

Explanation of the Correct Answer (Option B): The rule is triggered byAll comments, meaning any comment on an issue activates the rule.

The rule has twoIfconditions:

Pass with Valid Exam Questions Pool

8 of 26

Certs Exam

ATLASSIAN - ACP-120 If the initiator (the user who commented) is in theDevelopersproject role, the issue transitions toDEVELOPMENT. If the initiator is in theReviewersproject role, the issue transitions toREVIEW. Since you are only in theReviewersproject role, the secondIfcondition is met when you comment, and theThenaction transitions the issue toREVIEW. Exact Extract from Documentation:

Configure automation rules Automation rules consist of triggers, conditions, and actions.

Trigger: Defines when the rule runs (e.g., Comment Added).

Condition: Checks criteria like user roles (e.g., Initiator is in Reviewers).

Action: Performs tasks like transitioning an issue.Conditions are evaluated sequentially, and the corresponding action is executed if the condition is met. If multiple conditions apply, each matching condition’s action is executed unless restricted by rule logic.Note: The initiator is the user who triggers the rule (e.g., the commenter).(Source: Atlassian Support Documentation, "Automate your Jira Cloud instance") Why This Fits: As a member of theReviewersproject role, your comment satisfies theIf: Initiator is in Reviewerscondition, triggering theTransition the issue to REVIEWaction, making Option B the correct answer.

Why Other Options Are Incorrect: The rule does not execute (Option A): The rule is triggered byAll comments, so any comment, including yours, will execute the rule. The issue is not whether the rule executes but what action it performs.

Extract from Documentation: AComment Addedtrigger activates the rule whenever a comment is added to an issue, regardless of the user’ s role.

(Source: Atlassian Support Documentation, "Jira automation triggers") The rule executes but does not perform any actions (Option C): The rule executes and performs theTransition the issue to REVIEWaction because you are in theReviewersproject role, which satisfies the secondIfcondition. The rule will not skip actions if a condition is met.

Extract from Documentation:

Pass with Valid Exam Questions Pool

9 of 26

Certs Exam

ATLASSIAN - ACP-120

If a condition in an automation rule is met, the associated action is executed unless restricted by additional logic.

(Source: Atlassian Support Documentation, "Automate your Jira Cloud instance") The issue transitions to DEVELOPMENT (Option D): TheDEVELOPMENTtransition is only triggered if the initiator is in theDevelopersproject role. Since you are only in theReviewersrole, this condition is not met, and the issue will not transition toDEVELOPMENT. Extract from Documentation: Conditions likeInitiator is in [Role]check the user’s project role membership. Only the actions for matching conditions are executed.

(Source: Atlassian Support Documentation, "Jira automation conditions") Additional Notes: The rule assumes theDEVELOPMENTandREVIEWstatuses exist in the project’s workflow and that transitions to these statuses are valid from the issue’s current status.

If you were in bothDevelopersandReviewersroles, both actions could execute sequentially, but the question specifies you are only inReviewers, so only theREVIEWtransition applies. : Atlassian Support Documentation:Automate your Jira Cloud instance Atlassian Support Documentation:Jira automation triggers Atlassian Support Documentation:Jira automation conditions Question #:5 - [System Administration and Administering Jira] A Jira administrator makes the following changes to User Default Settings: • Default sharing for filters and dashboards is set to Public.

• Autowatch own issues is set to Yes. Which two statements are definitely true? (Choose two.)

A. Only newly created dashboards will reflect the new default setting.

B. Saved filters using the old default setting will reflect the new default setting.

C. Only newly created saved filters will reflect the new default setting.

D. Pass with Valid Exam Questions Pool

10 of 26

Certs Exam

ATLASSIAN - ACP-120

D. All users will become watchers of issues they have created in the past.

Answer: A C

Explanation The changes toUser Default Settingsaffect the default behavior for new filters, dashboards, and issue watching. The two statements that are definitely true areonly newly created dashboards will reflect the new default setting(Option A) andonly newly created saved filters will reflect the new default setting(Option C), as these settings apply to new creations only.

Explanation of the Correct Answers: Only newly created dashboards will reflect the new default setting (Option A): Changing theDefault sharing for filters and dashboardstoPublicin User Default Settings sets the default sharing option for newly created dashboards toPublic. Existing dashboards retain their original sharing settings (e.g., Private, Group) and are not affected by the change. Only dashboards created after the setting is updated will default toPublic.

Exact Extract from Documentation: Manage user default settings TheDefault sharing for filters and dashboardssetting determines the default sharing option for new filters and dashboards.

To configure: Go toSettings > System > User default settings.

SetDefault sharingtoPublic,Private, or another option.Impact: Only newly created filters and dashboards use the new default setting.

Existing filters and dashboards retain their original sharing settings.Note: Requires Jira administrator permissions.(Source: Atlassian Support Documentation, "Manage user default settings in Jira Cloud") Why This Fits: The change toPublicsharing applies only to newly created dashboards, making Option A definitely true.

Only newly created saved filters will reflect the new default setting (Option C): Similarly, theDefault sharingsetting affects the default sharing option for newly created saved filters. Filters created after the change will default toPublic, but existing filters keep their original sharing settings (e.g., Private, Group).

Exact Extract from Documentation:

Pass with Valid Exam Questions Pool

11 of 26

Certs Exam

ATLASSIAN - ACP-120

Manage user default settings Changing theDefault sharing for filters and dashboardstoPublicapplies to new filters and dashboards only.

Impact: Existing saved filters are not updated to the new default sharing setting.

New filters created after the change will default toPublic.(Source: Atlassian Support Documentation, "Manage user default settings in Jira Cloud") Why This Fits: The change toPublicsharing applies only to newly created saved filters, making Option C definitely true.

Why Other Options Are Incorrect: Saved filters using the old default setting will reflect the new default setting (Option B): Existing saved filters do not automatically update to the new default sharing setting (Public ). They retain their original sharing configuration (e.g., Private, Group) set at creation, so this statement is false.

Extract from Documentation: Existing filters and dashboards are unaffected by changes to theDefault sharingsetting. Only new creations use the updated default.

(Source: Atlassian Support Documentation, "Manage user default settings in Jira Cloud") All users will become watchers of issues they have created in the past (Option D): SettingAutowatch own issuestoYesenables autowatching for issues createdafterthe setting is changed. It does not retroactively add users as watchers to issues they created in the past.

For past issues, users must be manually added as watchers or an automation rule must be created, so this statement is not definitely true.

Extract from Documentation: TheAutowatch own issuessetting applies to issues created after the setting is enabled. It does not affect previously created issues.

(Source: Atlassian Support Documentation, "Manage user default settings in Jira Cloud") Additional Notes: ConfiguringUser Default SettingsrequiresJira administratorprivileges and is done inSettings > System > User default settings.

Users can override the default sharing setting when creating filters or dashboards (e.g., choosing Private instead of Public).

Pass with Valid Exam Questions Pool

12 of 26

Certs Exam

ATLASSIAN - ACP-120

To retroactively apply autowatching to past issues, a bulk operation or automation rule would be needed, but this is not automatic. : Atlassian Support Documentation:Manage user default settings in Jira Cloud Question #:6 - [Advanced User Features] You need to find unresolved issues assigned to suspended users. Identify the correct JQL query.

A. resolution is EMPTY AND assignee in inactiveUsers() B. statusCategory != Done AND assignee not in organizationMembers() C. resolution = Unresolved AND assignee changed to inactive D. statusCategory = Done AND assignee not in activeUsers() E. resolution = EMPTY AND assignee not in membersOf("jira-software-users") Answer: A

Explanation To find unresolved issues assigned to suspended users in Jira Software Cloud, the JQL query must check for issues with no resolution (unresolved) and an assignee who is inactive (suspended). The correct query is resolution is EMPTY AND assignee in inactiveUsers()(Option A), as it uses the appropriate field ( resolution) and function (inactiveUsers()) to identify these issues.

Explanation of the Correct Answer (Option A): Unresolved issues: In Jira, an issue is considered unresolved if itsresolutionfield is empty (i.e., not set to Resolved, Done, or similar). The JQL clauseresolution is EMPTYidentifies unresolved issues.

Suspended users: Suspended users are those whose accounts are inactive (e.g., deactivated or removed from the organization). TheinactiveUsers()function returns all inactive users in the Jira instance. The clauseassignee in inactiveUsers()filters for issues assigned to these users.

Combined query:resolution is EMPTY AND assignee in inactiveUsers()returns all unresolved issues assigned to inactive users.

Exact Extract from Documentation: Search for issues using JQL resolution is EMPTY: Finds issues with no resolution set (unresolved issues).

Pass with Valid Exam Questions Pool

13 of 26

Certs Exam

ATLASSIAN - ACP-120 assignee in inactiveUsers(): Finds issues assigned to users who are inactive (e.g., deactivated or suspended).Example: resolution is EMPTY AND assignee in inactiveUsers() returns unresolved issues assigned to inactive users.Note: TheinactiveUsers()function is specific to Jira Cloud and includes users who are no longer active in the instance.(Source: Atlassian Support Documentation, "Advanced searching - functions reference") Why This Fits: The query correctly usesresolution is EMPTYfor unresolved issues and inactiveUsers()for suspended users, making Option A the correct answer.

Why Other Options Are Incorrect: statusCategory != Done AND assignee not in organizationMembers() (Option B): statusCategory != Donechecks the status category (e.g., To Do, In Progress) but is less precise thanresolution is EMPTY, as some statuses in non-Done categories may still be resolved.assignee not in organizationMembers()is incorrect, asorganizationMembers() is not a valid JQL function in Jira Cloud, and it would not specifically target inactive users.

Extract from Documentation: statusCategory != Doneis broader thanresolution is EMPTYand may include resolved issues. No organizationMembers()function exists in JQL. (Source: Atlassian Support Documentation, "Advanced searching - fields reference") resolution = Unresolved AND assignee changed to inactive (Option C): resolution = Unresolvedis incorrect, asUnresolvedis not a valid resolution value; use resolution is EMPTYinstead.assignee changed to inactiveis invalid, aschanged to inactiveis not a supported JQL operator for theassigneefield.

Extract from Documentation: Useresolution is EMPTYfor unresolved issues. Thechangedoperator does not supportinactiveas a value for assignee.

(Source: Atlassian Support Documentation, "Advanced searching - operators reference") statusCategory = Done AND assignee not in activeUsers() (Option D): statusCategory = Doneis the opposite of what is needed, as it selects resolved or completed issues, not unresolved ones.assignee not in activeUsers()might include inactive users but is less precise thaninactiveUsers(), and thestatusCategoryclause makes the query incorrect.

Extract from Documentation:

Pass with Valid Exam Questions Pool

14 of 26

Certs Exam

ATLASSIAN - ACP-120

statusCategory = Doneselects issues in completed statuses, not unresolved issues. UseinactiveUsers()for precise inactive user filtering.

(Source: Atlassian Support Documentation, "Advanced searching - fields reference") resolution = EMPTY AND assignee not in membersOf("jira-software-users") (Option E): resolution = EMPTYis correct, butassignee not in membersOf("jira-software-users")is incorrect, asjira-software-usersis a default group for active users with Jira Software access, not a reliable indicator of suspended users. This would exclude active users in the group, not specifically target inactive ones.

Extract from Documentation: ThemembersOf()function checks group membership, not user activity status. UseinactiveUsers()to find suspended or deactivated users.

(Source: Atlassian Support Documentation, "Advanced searching - functions reference") Additional Notes: The query can be tested inIssues > Search for issuesand saved as a filter if needed. inactiveUsers()is specific to Jira Cloud and includes users who are deactivated or removed from the organization.

Ensure the user running the query hasBrowse Projectspermission for the relevantprojects. : Atlassian Support Documentation:Advanced searching - functions reference Atlassian Support Documentation:Advanced searching - fields reference Atlassian Support Documentation:Advanced searching - operators reference Atlassian Support Documentation:Search for issues using JQL Question #:7 - [Issue Types, Fields, Screens] You are configuring an issue layout in a company-managed project. Which statement is true?

A. You can reuse fields from a team-managed project.

B. You can copy a layout to another project using the same screen.

C. You can move any field to the Hidden fields section.

D. You can move any field to the Context fields section.

Pass with Valid Exam Questions Pool

15 of 26

Certs Exam

ATLASSIAN - ACP-120

Answer: B

Explanation In a company-managed project, theissue layoutdetermines how fields are displayed in the issue view (e.g., which fields are visible, hidden, or in the context panel). The true statement is thatyou can copy a layout to another project using the same screen(Option B), as Jira allows copying issue layouts to streamline configuration across projects.

Explanation of the Correct Answer (Option B): Theissue layoutin a company-managed project is configured inProject settings > Issue layout and is tied to a screen (via the screen scheme). Jira allows copying an issue layout to another project that uses the same screen, ensuring consistent field arrangements across projects.

Exact Extract from Documentation: Configure issue layouts in company-managed projects Issue layouts define which fields are displayed, hidden, or placed in the context panel in the issue view.

To copy a layout: Go toProject settings > Issue layout.

SelectCopy layoutand choose another project that uses the same screen.Note: The target project must use the same screen (via its screen scheme) for the layout to be compatible.

(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud") Why This Fits: Copying an issue layout to another project using the same screen is a supported feature, making Option B the correct answer.

Why Other Options Are Incorrect: You can reuse fields from a team-managed project (Option A): Fields in team-managed projects are project-specific and cannot be reused in companymanaged projects. Company-managed projects use global custom fields or system fields, managed inSettings > Issues > Custom fields. Fields from team-managed projects are isolated and not accessible.

Extract from Documentation: Custom fields in team-managed projects are project-specific and cannot be reused in company-managed projects. Company-managed projects use global custom fields.

(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud") You can move any field to the Hidden fields section (Option C):

Pass with Valid Exam Questions Pool

16 of 26

Certs Exam

ATLASSIAN - ACP-120

Not all fields can be moved to theHidden fieldssection. System fields likeSummary,Issue Type, andStatusare required and cannot be hidden. Only non-mandatory fields (e.g., custom fields, non-required system fields) can be hidden.

Extract from Documentation: In the issue layout, you can hide non-mandatory fields by moving them to theHidden fieldssection. Required fields like Summary, Issue Type, and Status cannot be hidden.

(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud") You can move any field to the Context fields section (Option D): TheContext fieldssection (right panel in the issue view) has restrictions on which fields can be placed there. Fields likeSummary,Description, and certain system fields cannot be moved to the context panel, as they are designed for the main issue view. Only eligible fields (e.g., custom fields, Labels, Components) can be moved to theContext fieldssection.

Extract from Documentation: TheContext fieldssection is for fields like Labels, Components, or custom fields. Core fields like Summary and Description cannot be moved to the context panel.

(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud") Additional Notes: Configuring issue layouts requiresproject adminprivileges for the project (Project settings > Issue layout).

Copying layouts is useful for maintaining consistency across projects with similar configurations. : Atlassian Support Documentation:Configure issue layouts in Jira Cloud Atlassian Support Documentation:Manage custom fields in Jira Cloud Question #:8 - [Advanced User Features] Christian has a saved filter showing bugs that have not been updated in the past two weeks. He plans to run a bulk operation to change the priority to Highest on all the issues in the filter. Identify one definite outcome of this action.

A. The saved filter will display no issues.

B. Filter subscriptions based on the filter will stop sending emails.

C. Christian will be added as a watcher on all the edited issues.

Pass with Valid Exam Questions Pool

17 of 26

Certs Exam

ATLASSIAN - ACP-120

D. Email notifications will be sent during the bulk operation.

Answer: A

Explanation Christian’s saved filter shows bugs that have not been updated in the past two weeks, likely using a JQL query like issuetype = Bug AND updated <= -2w. Running a bulk operation to change the priority toHigheston all issues in the filter will update the issues, affecting theirupdatedtimestamp. The definite outcome is thatthe saved filter will display no issues(Option A), as the issues will no longer meet the filter’s criteria after being updated.

Explanation of the Correct Answer (Option A): The saved filter likely uses a JQL query such as issuetype = Bug AND updated <= -2w, which returns bugs not updated in the past two weeks (i.e., updated timestamp is older than two weeks).

When Christian performs a bulk operation to change the priority toHighest, each issue’supdated timestamp is set to the current time, as any edit (including priority changes) updates this field.

After the operation, all issues in the filter will have a recentupdatedtimestamp (e.g., within the last few minutes), causing them to no longer satisfy the updated <= -2w condition. As a result, the filter will return no issues.

Exact Extract from Documentation: Bulk change issues Bulk operations (e.g., changing priority) update issue fields and metadata, including theupdatedtimestamp.

Impact on filters: If a filter uses a condition like updated <= -2w, updating issues will change theirupdated timestamp, potentially excluding them from the filter.To perform a bulk change: Run a filter inIssues > Search for issues.

SelectBulk changeand choose an action (e.g., Edit Issues).

Update fields (e.g., Priority to Highest).Note: Bulk changes trigger theIssue Updatedevent, updating theupdatedfield.(Source: Atlassian Support Documentation, "Bulk change issues in Jira Cloud") Why This Fits: The bulk operation updates theupdatedtimestamp of all issues, causing them to no longer meet the filter’s updated <= -2w condition, resulting in the filter displaying no issues, making Option A the definite outcome.

Why Other Options Are Incorrect: Filter subscriptions based on the filter will stop sending emails (Option B):

Pass with Valid Exam Questions Pool

18 of 26

Certs Exam

ATLASSIAN - ACP-120

Filter subscriptions send emails based on the filter’s results and schedule (e.g., daily, weekly). The bulk operation does not disable the subscription or change its configuration; it only affects the filter’s results. If the filter returns no issues after the operation, the subscription will send an email with no results, but it will not stop sending emails entirely.

Extract from Documentation: Filter subscriptions send emails based on the filter’s results and schedule. Empty results do not stop the subscription; they result in an empty email.

(Source: Atlassian Support Documentation, "Manage filters in Jira Cloud") Christian will be added as a watcher on all the edited issues (Option C): Adding a watcher during a bulk operation is not automatic. Users are not added as watchers unless explicitly included in the bulk operation (e.g., via anAdd Watcheraction, which is not part of changing priority). Christian’s user settings or automation rules could theoretically add him as a watcher, but this is not a definite outcome of the priority change.

Extract from Documentation: Bulk operations do not automatically add the user as a watcher. Use theAdd Watcheraction in abulk operation to add watchers explicitly.

(Source: Atlassian Support Documentation, "Bulk change issues in Jira Cloud") Email notifications will be sent during the bulk operation (Option D): Email notifications for theIssue Updatedevent (triggered by the priority change) depend on the project’snotification schemeand the recipients configured for the event (e.g., watchers, assignee). Notifications are not guaranteed, as they may be disabled or limited to specific users. Thus, this is not a definite outcome.

Extract from Documentation: Bulk operations trigger theIssue Updatedevent, but notifications depend on the notification scheme and may not be sent if not configured.

(Source: Atlassian Support Documentation, "Configure notification schemes") Additional Notes: The bulk operation requires Christian to have theEdit Issuespermission for the issues in the filter.

The filter’s JQL query (e.g., issuetype = Bug AND updated <= -2w) can be verified inIssues > Manage filters.

Pass with Valid Exam Questions Pool

19 of 26

Certs Exam

ATLASSIAN - ACP-120

To avoid impacting the filter, Christian could modify the JQL to exclude recently updated issues or create a temporary filter for the bulk operation. : Atlassian Support Documentation:Bulk change issues in Jira Cloud Atlassian Support Documentation:Manage filters in Jira Cloud Atlassian Support Documentation:Configure notification schemes Question #:9 - [Advanced User Features] You run the JQL query shown: assignee changed from currentUser() TO EMPTY and resolution changed to EMPTY Which statement is definitely true?

A. All returned issues are currently unresolved.

B. All returned issues are currently unassigned.

C. All returned issues were assigned to you at some point.

D. All returned issues are currently not assigned to you.

E. All returned issues were in Done status at some point.

Answer: C

Explanation The JQL query assignee changed from currentUser() TO EMPTY and resolution changed to EMPTY filters for issues based on their change history for theassigneeandresolutionfields. The statement that is definitely true isall returned issues were assigned to you at some point(Option C), as the query explicitly requires that theassigneefield changed from the current user toEMPTY. Explanation of the Correct Answer (Option C): The query consists of two conditions: assignee changed from currentUser() TO EMPTY: This means the issue’sassigneefield was changed from the current user (the person running the query) tounassigned(EMPTY) at some point in its history. For this condition to be true, the issue must have been assigned to the current user before being unassigned.

Pass with Valid Exam Questions Pool

20 of 26

Certs Exam

ATLASSIAN - ACP-120

resolution changed to EMPTY: This means theresolutionfield was changed toEMPTY (unresolved) at some point, typically indicating the issue was reopened (e.g., resolution was cleared).

Theassignee changed from currentUser() TO EMPTYcondition guarantees that all returned issues were assigned to the current user at some point, as the change history explicitly includes a transition from the current user to unassigned.

Exact Extract from Documentation: Advanced searching - operators reference TheCHANGEDoperator searches for issues where a field’s value changed from one value to another. assignee changed from currentUser() TO EMPTY: Finds issues where the assignee was changed from the current user to unassigned. resolution changed to EMPTY: Finds issues where the resolution was cleared (e.g., issue was reopened).Note: TheCHANGEDoperator examines the issue’s history, not its current state.(Source: Atlassian Support Documentation, "Advanced searching - operators reference") Why This Fits: The query’s conditionassignee changed from currentUser() TO EMPTY ensures that all returned issues were assigned to the current user at somepoint, making Option C definitely true.

Why Other Options Are Incorrect: All returned issues are currently unresolved (Option A): Theresolution changed to EMPTYcondition means the resolution was set toEMPTYat some point in the issue’s history, but the issue could have been resolved again later (e.g., resolution set to Done). The query does not check the current resolution state, so this is not definitely true.

Extract from Documentation: TheCHANGEDoperator does not guarantee the current state of a field. Use resolution is EMPTY to check if issues are currently unresolved.

(Source: Atlassian Support Documentation, "Advanced searching - operators reference") All returned issues are currently unassigned (Option B): Theassignee changed from currentUser() TO EMPTYcondition means the issue was unassigned at some point, but it could have been reassigned to another user later. The query does not check the current assignee state, so this is not definitely true.

Pass with Valid Exam Questions Pool

21 of 26

Certs Exam

ATLASSIAN - ACP-120 Extract from Documentation:

To check if issues are currently unassigned, use assignee is EMPTY. TheCHANGEDoperator only checks historical changes.

(Source: Atlassian Support Documentation, "Advanced searching - fields reference") All returned issues are currently not assigned to you (Option D): The query does not guarantee that issues are currently not assigned to the current user.

After being unassigned (TO EMPTY), the issue could have been reassigned to the current user again. The current assignee state is not checked, so this is not definitely true.

Extract from Documentation: TheCHANGEDoperator does not reflect the current field value. Use assignee != currentUser() to check if issues are not assigned to the current user.

(Source: Atlassian Support Documentation, "Advanced searching - operators reference") All returned issues were in Done status at some point (Option E): Theresolution changed to EMPTYcondition indicates the resolution was cleared (e.g., issue reopened), which often follows a resolved state (e.g., Done). However, the query does not explicitly require that the issue was in aDonestatus (or had a resolution set) before the change toEMPTY. For example, an issue could have had a resolution set to another value or cleared without being inDone. Thus, this is not definitely true.

Extract from Documentation: Theresolution changed to EMPTYcondition indicates a resolution was cleared, but it does not guarantee the issue was in a specific status like Done.

(Source: Atlassian Support Documentation, "Advanced searching - fields reference") Additional Notes: The query examines historical changes, not current states, so assumptions about currentresolution orassigneevalues are invalid.

To ensure current states, additional conditions like resolution is EMPTY or assignee is EMPTY would be needed.

The query requires the user to haveBrowse Projectspermission for the relevant projects. : Atlassian Support Documentation:Advanced searching - operators reference Atlassian Support Documentation:Advanced searching - fields reference

Pass with Valid Exam Questions Pool

22 of 26

Certs Exam

ATLASSIAN - ACP-120

Atlassian Support Documentation:Search for issues using JQL Question #:10 - [Issue Types, Fields, Screens] Requirements for field behavior in a company-managed project are shown: Issue Type Attribute (custom field) Epic Hidden Story Optional Bug Required What do you need to configure to meet the requirements?

A. Field configurations B. Screens C. Custom field contexts D. Screen schemes Answer: A

Explanation To meet the requirements for theAttributecustom field’s behavior (hidden for Epics, optional for Stories, required for Bugs) in a company-managed project, you need to configurefield configurations(Option A).

Field configurations define whether a field is required, optional, or hidden for specific issue types.

Explanation of the Correct Answer (Option A): Field configurationscontrol the behavior of fields (e.g., required, optional, hidden) for different issue types in a company-managed project. To meet the requirements: ForEpics, set theAttributefield toHidden.

ForStories, set theAttributefield toOptional(not required).

Pass with Valid Exam Questions Pool

23 of 26

Certs Exam

ATLASSIAN - ACP-120 ForBugs, set theAttributefield toRequired.

This is achieved by creating multiple field configurations (one for each issue type’s behavior) and associating them with afield configuration schemethat maps configurations to issue types.

Exact Extract from Documentation:

Configure field settings Field configurations define whether fields are required, optional, or hidden for specific issue types. A field configuration scheme maps field configurations to issue types in a project.

To configure: Go toSettings > Issues > Field configurations.

Create or edit field configurations (e.g., one for Epics, Stories, Bugs).

For each configuration: Mark a field asRequiredto enforce a value.

Mark a field asHiddento remove it from screens.

Leave a field asOptional(default) if not required.

Create a field configuration scheme (Settings > Issues > Field configuration schemes) and map configurations to issue types.

Assign the scheme to the project inProject settings > Fields.Example: Hide a field for Epics, make it optional for Stories, and required for Bugs.(Source: Atlassian Support Documentation, "Configure field settings") Why This Fits:Field configurationsallow you to set theAttributefield as hidden, optional, or required for different issue types, directly meeting the requirements.

Why Other Options Are Incorrect: Screens (Option B): Screens define which fields appear during issue operations (e.g., Create, Edit, View). While hiding a field on a screen for Epics could make it appear hidden, screens are not issue typespecific unless combined with ascreen scheme. Screens also cannot enforcerequiredor optionalbehavior, which is handled by field configurations.

Extract from Documentation: Screens control which fields are displayed but do not manage required or optional behavior. Use field configurations for field behavior.

Pass with Valid Exam Questions Pool

24 of 26

Certs Exam

ATLASSIAN - ACP-120

(Source: Atlassian Support Documentation, "Configure screens in Jira Cloud") Custom field contexts (Option C): Custom field contexts define the options and default values for a custom field across projects or issue types. They do not control whether a field is hidden, optional, or required, which is managed by field configurations.

Extract from Documentation: Custom field contexts set options and defaults for fields, not their visibility or required status. Use field configurations for behavior.

(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud") Screen schemes (Option D): Screen schemes map screens to issue operations (e.g., Create, Edit) for issue types. They control which fields appear on screens but do not manage whether fields are required or optional, which is handled by field configurations.

Extract from Documentation: Screen schemes assign screens to issue types but do not control field behavior like required or hidden. Use field configurations for this.

(Source: Atlassian Support Documentation, "Configure screen schemes in Jira Cloud") Additional Notes: Steps to configure: Create three field configurations inSettings > Issues > Field configurations: Epic: SetAttributetoHidden.

Story: SetAttributetoOptional.

Bug: SetAttributetoRequired.

Create a field configuration scheme inSettings > Issues > Field configuration schemes and map each configuration to the respective issue type (Epic, Story, Bug).

Assign the scheme to the project inProject settings > Fields.

Configuring field configurations requiresJira administratorprivileges.

Ensure theAttributecustom field is included on the relevant screens (except for Epics, where it is hidden) to avoid conflicts.

Pass with Valid Exam Questions Pool

25 of 26

Certs Exam

ATLASSIAN - ACP-120

: Atlassian Support Documentation:Configure field settings Atlassian Support Documentation:Configure screens in Jira Cloud Atlassian Support Documentation:Manage custom fields in Jira Cloud Atlassian Support Documentation:Configure screen schemes in Jira Cloud

Pass with Valid Exam Questions Pool

26 of 26

About certsout.com certsout.com was founded in 2007. We provide latest & high quality IT / Business Certification Training Exam Questions, Study Guides, Practice Tests.

We help you pass any IT / Business Certification Exams with 100% Pass Guaranteed or Full Refund. Especially Cisco, CompTIA, Citrix, EMC, HP, Oracle, VMware, Juniper, Check Point, LPI, Nortel, EXIN and so on.

View list of all certification exams: All vendors

We prepare state-of-the art practice tests for certification exams. You can reach us at any of the email addresses listed below.

Sales: sales@certsout.com Feedback: feedback@certsout.com Support: support@certsout.com Any problems about IT certification or our products, You can write us back and we will get back to you within 24 hours.