Pass the ATLASSIAN ACP-OA ACP-520 Questions and answers with ExamsMirror

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

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

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.

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

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?

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

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.

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

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.

https://community.atlassian.com/t5/Training-Certification-articles/How-to-prepare-for-ACP-520-Atlassian-Cloud-Organization-Admin/ba-p/2441713

https://support.atlassian.com/organization-administration/docs/learn-about-atlassian-organizations/

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