• Home
  • Articles
  • [Q18-Q40] Updated ACP-120 Dumps PDF - ACP-120 Real Valid Brain Dumps With 77 Questions!

[Q18-Q40] Updated ACP-120 Dumps PDF - ACP-120 Real Valid Brain Dumps With 77 Questions!

Share

Updated ACP-120 Dumps PDF - ACP-120 Real Valid Brain Dumps With 77 Questions!

100% Free ACP-120 Exam Dumps Use Real Jira Administrator Dumps

NEW QUESTION # 18
Your organization uses Jira Software and Confluence. Dave is a new employee who needs the following privileges
* Approve access requests
* Manage group memberships
* Update billing details
You need to give him enough but not too many privileges How should you configure Dave's user account? (Choose one)

  • A. As a member of the jira-administrators and confluence-administrators group
  • B. As an organization administrator
  • C. As a site administrator
  • D. As a trusted user
  • E. As a member of the administrators group

Answer: A


NEW QUESTION # 19
The Legal team has the following requirements
* Notify a list of individuals when issues are set to Pending status
* Allow project administrators to manage that list on an ongoing basis
Which combination of two configuration elements will meet these requirements (Choose two)

  • A. Workflow validator
  • B. Custom Event
  • C. Group
  • D. Project Role
  • E. Workflow condition

Answer: B,D


NEW QUESTION # 20
You need to find unresolved issues assigned to suspended users. Identify the correct JQL query.

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

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


NEW QUESTION # 21
Your team currently only uses a single issue type but wants to add a second one. Which configuration requires a separate project for the second issue type?

  • A. Different issue layouts per issue type
  • B. Different workflows per issue type
  • C. Different components per issue type
  • D. Different card colors per issue type
  • E. Different custom fields per issue type

Answer: B

Explanation:
In a company-managed project, adding a second issue type can often be accommodated within the same project by configuring issue type-specific settings (e.g., fields, layouts). However, if the second issue type requires adifferent workflow, a separate project may be necessary unless the project'sworkflow schemeis modified to support multiple workflows. Since the question implies a configuration thatrequiresa separate project,different workflows per issue type(Option E) is the most likely to necessitate this, as it involves complex workflow management that is often easier to handle in separate projects.
* Explanation of the Correct Answer (Option E):
* In a company-managed project, aworkflow schememaps workflows to issue types. It is possible to assign different workflows to different issue types within the same project by configuring the workflow scheme. However, managing multiple workflows within a single project can become complex, especially if the workflows have significantly different statuses, transitions, or rules.
Creating a separate project for the second issue type simplifies workflow management by isolating the workflows, as each project can have its own workflow scheme. The question's phrasing suggests a scenario where a separate project is required, likely due to the complexity or isolation needed for distinct workflows.
* Exact Extract from Documentation:
Configure workflow schemes
A workflow scheme maps workflows to issue types in a company-managed project.
To use different workflows:
* Go toSettings > Issues > Workflow schemes.
* Create or edit a scheme and assign different workflows to issue types (e.g., one for Issue Type A, another for Issue Type B).
* Apply the scheme to the project inProject settings > Workflows.Note: For complex or conflicting workflows, separate projects may be preferred to simplify management and avoid configuration conflicts.(Source: Atlassian Support Documentation, "Configure workflow schemes")
* Why This Fits: While different workflows can technically be managed within one project via a workflow scheme, the complexity or need for isolation (e.g., different teams, permissions, or configurations) often necessitates a separate project for the second issue type's workflow, making Option E the correct answer.
* Why Other Options Are Incorrect:
* Different custom fields per issue type (Option A):
* Different custom fields can be configured for eachCustom field contextsorscreen schemes allow different fields to be shown or hidden for specific issue types within the same project. A separate project is not required.
* Extract from Documentation:
Custom field contexts or screen schemes can restrict fields to specific issue types within a single project.
Separate projects are not needed.
(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")
* Different card colors per issue type (Option B):
* Card colors on boards (e.g., Kanban, Scrum) are configured per issue type usingboard settings(e.g., based on issue type or priority). This is managed within a single project and does not require a separate project.
* Extract from Documentation:
Card colors are configured inBoard settings > Card colorsand can vary by issue type within the same project.
(Source: Atlassian Support Documentation, "Configure boards in Jira Cloud")
* Different components per issue type (Option C):
* Componentsare project-specific, not issue type-specific. While components can be assigned to issues, they are not tied to issue types, and different components can be used within the same project without needing a separate project.
* Extract from Documentation:
Components are project-specific and can be assigned to any issue type within the same project.
(Source: Atlassian Support Documentation, "Manage components in Jira Cloud")
* Different issue layouts per issue type (Option D):
* Issue layoutscan be configured per issue type within a single project inProject settings > Issue layout. Different layouts for each issue type do not require a separate project.
* Extract from Documentation:
Issue layouts can be customized for each issue type inProject settings > Issue layoutwithin the same project.
(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud")
* Additional Notes:
* Steps to configure different workflows:
* Create a new workflow for the second issue type inSettings > Issues > Workflows.
* Update the project's workflow scheme inProject settings > Workflowsto map the new workflow to the second issue type.
* Alternatively, create a new project with its own workflow scheme for simplicity.
* Configuring workflows and schemes requiresJira administratorprivileges.
* A separate project may be preferred for organizational reasons (e.g., different teams, permissions), but technically, a single project can handle different workflows. The question's emphasis onrequiringa separate project points to workflows due to their complexity.
:
Atlassian Support Documentation:Configure workflow schemes
Atlassian Support Documentation:Manage custom fields in Jira Cloud
Atlassian Support Documentation:Configure boards in Jira Cloud
Atlassian Support Documentation:Manage components in Jira Cloud
Atlassian Support Documentation:Configure issue layouts in Jira Cloud


NEW QUESTION # 22
You are a site admin for your company.
Which function can you NOT perform? (Choose one)

  • A. Enable invite links for your products
  • B. Manage users and groups
  • C. Enable Single Sign On for your Atlassian Cloud site(s)
  • D. Deactivate a Cloud site
  • E. Configure products in your Atlassian Cloud site(s)

Answer: C


NEW QUESTION # 23
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 saved filters will reflect the new default setting.
  • B. All users will become watchers of issues they have created in the past.
  • C. Only newly created dashboards will reflect the new default setting.
  • D. Saved filters using the old default setting will reflect the new default setting.

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


NEW QUESTION # 24
You want to create a new link type that looks identical in linked issues. How can you achieve this?

  • A. Create the link type with no inward link description.
  • B. Choose the same name for the inward and outward link descriptions.
  • C. Disable bidirectional linking globally.
  • D. Create the link type with no outward link description.

Answer: B

Explanation:
To create a new link type in Jira Software Cloud that looks identical in linked issues (i.e., the link description is the same regardless of the direction of the link), you shouldchoose the same name for the inward and outward link descriptions(Option C). This ensures that the link type appears with the same description in both the source and target issues.
* Explanation of the Correct Answer (Option C):
* In Jira,issue link typesdefine relationships between issues, with anoutwarddescription(for the source issue) and aninward description(for the target issue). For example, a "Blocks" link type might have "blocks" as the outward description and "is blocked by" as the inward description. To make the link type look identical in both linked issues, you set the same description for both the inward and outward links (e.g., "relates to" for both). This results in the link appearing as "relates to" in both issues, regardless of which issue is the source or target.
* Exact Extract from Documentation:
Manage issue link types
Issue link types define relationships between issues, with separateoutwardandinwarddescriptions.
To create a link type:
* Go toSettings > Issues > Issue linking.
* Add a new link type.
* Enter aName(e.g., Relates), and set theOutward descriptionandInward description(e.g., both as "relates to").Impact: If the inward and outward descriptions are the same, the link appears identical in both linked issues.Note: Requires Jira administrator permissions.
(Source: Atlassian Support Documentation, "Configure issue linking in Jira Cloud")
* Why This Fits: Setting the same name for the inward and outward link descriptions ensures the link type looks identical in linked issues, meeting the requirement and making Option C the correct answer.
* Why Other Options Are Incorrect:
* Create the link type with no inward link description (Option A):
* Jira requires both aninwardandoutwarddescription when creating a link type. Leaving the inward description blank is not allowed, and even if possible, it would not make the link look identical in both issues-it would result in an empty or default description in the target issue.
* Extract from Documentation:
Bothinwardandoutwarddescriptions are required when creating a link type. Blank descriptions are not supported.
(Source: Atlassian Support Documentation, "Configure issue linking in Jira Cloud")
* Disable bidirectional linking globally (Option B):
* There is no concept ofbidirectional linkingin Jira's issue linking system, and no global setting exists to disable it. Issue links are inherently bidirectional (a link from issue A to B implies a reverse link from B to A), and the descriptions control how they appear.
Disabling linking is not an option.
* Extract from Documentation:
Issue links are bidirectional, with inward and outward descriptions defining the relationship. No global setting exists to disable bidirectionality.
(Source: Atlassian Support Documentation, "Configure issue linking in Jira Cloud")
* Create the link type with no outward link description (Option D):
* Similar to Option A, Jira requires anoutwarddescription when creating a link type.
Leaving it blank is not allowed, and it would not achieve identical appearance in both issues, as the source issue would lack a description.
* Extract from Documentation:
Bothoutwardandinwarddescriptions are mandatory for issue link types.
(Source: Atlassian Support Documentation, "Configure issue linking in Jira Cloud")
* Additional Notes:
* Steps to configure:
* Go toSettings > Issues > Issue linking.
* ClickAdd link type.
* Enter aName(e.g., "Relates") and set bothOutward descriptionandInward descriptionto the same value (e.g., "relates to").
* Save the link type.
* Configuring issue link types requiresJira administratorprivileges.
* The new link type will appear identically in both linked issues (e.g., "Issue A relates to Issue B" and "Issue B relates to Issue A").
:
Atlassian Support Documentation:Configure issue linking in Jira Cloud


NEW QUESTION # 25
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. The Issue Updated event does not list the current assignee as a recipient in the project's notification scheme
  • B. Henry adjusted his personal email notification preference to not notify him when he is the assignee of an issue
  • C. Henry is missing the Browse Projects project permission in the Jira project
  • D. Henry is missing the Assignable User project permission in the Jira project
  • E. The Issue Assigned event does not list the current assignee as a recipient in the projects notification scheme

Answer: A,E


NEW QUESTION # 26
You are configuring an issue layout in a company-managed project. Which statement is true?

  • A. You can copy a layout to another project using the same screen.
  • B. You can move any field to the Hidden fields section.
  • C. You can move any field to the Context fields section.
  • D. You can reuse fields from a team-managed project.

Answer: A

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 company- managed 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):
* 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


NEW QUESTION # 27
Which three factors should you consider when deciding between Jira Cloud and Jira Server? (Choose three.)

  • A. the commercial apps you would like to use
  • B. the number of workflows you will require
  • C. the ability to integrate with an external user directory (e.g. company LDAP directory)
  • D. the amount of time required for system administration
  • E. the availability of a REST API
  • F. the ability to integrate Jira with a cloud-based source repository (e.g. Bitbucket)

Answer: A,D,E

Explanation:
Reference: https://confluence.atlassian.com/cloud/compare-atlassian-cloud-vs-server-744721664.html


NEW QUESTION # 28
A new team requests a Jira project. They must be able to:
* Manage and prioritize all work from a central backlog.
* Track progress with a burndown chart.
* Move pre-production defects and production defects through a different QA process.
* Have the project share its schemes with another project in the future.
Which project type fulfills these requirements?

  • A. Company-managed Scrum
  • B. Team-managed Scrum
  • C. Company-managed Kanban
  • D. Team-managed Kanban

Answer: A

Explanation:
The requirements for the new Jira project include a central backlog, burndown chart, different QA processes for defect types, and the ability to share schemes with another project. Thecompany-managed Scrumproject type (Option B) best fulfills all these requirements due to its support for Scrum boards, burndown charts, flexible workflows, and shared configurations.
* Explanation of the Correct Answer (Option B):
* Manage and prioritize all work from a central backlog:
* Company-managed Scrum projects include aScrum boardwith a central backlog where issues (e.g., Stories, Defects) can be managed and prioritized.
* Exact Extract from Documentation:
Company-managed Scrum projects
Company-managed Scrum projects provide a Scrum board with a central backlog for managing andprioritizing work.
To access:
* Go toProject > Backlog.
* Prioritize issues by dragging and dropping.Note: The backlog supports all issue types in the project.(Source: Atlassian Support Documentation, "Manage Scrum projects in Jira Cloud")
* Track progress with a burndown chart:
* Company-managed Scrum projects supportburndown chartsin sprint reports, which track progress based on Story Points or issue count during a sprint.
* Exact Extract from Documentation:
Burndown charts in Scrum projects
Company-managed Scrum projects include burndown charts in sprint reports to track progress.
To view:
* Go toProject > Reports > Burndown Chart.
* Select the sprint to view progress.Note: Burndown charts require sprints and Story Points or issue counts.(Source: Atlassian Support Documentation, "Manage Scrum projects in Jira Cloud")
* Move pre-production defects and production defects through a different QA process:
* Company-managed projects allow different issue types (e.g., Pre-production Defect, Production Defect) to use distinct workflows via aworkflow scheme. This enables separate QA processes (e.g., different statuses or transitions) for each defect type.
* Exact Extract from Documentation:
Configure workflows in company-managed projects
A workflow scheme maps workflows to issue types. Different issue types (e.g., Pre-production Defect, Production Defect) can use different workflows to support unique processes.
To configure:
* Go toSettings > Issues > Workflow schemes.
* Assign workflows to issue types in the project's scheme.Note: Company-managed projects support complex workflow configurations.(Source: Atlassian Support Documentation, "Configure workflow schemes")
* Have the project share its schemes with another project in the future:
* Company-managed projects use shared configurations (e.g., permission schemes, workflow schemes, issue type schemes) that can be reused by other projects. This allows the new project to share its schemes with another project in the future.
* Exact Extract from Documentation:
Shared configurations in company-managed projects
Company-managed projects use schemes (e.g., workflow, permission, issue type) that can be shared across multiple projects.
To share:
* Create a project with a shared configuration inSettings > Projects > Create project.
* Select the same schemes for another project.Note: Team-managed projects have project-specific configurationsand cannot share schemes.(Source: Atlassian Support Documentation, "Create a project in Jira Cloud")
* Why This Fits: Thecompany-managed Scrumproject type supports a central backlog, burndown charts, distinct workflows for defect types, and shared schemes, fully meeting all requirements.
* Why Other Options Are Incorrect:
* Company-managed Kanban (Option A):
* While company-managed Kanban projects support a central backlog (Kanban board) and shared schemes, they do not natively provideburndown charts, which are specific to Scrum projects for tracking sprint progress. Additionally, while different workflows for defect types are possible, Kanban projects are less aligned with sprint-based tracking like burndown charts.
* Extract from Documentation:
Company-managed Kanban projects use a Kanban board but do not include burndown charts, which are specific to Scrum sprints.
(Source: Atlassian Support Documentation, "Manage Kanban projects in Jira Cloud")
* Team-managed Scrum (Option C):
* Team-managed Scrum projects support a backlog, burndown charts, and simplified workflows. However, they do not support shared schemes, as configurations (e.g., workflows, permissions) are project-specific and cannot be reused by other projects.
Additionally, team-managed projects have limited workflow flexibility, making it harder to define distinct QA processes for defect types.
* Extract from Documentation:
Team-managed projects have project-specific configurations and cannot share schemes with other projects.
Workflows are simplified and may not support complex processes for multiple issue types.
(Source: Atlassian Support Documentation, "Manage team-managed projects in Jira Cloud")
* Team-managed Kanban (Option D):
* Team-managed Kanban projects support a Kanban board but lackburndown charts, as they do not use sprints. They also have project-specific configurations, preventing scheme sharing, and limited workflow flexibility for distinct QA processes.
* Extract from Documentation:
Team-managed Kanban projects do not support burndown charts or shared schemes. Workflows are project- specific and simplified.
(Source: Atlassian Support Documentation, "Manage team-managed projects in Jira Cloud")
* Additional Notes:
* Creating a company-managed Scrum project requiresJira administratorprivileges (Settings > Projects > Create project).
* The project can be configured with aScrum board,workflow schemefor distinct defect workflows, and shared schemes for future projects.
* Burndown charts require sprints and Story Points or issue counts to be configured.
:
Atlassian Support Documentation:Manage Scrum projects in Jira Cloud
Atlassian Support Documentation:Manage Kanban projects in Jira Cloud
Atlassian Support Documentation:Manage team-managed projects in Jira Cloud Atlassian Support Documentation:Configure workflow schemes Atlassian Support Documentation:Create a project in Jira Cloud


NEW QUESTION # 29
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 issue transitions to DEVELOPMENT.
  • B. The rule executes but does not perform any actions.
  • C. The rule does not execute.
  • D. The issue transitions to REVIEW.

Answer: D

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


NEW QUESTION # 30
You are using a bulk move operation to migrate issues in a company-managed project from one issue type to another. Identify the two elements that might need to change. (Choose two.)

  • A. Statuses
  • B. Labels
  • C. Resolutions
  • D. Required fields
  • E. Priorities

Answer: A,D

Explanation:
When using a bulk move operation to migrate issues between issue types within a company-managed project, certain elements may need to change due to differences in configurations (e.g., workflows, field configurations) associated with the source and target issue types. The two elements that might need to change arestatuses(Option A) andrequired fields(Option C).
* Explanation of the Correct Answers:
* Statuses (Option A):
* Each issue type in a company-managed project can be associated with a different workflow via the project'sworkflow scheme. If the source and target issue types use different workflows, the statuses available in the target workflow may differ from those in the source workflow. During a bulk move, you must map the current status of each issue to a valid status in the target workflow, as the issue's status might not exist in the new workflow.
* Exact Extract from Documentation:
Move issues in Jira Cloud
When moving issues to a different issue type in a company-managed project, you may need to map statuses if the source and target issue types use different workflows.
To move issues:
* Select issues and chooseBulk change>Move issues.
* Choose the target issue type.
* Map statuses from the source workflow to the target workflow if they differ.Note:
Status mapping is required when workflows have different statuses.(Source:
Atlassian Support Documentation, "Move issues in Jira Cloud")
* Why This Fits: If the target issue type's workflow has different statuses, the issues' statuses must be mapped during the move, makingstatusesa potential element that needs to change.
* Required fields (Option C):
* Different issue types can be associated with differentfield configuration schemes, which define whether fields are required, optional, or hidden. If the target issue type requires fields that were not required for the source issuetype (e.g., a custom field or system field likeDue Date), you must provide values for these required fields during the bulk move operation.
* Exact Extract from Documentation:
Bulk move issues
When moving issues to a different issue type, you may need to update fields if the target issue type's field configuration requires fields that were not required for the source issue type.
During the move:
* The bulk move wizard prompts you to provide values for any newly required fields.
* Ensure all required fields have valid values to complete the move.Note: Field configurations are defined inSettings > Issues > Field configurations.(Source:
Atlassian Support Documentation, "Move issues in Jira Cloud")
* Why This Fits: Required fields may differ between issue types due to field configuration schemes, and the bulk move operation will prompt for values if the target issue type has additional required fields, makingrequired fieldsa potential element that needs to change.
* Why Other Options Are Incorrect:
* Priorities (Option B):
* Thepriorityfield is not typically tied to issue type-specific configurations (e.g., workflows or field configurations). Priorities are managed globally (Settings > Issues > Priorities) and are generally consistent across issue types unless restricted by a custom field configuration or workflow property, which is rare. A bulk move does not require changing priorities unless explicitly prompted by a field configuration, which is covered byrequired fields(Option C).
* Extract from Documentation:
Priorities are global and not issue type-specific. They are only updated during a move if required by the target issue type's field configuration.
(Source: Atlassian Support Documentation, "Manage priorities in Jira Cloud")
* Resolutions (Option D):
* Theresolutionfield is set or cleared based on workflow transitions (e.g., resolving or reopening an issue). Moving issues between issue types within the same project does not inherently require changing the resolution, as it is tied to the issue's status and workflow, not the issue type itself. Any status mapping (covered by Option A) handles resolution indirectly.
* Extract from Documentation:
Resolution is managed by workflow transitions, not issue type changes. Moving issues does not typically require updating resolution unless a specific transition is involved.
(Source: Atlassian Support Documentation, "Configure advanced work item workflows")
* Labels (Option E):
* Thelabelsfield is a standard field that is not issue type-specific and does not typically require changes during a move unless it is a required field in the target issue type's field configuration (covered by Option C). Labels are preserved during a move unless explicitly modified.
* Extract from Documentation:
Fields likeLabelsare preserved during a move unless the target issue type's field configuration requires a new value.
(Source: Atlassian Support Documentation, "Move issues in Jira Cloud")
* Additional Notes:
* The bulk move operation is performed viaIssues > Search for issues > Bulkchange > Move issues, requiring theMove Issuespermission.
* The need to changestatusesandrequired fieldsdepends on the differences in workflows and field configurations between the source and target issue types.
* If the issue types share the same workflow and field configuration, no changes may be needed, but the question asks for elements thatmightneed to change.
:
Atlassian Support Documentation:Move issues in Jira Cloud
Atlassian Support Documentation:Configure advanced work item workflows
Atlassian Support Documentation:Manage priorities in Jira Cloud


NEW QUESTION # 31
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 not use versions.
  • B. Change requests will have different component leads.
  • C. Change requests will require the Due Date field to be populated.
  • D. Change requests will notify different people for all system events.
  • E. Change requests will have a different workflow.

Answer: C,D


NEW QUESTION # 32
A company-managed project uses a single issue type. When must a second issue type be added to the project?

  • A. When adding a new status
  • B. When adding a new security level
  • C. When adding a new resolution
  • D. When adding a new workflow
  • E. When adding a new custom field

Answer: D

Explanation:
In a company-managed project with a single issue type, adding a second issue type is necessary when a configuration requires issue type-specific behavior that cannot be applied to the existing issue type. The requirement that necessitates a second issue type iswhen adding a new workflow(Option B), as different workflows for different issue types require separate issue types to be mapped in the project's workflow scheme.
* Explanation of the Correct Answer (Option B):
* In a company-managed project, aworkflow schememaps workflows to issue types. If the project currently uses a single issue type with one workflow, adding a new workflow (e.g., for a different process) requires a second issue type to associate with the new workflow. Without a second issue type, the new workflow cannot be applied, as a single issue type can only be mapped to one workflow in a given scheme. Adding a second issue type allows the project to use both the existing workflow (for the current issue type) and the new workflow (for the new issue type).
* Exact Extract from Documentation:
Configure workflow schemes
A workflow scheme maps workflows to issue types in a company-managed project.
To use a new workflow:
* Create or select a new workflow inSettings > Issues > Workflows.
* Update the project's workflow scheme inProject settings > Workflowsto assign the new workflow to a specific issue type.Note: To use multiple workflows in a project, you must have multiple issue types, as each issue type can only be associated with one workflow in a scheme.(Source: Atlassian Support Documentation, "Configure workflow schemes")
* Why This Fits: Adding a new workflow requires a second issue type to map the new workflow in the workflow scheme, as a single issue type cannot use multiple workflows, making Option B the correct answer.
* Why Other Options Are Incorrect:
* When adding a new resolution (Option A):
* Resolutionsare global settings (Settings > Issues > Resolutions) that apply to all issues in a project, regardless of issue type. Adding a new resolution does not require a new issue type, as resolutions are managed at the workflow level and can be used by the existing issue type.
* Extract from Documentation:
Resolutions are global and apply to all issue types. Adding a new resolution does not require new issue types.
(Source: Atlassian Support Documentation, "Manage resolutions in Jira Cloud")
* When adding a new status (Option C):
* A newstatuscan be added to the existing workflow for the single issue type without needing a new issue type. Statuses are part of a workflow, and the existing issue type can use the updated workflow with the new status.
* Extract from Documentation:
Statuses are added to workflows, not issue types. A new status can be used by the existing issue type's workflow.
(Source: Atlassian Support Documentation, "Configure advanced work item workflows")
* When adding a new custom field (Option D):
* A newcustom fieldcan be applied to the existing issue type via itscustom field contextor screen configuration. It does not require a new issue type, as fields can be shared across or restricted to specific issue types within the same project.
* Extract from Documentation:
Custom fields can be added to existing issue types via contexts or screens. New issue types are not required.
(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")
* When adding a new security level (Option E):
* A newsecurity levelin the issue security scheme applies to all issues in the project, regardless of issue type. It does not require a new issue type, as security levels are project- wide and not tied to specific issue types.
* Extract from Documentation:
Security levels apply to all issues in a project and are not issue type-specific. Adding a new level does not require new issue types.
(Source: Atlassian Support Documentation, "Configure issue security schemes")
* Additional Notes:
* Steps to add a second issue type for a new workflow:
* Add a new issue type to the project's issue type scheme inProject settings > Issue types.
* Create or select a new workflow inSettings > Issues > Workflows.
* Update the workflow scheme inProject settings > Workflowsto map the new workflow to the new issue type.
* These changes requireJira administratorprivileges.
* The need for a second issue type arises specifically from the workflow scheme's one-to-one mapping of workflows to issue types.
:
Atlassian Support Documentation:Configure workflow schemes
Atlassian Support Documentation:Manage resolutions in Jira Cloud
Atlassian Support Documentation:Configure advanced work item workflows
Atlassian Support Documentation:Manage custom fields in Jira Cloud
Atlassian Support Documentation:Configure issue security schemes


NEW QUESTION # 33
Which time tracking configuration can be controlled on a global basis for all projects in Jira?

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

Answer: A

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


NEW QUESTION # 34
You needed to replace the legacy Jira group all-staff-europe with a newly created all-staff-global group. You created the new group and you migrated all users to the new group. Then you deleted the legacy group.
Which four problems might users report after the change? (Choose four.)

  • A. Workflow transitions are hidden from certain users.
  • B. Users are not able to perform bulk change operations.
  • C. Filter results return an incorrect number of issues.
  • D. Filter subscriptions send out errors instead of issues statistics.
  • E. Comments that were restricted to the legacy group are lost.
  • F. Users are not able to log in to Jira anymore.

Answer: A,B,C,E


NEW QUESTION # 35
Francis needs to manage product subscriptions and billing on his Jira site. What administrator privileges does Francis definitely need?

  • A. Product admin role for Jira Administration
  • B. Organization admin role
  • C. Administer Jira global permission
  • D. Product admin role for Jira Software

Answer: B

Explanation:
Managing product subscriptions and billing for a Jira site is a task handled at the Atlassian organization level, not within the Jira product itself. Theorganization admin roleis required to perform these actions, as it grants access to billing and subscription management.
* Explanation of the Correct Answer (Option A):
* Theorganization admin roleallows users to manage the Atlassian organization, including product subscriptions, billing, and user access across all products (e.g., Jira Software, Confluence). Francis needs this role to manage subscriptions and billing for the Jira site.
* Exact Extract from Documentation:
Organization admin role
Organization administrators manage the Atlassian organization, including:
* Managing product subscriptions and billing.
* Adding or removing users from the organization.
* Configuring organization-wide settings like security policies.To manage billing:
* Go toadmin.atlassian.com.
* SelectBillingto view and update subscription details.Note: Only organization admins can manage subscriptions and billing. Product admins or Jira admins cannot access these settings.(Source: Atlassian Support Documentation, "Manage your Atlassian organization")
* Why This Fits: Theorganization admin roleis the only role that grants access to billing and subscription management, making Option A the correct choice.
* Why Other Options Are Incorrect:
* Product admin role for Jira Software (Option B):
* Theproduct admin role for Jira Softwareallows users to manage user access and settings specific to Jira Software (e.g., adding users to the product). It does not include access to billing or subscription management, which is handled at the organization level.
* Extract from Documentation:
Product admins for Jira Software manage user access and product-specific settings but cannot manage subscriptions or billing.
(Source: Atlassian Support Documentation, "Manage product access")
* Administer Jira global permission (Option C):
* TheAdminister Jiraglobal permission (Jira administrator role) allows usersto manage Jira- specific settings, such as schemes, workflows, and user groups. It does not grant access to organization-level billing or subscription management.
* Extract from Documentation:
TheAdminister Jirapermission allows managing Jira settings, such as schemes and permissions, but does not include billing or subscription management, which is handled by organization admins.
(Source: Atlassian Support Documentation, "Manage global permissions")
* Product admin role for Jira Administration (Option D):
* There is no distinctproduct admin role for Jira Administrationin Jira Cloud. The term may be confused with theJira administratorrole or product admin role for Jira Software, neither of which grants billing access.
* Extract from Documentation:
Jira Cloud uses roles like Jira administrator and product admin for Jira Software. Billing and subscriptions are managed by organization admins, not product-specific roles.
(Source: Atlassian Support Documentation, "Manage your Atlassian organization")
* Additional Notes:
* Francis must accessadmin.atlassian.comto manage subscriptions and billing, which requires the organization admin role.
* Other roles (e.g., Jira administrator) may be involved in configuring Jira settings but are irrelevant for billing tasks.
:
Atlassian Support Documentation:Manage your Atlassian organization
Atlassian Support Documentation:Manage product access
Atlassian Support Documentation:Manage global permissions


NEW QUESTION # 36
Max wants you to change the way the system fields Created or Updated are being displayed when viewing an issue.
How can this be achieved?

  • A. Adjust the jira.date.time.picker.java.format in the advanced settings configuration.
  • B. Adjust the Day Format in the Jira look and Feel configuration.
  • C. Adjust the language and time zone preferences in Max's user profile.
  • D. Adjust the jira.date.picker.java.format in the advanced settings configuration.
  • E. Adjust the Complete Date/Time Format in the Jira Look and Feel configuration.

Answer: C

Explanation:
Reference: https://virginpulse.zendesk.com/hc/en-us/articles/206180140-The-time-on-my-Max-is-wrong-


NEW QUESTION # 37
You were asked to modify the only workflow in a company-managed project. Which two requirements can be satisfied using only out-of-box functionality? (Choose two.)

  • A. Automatically clear Assignee when transitioning to Pending.
  • B. Only members of Testers project role can transition to Passed.
  • C. Only a subset of project users should be able to create epics.
  • D. Automatically set Due Date based on the issue type.
  • E. Automatically reassign an issue when Priority is edited.

Answer: A,B

Explanation:
In a company-managed project, workflows define the statuses and transitions for issues. Modifying a workflow using out-of-box functionality involves addingconditions,validators,post functions, orproperties to transitions. The two requirements that can be satisfied using only out-of-box functionality are automatically clear Assignee when transitioning to Pending(Option C) andonly members of Testers project role can transition to Passed(Option E).
* Explanation of the Correct Answers:
* Automatically clear Assignee when transitioning to Pending (Option C):
* This requirement can be met by adding apost functionto the workflow transition to the Pendingstatus. The out-of-boxClear Field Valuepost function can be used to clear the Assigneefield during the transition.
* Exact Extract from Documentation:
Configure workflow post functions
Post functions are executed after a transition is completed and can update issue fields or perform other actions. Out-of-box post functions include:
* Clear Field Value: Clears the value of a specified field (e.g., Assignee).To add a post function:
* Go toSettings > Issues > Workflows.
* Edit the workflow and select the transition to Pending.
* Add theClear Field Valuepost function and chooseAssignee.Note: Post functions are executed automatically during the transition, requiring no additional configuration.(Source: Atlassian Support Documentation, "Configure advanced work item workflows")
* Why This Fits: TheClear Field Valuepost function is an out-of-box feature that directly clears theAssigneefield during the transition toPending, satisfying the requirement without custom scripting or apps.
* Only members of Testers project role can transition to Passed (Option E):
* This requirement can be met by adding aconditionto the workflow transition to thePassed status. The out-of-boxUser Is In Project Rolecondition can restrict the transition to members of theTestersproject role.
* Exact Extract from Documentation:
Configure workflow conditions
Conditions restrict who can execute a workflow transition. Out-of-box conditions include:
* User Is In Project Role: Allows only users in a specified project role (e.g., Testers) to perform the transition.To add a condition:
* Go toSettings > Issues > Workflows.
* Edit the workflow and select the transition to Passed.
* Add theUser Is In Project Rolecondition and select theTestersrole.Note: Conditions are evaluated before the transition is displayed, ensuring only authorized users see the option.(Source: Atlassian Support Documentation, "Configure advanced work item workflows")
* Why This Fits: TheUser Is In Project Rolecondition is an out-of-box feature that restricts thePassedtransition to theTestersproject role, satisfying the requirement without custom scripting or apps.
* Why Other Options Are Incorrect:
* Automatically set Due Date based on the issue type (Option A):
* Out-of-box post functions allow setting a field to a specific value (e.g.,Update Issue Field) but do not support conditional logic based on issue type (e.g., setting different due dates for different issue types). This requirement would require a scripted post function or an automation rule, which goes beyond out-of-box workflow functionality.
* Extract from Documentation:
Out-of-box post functions can update fields with static values (e.g., set Due Date to a specific date).
Conditional logic based on issue type requires automation rules or third-party apps.
(Source: Atlassian Support Documentation, "Configure advanced work item workflows")
* Only a subset of project users should be able to create epics (Option B):
* Creating epics is controlled by theCreate Issuespermission in the project's permission scheme, not by workflow settings. While permissions can be restricted to a subset of users (e.g., a group or role), this is not a workflow modification. Additionally, restricting epic creation specifically (versus other issue types) requires issue type-specific permissions, which are not supported out-of-box without advanced configuration or apps.
* Extract from Documentation:
TheCreate Issuespermission controls who can create issues, including epics. Issue type-specific restrictions require advanced permission schemes or apps, not workflow changes.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Automatically reassign an issue when Priority is edited (Option D):
* Reassigning an issue when thePriorityfield is edited is not possible with out-of-box workflow post functions, as post functions are tied to transitions, not field edits. This requirement would require a Jira automation rule or a scripted listener, which goes beyond out-of-box workflow functionality.
* Extract from Documentation:
Post functions are executed during workflow transitions, not field edits. To react to field changes like Priority, use Jira automation or third-party apps.
(Source: Atlassian Support Documentation, "Automate your Jira Cloud instance")
* Additional Notes:
* Modifying workflows requiresJira administratorprivileges, as workflows are managed at the system level (Settings > Issues > Workflows).
* Out-of-box functionality refers to native Jira features without scripting, third-party apps, or automation rules. Options C and E leverage standard post functions and conditions, while A, B, and D require additional logic or non-workflow configurations.
:
Atlassian Support Documentation:Configure advanced work item workflows
Atlassian Support Documentation:Manage permissions in Jira Cloud
Atlassian Support Documentation:Automate your Jira Cloud instance


NEW QUESTION # 38
You have been asked to take on the administration of a second Jira installation in your company.
You were given the following information about user accounts:
- The company standard is to use Active Directory (AD) to provide user accounts.
- There are several Active Directory systems in use by different business units.
- The second Jira is not to be merged with your main Jira.
- The main Jira system is connected to Active Directory for user accounts.
- The second Jira is using internal user accounts, not Active Directory.
- People using the second Jira are using the same login ID as they would use in Active Directory.
- Your company would like to use Single Sign-on (SSO) but has not yet implemented it for either Jira system.
Which authentication method should you recommend?

  • A. Change the new Jira to link directly to the required AD servers.
  • B. Change the new Jira to use your main Jira's directory services, as that is already reading your Active Directory services.
  • C. Set up a Crowd server to pull in all the AD services, and plan to migrate internal users.
  • D. Set up a Crowd server to get the user lists from all internal directories and AD, and use AD directly for the password checking.

Answer: D


NEW QUESTION # 39
Jon needs to create groups and manage membership in groups. Which administrator privilege does Jon need?

  • A. Product Admin role for Jira
  • B. Project administrator
  • C. Jira administrator
  • D. Organization admin
  • E. System administrator

Answer: C

Explanation:
Creating groups and managing group membership in Jira Software Cloud are system-level tasks that require theJira administratorprivilege. This privilege allows Jon to access user management settings and perform group-related actions.
* Explanation of the Correct Answer (Option D):
* TheJira administratorprivilege grants users the ability to manage global settings, including creating groups and managing their membership. This includes adding or removing users from groups, which is necessary for Jon's requirements.
* Exact Extract from Documentation:
Jira administrator permissions
Jira administrators can manage global settings, including:
* Creating and deleting groups.
* Adding or removing users from groups.
* Managing global permissions and user access.To create or manage groups:
* Go toSettings > User management > Groups.
* Create a new group or edit existing group membership.Note: Only Jira administrators or organization admins with user management permissions can perform these actions.(Source:
Atlassian Support Documentation, "Manage groups in Jira Cloud")
* Why This Fits: TheJira administratorprivilege directly enables Jon to create groups and manage their membership, making Option D the correct choice.
* Why Other Options Are Incorrect:
* Organization admin (Option A):
* Organization admins manage the Atlassian organization, including user access to products and billing. While they can manage users and groups at the organization level, creating groups specifically in Jira requiresJira administratorprivileges unless the organization admin also has this role.
* Extract from Documentation:
Organization admins manage user access, billing, and security at the Atlassian organization level. Managing Jira-specific groups requires Jira administrator privileges.
(Source: Atlassian Support Documentation, "Manage your Atlassian organization")
* Product Admin role for Jira (Option B):
* TheProduct Adminrole for Jira grants access to manage product-specific settings, such as user access to Jira Software. However, creating and managing groups is a system-level task that requiresJira administratorprivileges.
* Extract from Documentation:
Product admins manage user access to specific products (e.g., Jira Software). Group management requires Jira administrator or organization admin privileges.
(Source: Atlassian Support Documentation, "Manage product access")
* System administrator (Option C):
* The termsystem administratoris not a standard role in Jira Cloud. In some contexts, it may refer toJira administratorsororganization admins, but it is not a distinct privilege for group management.
* Extract from Documentation:
Jira Cloud uses roles like Jira administrator and organization admin. There is no distinct "system administrator" role for group management.
(Source: Atlassian Support Documentation, "Manage users and groups")
* Project administrator (Option E):
* Project administrators manage settings for specific projects (e.g., permissions, components) but cannot create or manage groups, as these are global settings.
* Extract from Documentation:
Project administrators manage project-specific settings but cannot access global settings like user or group management.
(Source: Atlassian Support Documentation, "Manage project permissions")
* Additional Notes:
* Jon's tasks require access toSettings > User management > Groups, which is restricted toJira administrators.
* If Jon is also an organization admin, he might have overlapping permissions, but theJira administratorrole is the most direct for group management in Jira.
:
Atlassian Support Documentation:Manage groups in Jira Cloud
Atlassian Support Documentation:Manage your Atlassian organization
Atlassian Support Documentation:Manage product access
Atlassian Support Documentation:Manage project permissions


NEW QUESTION # 40
......


To be eligible for the exam, candidates are required to have a good understanding of Jira Cloud and must have completed the ATLASSIAN Jira Cloud Essentials course. ACP-120 course provides candidates with a comprehensive overview of Jira Cloud and covers the core concepts and features of the platform.

 

Pass Your ACP-120 Exam Easily With 100% Exam Passing Guarantee: https://actualtests.real4prep.com/ACP-120-exam.html

Related Articles

more
ATLASSIAN ACP-120 Certification Practice Exam