ATLASSIAN ACP-520 Dumps

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.

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 deletion1. 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 directory1.

References :

• Delete a group

Application tunnels provide a secure pathway between your Atlassian cloud organization and Data Center or Server instances that live in your network. You can link only one such organization (and its multiple products) to a single self-managed instance, for example Confluence Data Center.

References: What are application tunnels?, Application tunnels overview

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

The statement that is true is that the group is definitely not used to restrict who can invite teammates to Jira. This is because inviting teammates to Jira is a site administration function that is controlled by the site admin role, not by any group. The other statements are false, as the group could be used for those purposes, depending on how the group is configured in the global permissions, the permission schemes, the issue security schemes, or the workflow conditions.

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

This statement is false because every site belongs to an organization. When you create a new site, you either join an existing organization or create a new one1. You cannot have a site without an organization.

References: Get started with an Atlassian organization, Understand Atlassian sites and organizations

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

The only statement that is definitely true is that Drew’s email address is verified. This is because product access requests must be made by a user with a verified email address and Atlassian account1 The other statements are not necessarily true, as they depend on other factors, such as the roles and permissions of Beth and Drew, the existing users on the site, and the self-signup settings2

References = Approve or deny product access requests, Manage product access

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

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.

ReferencesSet your site’s landing product Request access to a product

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]

According to the Atlassian Cloud Organization Admin ACp-520 documents and learning resources, only an org admin can make another user an org admin. In this case, Owen is the only org admin, so he is the only one who can make Praj an org admin.

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]

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]

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

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

Currently, you can only create one sandbox for each linked product1. 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

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