Free ACP-520 Exam Dumps Preview

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 References = Manage product access, Manage your bill for Standard and Premium plans

Martha needs to be able to use and update global templates and blueprints. The correct product access configuration for Martha is Confluence Administration with Product admin role. This role allows her to manage global templates and blueprints, as well as other site-wide settings for Confluence. She also needs the User role for Confluence to access and edit pages.
References:
Manage product access, Administer global templates

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

Out of the five tasks, only verifying an email domain and adding a custom email address require org admin permissions. Configuring an email handler, customizing a notification scheme, and managing personal notification settings can be done by project admins or site admins.
References:
Verify a domain to manage accounts, Add custom email addresses for product notifications,
Create issues and comments from email, Configure notification schemes, Manage your Jira personal settings

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

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 org admin can remove a group from a product, but they cannot update or delete a group, or make a group a default group.
References:
How to prepare for ACP-520 Atlassian Cloud Organization Admin Learn about Atlassian organizations

The Product admin role for Jira Administration is only available for groups that have access to Jira Software1. 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

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