A. The "Invite anyone" setting is configured for one of the products but not the other.

Answer DescriptionExplanation:

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.

References

Invite anyone to your site Specify how users get site access

D. You have 8 billable users.

Answer DescriptionExplanation: 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

C. groups

Answer DescriptionExplanation:

The most likely root cause of Omar being able to see Jira projects is that he belongs to a group that has access to both Confluence and Jira products. Groups are used to manage users who need the same permissions or restrictions, and they can be assigned to multiple products. When you invite a user to join your site and a product, you can also add them to a group that has access to that product. However, if the group also has access to other products, the user will be able to see those products as well. To prevent this, you can either create a new group that only has access to Confluence, or remove the Jira access from the existing group that Omar is in.

References = [Manage groups] and [Give users access to products]

A. at least 2 sites

Answer DescriptionExplanation: 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.

A. site admin

A. 0 additional sandboxes

Answer DescriptionExplanation: Currently, you can only create one sandbox for each linked product1. Since you have only two products (Jira Software and Confluence), and you already have a sandbox for Confluence, you cannot create any more sandboxes for your organization.

A. One of your managed accounts created a product in another Cloud organization.

Answer DescriptionExplanation: 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.

A. "site-admins" group

Answer DescriptionWhen you start a site with a Premium subscription trial to a Cloud product, you automatically create a “site-admins” group that contains your account as the only member. The “site-admins” group has the site admin role, which allows you to manage the site settings, products, users, and groups. You can also add other users to the “site-admins” group if you want to delegate some of the site administration tasks. References = Create and update groups and Manage site-level permissions