ATLASSIAN ACP-520 Dumps

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

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.

To access the Project Role Browser and set a default group for a project role, Foogie must have the Administer Jira global permission, which is granted by the site admin role1. The product admin role for Jira Administration does not have this permission2. The project admin role can only manage project role members for specific projects, not the default members3. The product admin role for Confluence and the org admin role are irrelevant for this task.

References: Manage project roles, Jira Cloud site and product administration, Project permissions

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

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

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

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

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]

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]

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.

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.

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

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

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?

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

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