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

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

With a Standard subscription plan, you can add multiple products to your existing site, such as Jira Service Management1. You can also add Jira Software to a new site, if you need to create a separate instance for a different team or project2. However, you cannot create or use sandboxes, which are only available for Premium and Enterprise plans3. You also cannot change release tracks, which are only available for Enterprise plans4.

References: Manage your bill for Standard and Premium plans, Add a new product to your organization, How many instances of a product does my organization need?, Manage product sandboxes, Release tracks for cloud products

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 Ravi invites a teammate to join a product, an access request is generated for that product only. If the teammate needs access to another product on the same site, they can request it themselves or Ravi can invite them again. Therefore, if Ravi wants his teammate to have access to both Confluence and Jira Software, he needs to send two invitations, resulting in two access requests.

ReferencesInvite users to your site Approve or deny product access requests

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

The Product admin role for Jira Administration is only available for groups that have access to Jira Software1. The “confluence-admins” group does not have access to Jira Software by default, so you cannot grant them this role. You can only grant this role to groups that have the Jira Software User role or the Jira Software Admin role2.

References:

• Manage groups
• Manage product roles

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

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

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

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

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

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

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

Each site in an organization must have a unique name and URL. You cannot have two sites with the same name or URL in the same organization.

ReferencesAdd a new product to your organization Update a product URL to a new URL

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/

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]