An organization has three company-managed projects (A, B, C) that all use the same permission scheme. The admin needs to modify the permission scheme for Project A only, without affecting Projects B and C. What is the recommended approach?

Edit the shared permission scheme directly; the change will apply to all three projects.

Create a copy of the shared scheme, associate the copy with Project A, and then edit the copy.

Delete the shared scheme and create a new one for Project A.

Create a new project and migrate all issues from Project A to it.

What is a key limitation when migrating a company-managed project to a team-managed project?

Custom fields are not supported in team-managed projects

Permission schemes are not converted

Workflow schemes are converted to simplified workflows, and some advanced features may be lost

When you change the workflow scheme associated with a project, what happens to existing issues?

Existing issues remain on the old workflow until they are edited

Existing issues are migrated to the new workflow, but you must map their current statuses to the new workflow's statuses

Existing issues are automatically migrated to the new workflow's statuses

When you edit a field configuration scheme and change a field to 'required', what is the effect on existing issues?

The change only affects new projects that use the scheme

The field becomes required for new issues and when editing existing issues

Existing issues are immediately updated to have the field populated

A team-managed project's workflow has been customized by the project team. The organization's Jira admin wants to enforce a company-wide approval step for all 'High' priority issues. What is the most accurate statement about applying this requirement to the team-managed project?

The admin can request the project team add the approval step, but the admin cannot directly apply it from the admin console.

The admin must convert the project to a company-managed project to apply a global workflow scheme.

The admin can edit the team-managed project's workflow directly from the admin console.

The admin can create a new workflow scheme and associate it with the team-managed project.

Jira Administration for Cloud (ACP-120)

Domain 4Objective 2

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

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

26questions here

6free pages

8concepts

Questions 16–20

16application · medium
An organization has three company-managed projects (A, B, C) that all use the same permission scheme. The admin needs to modify the permission scheme for Project A only, without affecting Projects B and C. What is the recommended approach?
Select an answer first
17foundation · easy
What is a key limitation when migrating a company-managed project to a team-managed project?
Select an answer first
18foundation · easy
When you change the workflow scheme associated with a project, what happens to existing issues?
Select an answer first
19foundation · easy
When you edit a field configuration scheme and change a field to 'required', what is the effect on existing issues?
Select an answer first
20application · medium
A team-managed project's workflow has been customized by the project team. The organization's Jira admin wants to enforce a company-wide approval step for all 'High' priority issues. What is the most accurate statement about applying this requirement to the team-managed 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.