Pass the ATLASSIAN Jira Administrator ACP-120 Questions and answers with ValidTests

To create projects in Jira Software Cloud without having full Jira administrator privileges, George needs a specificglobal permission, namely theCreate Projectspermission. This permission allows users to create new projects without granting them broader administrative access.

Explanation of the Correct Answer (Option D):

TheCreate Projectsglobal permission enables a user to create new projects in Jira. This permission is distinct from Jira administrator privileges, which include managing global settings like schemes, users, and workflows. By granting George this permission, he can create projects while maintaining a limited scope of authority.

Exact Extract from Documentation:

Global permissions

Global permissions control access to system-wide actions in Jira. TheCreate Projectspermissionallows users to create new projects without requiring full Jira administrator privileges.

To grant this permission:

Go toSettings > System > Global permissions.

Add a user, group, or role to theCreate Projectspermission.Note: Users with this permission can create projects but cannot modify global configurations like schemes or user management unless they have additional permissions.(Source: Atlassian Support Documentation, "Manage global permissions")

Why This Fits: TheCreate Projectsglobal permission directly addresses the requirement for George to create projects without needing Jira administrator privileges, making Option D the correct choice.

Why Other Options Are Incorrect:

Project role (Option A):

Project roles (e.g., Administrator, Developer) are used within a project’s permission scheme to grant project-specific permissions, such asAdminister ProjectsorBrowse Projects. They do not control the ability to create new projects, which is a system-level action.

Extract from Documentation:

Project roles are used in permission schemes to grant permissions within a specific project. They do not apply to global actions like creating projects.

(Source: Atlassian Support Documentation, "Manage project roles")

Product access (Option B):

Product access determines whether a user can use Jira Software or other Atlassian products. While George needs product access to use Jira, this does not grant the specific ability to create projects.

Extract from Documentation:

Product access allows users to log in and use Jira products. Specific actions, like creating projects, require global or project permissions.

(Source: Atlassian Support Documentation, "Manage product access")

Project permission (Option C):

Project permissions (e.g.,Administer Projects,Browse Projects) are defined in a project’s permission scheme and apply to actions within a specific project. Creating a project is a global action, not tied to any existing project’s permission scheme.

Extract from Documentation:

Project permissions control actions within a project, such as editing issues or managing components. Global permissions control system-wide actions like creating projects.

(Source: Atlassian Support Documentation, "Manage project permissions")

Product role (Option E):

Product roles (e.g., Jira Software User, Jira Service Management Agent) define access to specific Atlassian products but do not grant permissions for actions like creating projects. This is not relevant to the requirement.

Extract from Documentation:

Product roles determine access to Atlassian products and are not related to specific permissions like creating projects.

(Source: Atlassian Support Documentation, "Manage product roles")

Additional Notes:

TheCreate Projectspermission can be granted to George via a group or directly to his user account inSettings > System > Global permissions.

As a project lead, George likely already has project-level permissions (e.g.,Administer Projectsfor his projects), but these do not extend to creating new projects.

TheImport Jira Cloudfeature allows migration of data between Jira Cloud sites, including projects, issues, configurations, and attachments. However,deleted issues(Option C) cannot be imported, as they are not included in standard Jira Cloud backups or export data.

Explanation of the Correct Answer (Option C):

Deleted issuesare permanently removed from Jira Cloud and are not included in backups or export files created for migration. TheImport Jira Cloudfeature only imports data that exists in the source site’s backup, which excludes issues that have been deleted.

Exact Extract from Documentation:

Import Jira Cloud data

TheImport Jira Cloudfeature allows migration of data between Jira Cloud sites, including:

Projects (company-managed and team-managed).

Issues, comments, and attachments.

Configurations (e.g., custom fields, workflows, automation rules).Limitations:

Deleted issues are not included in backups or exports and cannot be imported.To import:

Create a backup from the source site inSettings > System > Backup manager.

UseSettings > System > Import Jira Cloudon the target site.Note: Requires Jira administrator permissions and may involve Atlassian support for full migrations.(Source: Atlassian Support Documentation, "Import data to Jira Cloud")

Why This Fits:Deleted issuesare not part of the data exported from the source site, making them impossible to import, so Option C is the correct answer.

Why Other Options Are Incorrect:

Automation rules (Option A):

Automation rulesare included in Jira Cloud backups and can be imported to the target site using theImport Jira Cloudfeature, provided they are compatible with the target site’s configuration.

Extract from Documentation:

Automation rules are included in Jira Cloud backups and can be imported, though some rules may require reconfiguration if dependencies (e.g., custom fields) differ.

(Source: Atlassian Support Documentation, "Import data to Jira Cloud")

Custom fields (Option B):

Custom fieldsare part of the configuration data in a Jira Cloud backup and are imported to the target site. Their contexts and options are preserved during migration.

Extract from Documentation:

Custom fields, including their configurations and contexts, are included in backups and imported to the target site.

(Source: Atlassian Support Documentation, "Import data to Jira Cloud")

Team-managed projects (Option D):

Team-managed projectsare fully supported in Jira Cloud backups and can be imported to the target site, including their issues, configurations, and settings.

Extract from Documentation:

Both company-managed and team-managed projects are included in Jira Cloud backups and can be imported to another site.

(Source: Atlassian Support Documentation, "Import data to Jira Cloud")

Attachments (Option E):

Attachments(media files) are included in Jira Cloud backups and can be imported to the target site, provided the backup includes media data.

Extract from Documentation:

Attachments are included in Jira Cloud backups and imported to the target site if media import is enabled.

(Source: Atlassian Support Documentation, "Import data to Jira Cloud")

Additional Notes:

TheImport Jira Cloudfeature is accessed viaSettings > System > Import Jira Cloudand typically requiresJira administratorprivileges, with possible Atlassian support for full migrations.

Deleted issues are permanently removed and cannot be recovered unless a backup from before deletion is available, but even then, they are not part of standard exports.

Other data (e.g., automation rules, custom fields) may require post-import reconfiguration if there are incompatibilities between sites.