Jira Administrator v1.0 (ACP-100)

Page:    1 / 5   
Total 75 questions

Jon is a new Jira user. He reports that adding comments to Jira isn"™t working as expected. When he attempts to @mention a user, no list of available users is provided. Because he does not know everyone"™s username, he is unable to target comments to specific users.
What is the cause of this problem?

  • A. Jon does not have the Browse Users global permission.
  • B. Jon does not have the View Users project permission.
  • C. Jon does not have the correct field security permission for the Comment field.
  • D. The field configuration for the Comment field is not set to Autocomplete Renderer.


Answer : D

Reference:
https://community.atlassian.com/t5/Jira-questions/Can-t-Mention-other-users/qaq-p/5238

You needed to replace the legacy Jira group all-staff-europe with a newly created all-staff-global group.
You created the new group and you migrated all users to the new group.
Then you deleted the legacy group.
Which four problems might users report after the change? (Choose four.)

  • A. Filter subscriptions send out errors instead of issues statistics.
  • B. Workflow transitions are hidden from certain users.
  • C. Users are not able to perform bulk change operations.
  • D. Users are not able to log in to Jira anymore.
  • E. Comments that were restricted to the legacy group are lost.
  • F. Filter results return an incorrect number of issues.


Answer : BCEF

Critical production bugs in a Jira Software project are hidden with an issue security scheme that has a single security level.
Only project administrators are listed in the security level and granted the Set Issue Security permission.
A new requirement states that a few other Jira Core users, who have Browse Projects permission, should be able to see the hidden issues. These users will vary per issue and be selected from across various groups.
What needs to be added to the security level?

  • A. Application access
  • B. User custom field value
  • C. Group custom field value
  • D. Project role
  • E. Single Users
  • F. Group


Answer : D

Reference:
https://confluence.atlassian.com/adminjiracloud/configuring-issue-level-security-776636711.html

You have just deployed a new Support Workflow and Support Notification Scheme. Manager Maria should be receiving notifications when users click the Escalate workflow transition, but she is not.
Identify two possible reasons Maria is not receiving the notifications. (Choose two.)

  • A. Maria is not listed in the right custom event of the Support Notification Scheme.
  • B. The Escalate workflow transition is firing the wrong event.
  • C. The right custom event has been deleted from the Support Notification Scheme.
  • D. Maria is not listed in the Issue Escalated (System) event of the Support Notification Scheme.
  • E. The Escalate workflow transition is firing the right event, but the event is marked Inactive.
  • F. The Escalate workflow transition is firing the right event but uses the wrong email template.


Answer : CF

Your business users want to know more about what is happening with the issues raised by their business unit. They gave you a list of situations in which they want to get emails, so you know which parts of the shared notification scheme they want to be added to.
You consult with the project owner.
He doesn"™t want any changes to the emails that go to developers and testers.
The project owner approves of the business users getting the emails, but he would like to retain control of who gets emails for his project.
How can you satisfy these requests?

  • A. Place the business users in a group and add that group to the events in the notification scheme.
  • B. Modify the events in the workflow so they send the emails to the business users.
  • C. Create a role for business users and add that role to the events in the notification scheme.
  • D. Add the business users as Watchers on the issues.


Answer : A

The HR team approaches you with new requirements they want you to implement:
✑ Allow users to send requests into Jira by emailing "[email protected]."
✑ Have those emails automatically turned into "Holiday Requests" in the HR project.
You have already set up an Incoming Mail Server and a mail handler to "Create a new issue or add a comment to an existing issue."
Which three additional options can you set with this mail configuration? (Choose three.)

  • A. Create new Jira users based on the From address.
  • B. Set Assignee and Watchers.
  • C. Set default Reporter.
  • D. Set a custom field.
  • E. Set Environment.


Answer : CDE

Inspect your current Incoming Mail Handler configuration:


Identify one reason why the current configuration is not fetching emails as planned.

  • A. The blank space in the Incoming Mail Handler name will cause internal errors.
  • B. The syntax of the specified Folder Name is invalid and should be corrected to "˜/spam"™.
  • C. A delay of 10000 minutes is not a valid setting and will cause an error.
  • D. The external mail service is not able to write the messages to the specified folder.


Answer : D

Reference:
https://confluence.atlassian.com/jirakb/troubleshoot-incoming-mail-in-jira-service-desk-790960076.html

You inherited a mature Jira instance with hundreds of projects and associated schemes. You are trying to optimize the administration of the instance.
You need to create a new project and determine which schemes to apply.
Select the two best approaches. (Choose two.)

  • A. Create a custom project template that uses the most common shared schemes.
  • B. Use the Scheme Helper admin tool to see which combinations of schemes are compatible.
  • C. Use one of the project templates other than Jira Default Schemes.
  • D. Attempt to generalize existing schemes with project roles and share those.
  • E. Evaluate existing shared schemes based on common project category or other criteria.
  • F. Create a project using the Jira Default Schemes and then create new schemes to avoid sharing conflicts.


Answer : BE

You are designing a complex new workflow. Two of the requirements are listed below:
1. Any user should be able to trigger the Put On Hold transition from any status in the workflow.
2. Only users with the Close Issues permission should be able to Close the issue at any point in the flow.
Based only on these requirements, which two workflow elements should you use? (Choose two.)

  • A. Global Transitions
  • B. Conditions
  • C. Triggers
  • D. Validators
  • E. Common Transitions


Answer : BC

Reference:
https://confluence.atlassian.com/adminjiracloud/working-with-workflows-776636540.html

A project is using the Approval workflow shown.


The project lead has communicated the following change requests:
✑ It should be possible to transition issues into the Awaiting Approval status from any other status apart from the Approved status.
✑ Different transition screens will be needed for each transition into the Awaiting Approval status.
How do you configure the workflow to satisfy these requirements?
A.
✑ Create a global transition to the Awaiting Approval status.
✑ Create multiple appropriate transition screens and associate it with the global transition.
B.
✑ Reuse the Request approval transition between the Open and Awaiting Approval status.
✑ Create an appropriate transition screen and associate it with the transition.
C.
✑ Create a transition from the Open to the Awaiting Approval status.
✑ Create appropriate transition screens and associate them with the individual transitions into the Awaiting Approval status.
D.
✑ Create a global transition to the Awaiting Approval status.
✑ Create an appropriate transition screen and associate it with the global transition.
E.
✑ Create a transition from the Open to the Awaiting Approval status.
✑ Reuse the existing transition screen from the Request approval transition.



Answer : D

You receive workflow configuration requirements for issues in the Closed status. They are as follows:
✑ Users must NOT be able to edit issues in this status.
✑ Jira administrators must be able to edit issues in this status.
✑ Only users in the release-managers group should see the transition to the Re-opened status
Which combination of two workflow configuration items should you use to meet these requirements? (Choose two.)

  • A. Properties
  • B. Post functions
  • C. Conditions
  • D. Validators
  • E. Triggers


Answer : CD

You need to make the following changes to an existing workflow:
1. A transition should only be available if code has been committed against the issue.
2. Only users in a specific project role can see a transition
3. Issues must not be commented on in a specific status.
4. The resolution should be set automatically.
5. A transition should send out a specific notification email.
Which workflow elements will you use to implement the desired changes?

  • A. 1 condition, 1 validator, 2 post functions, 1 property
  • B. 2 conditions, 2 validators, 1 property
  • C. 1 condition, 1 validator, 1 post function, 2 properties
  • D. 2 validators, 2 post functions, 1 property
  • E. 2 conditions, 2 post functions, 1 property


Answer : C

A user says she can see the Ready for Testing transition but cannot successfully execute it.
Why can"™t the user execute this transition?


  • A. The status property of Code Review prevents the Developer role from executing the transition.
  • B. A Condition on the transition requires the user to be in the Developer role.
  • C. A Validator on the workflow transition requires the user to be in the Developer role.
  • D. The status property of In Progress prevents the Developer role from executing the transition.


Answer : D

You have a project with several issue types, associated unique workflows, and a number of components.
The decision has been made to have all new issues assigned automatically.
To that end, you"™ve set default assignee(s) for the project lead, component leads, and removed the Assignee field from the screens associated with the Create
Issue operation.
One of the issue types is still being created without an Assignee.
What is the most likely cause of the problem?

  • A. The issue type"™s field configuration for Component/s is not set to Required.
  • B. The default assignee for the issues"™ component is still set to Unassigned.
  • C. The post function Assign to Lead Developer is missing in the create transition.
  • D. Users creating this issue type do not have the Assign Issue permission.
  • E. The assignee is being set to Unassigned in the first post-function of the create transition.


Answer : E

Your project has three issue types that share a common workflow.
Which reason would make you recommend the implementation of separate workflows for each issue type?

  • A. The issue types need different sets of priorities.
  • B. Each issue type uses a different issue security level.
  • C. Different project roles are working on the issue types.
  • D. One of the issue types needs a new status.
  • E. The issue types need different sets of resolutions.


Answer : B

Page:    1 / 5   
Total 75 questions