A company has a team-managed project for a short-term internal event. After the event, they want to archive it but keep the data for historical reference. What is the best approach?

Delete the project to free up space

Leave the project active but restrict permissions

Migrate the project to a company-managed project

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

All issue data is preserved, but some settings may need to be reconfigured.

Team-managed projects cannot be migrated to company-managed.

The migration is automatic and requires no user action.

The project key must change after migration.

An organization has a company-managed project for its IT help desk. They want to give a new, autonomous team the ability to manage their own sub-project without involving the Jira admin. They also need to keep the ability to report on both projects together. What is the best approach?

Create a new team-managed project and use a company-managed project as a parent

Create a new company-managed project and grant the team lead project admin rights

Migrate the existing project to a team-managed project

Create a new team-managed project and use a dashboard to combine reports

A marketing team of six people wants to manage a product launch campaign. They need to create their own workflow statuses (e.g., 'Drafting Copy', 'Awaiting Legal Review') without involving a Jira admin, and they want to control who can see the project. The company has no existing workflow requirements for this team. Which project type should the Jira admin recommend?

Company-managed project with a custom workflow created by the Jira admin

Team-managed project with a company-wide permission scheme

An organization needs to enforce a standard workflow across all projects for regulatory compliance. They also need to generate a roll-up report of all issues across these projects for an external audit. Which project type should they use?

Multiple company-managed projects with a shared workflow

A single company-managed project

Managing Jira Projects for Cloud (ACP-620)

Domain 1Objective 1

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

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

14questions here

3free pages

4concepts

Questions 1–5

1application · medium
A company has a team-managed project for a short-term internal event. After the event, they want to archive it but keep the data for historical reference. What is the best approach?
Select an answer first
2foundation · easy
What is a key consideration when migrating a project from team-managed to company-managed?
Select an answer first
3expert · hard
An organization has a company-managed project for its IT help desk. They want to give a new, autonomous team the ability to manage their own sub-project without involving the Jira admin. They also need to keep the ability to report on both projects together. What is the best approach?
Select an answer first
4application · medium
A marketing team of six people wants to manage a product launch campaign. They need to create their own workflow statuses (e.g., 'Drafting Copy', 'Awaiting Legal Review') without involving a Jira admin, and they want to control who can see the project. The company has no existing workflow requirements for this team. Which project type should the Jira admin recommend?
Select an answer first
5application · medium
An organization needs to enforce a standard workflow across all projects for regulatory compliance. They also need to generate a roll-up report of all issues across these projects for an external audit. Which project type should they use?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back 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.