Atlassian ACP-520 - Questions & Answers

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

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

The correct product access configuration for Bob is Jira Administration with Product admin role and Jira Software with User role. This will allow Bob to update project schemes in Jira Software, as well as other project settings, without using a license. The Product admin role for Jira Administration grants access to the Jira Administration product, which is aseparate product from Jira Software that does not consume a license. The User role for Jira Software grants access to the Jira Software product, which does consume a license, but is necessary for Bob to view and edit project schemes12 References = Manage product
access, Jira Administration overview

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

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

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
References:
View and manage your bill, Remove or suspend a user

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

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 role 1. The product admin role for Jira Administration does not have this permission 2. The project admin role can only manage project role members for specific projects, not the default members 3. 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 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

Adding an upstream port is one of the configuration steps that must be done in a self-managed instance to enable a secure pathway between a self-managed Jira Software instance and several Atlassian Cloud products. An upstream port is the port on your self-managed instance that receives traffic from the application tunnel. You need to configure the upstream port for each product that you want to connect to the tunnel.
References:
Configure required connections and upstream ports and Create an application tunnel to your self-managed instance