ACP-520 Atlassian Cloud Organization Admin Certification Questions and Answers

Users who have access to at least one product are considered billable. In this case, Clyde, Derek, Earl, Francis, and Anne are billable users. Bob is not billable because he has not accepted the invitation to join the organization.

References = [Manage users and user tiers] and [Control how users get access to products]

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 Enterpriseplan and whether you have created a sandbox from your organization. Having multiple sites or products does not automatically mean that you have sandboxes.

References :

• 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 table is showing the total number of managed accounts in the organization and the number of deactivated accounts. The total number of managed accounts is the number ofbillable users in the organization, regardless of whether they have verified their email addresses or not. The deactivated accounts are the accounts that have been suspended by the organization admin and do not consume a license. Therefore, you can definitely conclude that you have 8 billable users in your organization12

References = View and manage your bill, Remove or suspend a user

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

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

Converting a managed account to an unmanaged account requires changing the email address of the account to a domain that is not verified by the organization. This action can only be done for all accounts from a verified domain, not for individual accounts.

https://support.atlassian.com/user-management/docs/make-changes-to-a-managed-user-account/

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.

The groups jira-software-users-acme and jira-admins-acme are default groups that are automatically created when you invite users to Jira Software or assign them the Jira admin role in your organization. The suffix acme indicates that the groups belong to the organization with the domain name acme.com. The groups are used to manage product accessand permissions for Jira Software, but they do not imply anything about Confluence access or org admin privileges. Therefore, the only statement that is definitely true is that your organization has the Jira Software product.

References :

• Default groups and permissions
• Users & Permissions | Jira Software.

Managed accounts are accounts with an email address that you have claimed from your verified domain1. Verifying a domain proves that you own it and allows you to manage the accounts associated with it2. Managed accounts do not necessarily have product access, verified email addresses, or billable status.

References:

• What are managed accounts?
• Verify a domain to manage accounts

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]

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”

Application tunnels provide a secure pathway between your Atlassian cloud organization and Data Center or Server instances that live in your network. You can link only one such organization (and its multiple products) to a single self-managed instance, for example Confluence Data Center.

References: What are application tunnels?, Application tunnels overview

As an Org admin, Amit has the highest level of administrative privileges, which includes managing user accounts within the organization. This means that Amit has the authority to deactivate any user's account, including Lakshmi's. The Org admin role typically has more comprehensive permissions than the Confluence admin or a Space admin, who would have more limited and specific administrative powers within the scope of Confluence itself.

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