ATLASSIAN ACP-520 Atlassian Cloud Organization Admin Exam Exam Practice Test

The correct product access configuration for Bob is Jira Administration with Product admin role and Jira Software with User role. This will allow Bob to update project schemes in Jira Software, as well as other project settings, without using a license. The Product admin role for Jira Administration grants access to the Jira Administration product, which is aseparate product from Jira Software that does not consume a license. The User role for Jira Software grants access to the Jira Software product, which does consume a license, but is necessary for Bob to view and edit project schemes12

References = Manage product access, Jira Administration overview

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 more12

References = Manage product access, Manage groups

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 status “Active” means that the user has an active account and can access the products they have been granted access to1. It does not imply anything about the user’s group membership, account type, last login time, or product access.

References:

• Manage users in your organization

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

As an organization admin, you can delete both managed and unmanaged accounts. Managed accounts are those that belong to your organization and are verified by a domain or an allowlist. Unmanaged accounts are those that do not belong to your organization and are not verified by a domain or an allowlist. Deleting an account removes the user’s access to all Atlassian products and services, and deletes their personal data.

Managed accounts are accounts with an email address that you have claimed from your verified domain1. Verifying a domain proves that you own it and allows you to manage the accounts associated with it2. Managed accounts do not necessarily have product access, verified email addresses, or billable status.

References:

• What are managed accounts?
• Verify a domain to manage accounts

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

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

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

Groups are used to manage users with your organization who need the same permissions or restrictions. You can assign groups to one or more products within your organization, such as Jira Software, Confluence, or Bitbucket1.

References: Manage groups, Create and update groups

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]

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 A12

References = Manage product access, Manage project roles

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

Shadow IT refers to the product creation and usage administered outside of an organization’s IT department, which can lead to unexpected costs, security and compliance concerns, and operational complexity1. Atlassian Access is a service that provides enhanced security and governance features for Atlassian Cloud products, such as SAML SSO, user provisioning, enforced two-step verification, and audit logs2. Atlassian Access also offers a feature called automatic product discovery, which helps admins discover and manage the shadow IT products created by their managed users1.

A managed user is a user whose account is on a domain that is verified by an organization3. A verified domain is a domain that an organization has proven ownership of by adding a DNS or HTTPS record4. For example, if an organization verifies the domain acme.com, then any user with an email address ending with @acme.com is a managed user of that organization.

A product is an instance of an Atlassian Cloud product, such as Jira Software, Confluence, Bitbucket, or Trello5. A product belongs to a site, which is a collection of products that share a URL and administration settings6. A site belongs to an organization, which is a way to group and manage multiple sites and products under one central admin console7.

A managed user can create a product in another Cloud organization by using their work email address to sign up for a new site or join an existing site that is not owned by their organization1. This creates a shadow IT product that is not visible or controlled by their organization’s admins. Atlassian Access can discover these shadow IT products by scanning the domains of all Atlassian Cloud products and matching them with the domains of the organizations that have Atlassian Access enabled1. Atlassian will proactively send an email to the organization admins with the number of shadow IT products created by their managed users and what the exact shadow IT product is. Within admin.atlassian.com, organization admins can also view additional information, such as the owner of these products, how many users are in that product, and the date it was created1.

Therefore, the statement that explains how Atlassian Access discovered shadow IT is that one of your managed accounts created a product in another Cloud organization.

References :

• Automatic product discovery in Atlassian Access
• Atlassian Access: Enhanced Cloud Data Security & Governance
• What is a managed account?
• Verify a domain to manage accounts
• What is a product?
• Understand Atlassian sites and organizations
• What is an Atlassian organization?

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