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

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 go to the Jira Software product pricing page, you can sign up for a new Atlassian site by clicking the Try it free button. You will be asked to enter your email address and choose a site name and URL. However, you must use an email address from a non-public domain, such as your company or organization domain. You cannot use an email address from a public domain, such as Gmail or Yahoo, because they are not allowed for security reasons12

References = Sign up for an Atlassian Cloud site, Atlassian Cloud site and organization domains

A direct cause for the “engineers” group having a lot more members than you have added manually is that it is a default group for Jira Software product access. This means that any new user who joins your site and has access to Jira Software will automatically be added to the “engineers” group. You can check and change the default group for Jira Software by going to Products > Jira Software > Manage product > Product roles.

References = [Default groups and permissions] and [Manage role and product permissions]

The Billing page shows you the number of billable users for each product on your site, as well as the user tier and the monthly cost. You can filter by product and site to see the specific details for Jira Software on “acme.atlassian.net”.

References:

• How to prepare for ACP-520: Atlassian Cloud Organization Admin Certification, section “Manage product subscriptions & billing”
• Manage your bill for Standard and Premium plans, subsection “View your bill”

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.

If you want to manage users and groups from both corporations in a single location, you need to consolidate your Atlassian Cloud organizations. This can be done by transferring all product instances in one organization to another. After the transfer, the unwanted organization is deleted1. This feature is called Transfer products and it is available from the organization settings2.

The other options are not features that can help you merge your organizations. Organization insights is a feature that provides analytics and reports on your organization’s users, products, and security3. Release tracks is a feature that allows you to choose when your cloud products receive new features and improvements4. Verify domains is a feature that allows you to manage the Atlassian accounts of your users and apply security policies to them5. Identity providers is a feature that allows you to integrate your organization with external identity services, such as SAML or SCIM6.

References :

• Should I merge my Atlassian organizations?
• Transfer all products to another organization
• View organization insights
• Choose a release track for your cloud products
• Verify a domain to manage accounts
• Manage users from your identity provider

The statement that is definitely true is that the site contains at least one Confluence space. This is because when you create a new site with Confluence, a default space called “Welcome to Confluence” is automatically created for you. You can see this space by going to gobasics.atlassian.net/wiki and clicking on Spaces in the sidebar. The other statements are not necessarily true, as they depend on other factors, such as how many products, admins, or projects you have added to your site.

References = Create a space and Create and update groups

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

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

By removing the default group from the Jira Software User product role, you can prevent new users from automatically getting access to Jira Software when they join your site. This way, you can control who gets access to Jira Software and how many licenses are consumed.

ReferencesManage product access Product roles and permissions

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

When a user is invited to join a product or site, they automatically get an Atlassian account. The status “Invited” means that the user has not accepted the invitation yet, but they already have an account created for them.

References:

• Accept the invitation to join your service project team
• Customer is not receiving invitation emails when invited to a Service Management project

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

If a group that was used to share a filter or a dashboard was deleted, the users who belonged to that group would no longer receive the filter subscriptions or see the dashboard .

References:

• [Manage shared filters and dashboards]
• [Manage users, groups, permissions, and roles in Jira Cloud]

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

Permission schemes control who can see and do what in Jira projects. If the org admin changed the permission scheme for the project that Jack was working on, it could affect his visibility and access to the issues.

References:

• How to prepare for ACP-520: Atlassian Cloud Organization Admin Certification, section “Users and Groups”
• Manage project permissions

The table is showing the total number of managed accounts in the organization and the number of deactivated accounts. The total number of managed accounts is the number ofbillable users in the organization, regardless of whether they have verified their email addresses or not. The deactivated accounts are the accounts that have been suspended by the organization admin and do not consume a license. Therefore, you can definitely conclude that you have 8 billable users in your organization12

References = View and manage your bill, Remove or suspend a user

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.