ACP-520 Practice Exam Questions with Answers Atlassian Cloud Organization Admin Certification

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

The correct product access configuration for Bob is Jira Administration with Product admin role and Jira Software with User role. This will allow Bob to update project schemes in Jira Software, as well as other project settings, without using a license. The Product admin role for Jira Administration grants access to the Jira Administration product, which is aseparate product from Jira Software that does not consume a license. The User role for Jira Software grants access to the Jira Software product, which does consume a license, but is necessary for Bob to view and edit project schemes12

References = Manage product access, Jira Administration overview

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

References = Manage product access, Manage groups

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

By removing the default group from the Jira Software User product role, you can prevent new users from automatically getting access to Jira Software when they join your site. This way, you can control who gets access to Jira Software and how many licenses are consumed.

ReferencesManage product access Product roles and permissions

By unselecting the User product role for Confluence, you are removing the site-admins group from the default groups that manage roles for that product1. This means that ACME site admins will lose their Confluence admin permissions, such as managing Confluence settings, space permissions, etc2. They will still be able to see Confluence users, but not edit their roles or access.

References: Default groups and permissions, Confluence Admin Permission Levels Explained

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]

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

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.

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

Adding an upstream port is one of the configuration steps that must be done in a self-managed instance to enable a secure pathway between a self-managed Jira Software instance and several Atlassian Cloud products. An upstream port is the port on your self-managed instance that receives traffic from the application tunnel. You need to configure the upstream port for each product that you want to connect to the tunnel.

References = Configure required connections and upstream ports and Create an application tunnel to your self-managed instance

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

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”

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.