ACP-520 ATLASSIAN Atlassian Cloud Organization Admin Certification Free Practice Exam Questions (2025 Updated)

The problem that did not occur for Joe and John is that they could no longer view the billing history. This is because the billing history is not related to the groups or permissions in Jira, but to the organization and site administration. Only the organization admin or the billing contact can view the billing history for the products and subscriptions12

The other problems could have occurred for Joe and John if the group “engineers” had specific permissions or roles in Jira that were not granted to the new groups. For example, if the group “engineers” had the Browse Users global permission, they could select other users in dropdown fields, such as assignee or reporter. If the group “engineers” had the View Dashboard project permission, they could view some dashboards that were shared with the project. If the group “engineers” had the Edit Own Comments issue permission, they could edit their own comments on issues. If the group “engineers” had the Transition Issues issue permission, they could transition issues from one status to another345

References = View your billing history, Manage your bill for Standard and Premium plans, Manage global permissions, Manage project permissions, Manage project roles

This statement is false because every site belongs to an organization. When you create a new site, you either join an existing organization or create a new one1. You cannot have a site without an organization.

References: Get started with an Atlassian organization, Understand Atlassian sites and organizations

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.

References:

Accept the invitation to join your service project team

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

As an organization admin, you can log in as another user to ensure their permissions in a product are set correctly, and complete other configuration tasks in a product. However, you can’t use this feature to log in as a user who has the same role as you or higher (meaning, if you’re an organization admin, you can’t log in as another organization admin)1.

References:

Log in as another user

If you want to manage users and groups from both corporations in a single location, you need to consolidate your Atlassian Cloud organizations. This can be done by transferring all product instances in one organization to another. After the transfer, the unwanted organization is deleted1. This feature is called Transfer products and it is available from the organization settings2.

The other options are not features that can help you merge your organizations. Organization insights is a feature that provides analytics and reports on your organization’s users, products, and security3. Release tracks is a feature that allows you to choose when your cloud products receive new features and improvements4. Verify domains is a feature that allows you to manage the Atlassian accounts of your users and apply security policies to them5. Identity providers is a feature that allows you to integrate your organization with external identity services, such as SAML or SCIM6.

References :

Should I merge my Atlassian organizations?

Transfer all products to another organization

View organization insights

Choose a release track for your cloud products

Verify a domain to manage accounts

Manage users from your identity provider

If a group that was used to share a filter or a dashboard was deleted, the users who belonged to that group would no longer receive the filter subscriptions or see the dashboard .

References:

[Manage shared filters and dashboards]

[Manage users, groups, permissions, and roles in Jira Cloud]

For Atlassian Access billing, users on paid plans, like the Confluence Enterprise plan, are included in the bill. Atlassian Access provides security and centralized administration across all Atlassian Cloud products. Users on free plans, deactivated accounts, and portal-only customers (who typically access only a service desk portal and do not use licensed seats) are not counted as billable users for Atlassian Access.

When you copy data from production to a sandbox, the user permissions and groups are also copied. This means that project admins from production can access and manage the same projects in the sandbox. However, customers and agents from production cannot log into the same portals or projects in the sandbox, because we disable app links, external email notifications, and integrations with Bitbucket and Slack. Attachments and comments are also not copied to the sandbox, unless you choose to copy with media files.

References = Manage product sandboxes, Copy data to sandbox

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.

ReferencesInvite users to your site Approve or deny product access requests

When you start a site with a Premium subscription trial to a Cloud product, you automatically create a “site-admins” group that contains your account as the only member. The “site-admins” group has the site admin role, which allows you to manage the site settings, products, users, and groups. You can also add other users to the “site-admins” group if you want to delegate some of the site administration tasks.

References = Create and update groups and Manage site-level permissions

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.

ReferencesSpecify how users get site access User access settings

If Ann’s email domain is not verified by your organization, it means that you do not own or manage her account. However, she may have a managed account in another organization that has verified her domain. In that case, you cannot enforce security policies, deactivate, or delete her account12.

References:

Verify a domain to manage accounts

Solved: Verify domain - Missing accounts

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.

References: 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

Removing a user from an Atlassian Cloud Organization does not affect the subscription plan for the products. The subscription plan remains the same until you change it manually or it expires. The billing preview shows the estimated cost for the next billing cycle based on the current number of users and the subscription plan. If you remove a user, the billing preview will reflect the reduced cost, but the subscription plan will not change12

References = Manage product access, Manage your bill for Standard and Premium plans

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.

References :

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 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”.

References:

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”

The “Invite anyone” setting allows users to invite anyone to join a product without admin approval. If this setting is enabled for one product but not the other, then Arjun can join the former product immediately but will need admin approval for the latter product.

ReferencesInvite anyone to your site Specify how users get site access

A direct cause for the “engineers” group having a lot more members than you have added manually is that it is a default group for Jira Software product access. This means that any new user who joins your site and has access to Jira Software will automatically be added to the “engineers” group. You can check and change the default group for Jira Software by going to Products > Jira Software > Manage product > Product roles.

References = [Default groups and permissions] and [Manage role and product permissions]