Braindumps and Exam Dumps for ACP-520, Atlassian's Jira Project Management Certification

Generate a user API token is correct. Liam still has a regular user account so he can create personal API tokens that are tied to his own identity.

Generate a user API token is an operation that typically only requires an active user account and whatever permissions that account already has. Creating a token for personal use does not require organization administrator privileges because the token is associated with the individual user rather than the organization.

Create an organization API key is incorrect because creating organization level keys is an administrative task. Those actions normally require organization administrator rights or a similarly elevated role and cannot be performed by a regular user account.

Revoke an organization API key is incorrect because revoking or managing organizational keys is also an administrative responsibility. Without the organization administrator role Liam would not have the authority to revoke keys that belong to the organization.

Inspect user API token usage reports is incorrect because inspecting organization or usage reports is generally a privileged activity. Access to audit logs and organization level usage reports is controlled by roles that regular users do not have by default.

Do not allow invites is the correct option.

Choosing Do not allow invites prevents regular users from initiating invitations so only administrators with the appropriate organization or user access administration roles can create or invite new accounts. This setting is explicitly restrictive so it meets the requirement to block ordinary users while preserving admin capabilities.

Allow any user to invite others is incorrect because that option would let regular users send invitations and would not prevent them from creating new accounts.

Require administrator approval for requests is incorrect because that option still allows regular users to submit invitation requests and only controls approval. The question asks for a setting that prevents regular users from inviting in the first place.

The site includes at least one Confluence instance and The site contains at least two distinct products are correct.

The site includes at least one Confluence instance is supported because the URL contains the /wiki path which is the standard path used to serve Confluence content on Atlassian Cloud sites and therefore indicates a Confluence instance on that site.

The site contains at least two distinct products is supported because the site serves content at both /jira and /wiki paths and those distinct paths correspond to separate Atlassian products so the presence of both paths shows at least two products are hosted on the same site.

The site has at least two product administrators is incorrect because the number of administrators cannot be determined from public URLs. Administrative roles and counts are stored in site configuration and are not exposed by the product URLs.

The site exposes more than one landing page is incorrect because the given URLs show product entry points and not the site�s configured landing page. You cannot infer multiple landing pages from the presence of multiple product paths alone.

The site has at least one Jira Software product is incorrect because the /jira path only indicates a Jira product in general. The URLs do not reveal the specific Jira product type or edition so you cannot conclude it is specifically Jira Software.

Certain tickets are restricted by “Issue Level Security” and The viewer does not have the “Browse Projects” permission on some projects are correct.

Certain tickets are restricted by “Issue Level Security” hide issues from users who are not in the issue security level or who are not in roles allowed to see them. Boards only show issues the viewer is allowed to see and an issue that is protected by an issue security level will not appear on a board even when the board spans multiple projects.

The viewer does not have the “Browse Projects” permission on some projects prevents the user from seeing any issues in those projects. When a board includes several company managed projects any missing Browse Projects permission will make the issues from those projects invisible to that viewer and they will not show up on the board.

Some statuses are not mapped to the board columns correctly is incorrect because unmapped statuses normally cause issues to appear in an unmapped or backlog area rather than make them vanish for users who already have permission to view them. Status mapping affects placement on the board and not basic visibility for permitted users.

The board’s saved filter JQL excludes those tickets is incorrect in this question because although a saved filter can hide issues it is not the root cause indicated here. The scenario points to visibility controls across projects and permissions which is why issue security and Browse Projects permission are the correct causes.

A group can belong to only one organization is the correct statement.

Groups are typically created and managed within a single organizational boundary and their ownership and configuration are tied to that organization. You can add members from other domains or organizations, and you can grant access across organizations, but that does not make the group belong to more than one organization.

A default access group can be deleted is incorrect because default or system created groups are often protected from deletion to preserve baseline access controls and settings.

A group can be suspended if it has no members is incorrect because suspension usually applies to user accounts rather than to group objects, and having no members does not generally trigger a suspend action for a group.

A group can belong to multiple organizations is incorrect because a group resource is owned by and scoped to a single organization even though its membership can include principals from other organizations.

The correct answer is Ask the Confluence administrator to enable anonymous access for the specific space.

Enabling anonymous access for the specific space allows external clients to view pages without signing in and without needing site administrator approval for each visitor. A Confluence or space administrator can grant view only permissions to anonymous users at the space level so content remains read only while avoiding account creation.

Request the site admin to generate a shareable invitation link is incorrect because a shareable invite typically creates or requires user accounts and it depends on site admin actions rather than providing unauthenticated read only viewing.

Ask the site admin to set the “User invites” setting to “Invite anyone” for Jira Software is incorrect because this refers to Jira Software invite settings and it changes invitation policies rather than enabling unauthenticated, read only access to a Confluence space.

Ask the Confluence admin to create external read only accounts for the customers is incorrect because creating accounts is more administratively heavy and may affect licensing while anonymous space access provides a simpler read only option without provisioning accounts.

Page comments and Archived spaces are correct because these content types are included when cloning site content into a sandbox.

Page comments are part of page content and are exported with pages so they are preserved for testing and review in the sandbox copy.

Archived spaces can be included in a full site or space export so historical or archived content can be restored into the sandbox for validation and development work.

Private spaces are not automatically transferred because they often contain restricted data and require separate permission handling or targeted export steps to move safely.

Marketplace apps are not transferred as part of a content clone because apps are installed and licensed separately and usually need reinstallation or a dedicated migration process.

Collaborative whiteboards are typically live interactive artifacts that are not included in standard content exports and they often require a specialized export or separate migration tool to move.

The correct options are Issue Security Level, Saved Filter Subscription, and Dashboard Access.

A project role can be added to an Issue Security Level so that only members of the role can view issues protected by that security level. You assign roles when you configure the issue security scheme for a project and the role membership controls visibility.

Saved filters can be shared with a project role and you can set up subscriptions that effectively target a role so members receive the filter results. This is why Saved Filter Subscription can be assigned to project roles through filter sharing and subscription settings.

Dashboards support sharing by project role so granting a role access to a dashboard gives all members of that role the same view and gadget access. That is why Dashboard Access is assignable to project roles.

Application Permissions is incorrect because application permissions are global level permissions that grant capabilities across the Jira instance and they are granted to groups or global roles rather than to project roles.

Clara has a 10-day grace period to restore Omar’s account is the correct choice.

This statement is correct because the system retains recently disabled accounts for a limited retention window so administrators can restore them without data loss. The scenario specifies a ten day restoration window which makes this option the definitive choice.

Omar is no longer a billable user is not a safe conclusion because disabling an account does not automatically remove its license or billing status. Billing and seat assignment policies vary and an account can remain billable until its license is explicitly released or the user is deleted.

Omar is a managed account is not supported by the prompt because nothing in the scenario identifies the account type. Managed versus external identity is a separate attribute and cannot be inferred from the fact that the account was disabled.

Omar can no longer access the AtlasHub marketplace cannot be assumed because marketplace entitlements and sign in behavior may be controlled separately. The prompt does not provide enough detail to state marketplace access is definitively lost.

Clara is an organization administrator is not necessarily true because the ability to disable users can be granted to roles with varying scopes. The scenario does not prove she holds full organization administrator privileges.

The correct options are Maya can enable both Jira Software and Jira Work Management on the site, Maya can assign multiple site administrators, and Maya’s site must include at least one product.

Maya can enable both Jira Software and Jira Work Management on the site is correct because an Atlassian Cloud site can host multiple products at the same time and you can enable both Jira Software and Jira Work Management on a single site to serve different teams or use cases.

Maya can assign multiple site administrators is correct because site administration is a role that can be granted to more than one user so that responsibilities for user management and product access can be shared among team members.

Maya’s site must include at least one product is correct because a Cloud site is associated with products to provide functionality and you cannot have a functioning site without at least one product provisioned.

Maya can provision another site using the same site address maya-training.example.com is incorrect because site addresses are unique across Atlassian Cloud and you cannot create a second site using an address that is already taken.

Maya can create two separate Jira Software instances on the same site is incorrect because a site has products added to it rather than multiple independent instances of the same product and you would instead create multiple projects within the single Jira Software product on the site.

Verify a domain and Configure Atlassian Access are correct.

Verify a domain is an organization level action because it ties an email domain to the Atlassian organization and enables centralized controls such as SSO and user provisioning. Verifying a domain is performed at the organization level and affects all products and sites that belong to that organization.

Configure Atlassian Access is an organization level configuration because Atlassian Access provides enterprise features like single sign on, enforced security policies, and SCIM provisioning across multiple products. Enabling and configuring Access is done for the organization rather than from an individual product site on the Standard tier.

Manage product release tracks is incorrect because release track controls are handled at the product level by product administrators and are not an organization wide setting that a site admin would change for the organization.

Create a sandbox environment is incorrect because sandbox environments are offered at higher subscription tiers and through organization administration. Standard tier sites do not provide the ability to create a sandbox from site settings.

Set IP allowlists for product access is incorrect because IP allowlisting for access is typically managed through Atlassian Access or organization policies and may require the appropriate Access subscription and organization administrator privileges. A Standard site admin cannot set organization wide IP allowlists from the product site settings.

The correct options are Group members need the ability to perform bulk operations across many issues, Site administrator will control membership of the group, The same people will be assigned to multiple projects, and Permissions need to be granted at the global level.

Using a group makes sense when Group members need the ability to perform bulk operations across many issues because bulk change and similar mass actions are managed by permissions that are easiest to grant centrally to a group rather than to many individual accounts.

It is appropriate when Site administrator will control membership of the group because groups are typically managed at the site or user directory level and that central control avoids inconsistent membership across projects.

You should choose a group when The same people will be assigned to multiple projects because assigning permissions to a group removes the need to repeat the same assignments in each project and simplifies ongoing administration.

Groups are also the right mechanism when Permissions need to be granted at the global level since Jira uses groups for global permissions and those cannot be granted to project roles alone.

Team needs the Work On Issues permission to log time is incorrect because needing the Work On Issues permission for time logging does not by itself require a group. That permission can be granted to a project role or to individual users when finer grain control is desired.

Project administrator is expected to maintain group membership is incorrect because project administrators normally do not manage global groups. Group membership is usually handled by site admins or an external directory and expecting project admins to maintain groups is not the typical or recommended model.

The tunnel client application on the self managed instance cannot connect to the tunnel server in Atlassian Cloud is the correct option.

The tunnel client application on the self managed instance cannot connect to the tunnel server in Atlassian Cloud is the most likely cause because the Data Center nodes report an “Unavailable” status when they cannot establish the network tunnel to Atlassian Cloud. If the tunnel client cannot reach the cloud endpoint due to firewall rules proxy settings DNS failures or routing issues then the nodes will be unable to communicate and will show Unavailable.

At least one cluster node has not connected to the tunnel is incorrect because a single node failing to join the tunnel would normally show that node as offline or degraded rather than all Data Center nodes marked Unavailable. The symptom in the question points to a broader connectivity failure between the instance and the cloud tunnel server.

The tunnel client could reach the tunnel server but failed to validate the security key is incorrect because key validation failures produce explicit authentication errors or rejected connections in the logs. The described Unavailable status indicates the tunnel connection could not be established at the network level rather than an authentication rejection.

The reciprocal application link on the self managed instance was created by a different administrator is incorrect because who created the reciprocal application link does not affect whether the tunnel can be established. Administrative ownership or creator metadata does not cause nodes to become Unavailable and the root cause is connectivity between the tunnel client and the Atlassian Cloud server.

The correct option is Shareable Confluence invite link.

Shareable Confluence invite link lets regular users generate or send an invitation URL so recipients can join and receive the permissions granted on joining. This enables invited users to create pages and add comments according to the space or site permissions they inherit when they accept the invite without waiting for a site administrator to approve each invite.

Change site user invites policy to Invite anyone is incorrect because changing site or organization invite policies requires administrator privileges and it does not describe the user level, link based invitation flow the question asks for. Making a policy change is an admin action and is not the same as allowing individual users to send shareable invites.

Configure approved domain invites is incorrect because restricting or approving domains controls which email domains are allowed or automatically approved and it does not provide a mechanism for individual users to create a shareable invite link that lets invited users immediately create content and comment without admin approval.

The correct option is Invite anyone.

Selecting Invite anyone allows current users to send invitations without administrator approval and without domain restrictions. This setting matches Carlos goal of letting team members add new people freely and instantly.

Invite approved domains is incorrect because that choice limits invitations to specific email domains and would prevent users from inviting arbitrary external addresses.

Require admin approval is incorrect because that setting forces each invitation to be reviewed by an administrator and so does not allow free user invitations.

Do not allow invites is incorrect because it blocks users from sending any invitations and would stop adding new team members entirely.

The correct option is Release tracks.

Change the Release tracks setting because release tracks control how frequently feature updates and administrative notifications are delivered to users. Switching the release track to a scheduled or monthly cadence will move TaskFlow notifications to an approximately four week cycle and that is the configuration Ana needs to change.

Product updates is incorrect because that term usually describes the content of announcements and not the administrative setting that controls delivery cadence.

Identity providers is incorrect because identity providers manage authentication and single sign on and they do not determine when product notifications are released.

Manage subscription is incorrect because subscription management affects billing and tier level and does not control the update cadence, and Ana is already on the Premium tier.

Maya can access at least one product on the site and The site hosts Confluence and at least one other Jira product are correct.

The presence of the change site landing product dialog implies that Maya has at least one product available to select so she can choose a landing page for the site. The dialog would not present product choices if no products were accessible.

The fact that Confluence appears alongside a selectable Jira product means the site includes Confluence and at least one Jira product. The dialog shows product categories available to set as the landing page and that is why you can infer both Confluence and another Jira product are present.

The site contains only Confluence and no other Jira products is incorrect because the dialog indicates there is at least one additional Jira product available and not only Confluence.

The site specifically includes Jira Software and Jira Work Management is incorrect because the dialog does not list specific Jira product names unless they are shown. You can infer a Jira product exists but you cannot infer which exact Jira products are present.

The site includes Jira Service Management is incorrect because the presence of a Jira product in the landing dialog does not prove that Jira Service Management is the specific product on the site. The dialog only indicates that at least one Jira product is available.

The correct options are Project classification, Project web address, and Project overview.

Project classification is an optional metadata field used to group or label projects and it does not affect the project key or features. Jira administrators can set or leave this classification blank as needed.

Project web address is an optional URL field for linking external documentation or a project site and it is not required for project operation. It can be added or removed without changing the core project configuration.

Project overview refers to the project description or summary and is purely descriptive. It is optional metadata that helps users understand the project purpose and can be modified freely by administrators.

Component is not listed as an optional project field in the same sense because components are a separate project configuration used to organize issues rather than a simple descriptive field in the project details form.

Project name is a required identifier for a project. While an administrator can rename a project, the name itself is a core attribute and not considered an optional descriptive field.

Project type determines the project template and available features and is not a simple optional metadata field. Changing a project type is typically restricted or requires additional migration steps.

The correct options are Create an organization API key and Remove an organization API key.

Organization level API keys affect the entire account and shared resources so only account administrators are permitted to manage them. That is why Create an organization API key is limited to the account administrator and Remove an organization API key is also limited to the account administrator.

Use an API key inside a script is incorrect because using an API key is an action any user or service with a valid key can perform and it does not require account administrator privileges.

Revoke a user API token from a personal account is incorrect because personal tokens are typically managed by the individual user and do not require the account administrator to revoke them.

Generate a personal user API token is incorrect because creating a personal token is a user level operation and does not need administrator rights.

The correct statement is Only the account owner can change their personal account details.

Unmanaged user accounts are personal accounts that are not controlled by an organization administrator and only the individual owner can modify their profile and personal settings. Organization administrators do not have the ability to change those personal account details unless the account is converted to a managed account or brought under the organization.

They are counted as billable users is incorrect because billing and license counts apply to managed or licensed users within an organization. Unmanaged accounts are not counted as organizational billable users unless they are converted or explicitly licensed by the organization.

They must belong to a group is incorrect because unmanaged accounts do not have to be members of any organizational group. An unmanaged account exists independently and group membership is not a requirement for such an account.

The correct option is Two individual access requests one for Confluence and one for Jira Software.

This option is correct because access is granted at the product level and requests should be scoped to the specific product being accessed. Submitting separate requests for Confluence and for Jira Software lets each product owner review and approve access independently and keeps approvals and audit records clear.

One single access request covering Confluence and Jira Software is wrong because a single combined request would span two distinct products and product access is handled separately. A combined request would not follow the typical product level approval process.

A single request that spans products from multiple organizations is wrong because organizations are separate administrative boundaries. Requests cannot cross organization boundaries and each organization must manage its own access approvals.

One request that includes products from more than one site is wrong because sites represent separate deployment or administrative scopes. Access requests must respect site boundaries and be submitted per site when applicable.

One access request for Jira Software and Jira Work Management is wrong because those are managed as separate products or product spaces and each requires its own access handling. Combining them in one request would bypass the separate approval flows that owners use for each product.

The production workspace is on a Standard subscription which does not include sandbox environments is correct.

This is because the Standard subscription which does not include sandbox environments does not include sandbox support. The subscription tier determines which features are available and a Standard subscription commonly excludes sandbox environments so administrators must upgrade to a plan that includes sandboxes before provisioning one.

A sandbox is already linked to the production workspace is incorrect because the scenario describes an inability to provision a sandbox due to plan limitations rather than an existing linked sandbox. If a sandbox were already linked the administrator would normally see that existing relationship or a distinct message stating only one sandbox is allowed.

The administrator does not have the necessary organization permissions to create a sandbox is incorrect because the question specifies Marco is an organization administrator. An organization administrator typically has the required permissions so the limitation is more likely caused by the subscription level.

Paid marketplace apps on the production workspace are blocking sandbox creation is incorrect because paid marketplace apps generally do not prevent creating a sandbox. Feature availability is controlled by the subscription or plan and not by installed marketplace applications.

Display name and Email address are the fields Mateo can recommend she modify.

The Display name is a personal profile field that users can edit in their Google Account or profile settings so she can change how her name appears to others. The Email address is part of her contact information and can be updated where account settings allow users to manage their contact addresses.

Department is usually an organizational directory attribute that is managed by an administrator and not something an unmanaged user can reliably change.

Avatar image is not the focus of this question and may be handled through account picture settings rather than the directory fields referenced here, so it is not one of the recommended profile fields in this scenario.

Job title is another directory attribute that is commonly set by administrators and is not typically edited by an unmanaged account holder.

The site creator can pick up to 2 Atlassian products during setup is the correct option.

When you create a new Atlassian Cloud site the setup flow lets the creator choose a small set of products to start with and the UI limits the initial selection to up to two products so teams can get started quickly. You can always add more Atlassian products and apps later from the site administration console once the site is created.

Billing or payment details must be provided when creating the site is incorrect because creating a Cloud site can be done without entering payment information. You can start with free tiers or trials and add billing information later when you upgrade or subscribe to paid plans.

A credit card number is required to complete the site creation is incorrect for the same reason. A credit card is not required to create the site and is only needed if you choose to subscribe to a paid plan or add paid products immediately.

The account used to create the site must be a verified organizational domain is incorrect because domain verification is an organization level step used for managing and proving ownership of domains. It is not a prerequisite for creating an individual Cloud site with a standard Atlassian account.

Only a corporate email address may be used to register the site is incorrect because Atlassian allows accounts with personal or corporate email addresses to create sites. Corporate emails may be required for some managed organization features but they are not mandatory to register a site.

The correct answers are Select List (single choice) and Radio Button.

The Select List (single choice) and the Radio Button are single-value fields so a user can pick only one option. Both field types support a default value so you can preselect an option. These custom field types are created as shareable fields so they can be used across all projects and they support field contexts so you can define different sets of options per project.

Checkbox is incorrect because checkbox fields allow multiple selections and do not enforce a single choice.

Labels is incorrect because labels are freeform tags rather than a controlled set of selectable options and they do not provide a reliable default value or per-project option lists in the same way option-based fields do.

Components is incorrect because components are managed at the project level and are not intended to be a globally shareable, single-choice, option list across all projects.