Free Preparation Discussions
MENU
Atlassian ACP-520 Exam Questions
- Topic 1: Atlassian Organizations: This section of the exam measures skills of an Atlassian Organization Administrator and covers creating and managing Atlassian organizations, handling multiple sites and products, managing product access, handling access requests, and managing subscriptions and billing processes for cloud environments.
- Topic 2: Users and Groups: This section of the exam measures the skills of a Cloud Identity Manager and covers managing users and distinguishing between managed and unmanaged accounts. It includes creating managed accounts, administering groups, updating user access, and troubleshooting user and group changes across Jira and Confluence.
- Topic 3: Admin Roles: This section of the exam measures skills of an Atlassian Organization Administrator and covers distinguishing and assigning administrative roles. It focuses on understanding the responsibilities of org admins, product admins, project admins, and space admins, and the tasks associated with these roles.
- Topic 4: Advanced Features: This section of the exam measures skills of a Cloud Identity Manager and covers configuring advanced features like custom email addresses, release tracks, sandboxes, IP allowlisting, admin APIs, application tunnels, data residency, and understanding Atlassian Access integration for secure identity management and user provisioning.
Free Atlassian ACP-520 Exam Actual Questions
Note: Premium Questions for ACP-520 were last updated On May. 31, 2026 (see below)
Your company has a single Atlassian Cloud organization.
Atlassian Access discovered "shadow IT".
Which statement explains how this occurred?
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.
Automatic product discovery in Atlassian Access
Atlassian Access: Enhanced Cloud Data Security & Governance
What is a managed account?
Verify a domain to manage accounts
What is a product?
Understand Atlassian sites and organizations
What is an Atlassian organization?
Your Cloud organization has multiple products on multiple sites.
Currently, Edmund is a brand new user with no product access.
You selected Edmund from Directory > Users, clicked "Add products", and set the User product role from the Product roles dropdown for a single product on
a single site. For all other products, the Product roles dropdown was None.
Which is NOT a possible outcome for Edmund?
The only outcome that is not possible for Edmund is that he is granted org admin privileges. This is because org admin privileges are not related to product access or product roles, but to organization settings and management. To grant Edmund org admin privileges, you would need to go to Settings > Organization admins and add him there. The other outcomes are possible depending on the product access settings and the groups that Edmund belongs to.
Reference= [Give users access to products] and [Manage organization admins]
A secure pathway needs to be configured between a self-managed Jira Software instance and several Atlassian Cloud products.
Identify one configuration step that must be done in a self-managed instance.
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.
Reference=Configure required connections and upstream portsandCreate an application tunnel to your self-managed instance
Your company has a single Atlassian Cloud organization.
Atlassian Access discovered "shadow IT".
Which statement explains how this occurred?
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.
Automatic product discovery in Atlassian Access
Atlassian Access: Enhanced Cloud Data Security & Governance
What is a managed account?
Verify a domain to manage accounts
What is a product?
Understand Atlassian sites and organizations
What is an Atlassian organization?
A secure pathway needs to be configured between a self-managed Jira Software instance and several Atlassian Cloud products.
Identify one configuration step that must be done in a self-managed instance.
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.
Reference=Configure required connections and upstream portsandCreate an application tunnel to your self-managed instance
- Select Question Types you want
- Set your Desired Pass Percentage
- Allocate Time (Hours : Minutes)
- Create Multiple Practice tests with Limited Questions
- Customer Support
Eric Phillips
11 days agoThomas Thomas
24 days agoLinda Martinez
1 month agoHeather Smith
1 month agoStephen Taylor
26 days agoEric Rogers
21 days agoMelissa Brown
17 days agoLisa Brown
1 month agoKeneth
2 months agoQueen
2 months agoIsadora
2 months agoShaunna
3 months agoTrevor
3 months agoMoon
3 months agoRosio
3 months agoYuki
4 months agoEugene
4 months agoElin
4 months agoAngelo
4 months agoAngelo
5 months agoJacqueline
5 months agoDelsie
5 months agoCorinne
5 months agoDemetra
6 months agoHoa
6 months agoParis
6 months agoLeslie
6 months agoBeata
7 months agoShannan
7 months agoIra
7 months agoNorah
7 months agoLizbeth
8 months agoLorrie
8 months agoRaina
8 months agoCheryl
8 months agoSerita
8 months agoMelvin
8 months agoAdria
9 months agoPura
9 months agoCheryl
9 months agoVilma
11 months agoHobert
11 months agoLaticia
12 months agoXenia
12 months agoLavonda
1 year agoBasilia
1 year agoColette
1 year agoJudy
1 year agoChandra
1 year ago