ACP-520 Atlassian Cloud Organization Admin Certification Questions and Answers

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

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

After the products from Original were transferred to Destination, Jira Software will appear as a single product under the Destination URL. This is because the Original organization was deleted, so there is no longer a separate URL for it.

References:

• How to prepare for ACP-520: Atlassian Cloud Organization Admin Certification, section “Manage multiple sites and products”
• Transfer products to another organization, subsection “What happens after you transfer products?”

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

Anonymous access is a method to grant Confluence product access to new users without requiring admin approval or an Atlassian account. Users can view public spaces and pages in Confluence without logging in. However, anonymous access does not allow users to edit, comment, or create content in Confluence.

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 most likely root cause of Omar being able to see Jira projects is that he belongs to a group that has access to both Confluence and Jira products. Groups are used to manage users who need the same permissions or restrictions, and they can be assigned to multiple products. When you invite a user to join your site and a product, you can also add them to a group that has access to that product. However, if the group also has access to other products, the user will be able to see those products as well. To prevent this, you can either create a new group that only has access to Confluence, or remove the Jira access from the existing group that Omar is in.

References = [Manage groups] and [Give users access to products]

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

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]

Organization insights is a feature that provides analytics and reports on your organization’s users, products, and security. You can access it from the Insights tab in your organization settings. Organization insights is available for all Atlassian cloud products and plans1.

References :

• View organization insights

When you click “Grant access to Jira Software” in the access request, the user is granted access to Jira Software only. They are not added to multiple product access groups, granted the User role for Jira Software, added to only one default group, or granted any Product Admin roles. References: Manage product access, [Manage users and groups]

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

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

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