A team is migrating from a company-managed project to a team-managed project. They currently use a complex workflow with multiple statuses and conditions. What is a key limitation they will face after migration?

They will not be able to add new members

They will lose all their issues

They will not be able to use the same project key

They will lose the ability to have a workflow with conditions

A Jira admin is migrating a company-managed project to a team-managed project. The company-managed project uses a workflow with a 'QA Approved' status that has a condition restricting the transition to only the 'QA Lead' role. After migration, what is the most likely outcome for this workflow?

The workflow and its conditions are preserved exactly as they were

The migration fails because the workflow is too complex

The workflow is converted to a simple workflow with only the default statuses

The workflow is preserved, but the condition is removed

A startup's engineering team wants to adopt Jira. They are a small, agile team that values flexibility and wants to change their workflow frequently as they learn. They do not need complex reporting or integration with other company projects. Which project type is most suitable?

Company-managed project with a Jira admin on the team

Team-managed project with a complex permission scheme

A Jira admin is evaluating whether to use a team-managed or company-managed project for a new initiative. The key requirement is that the project must support a custom field that is used across multiple projects in the organization. Which project type should be chosen?

Company-managed project with a local field

Team-managed project with a custom field created in the project

Managing Jira Projects for Cloud (ACP-620)

Domain 1Objective 1

Work with Team-Managed and Company-Managed Projects ACP-620 Practice Questions (Page 3)

Part of the Project Types domain, which makes up ~23% of our current practice bank.

14questions here

3free pages

4concepts

Questions 11–14

11application · medium
A team is migrating from a company-managed project to a team-managed project. They currently use a complex workflow with multiple statuses and conditions. What is a key limitation they will face after migration?
Select an answer first
12expert · hard
A Jira admin is migrating a company-managed project to a team-managed project. The company-managed project uses a workflow with a 'QA Approved' status that has a condition restricting the transition to only the 'QA Lead' role. After migration, what is the most likely outcome for this workflow?
Select an answer first
13application · medium
A startup's engineering team wants to adopt Jira. They are a small, agile team that values flexibility and wants to change their workflow frequently as they learn. They do not need complex reporting or integration with other company projects. Which project type is most suitable?
Select an answer first
14application · medium
A Jira admin is evaluating whether to use a team-managed or company-managed project for a new initiative. The key requirement is that the project must support a custom field that is used across multiple projects in the organization. Which project type should be chosen?
Select an answer first

Finished these 4 questions?

Review the revealed explanations, or continue through the curriculum.

No more pagesBack to ACP-620

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-620” is a trademark of its owner, used for identification only.