How can you share a scheme across multiple company-managed projects?

By copying the scheme to each project

By associating the same scheme with each project

By using the 'Share' button in the scheme editor

Which of the following is true about migrating schemes between company-managed and team-managed projects?

Schemes can be freely shared between the two project types

Team-managed projects can use company-managed schemes if they are associated

When migrating, schemes are converted to the target project type's format, with some limitations

Migration is not possible between the two project types

A company-managed project uses a custom permission scheme. The admin wants to replace it with the default permission scheme. What is the most critical step to avoid disrupting user access?

Edit the custom scheme to match the default scheme, then delete it.

Create a new project and migrate all issues to it.

Associate the project with the default permission scheme, then delete the custom scheme.

Delete the custom scheme first; Jira will automatically apply the default scheme.

An organization has a 'Standard' issue type scheme used by 10 company-managed projects. The admin needs to add a new issue type 'Epic' to only 3 of these projects. What is the recommended approach?

Create a new issue type scheme from scratch and associate it with the 3 projects.

Create a copy of the 'Standard' scheme, add 'Epic' to the copy, and associate the copy with the 3 projects.

Add 'Epic' to the project's field configuration instead of the issue type scheme.

Edit the 'Standard' issue type scheme; the change will apply to all 10 projects.

An admin edits a workflow scheme to change the workflow for the 'Story' issue type. The new workflow has a different set of statuses. What is the immediate impact on existing stories in the project?

Existing stories are moved to a 'Migrated' status automatically.

Existing stories are automatically transitioned to the first status of the new workflow.

Existing stories are deleted to prevent data inconsistency.

Existing stories remain in their current statuses, but may not be able to transition if their status is not in the new workflow.

Jira Administration for Cloud (ACP-120)

Domain 4Objective 2

Manage Schemes Across Company-Managed and Team-Managed Projects ACP-120 Practice Questions (Page 2)

Part of the Workflows and Schemes domain, which makes up ~26% of our current practice bank.

26questions here

6free pages

8concepts

Questions 6–10

6foundation · easy
How can you share a scheme across multiple company-managed projects?
Select an answer first
7foundation · easy
Which of the following is true about migrating schemes between company-managed and team-managed projects?
Select an answer first
8expert · hard
A company-managed project uses a custom permission scheme. The admin wants to replace it with the default permission scheme. What is the most critical step to avoid disrupting user access?
Select an answer first
9application · medium
An organization has a 'Standard' issue type scheme used by 10 company-managed projects. The admin needs to add a new issue type 'Epic' to only 3 of these projects. What is the recommended approach?
Select an answer first
10application · medium
An admin edits a workflow scheme to change the workflow for the 'Story' issue type. The new workflow has a different set of statuses. What is the immediate impact on existing stories in the project?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to ACP-120

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Atlassian. “ACP-120” is a trademark of its owner, used for identification only.