Atlassian ACP-620 Jira Projects Certification Sample Questions

A software company called NimbusWorks uses TrackMate Cloud for team collaboration. Which statements about TrackMate Cloud billing are accurate? (Choose 2)

• ❏ A. Only organization administrators and site administrators can modify the subscription plan

• ❏ B. Users who are added to a product count toward billing even if they never accept the invitation or sign in

• ❏ C. Changing from monthly to annual billing automatically upgrades your subscription to a Premium tier

• ❏ D. You cannot switch to a Free tier while your subscription is billed annually

Aisha manages Jira Software for her team at a mid sized fintech and she needs to change a Jira global permission for the team. Which product role should Aisha request so she can modify the global permission without being granted unnecessary rights?

• ❏ A. User access admin for Jira Software

• ❏ B. Product admin for Jira Software

• ❏ C. Product admin for Jira Administration

• ❏ D. User for Jira Software

• ❏ E. Jira system administrator

Leah needs her Kanban board to show only content marketing issues by component without having to toggle any board buttons and she also wants the Pie Chart report to continue showing the full dataset unchanged. Which feature will let her accomplish this?

• ❏ A. Quick filters

• ❏ B. Issue detail view

• ❏ C. Board sub filter

• ❏ D. Board filter

• ❏ E. Swimlanes

• ❏ F. Hide completed issues

Omar removed Maia’s managed account on AtlasCloud yet she still has access to several products. Which of the following products will require AtlasCloud support to remove the user account? (Choose 2)

• ❏ A. Trello

• ❏ B. Bitbucket

• ❏ C. Jira Align

• ❏ D. Halp

• ❏ E. Opsgenie

• ❏ F. Atlassian Access

Which details should you confirm before purchasing an Enterprise subscription? (Choose 2)

• ❏ A. Enterprise plans require a minimum seat commitment

• ❏ B. Enterprise subscriptions convert related products to annual billing

• ❏ C. Enterprise subscriptions can be billed monthly or annually

• ❏ D. Enterprise plans bundle centralized access and are billed together

Liam recently lost his organization administrator role at Redwood Labs while he still has a regular user account. Which of the following actions can Liam still carry out?

• ❏ A. Create an organization API key

• ❏ B. Generate a user API token

• ❏ C. Revoke an organization API key

• ❏ D. Inspect user API token usage reports

At Brightline Technologies only organization administrators and user access administrators should be allowed to invite new user accounts. Which product invitation permission setting is appropriate for this requirement?

• ❏ A. Allow invites only from approved domains

• ❏ B. Allow any user to invite others

• ❏ C. Do not allow invites

• ❏ D. Require administrator approval for requests

Maya manages a single Atlassian site for her team and it is reachable at https://devteam.scrumtuous.com/jira and https://devteam.scrumtuous.com/wiki Which of the following statements are correct? (Choose 2)

• ❏ A. The site has at least two product administrators

• ❏ B. The site includes at least one Confluence instance

• ❏ C. The site exposes more than one landing page

• ❏ D. The site contains at least two distinct products

• ❏ E. The site has at least one Jira Software product

Maya is creating a new Kanban board that spans several company-managed projects for Orion Tech and notices some tickets do not appear on the board. What are possible reasons those tickets are missing? (Choose 2)

• ❏ A. Some statuses are not mapped to the board columns correctly

• ❏ B. Certain tickets are restricted by “Issue Level Security”

• ❏ C. The board’s saved filter JQL excludes those tickets

• ❏ D. The viewer does not have the “Browse Projects” permission on some projects

Which of the following statements is definitely true about a user group in an organization?

• ❏ A. A default access group can be deleted

• ❏ B. A group can belong to only one organization

• ❏ C. A group can belong to multiple organizations

All exam questions come from my Jira ACP-620 Udemy course and certificationexam.pro

A documentation owner at HarborDocs wants to let external clients view a Confluence page without requiring site administrator approval. What should they request to enable read only access?

• ❏ A. Request the site admin to generate a shareable invitation link

• ❏ B. Ask the Confluence administrator to enable anonymous access for the specific space

• ❏ C. Ask the site admin to set the “User invites” setting to “Invite anyone” for Jira Software

• ❏ D. Ask the Confluence admin to create external read only accounts for the customers

Lina needs to clone her WikiSpace Cloud production site content into a sandbox for testing and development. Which of the following types of data can she transfer? (Choose 2)

• ❏ A. Private spaces

• ❏ B. Page comments

• ❏ C. Marketplace apps

• ❏ D. Archived spaces

• ❏ E. Collaborative whiteboards

At a technology firm using Jira Cloud what items can be assigned to project roles within a single project? (Choose 3)

• ❏ A. Application Permissions

• ❏ B. Dashboard Access

• ❏ C. Site-wide Permission

• ❏ D. Saved Filter Subscription

• ❏ E. Group Membership

• ❏ F. Issue Visibility Level

While disabling dormant user accounts at Cygnus Tech, Clara accidentally disabled Omar’s account. Which of the following statements is definitely false?

• ❏ A. Omar is no longer a billable user

• ❏ B. Clara has a 10-day grace period to restore Omar’s account

• ❏ C. Omar is a managed account

• ❏ D. Omar can no longer access the AtlasHub marketplace

• ❏ E. Clara is an organization administrator

Which of the following statements about an Atlassian Cloud site are true? (Choose 3)

• ❏ A. Assign multiple site administrators

• ❏ B. Run two instances of the same product on one site

• ❏ C. Can enable Jira Software and Jira Work Management on the same site

• ❏ D. Site must include at least one product

Maya administers a site that runs Jira Software and Confluence on the Standard tier and she needs to update organization level settings. Which site level configurations can she change? (Choose 2)

• ❏ A. Manage product release tracks

• ❏ B. Create a sandbox environment

• ❏ C. Verify a domain

• ❏ D. Set IP allowlists for product access

• ❏ E. Configure Atlassian Access

Which situations are appropriate for using a Jira group instead of assigning permissions to individual users or project roles? (Choose 4)

• ❏ A. Group members need the ability to perform bulk operations across many issues

• ❏ B. Team needs the Work On Issues permission to log time

• ❏ C. Site administrator will control membership of the group

• ❏ D. The same people will be assigned to multiple projects

• ❏ E. Project administrator is expected to maintain group membership

• ❏ F. Permissions need to be granted at the global level

Marco at BluePeak Technologies configured an application tunnel but his Data Center nodes report an “Unavailable” status. What is the most likely cause of this condition?

• ❏ A. At least one cluster node has not connected to the tunnel

• ❏ B. The tunnel client could reach the tunnel server but failed to validate the security key

• ❏ C. The tunnel client application on the self managed instance cannot connect to the tunnel server in Atlassian Cloud

• ❏ D. The reciprocal application link on the self managed instance was created by a different administrator

Ethan from HarborDocs wants to invite new team members to his Confluence site without waiting for the site administrator to approve them and the invited users must be able to create pages and add comments. What should he request the administrators to do?

• ❏ A. Ask the site administrator to create a shareable Confluence invite link

• ❏ B. Ask the Confluence administrator to enable anonymous viewing of public spaces

• ❏ C. Ask the site admin to change the site ‘User invites’ policy to ‘Invite anyone’ for Confluence

• ❏ D. Request that the site admin configure an approved domain invite for Confluence

Which invitation permission permits existing users to invite any email address without needing administrator approval?

• ❏ A. Restrict invites to admins

• ❏ B. Invite anyone

• ❏ C. Invite approved domains

Ana needs TaskFlow notifications delivered every four weeks and she is already on the Premium tier. Which configuration does she need to change to switch the update cadence to a monthly schedule?

• ❏ A. Product updates

• ❏ B. Identity providers

• ❏ C. Manage subscription

• ❏ D. Release tracks

In the Change site landing product dialog Maya can select which product appears as the site landing page. What can be inferred about the products present on her cloud site? (Choose 2)

• ❏ A. Maya can access at least one product on the site

• ❏ B. The site hosts Confluence and at least one other Jira product

• ❏ C. The site contains only Confluence and no other Jira products

• ❏ D. The site specifically includes Jira Software and Jira Work Management

• ❏ E. The site includes Jira Service Management

A departmental reshuffle at BeaconSoft requires Maya to update her Jira project settings. As a Jira administrator which project fields are optional for Maya to modify? (Choose 3)

• ❏ A. Project classification

• ❏ B. Component

• ❏ C. Project name

• ❏ D. Project web address

• ❏ E. Project type

• ❏ F. Project overview

Which actions are limited to the account administrator for Bluewave Solutions? (Choose 2)

• ❏ A. Remove an organization API key

• ❏ B. Use an API key inside a script

• ❏ C. Create an organization API key

• ❏ D. Revoke a user API token from a personal account

• ❏ E. Generate a personal user API token

Which of the following statements regarding unmanaged user accounts is always true?

• ❏ A. They are counted as billable users

• ❏ B. Only the account owner can change their personal account details

• ❏ C. They must belong to a group

Asha recently joined a product team and needs access to resources that Miguel owns. Which of the following request patterns complies with the access model and organizational structure?

• ❏ A. One single access request covering Confluence and Jira Software

• ❏ B. A single request that spans products from multiple organizations

• ❏ C. Two individual access requests one for Confluence and one for Jira Software

• ❏ D. One request that includes products from more than one site

• ❏ E. One access request for Jira Software and Jira Work Management

As an organization administrator Marco cannot provision a new sandbox for his production workspace. What is the most likely reason for this limitation?

• ❏ A. A sandbox is already linked to the production workspace

• ❏ B. The production workspace is on a Standard subscription which does not include sandbox environments

• ❏ C. The administrator does not have the necessary organization permissions to create a sandbox

• ❏ D. Paid marketplace apps on the production workspace are blocking sandbox creation

Sofia is signed in with an unmanaged account and Mateo wants to ask her to update her profile details. Which profile fields can Mateo recommend she modify? (Choose 2)

• ❏ A. Department

• ❏ B. Display name

• ❏ C. Avatar image

• ❏ D. Job title

• ❏ E. Email address

After a department reshuffle, Alex must set up a new workspace for his group. Which of the following statements is accurate when establishing a new site on Atlassian Cloud?

• ❏ A. Billing or payment details must be provided when creating the site

• ❏ B. The site creator can pick up to 2 Atlassian products during setup

• ❏ C. A credit card number is required to complete the site creation

• ❏ D. The account used to create the site must be a verified organizational domain

• ❏ E. Only a corporate email address may be used to register the site

Which Jira custom field type can be shared across projects, allows a single selection with a default value, and supports project specific option sets? (Choose 2)

• ❏ A. Select List (single choice)

• ❏ B. Checkbox

• ❏ C. Radio Buttons

All exam questions come from my Jira ACP-620 Udemy course and certificationexam.pro

Which statement about managed user accounts in a cloud organization is always true?

• ❏ A. The account belongs to one or more groups

• ❏ B. An organization administrator can alter the managed account

• ❏ C. The organization has confirmed ownership of the user’s email domain

• ❏ D. The user has validated their email address

Marisol runs an organization that contains six separate sites and each site operates its own Jira Software instance. Which statement must always be true?

• ❏ A. Each site uses identical default user groups

• ❏ B. All sites share the same organization administrators

• ❏ C. Every site is linked to a single shared sandbox environment

• ❏ D. All sites are managed by the same Jira product administrators

A developer named Maya at Nimbus Software needs to connect her self-managed Atlassian instance through an application tunnel. What should she do first?

• ❏ A. Configure an upstream port and add an HTTP connector

• ❏ B. Create a tunneled application link to the self-hosted instance

• ❏ C. Install the Application Tunnels app from the Atlassian Marketplace

• ❏ D. Install the security key on the target server

Alex must add a new product role in a Jira Cloud environment and then set a default group for that role. Which administrative privilege should Alex request?

• ❏ A. Project Administrator

• ❏ B. Site Administrator

• ❏ C. Jira Software user role

• ❏ D. Jira Administrator product admin role

Which actions can a Jira Cloud organization administrator perform within the organization settings? (Choose 3)

• ❏ A. Manage site billing

• ❏ B. Approve pending user access requests

• ❏ C. Verify the company domain

• ❏ D. Create and manage directory groups

The correct options are Users who are added to a product count toward billing even if they never accept the invitation or sign in and You cannot switch to a Free tier while your subscription is billed annually.

With Users who are added to a product count toward billing even if they never accept the invitation or sign in TrackMate bills based on provisioned seats rather than activated accounts. This means an invited user still consumes a billable seat even if they never accept or sign in and administrators should remove unused invitations to avoid unnecessary charges.

You cannot switch to a Free tier while your subscription is billed annually reflects an annual commitment to the vendor. Annual billing typically locks the subscription for the paid term so you cannot immediately downgrade to a free plan until the annual period ends or you negotiate a billing change with the vendor.

Only organization administrators and site administrators can modify the subscription plan is incorrect because subscription and billing changes are normally tied to specific billing owners or subscription managers and not strictly limited to those two admin roles.

Changing from monthly to annual billing automatically upgrades your subscription to a Premium tier is incorrect because changing billing cadence affects payment frequency and often per seat pricing but does not by itself change the feature tier. Upgrading tiers normally requires an explicit plan change.

When answering billing questions pay attention to whether seats are counted when users are added or when they accept and watch for wording that implies an annual commitment which can prevent immediate downgrades.

Product admin for Jira Administration is correct.

Product admin for Jira Administration gives the product administration rights needed to modify Jira global permission schemes without granting full system or site level privileges. This role lets Aisha manage product settings and global permissions while keeping permissions limited to what is required.

User access admin for Jira Software is focused on provisioning and managing user access across products and it does not grant the in-product global permission changes inside Jira.

Product admin for Jira Software administers the Jira Software product features but it is distinct from the Jira Administration product role and usually cannot change the global permission schemes that belong to Jira Administration.

User for Jira Software is a regular user role and it does not include administrative capabilities to modify global permissions.

Jira system administrator would be able to change global permissions but it grants far broader system level rights than necessary so it is not the minimal privilege Aisha should request.

Least privilege matters in role selection. For questions about changing product settings choose the product administration role that matches the administration domain rather than a full system administrator.

The correct option is Board sub filter.

The Board sub filter allows Leah to apply additional JQL that limits what appears on the Kanban board without changing the board’s primary filter. This means the board view can be restricted to component = “Content Marketing” for all users while the main filter remains intact and the Pie Chart report continues to show the full dataset.

Quick filters are wrong because they require users to toggle buttons to apply the filter and they do not persist a global board view for all users.

Issue detail view is wrong because it only displays details for a selected issue in a side panel and it does not filter or change which issues appear on the board.

Board filter is wrong because changing the main filter alters the board’s underlying saved filter and that change will also affect reports and gadgets such as the Pie Chart.

Swimlanes are wrong because they only group or partition issues on the board and they do not remove non matching issues from the board or change the dataset used by reports.

Hide completed issues is wrong because it only hides issues in completed statuses and it does not filter by component or preserve the full dataset used by the Pie Chart.

When a question asks for a board specific view that must not affect reports look for a feature that applies only to the board. The sub filter in board settings is the common choice for that scenario.

Jira Align and Halp are correct.

Jira Align requires AtlasCloud support to remove the user account because Jira Align keeps user records in its own system and managed account unlinking must be handled by the product support team rather than through the standard AtlasCloud managed account UI.

Halp also requires AtlasCloud support to remove the user account because Halp’s provisioning and integrations are handled separately and removal of managed accounts is processed through support.

Trello is incorrect because Trello user access can be removed by organization administrators or through normal provisioning flows and does not generally require contacting AtlasCloud support.

Bitbucket is incorrect because Bitbucket Cloud accounts can be managed and deactivated by product or organization admins and via Atlassian Access provisioning without needing support intervention.

Opsgenie is incorrect because Opsgenie supports user management through its admin console or federated provisioning so support is not typically required to remove a managed account.

Atlassian Access is incorrect because Atlassian Access is the identity and access management layer and user removal or unlinking is handled through its controls rather than by opening a support ticket.

Check whether the product maintains its own user directory or requires support for account unlinking before selecting answers on managed account removal.

Enterprise subscriptions convert related products to annual billing and Enterprise plans bundle centralized access and are billed together are correct.

Enterprise subscriptions convert related products to annual billing means that moving to an enterprise subscription often changes the billing cadence of associated products to an annual contract, so buyers should confirm the annual commitment and how it affects costs before purchasing.

Enterprise plans bundle centralized access and are billed together means that multiple products or seats are frequently managed under a single enterprise agreement and invoiced as a consolidated bill, which impacts budget planning and who is charged.

Enterprise plans require a minimum seat commitment is incorrect because minimum seat requirements are not an inherent rule for all enterprise plans and they vary by vendor and specific agreement.

Enterprise subscriptions can be billed monthly or annually is incorrect in this context because the correct option specifies conversion to annual billing and the question concerns verifying whether enterprise subscriptions force annual billing rather than offering monthly billing as an option.

Before you buy verify the billing cadence and which products are bundled so you understand any annual commitments and how charges will be consolidated.

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.

When a question contrasts organization and user abilities focus on the scope of the action. Organization keys and reports are org scoped and usually need admin roles while personal tokens are user scoped and can be created by the account owner.

The correct option is Do not allow invites.

Choosing Do not allow invites prevents non administrators from creating or inviting new accounts so only organization administrators and user access administrators can provision users through the admin console or through approved provisioning workflows. This setting enforces strict control over account creation and removes self service invitation paths that would allow unauthorized users to add accounts.

Allow invites only from approved domains is incorrect because it still permits users to invite others as long as the email domain matches an allowed list. That does not meet the requirement to restrict invitations only to administrators.

Allow any user to invite others is incorrect because it explicitly allows all users to invite new accounts which is the opposite of the desired restriction.

Require administrator approval for requests is incorrect because it allows users to request invitations and relies on an approval workflow. Requests still originate from non administrators so this does not satisfy the requirement that only administrators should be able to invite new accounts.

When a question asks for only administrators to perform an action look for settings that completely disable user initiated flows rather than settings that limit or gate them with approval.

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.

When you evaluate URLs look for product-specific path segments such as /wiki for Confluence and remember that URLs usually show which products are present but they do not reveal administrator counts or product editions.

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.

When issues are missing from a multi project board first check the board filter and then verify project permissions and issue security levels because visibility problems are often caused by permissions or security schemes rather than column mappings.

A group can belong to only one organization is correct.

Groups are created and managed within a single Cloud Identity or Workspace account and their membership and policies are tied to that organization’s directory. Because of that a group cannot be owned by or natively shared across multiple separate organizations at the same time.

A default access group can be deleted is incorrect because default or system groups are typically managed by the directory service and have restrictions that prevent them from being removed like normal user created groups. The statement assumes a deletable default group which is not generally true.

A group can belong to multiple organizations is incorrect because groups are scoped to the organization that created them and are not designed to be members of multiple organizations simultaneously.

When you see identity and access questions focus on the scope of the resource and who owns it. For groups the creating organization usually defines that scope and that will tell you whether cross organization membership is allowed.

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.

When a question asks about letting external users view content without accounts focus on anonymous access and space permissions and check whether the change can be made at the space level rather than requiring site admin invites.

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.

When you decide what to clone remember to separate exported content from installed apps and check permissions and licensing for private or third party items before starting the transfer.

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

Dashboard Access is correct because dashboards can be shared with project roles so that everyone assigned to a role in that single project can view the dashboard that has been shared with that role.

Saved Filter Subscription is correct because filter subscriptions and saved filters can be shared or subscribed to by project roles so members of the role receive the scheduled filter results or can use the shared filter within the project.

Issue Visibility Level is correct because issue security schemes allow you to set security levels that can include project roles so role members see issues restricted by those visibility levels.

Application Permissions is incorrect because application permissions are managed at the application or site level and are not items you share with project roles inside a single project.

Site-wide Permission is incorrect because site-wide permissions apply across the whole Jira site and are not configurable as a per-project share target for project roles.

Group Membership is incorrect in this context because group membership is a user directory concept and is not an item you assign to project roles as a shareable resource even though you can add groups into a role, the option listed refers to group membership itself which is not a shareable item for a project role.

When deciding what can be assigned to project roles think about what can be used as a share target or included in an issue security level rather than about global or application level permissions.

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.

Focus on what the question definitely states and be wary of choices that require unstated assumptions. If a choice depends on details not in the stem it is unlikely to be the correct answer.

The correct answers are Assign multiple site administrators, Can enable Jira Software and Jira Work Management on the same site, and Site must include at least one product.

Assign multiple site administrators is correct because an Atlassian Cloud site supports more than one site administrator so organizations can share administrative duties and maintain continuity if an individual is unavailable.

Can enable Jira Software and Jira Work Management on the same site is correct because a single site can host multiple products and the Jira products can be enabled together so teams can use the different project templates and features within the same site and user directory.

Site must include at least one product is correct because a site is a container for products and a site without any products does not meet the platform model for Atlassian Cloud.

Run two instances of the same product on one site is incorrect because you cannot create two separate independent instances of the same cloud product within a single Atlassian Cloud site. You can create multiple projects or configurations but not duplicate isolated instances of the same product on one site.

When a question refers to an Atlassian Cloud site think of the site as a container for products and administration. Remember that sites can host multiple products and multiple admins but they cannot host two separate instances of the same cloud product.

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.

When a question asks about organization level settings think about whether the action requires an organization administrator or an Atlassian Access subscription rather than a product site admin.

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.

When a scenario mentions many projects or global permissions favor groups. If the question emphasizes per project control or that project admins will change membership then consider project roles instead.

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.

When you see an Unavailable status start by checking network connectivity and firewall rules and then review the tunnel client logs for errors.

The correct answer is Ask the site administrator to create a shareable Confluence invite link.

Ask the site administrator to create a shareable Confluence invite link lets the site administrator generate a join link that prospective team members can use to sign up without waiting for per user approval. The administrator can attach Confluence product access and appropriate permissions to those who join so the invited users can create pages and add comments.

Ask the Confluence administrator to enable anonymous viewing of public spaces is incorrect because anonymous viewing only allows read access and does not permit creating pages or adding comments. That option does not meet the requirement for invited users to have authoring and commenting rights.

Ask the site admin to change the site ‘User invites’ policy to ‘Invite anyone’ for Confluence is incorrect because that policy change governs who can send invites or which users may be invited and not a mechanism to let users join immediately with assigned Confluence access. It does not by itself provide a sign up link that grants the needed product permissions.

Request that the site admin configure an approved domain invite for Confluence is incorrect because allowing an approved domain controls sign ups by email domain and usually requires organization domain management. It does not directly provide a public shareable link for immediate sign up with preset authoring and commenting permissions.

Shareable invite links are the likely answer when you need users to join without per user approval. Always check whether the option grants create and comment rights rather than only view rights.

The correct option is Invite anyone.

The Invite anyone setting allows existing users to send invitations to any email address without administrator approval. When this option is enabled users can invite external addresses or create guest accounts directly and the flow does not require an admin to approve each invite.

Restrict invites to admins is incorrect because that option limits invitations so only administrators can invite new users or approve invites. It is the opposite of allowing any user to invite arbitrary email addresses.

Invite approved domains is incorrect because that setting confines invitations to a list of allowed domains. It does not permit invites to any email address outside the approved domains.

Read the option wording carefully and notice whether it permits anyone or imposes limits. Terms like restrict or approved domains indicate controlled invitations rather than unrestricted invites.

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.

When a question asks about how often users receive features or notifications look for settings named release tracks or release channels rather than billing, identity, or generic product announcement pages.

All exam questions come from my Jira ACP-620 Udemy course and certificationexam.pro

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.

When an interface shows choices infer only what is directly presented. If a product category or option is available then that product is present but do not assume specific product names unless they are explicitly shown. Presence does not equal identity.

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.

Focus on whether a field is descriptive metadata or a core identifier. Descriptive metadata like classification, web address, and overview are more likely to be optional while names and types are core.

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.

When deciding which actions are admin only focus on whether the action affects organization wide credentials or settings. Create and Remove of organization API keys are common admin responsibilities.

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.

When you see questions about managed or unmanaged accounts identify who controls the account settings. Pay attention to words like owner and managed because they indicate who can change settings and who is responsible for billing.

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.

When a question mentions multiple products or multiple sites prefer answers that respect per product and per site boundaries. Think about who needs to approve access and where audit trails will be kept.

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.

When you see a choice that mentions a specific subscription or edition remember that feature access is often gated by the plan. First check the edition or subscription level before assuming permissions or other factors are the cause.

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.

When a question mentions an unmanaged account think about which fields users control in their personal Google Account and which fields are set by an administrator in the directory.

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.

When answering setup questions focus on the initial user flow in the documentation and remember that creating a Cloud site usually does not require entering payment details and that you can choose up to two products during the first setup.

All exam questions come from my Jira ACP-620 Udemy course and certificationexam.pro

The correct options are Select List (single choice) and Radio Buttons.

A Select List (single choice) is a single selection custom field that supports field contexts so you can define different option sets per project and also set a default value for each context. This makes the field shareable across projects while still allowing project specific option lists and defaults.

A Radio Buttons field is also a single selection type and it supports contexts and default values in the same way, so it likewise meets the requirement for being shareable and for allowing project specific option sets with a default.

An Checkbox field is designed for multiple selections so it does not meet the single selection requirement. Even though it may support contexts, it cannot be restricted to a single choice and is therefore not correct.

When you see a question about single selection and project specific option sets think about whether the field type supports field contexts and default values and then pick a single choice type.

The organization has confirmed ownership of the user’s email domain is the correct statement about managed user accounts in a cloud organization.

The organization has confirmed ownership of the user’s email domain is true because a managed account is tied to the organization having verified and claimed the email domain. Domain verification is the system level action that allows the organization to provision and assert management over accounts that use that domain.

The account belongs to one or more groups is not always true because group membership is optional and a user can exist without being assigned to any groups in the organization.

An organization administrator can alter the managed account is not always true because the ability to modify an account depends on the identity setup and the administrator’s directory role. If identities are controlled by an external provider or the admin lacks the right permissions then the admin may not be able to change the account.

The user has validated their email address is not always true because managed status is based on domain ownership rather than on whether the individual user has completed an email validation or acceptance step. Users may still need to finish setup but that is not guaranteed for every managed account.

When a question asks what is always true focus on system level requirements rather than optional behaviors. For managed accounts look for answers about domain verification because that is the defining requirement.

The correct answer is All sites share the same organization administrators.

All sites share the same organization administrators because Atlassian organizations provide centralized administration and the organization administrators role spans every site in that organization. The organization administrators can manage users and organization settings and they have visibility across all sites that belong to the same organization.

Each site uses identical default user groups is incorrect because sites can have different group and permission configurations. Default groups are not enforced to be identical across separate site instances and site level settings can diverge.

Every site is linked to a single shared sandbox environment is incorrect because sandboxes are provisioned and scoped by product and by site. Sandboxes are not inherently a single shared environment across multiple sites and availability depends on the product plan and configuration.

All sites are managed by the same Jira product administrators is incorrect because product administrator roles are assigned per site and per product. Different sites can therefore have different Jira product administrators even when they belong to the same organization.

When a question asks about scope think about whether the role is at the organization level or at the site or product level. Organization level roles apply across all sites while site or product roles apply only to that site.

Install the Application Tunnels app from the Atlassian Marketplace is the correct first step to connect a self-managed Atlassian instance through an application tunnel.

You must install the Application Tunnels app from the Atlassian Marketplace so that the tunnel components and connectors are available. The app provides the tooling and workflows that create and manage the secure tunnel and it is installed before you configure links, ports, or keys on the target server.

Configure an upstream port and add an HTTP connector is not the first step because those network and connector settings are configured after the tunneling app or agent is installed and the tunnel framework is in place. You do not begin by manually opening upstream ports before installing the tunnel software.

Create a tunneled application link to the self-hosted instance is incorrect as the initial action because creating the tunneled link depends on the Application Tunnels app being present and configured first. The application link is created once the tunnel endpoint and permissions are established.

Install the security key on the target server is not the right first action because security keys or certificates are usually part of the installation or later configuration steps for the tunnel. The required app must be installed first so the correct key generation or installation process can be followed.

When a question asks what to do first look for installing a required app or agent before making network or configuration changes. Installing the Application Tunnels app is typically the initial step.

The correct option is Jira Administrator product admin role.

Jira Administrator product admin role grants the product level administration needed to create and manage product roles and to set a default group for a role in a Jira Cloud product. This role gives the necessary access to Jira product settings where role definitions and default group assignments are configured so Alex can add a new product role and assign its default group.

Project Administrator is incorrect because a project administrator only manages settings within a single project and does not have the global product level permissions required to create new product roles or set role default groups across the Jira product.

Site Administrator is incorrect because site administration covers site wide tasks such as billing and user provisioning and does not automatically grant the Jira product administration rights needed to manage product roles unless the person is also granted the Jira product admin role.

Jira Software user role is incorrect because that role only provides access to use Jira Software and it does not include administrative privileges to create product roles or change default group assignments.

When a task involves creating or managing roles and default groups think product level administration rather than project level. Request the Jira Administrator product admin role when you need to manage Jira product roles and their default group assignments.

The correct options are Approve pending user access requests, Verify the company domain, and Create and manage directory groups.

Approve pending user access requests is correct because organization admins handle user access at the organization level and can review and approve requests for users to join sites and products. This lets the organization control who receives access to managed Atlassian products.

Verify the company domain is correct because organization admins must verify ownership of an email domain to claim and manage accounts for users and to enforce centralized identity controls. Domain verification is required to establish managed accounts and apply organization level policies.

Create and manage directory groups is correct because organization admins maintain the organization directory and can create groups to simplify provisioning and permission management across sites and products. Groups make it easier to assign access consistently at the organization level.

Manage site billing is incorrect because billing and subscription management are handled by site level billing or subscription owners rather than by organization admins. Organization admins focus on user, domain, and directory management rather than on managing site billing.

Focus on the scope of each role and ask whether the action is about user and identity management or about billing and subscriptions when you choose your answers.