ACP-520 Practice Questions

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. Reference: Manage

product access, [Manage users and groups]

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.

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.

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

Removing a user from an Atlassian Cloud Organization does not affect the subscription plan for the

products. The subscription plan remains the same until you change it manually or it expires. The

billing preview shows the estimated cost for the next billing cycle based on the current number of

users and the subscription plan. If you remove a user, the billing preview will reflect the reduced

cost, but the subscription plan will not change12

Reference = Manage product access, Manage your bill for Standard and Premium plans

The groups jira-software-users-acme and jira-admins-acme are default groups that are automatically

created when you invite users to Jira Software or assign them the Jira admin role in your

organization. The suffix acme indicates that the groups belong to the organization with the domain

name acme.com. The groups are used to manage product access and permissions for Jira Software,

but they do not imply anything about Confluence access or org admin privileges. Therefore, the only

statement that is definitely true is that your organization has the Jira Software product.

Reference :

Default groups and permissions

Users & Permissions | Jira Software.

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.

Reference:

Manage product access

Manage product roles

Thank you for your visit.

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.

Reference

Invite anyone to your site Specify how users get site access

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.

Reference =

[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 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.

Reference = Manage product sandboxes, Copy data to sandbox

: