Free ATLASSIAN ACP-520 Practice Exam with Questions & Answers

If you want to ensure that the script can no longer access the information about the domains in your Cloud organization, you need to revoke the API key that was used to authenticate the script. An API key is a token that allows you to manage your organization via the admin APIs1. You can create, view, and revoke API keys from the organization settings2. Revoking an API key will invalidate it and prevent any further requests using that key2.

The other options are not relevant or effective for stopping the script from accessing the information. Removing DNS records or removing a verified domain will not affect the API key that was used by the script. It will only affect the verification status of your domain and the management of your users and accounts3. Regenerating a security key will not affect the API key that was used by the script. It will only affect the encryption of your data at rest4. Deleting an IP allowlist will not affect the API key that was used by the script. It will only affect the IP addresses that are allowed to access your organization and products5.

References :

• Manage an organization with the admin APIs
• Create and revoke API keys
• Verify a domain to manage accounts
• Regenerate your security key
• Set up an IP allowlist

 Updating the product URL changes the email address from which notifications are sent and received. Ahmed should have configured the sender email address for the Jira Software project to use the custom email address “support@acme.com”.

References: Configure email notifications, Update a product URL to a new URL

A direct cause for the “engineers” group having a lot more members than you have added manually is that it is a default group for Jira Software product access. This means that any new user who joins your site and has access to Jira Software will automatically be added to the “engineers” group. You can check and change the default group for Jira Software by going to Products > Jira Software > Manage product > Product roles.

References = [Default groups and permissions] and [Manage role and product permissions]

If a group that was used to share a filter or a dashboard was deleted, the users who belonged to that group would no longer receive the filter subscriptions or see the dashboard .

References:

• [Manage shared filters and dashboards]
• [Manage users, groups, permissions, and roles in Jira Cloud]

As an organization admin, you can delete both managed and unmanaged accounts. Managed accounts are those that belong to your organization and are verified by a domain or an allowlist. Unmanaged accounts are those that do not belong to your organization and are not verified by a domain or an allowlist. Deleting an account removes the user’s access to all Atlassian products and services, and deletes their personal data.

When you click “Grant access to Jira Software” in the access request, the user is granted access to Jira Software only. They are not added to multiple product access groups, granted the User role for Jira Software, added to only one default group, or granted any Product Admin roles. References: Manage product access, [Manage users and groups]

Only Bob and Emily have performed tasks that are exclusive to org admins. However, Emily’s task could have been performed by a site admin as well. Therefore, only Bob is definitely an org admin.

References =

• [Manage an organization with the admin APIs] and [Manage API tokens for your Atlassian account]
• [Verify a domain to manage accounts] and [Manage verified domains]
• [Manage users, groups, permissions, and roles in Jira Cloud] and [Manage role and product permissions]
• [Create an application tunnel to your self-managed instance] and [Configure required connections and upstream ports]
• [Manage site-level permissions] and [Manage global permissions]

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

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