ACP-520 Atlassian Cloud Organization Admin Exam Question and Answers

The statement that is definitely true is that the site contains at least one Confluence space. This is because when you create a new site with Confluence, a default space called “Welcome to Confluence” is automatically created for you. You can see this space by going to gobasics.atlassian.net/wiki and clicking on Spaces in the sidebar. The other statements are not necessarily true, as they depend on other factors, such as how many products, admins, or projects you have added to your site.

References = Create a space and Create and update groups

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]

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/

Only Bob and Emily have performed tasks that are exclusive to org admins. However, Emily’s task could have been performed by a site admin as well. Therefore, only Bob is definitely an org admin.

References =

• [Manage an organization with the admin APIs] and [Manage API tokens for your Atlassian account]
• [Verify a domain to manage accounts] and [Manage verified domains]
• [Manage users, groups, permissions, and roles in Jira Cloud] and [Manage role and product permissions]
• [Create an application tunnel to your self-managed instance] and [Configure required connections and upstream ports]
• [Manage site-level permissions] and [Manage global permissions]

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

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

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.

One other access request you might see for Ann on the Access Requests page is access to another product. This could happen if Ann tries to access a product that she does not have access to, such as Confluence or Jira Service Management. She would see a message prompting her to request access, and you would see her request on the Access Requests page. You can approve or deny her request from there1

References = Approve or deny product access requests

Each site in an organization must have a unique name and URL. You cannot have two sites with the same name or URL in the same organization.

ReferencesAdd a new product to your organization Update a product URL to a new URL

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

Deleting the group “jira-software-users-acme” means that all the users in that group lose their product access to Jira Software1. This means that they can no longer perform any actions that require the Jira Software User role, such as updating an agile board2. The other options are not directly affected by deleting the group, as they depend on other factors such as personal settings, Confluence permissions, service project roles, and API tokens.

References:

• Manage product access
• Manage product roles

This is because the access request shown in the image is for Confluence and the reason stated is “Needs to access Confluence”. Hence, Monica is granted the User role for Confluence, which allows her to view and edit pages and spaces in Confluence. She is not granted access to any other products or any Product Admin roles, which require higher permissions. She is also added to only one default group, which is the confluence-users group, unless the site admin has changed the default group for Confluence.

References = [Approve or deny product access requests], [Manage product access]

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

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

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

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