ACP-520 practice question 7 of 15

Laura went to Add People from within Jira. She chose to invite Arjun to join Jira Software and Jira Service Management. Arjun was able to join one of the products immediately but needed admin approval for the other. What accounts for this difference?

Full set: 65 questions

Domain Configuring and Managing Jira for Advanced Roadmaps

Answer options
A: The "Invite anyone" setting is configured for one of the products but not the other. Correct answer
B: Laura is a Jira admin for one of the products but not the other.
C: Laura's email address is unverified in one of the products but not the other.
D: Laura is on the same site as one of the products but not the other.
E: Arjun's email address is unverified in one of the products but not the other.
Correct Answer:
A. The "Invite anyone" setting is configured for one of the products but not the other.
Explanation

In Atlassian Cloud, organization administrators can configure "User access settings" to control how new users gain access to products. These settings can be applied differently to various products. If one product (e.g., Jira Software) is configured to allow existing users to invite anyone who then gets immediate access, Arjun would join instantly. If the other product (e.g., Jira Service Management) is configured to require administrator approval for new users, Arjun's access request, triggered by Laura's invitation, would be placed in a queue for an admin to approve. This difference in product-specific access settings directly accounts for the scenario.

Why Incorrect

B. Laura's admin status for a product determines her ability to manage that product, not the site-wide user access approval process for an invited user like Arjun.
C. Laura's email verification status is tied to her Atlassian account for the entire site, not configured on a per-product basis.
D. The invitation process described originates from a single Atlassian site that contains both products; it is not possible for Laura to be on different sites for this action.
E. Arjun's email verification is a one-time action for his new Atlassian account and is not a per-product status.

References

1. Atlassian Cloud Support Documentation, "Specify how users get access to products." This document details the different user access settings available to organization admins. It explains the options for allowing users to join immediately versus requiring admin approval. The settings can be configured for product groups, allowing for the discrepancy described in the question. (Accessed under the "Control how users get access" section).

2. Atlassian Cloud Support Documentation, "Invite users." This guide explains the invitation workflow and explicitly states, "When you invite a user to a product, they'll get an email with a link to join. What happens next depends on your user access settings." This directly links the invitation action to the site's access configuration, which can differ between products. (See the "Before you begin" section).

Scroll to Top