Atlassian Atlassian Certifications ACP-520 Questions & Answers

• Question 11:

  Which statement is true about Atlassian Access?

  A. It complies with both Cloud and Data Center platforms.

  B. It works across multiple sites within an organization.

  C. It manages all your company's products, including shadow IT.

  D. It enforces policies for both managed and non-managed accounts.

  E. It calculates billing across multiple Cloud organizations.

  Correct Answer: B

  Atlassian Access is a subscription that connects your Atlassian cloud products to your identity provider. It allows you to enable enterprise-grade authentication features, and additional oversight, across your company domains1. References: Understand Atlassian Access, Atlassian Access: Enhanced Cloud Data Security and Governance

• Question 12:

  Which set of unique billable users will definitely be included in your bill for Atlassian Access?

  A. managed accounts with access only to Jira Software Free

  B. deactivated accounts on Jira Software Standard plan

  C. users on the Confluence Enterprise plan

  D. portal-only customers on Jira Service Management Standard

  Correct Answer: C

  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.

• Question 13:

  You deleted the group "jira-software-users-acme". Identify a possible impact in the Jira Software product.

  A. Bob can no longer change his personal settings.

  B. Bob can no longer update an agile board.

  C. Bob can no longer view a particular space.

  D. Bob can no longer update SLAs.

  E. Bob can no longer create an API key.

  Correct Answer: B

  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

• Question 14:

  You are the org admin. From time to time, you manually add new members to the "engineers" group.

  Today, you noticed that the group has a lot more members than you have added manually.

  Identify a direct cause.

  A. Invitation links for Jira Software have been enabled.

  B. User invites for Jira Software have been changed to "Invite anyone".

  C. It is a default group for Jira Software product access.

  D. Project admins have been modifying the group.

  E. Jira product admins have been modifying the group.

  Correct Answer: C

  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]

• Question 15:

  Laura went to Add People from within Jira.

  She chose to invite Arjun to join Jira Software and Jira Service Management.

  Arjun was able to join one of the products immediately but needed admin approval for the other.

  What accounts for this difference?

  A. The "Invite anyone" setting is configured for one of the products but not the other.

  B. Laura is a Jira admin for one of the products but not the other.

  C. Laura's email address is unverified in one of the products but not the other.

  D. Laura is on the same site as one of the products but not the other.

  E. Arjun's email address is unverified in one of the products but not the other.

  Correct Answer: A

  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

• Question 16:

  You can perform various actions on a single managed account. One action can only be performed for all managed accounts from a particular verified domain and not just for one single account. Identify that action.

  A. enforce two-step verification

  B. revoke API tokens

  C. convert to unmanaged

  D. deactivate account

  E. view discovered products

  F. add to an authentication policy

  Correct Answer: C

  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/

• Question 17:

  Jack could see several issues. Then an org admin made a change in the admin hub.

  Now Jack can no longer see those same issues, but he can see others.

  Where in the admin hub was the change made?

  A. groups

  B. user access settings

  C. managed accounts

  D. permission schemes

  E. security

  Correct Answer: D

  Permission schemes control who can see and do what in Jira projects. If the org admin changed the permission scheme for the project that Jack was working on, it could affect his visibility and access to the issues.

  References:

  How to prepare for ACP-520: Atlassian Cloud Organization Admin Certification, section "Users and Groups"

  Manage project permissions

• Question 18:

  You want to delete a group that is currently used throughout Jira.

  Where is the group definitely NOT used?

  A. to search using the membersOf("") function

  B. to limit who can make bulk updates

  C. to restrict who can invite teammates to Jira

  D. to hide workflow transitions

  E. to secure the visibility of certain issues

  Correct Answer: C

  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.

• Question 19:

  As an org admin, you want to ensure that permissions for user Felix are set correctly.

  When are you not able to log in as Felix?

  A. if Felix is an org admin

  B. if Felix has a managed account

  C. if Felix has access to multiple sites

  D. if Felix is a product admin of multiple products

  E. if Felix has access to multiple products

  Correct Answer: A

  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

• Question 20:

  You are an org admin. Your organization contains the two users shown below.

  

  Which statement is true?

  A. You can only delete Ula's account.

  B. Both Maya and Ula can delete their accounts.

  C. You can only delete Maya's account.

  D. Only Maya can delete her account.

  E. You can delete both accounts.

  Correct Answer: E

  As an organization admin, you can delete both managed and unmanaged accounts. Managed accounts are those that belong to your organization and are verified by a domain or an allowlist. Unmanaged accounts are those that do not belong to your organization and are not verified by a domain or an allowlist. Deleting an account removes the user's access to all Atlassian products and services, and deletes their personal data.