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

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

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

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

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

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

This statement is false because every site belongs to an organization. When you create a new site, you either join an existing organization or create a new one1. You cannot have a site without an organization.

References: Get started with an Atlassian organization, Understand Atlassian sites and organizations

The groups jira-software-users-acme and jira-admins-acme are default groups that are automatically created when you invite users to Jira Software or assign them the Jira admin role in your organization. The suffix acme indicates that the groups belong to the organization with the domain name acme.com. The groups are used to manage product accessand permissions for Jira Software, but they do not imply anything about Confluence access or org admin privileges. Therefore, the only statement that is definitely true is that your organization has the Jira Software product.

References :

• Default groups and permissions
• Users & Permissions | Jira Software.

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

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.

References: Manage product sandboxes

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

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

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