Free Practice Questions for the ATLASSIAN ACP-OA ACP-520 Exam (2026 Updated)

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.

References Specify how users get site access   User access settings

Currently, you can only create one sandbox for each linked product 1 . Since you have only two products (Jira Software and Confluence), and you already have a sandbox for Confluence, you cannot create any more sandboxes for your organization.

References :  Manage product sandboxes

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]

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.

When you delete a group from your organization, the group name and its members are removed from your organization’s directory. However, the group name and its members are not deleted from the products that the group had access to.  Therefore, if you recreate a group with the same name, the group will automatically regain access to the same products and inherit the same product roles and permissions that it had before deletion 1 . This means that the group membership is automatically restored as a result of recreating the group with the same name.

The other options are not automatically restored as a result of recreating the group with the same name. Access to a User product role, access to a Product Admin role, global permissions, and access to shared filters are all product-specific settings that depend on how the group is configured in each product.  They are not affected by deleting or recreating the group from the organization’s directory 1 .

References  :

Delete a group

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 subscriptions 1 2

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 another 3 4 5

References  =  View your billing history ,  Manage your bill for Standard and Premium plans ,  Manage global permissions ,  Manage project permissions ,  Manage project roles

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 product 1 .  A site has its own URL and administration settings 2 . 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 them 3 . 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 site 4 . 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 Management 5 . 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 production 6 .  A sandbox is available for Jira Software, Jira Service Management, and Confluence with Premium and Enterprise plans 6 . You may or may not have sandboxes for your products, depending on whether you have a Premium or Enterprise plan 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

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 plans 1 .

References  :

View organization insights

By unselecting the User product role for Confluence, you are removing the site-admins group from the default groups that manage roles for that product 1 .  This means that ACME site admins will lose their Confluence admin permissions, such as managing Confluence settings, space permissions, etc 2 . 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

The Product admin role for Jira Administration is only available for groups that have access to Jira Software 1 . The “confluence-admins” group does not have access to Jira Software by default, so you cannot grant them this role.  You can only grant this role to groups that have the Jira Software User role or the Jira Software Admin role 2 .

References :

Manage groups

Manage product roles

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

By default, Jira Software creates two groups: jira-software-users and jira-software-admins. The jira-software-users group is granted the Jira Software User role, and the jira-software- admins group is granted the Jira Software Admin role. These roles determine the permissions and access that the group members have within Jira Software. The default groups also have a suffix that matches the site name, in this case “ewok7a”.  Therefore, the default groups for Jira Software on the “ewok7a” cloud site are jira-software-users-ewok7a and jira-software-admins-ewok7a, as shown in Option A 1 2

References  =  Manage product access ,  Manage project roles

 Updating the product URL changes the email address from which notifications are sent and received. Ahmed should have configured the sender email address for the Jira Software project to use the custom email address “support@acme.com”.

References :  Configure email notifications ,  Update a product URL to a new URL

When Bob logs into the site for the first time, he will be redirected to the landing product, which is Jira. However, since he does not have product access to Jira, he will see a message that says “You don’t have access to this product” and a button that says “Request access”. If he clicks on the button, an access request will be generated for Jira, which will need to be approved by a product admin.

References Set your site’s landing product   Request access to a product

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 more 1 2

References  =  Manage product access ,  Manage groups