Managing Jira Service Projects for Cloud Free Sample Questions
Description
Covers managing users, roles and permissions, queue and SLA configuration, assets and service management features, request types, the customer portal, knowledge base, reporting, and automation.
12 free sample questions135 in the full practice test
Distinguish Among Users, Project Roles, and Permissions · Define External Users and Roles
A financial services organization uses Jira Service Management to handle requests from external vendors. A vendor submits a complex procurement request. The vendor's external legal counsel needs to view this specific ticket and receive email updates, but the counsel should not be added to the vendor's Organization group in JSM, as they are not authorized to view other tickets from that vendor. Which role is most appropriate for the legal counsel in this scenario?
Answer and explanation
Correct answer: B
A Request Participant is an external user who is added to a specific ticket. They can view the ticket, receive notifications, and add comments, but this access is strictly limited to that single request. Adding them to an Organization would give them visibility into all requests shared with that Organization. Collaborator is an internal role, and Customer is the base role (the reporter is a customer).
Q2Question 2
AdvancedMultiple answers
Distinguish Among Users, Project Roles, and Permissions · Manage Customers and Organizations
To optimize the B2B support experience, you are configuring a new JSM project for enterprise clients. The business requirement states that anyone from specific approved client email domains (e.g., @clientA.com, @clientB.com) should be able to email the service desk and have an account automatically created. However, the customer portal itself should not have a public 'Sign up' button, preventing random internet users from creating accounts. Which TWO global and project-level settings must be combined to achieve this? (Select TWO)
Answer and explanation
Correct answers: A, B
To allow automatic account creation via email for specific domains, the global setting must allow open access (Anyone can email...), while the project-level setting restricts it to customers added to the project. The domain allowlist handles the specific domain restriction.
By setting the project permission to 'Customers my team adds', you remove the public sign-up link from the portal. When combined with an email domain allowlist, approved domains bypass this restriction for email creation.
Q3Question 3
Advanced
Distinguish Among Users, Project Roles, and Permissions · Manage Team Members
A Human Resources service desk has strict confidentiality requirements.
Background: The HR team handles 'Onboarding', 'Benefits', and 'Termination' request types.
Constraint 1: 'Termination' requests must only be visible to the Reporter and members of the 'HR-Managers' group. Constraint 2: Regular HR agents (in the 'HR-Agents' group) handle 'Onboarding' and 'Benefits', but must be completely blocked from viewing or searching 'Termination' tickets.
As the JSM administrator, you decide to implement Issue-Level Security. Which approach represents the correct configuration to meet these requirements?
flowchart TD
A[Create Issue Security Scheme] --> B[Create Security Level: Highly Confidential]
B --> C[Add 'Reporter' to Level]
B --> D[Add 'Project Role: Administrators' to Level]
D --> E[Assign Scheme to HR Project]
E --> F[Automation: Set Security Level on Creation]
Answer and explanation
Correct answer: C
Issue-level security determines who can view specific tickets within a project. To restrict access to a subset of agents, you must create a specific security level that includes the Reporter (so the customer can still see their ticket) and a specific Project Role (or group) that represents the elevated agents. The 'Service Desk Team' role includes all agents, which violates Constraint 2. Automation is the standard way to dynamically apply issue security based on Request Type in JSM Cloud.
Q4Question 4
Intermediate
Distinguish Among Users, Project Roles, and Permissions · Manage Team Members
During the rollout of a new IT service desk, the manager requests that all hardware-related tickets be automatically assigned to 'John Doe', who is the lead for the Hardware team. Software tickets should be assigned to 'Mary Smith'. Which assignee configuration method is the most scalable and native way to achieve this without using automation rules?
Answer and explanation
Correct answer: A
Using Components and assigning a Component Lead is the native, scalable way to route tickets based on categorization without building automation rules. When a ticket is created with that component, Jira automatically assigns it to the designated Component Lead if the component's default assignee is configured that way.
Q5Question 5
Beginner
Distinguish Among Users, Project Roles, and Permissions · Manage Team Members
True or False: Internal users granted the 'Collaborator' role in a Jira Service Management project can communicate directly with customers by adding public comments to tickets on the customer portal.
Answer and explanation
Correct answer: B
False. Collaborators are internal users who do not consume a JSM agent license. They can view tickets and add internal comments to assist agents, but they cannot communicate directly with customers (they cannot add public comments or transition tickets to customer-facing statuses).
Q6Question 6
Beginner
Distinguish Among Users, Project Roles, and Permissions · Define Users, Project Roles, and Permissions
A newly hired support engineer reports that they cannot see the Jira Service Management icon in their Atlassian Cloud app switcher, and they cannot access any service projects. The Jira administrator verifies that the user was added to the 'Service Desk Team' role in the specific project. What is the most likely cause of this access issue?
Answer and explanation
Correct answer: A
Product Access is the foundational layer of permissions in Atlassian Cloud. If a user does not have a license/product access to Jira Service Management granted via the Admin hub, they cannot access the product interface at all, regardless of what project-level roles they have been assigned.
Register free for 6 more questions
Or unlock all 135 ACP-420 questions with explanations, timed mode and flashcards.
