Free ACP-520 Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

With a Standard subscription plan, you can add multiple products to your existing site, such as Jira

Service Management1. You can also add Jira Software to a new site, if you need to create a separate

instance for a different team or project2. However, you cannot create or use sandboxes, which are

only available for Premium and Enterprise plans3. You also cannot change release tracks, which are

only available for Enterprise plans4.

Reference: Manage your bill for Standard and Premium plans, Add a new product to your

organization, How many instances of a product does my organization need?, Manage product

sandboxes, Release tracks for cloud products

Out of the five tasks, only verifying an email domain and adding a custom email address require org

admin permissions. Configuring an email handler, customizing a notification scheme, and managing

personal notification settings can be done by project admins or site admins.

Reference: Verify a domain to manage accounts, Add custom email addresses for product

notifications, Create issues and comments from email, Configure notification schemes, Manage your

Jira personal settings

The only statement that is definitely true is that Drew’s email address is verified. This is because

product access requests must be made by a user with a verified email address and Atlassian

account1 The other statements are not necessarily true, as they depend on other factors, such as the

roles and permissions of Beth and Drew, the existing users on the site, and the self-signup settings2

Reference = Approve or deny product access requests, Manage product access

The org admin can remove a group from a product, but they cannot update or delete a group, or

make a group a default group.

Reference:

How to prepare for ACP-520 Atlassian Cloud Organization Admin

Learn about Atlassian organizations

When you go to the Jira Software product pricing page, you can sign up for a new Atlassian site by

clicking the Try it free button. You will be asked to enter your email address and choose a site name

and URL. However, you must use an email address from a non-public domain, such as your company

or organization domain. You cannot use an email address from a public domain, such as Gmail or

Yahoo, because they are not allowed for security reasons12

Reference = Sign up for an Atlassian Cloud site, Atlassian Cloud site and organization domains

When Ravi invites a teammate to join a product, an access request is generated for that product only.

If the teammate needs access to another product on the same site, they can request it themselves or

Ravi can invite them again. Therefore, if Ravi wants his teammate to have access to both Confluence

and Jira Software, he needs to send two invitations, resulting in two access requests.

Reference

Invite users to your site Approve or deny product access requests

If you want to ensure that the script can no longer access the information about the domains in your

Cloud organization, you need to revoke the API key that was used to authenticate the script. An API

key is a token that allows you to manage your organization via the admin APIs1. You can create, view,

and revoke API keys from the organization settings2. Revoking an API key will invalidate it and

prevent any further requests using that key2.

The other options are not relevant or effective for stopping the script from accessing the information.

Removing DNS records or removing a verified domain will not affect the API key that was used by the

script. It will only affect the verification status of your domain and the management of your users and

accounts3. Regenerating a security key will not affect the API key that was used by the script. It will

only affect the encryption of your data at rest4. Deleting an IP allowlist will not affect the API key that

was used by the script. It will only affect the IP addresses that are allowed to access your organization

and products5.

Reference :

Manage an organization with the admin APIs

Create and revoke API keys

Verify a domain to manage accounts

Regenerate your security key

Set up an IP allowlist

:

The only outcome that is not possible for Edmund is that he is granted org admin privileges. This is

because org admin privileges are not related to product access or product roles, but to organization

settings and management. To grant Edmund org admin privileges, you would need to go to Settings >

Organization admins and add him there. The other outcomes are possible depending on the product

access settings and the groups that Edmund belongs to.

Reference = [Give users access to products] and [Manage organization admins]

An Atlassian Cloud organization can have one or more sites, each containing one instance of each

product1. A site has its own URL and administration settings2. Since your organization has two

instances of Jira Software and two instances of Confluence, it must have at least two sites to host

them. For example, one site could have the URL acme.atlassian.net and contain Jira Software and

Confluence, while another site could have the URL acme-dev.atlassian.net and contain another

instance of Jira Software and Confluence.

The other options are not necessarily true for your organization. Having multiple sites does not imply

that you have verified your domain, which is a process that allows you to manage the Atlassian

accounts of your users and apply security policies to them3. You may or may not have verified your

domain, depending on whether you have access to your domain’s DNS or HTTPS settings. Verifying

your domain is not required to use Atlassian cloud products.

A landing product is the product that your users see first when they log in to your site4. You can only

set the landing product to Jira or Confluence. Therefore, you cannot have exactly four landing

products, as you can only have one landing product per site. You may have two landing products if

you set one for each site, or you may have none if you do not set any.

A Premium subscription plan is a plan that offers advanced features, unlimited storage, 99.9%

uptime SLA, and 24/7 Premium support for Jira Software, Confluence, Jira Service Management, and

Jira Work Management5. You may or may not have a Premium subscription plan for your products,

depending on your needs and budget. Having multiple sites or products does not automatically

mean that you have a Premium subscription plan.

A sandbox is an isolated environment where you can test and experiment before making changes to

production6. A sandbox is available for Jira Software, Jira Service Management, and Confluence with

Premium and Enterprise plans6. You may or may not have sandboxes for your products, depending

on whether you have a Premium or Enterprise plan and whether you have created a sandbox from

your organization. Having multiple sites or products does not automatically mean that you have

sandboxes.

Reference :

Understand Atlassian sites and organizations

What is an Atlassian organization?

Verify a domain to manage accounts

Set your site’s landing product

Atlassian Cloud Premium

Manage product sandboxes

The Billing page shows you the number of billable users for each product on your site, as well as the

user tier and the monthly cost. You can filter by product and site to see the specific details for Jira

Software on “acme.atlassian.net”.

Reference:

How to prepare for ACP-520: Atlassian Cloud Organization Admin Certification, section “Manage

product subscriptions & billing”

Manage your bill for Standard and Premium plans, subsection “View your bill”

When a user is invited to join a product or site, they automatically get an Atlassian account. The

status “Invited” means that the user has not accepted the invitation yet, but they already have an

account created for them.

Reference:

Accept the invitation to join your service project team

Customer is not receiving invitation emails when invited to a Service Management project

The statement that is true is that the group is definitely not used to restrict who can invite

teammates to Jira. This is because inviting teammates to Jira is a site administration function that is

controlled by the site admin role, not by any group. The other statements are false, as the group

could be used for those purposes, depending on how the group is configured in the global

permissions, the permission schemes, the issue security schemes, or the workflow conditions.

When you add a domain to user access settings, you can specify the default product role for each

product in your organization. This determines the level of access that users with verified email

addresses from that domain will have when they join your site. If you set the product role to None,

users will not have access to that product unless you manually grant them access later.

Reference

Specify how users get site access User access settings

When Holly signed up for a new Confluence Cloud site, two groups were definitely created along

with the site. These are the default groups for Confluence: confluence-users and site-admins. The

confluence-users group grants access to Confluence and allows users to create and edit pages. The

site-admins group grants administrative privileges for Confluence and allows users to manage global

settings, templates, permissions, and more12

Reference = Manage product access, Manage groups