Project Administration in Jira Server v1.0
Question 1
A project uses two issue types named Task and Sub-task which share the workflow shown below.
What is the maximum number of screens that can be used in the current project configuration?
- A. 9
- B. 10
- C. 8
- D. 5
- E. 6
Answer : D
Reference:
https://marketplace.atlassian.com/apps/1214484/issue-type-resolutions-for-jira?hosting=server&tab=overview
Question 2
Below you are shown an extract of a field configuration used by all issue types in your project.
The field 'A detailed description' is a custom field of type Text field (multi-line). Which two statements are true? (Choose two.)
- A. Users will be able to format text in the field.
- B. The field can only be used in combination with the Description system field.
- C. The field is mandatory in each issue type used in the project.
- D. The project is configured to use only a single screen.
- E. The maximum text length is limited to 100 characters.
Answer : AB
Reference:
https://mraddon.blog/2018/02/25/how-to-make-text-field-mu
Question 3
A project administrator wants to modify his project screen.
The project screen meets all the prerequisites for him to be able to edit it.
Which two actions can he NOT perform? (Choose two.)
- A. Remove a field
- B. Rename a tab
- C. Make a field required
- D. Rearrange existing fields
- E. Create a new field
- F. Move a tab
Answer : CE
Reference:
https://confluence.atlassian.com/jiracoreserver085/customizing-the-issues-in-a-project-981157708.html
Question 4
Elaine is the project administrator for the Finance project.
The team requests a brand new field called Currency. It must be added to the screen used on the Approval transition. How can these requirements be met?
- A. Elaine can create the field and add it to the screen.
- B. A Jira administrator must create the field and add it to the screen.
- C. A Jira administrator must create the field but Elaine can add it to the screen.
- D. Elaine can create the field but a Jira administrator must add it to the screen.
Answer : B
Explanation:
You will be taken directly to the Configure Screen page, where you can add fields to your new screen
Question 5
You are asked to change who receives notifications when issues are moved.
The settings in the default notification scheme used by your project are shown in the table below.
As a project administrator, why are you NOT able to update the notification scheme?
- A. The notification scheme is shared.
- B. You are not a Jira administrator.
- C. The extended project administration option is not enabled.
- D. The default notification scheme cannot be edited.
Answer : B
Reference:
https://community.atlassian.com/t5/Jira-questions/What-permission-is-needed-to-change-project-notification-scheme/qaq-p/947939
Question 6
A user approaches you with a problem.
She cannot see or edit the Priority system field on any of the screens of a Process Management project.
What explains the problem?
- A. The field does not have the correct configuration context.
- B. She is not listed in the priority scheme.
- C. The field is hidden in the field configuration.
- D. The field is not available for this project template.
- E. She does not have the correct permission.
Answer : C
Reference:
https://www.oasis-open.org/committees/download.php/51095/jira-manual-config.pdf
Question 7
A Jira project uses a single issue type.
Alana complains that she is not able to see the custom field Approval Board when she views a specific issue.
She can see the field on other issues in the project.
You check the screen configuration and confirm that the field is on the correct screen.
Why does Alana NOT see the field on that specific issue?
- A. The field is hidden in the field configuration.
- B. The field was disabled by a Jira administrator.
- C. The field has no value at the moment.
- D. The field is hidden by the workflow status.
- E. The field is hidden by a security level.
Answer : B
Reference:
https://confluence.atlassian.com/jirakb/fields-missing-on-screens-in-jira-server-163416168.html
Question 8
Malik is a project administrator for the HR project.
He cannot remove the Fix Version/s field from the HR project screen. Why is he NOT able to do this?
- A. Fix Version/s for the project have been archived.
- B. The Fix Version/s field is locked.
- C. The screen is used by another project.
- D. System fields cannot be removed from screens.
- E. Fix Version/s is a required field.
Answer : A
Explanation:
No further changes can be made to this version unless it is un-archived. Also it is not possible to remove any existing archived versions from an issue's affected and fix version fields or add any new archived versions.
Reference:
https://confluence.atlassian.com/adminjiraserver/managing-versions-938847201.html
Question 9
Which statement is true about configuring issue types in a project?
- A. Standard and sub-task issue types must always have their own workflows.
- B. Epics cannot have sub-tasks in a Jira Software project.
- C. There are three levels of issue types in a Jira Software project; Epic, Story, Sub-task.
- D. Sub-task issue types can have a different issue security level than their parent.
- E. An issue type scheme can have unlimited sub-task issue types.
- F. You can disable the Create Sub-task operation on some standard issue types.
Answer : F
Reference:
https://blog.testlodge.com/how-to-write-test-cases-in-jira/
Question 10
As the project administrator for the DEV project you are also responsible for managing the team's board and various filters being used on the team's dashboard.
They asked you to add a new status called Testing to the project's workflow.
What two other changes might be required? (Choose two.)
- A. The filters need to be updated to reflect the changes.
- B. The workflow screens need to be updated to reflect the new status.
- C. The new status needs to be mapped to a column on the board.
- D. The workflow has to be mapped to the issue types used in the project.
- E. Project permissions need to be updated so users can transition to the new status.
Answer : DE
Question 11
The support team has a request.
When a Bug is created, it should only display five fields. However, when it is edited, it should display fourteen fields.
Which configuration is used to implement this requirement?
- A. Issue Type Scheme
- B. Workflow Scheme
- C. Permission Scheme
- D. Field Configuration Scheme
- E. Screen Scheme
Answer : D
Explanation:
Field Configuration Scheme (Enterprise only) - the project's field configuration scheme determines which field configuration applies to issue types in this project. (A field configuration determines fields' overall visibility, requiredness, formatting (wiki/rich-text or plain) and existence on various screens).
Reference:
https://www.oasis-open.org/committees/download.php/51095/jira-manual-config.pdf
Question 12
You Update the My Changes setting in your user profile to Do not notify me.
Which statement is true?
- A. You will only be notified by email about issue operations.
- B. You will be opted out of all email notifications.
- C. You will not be notified by email of any changes you make.
- D. You will only be notified by email about workflow events.
Answer : C
Explanation:
By default all users start with preferences to not be notified by their own updates.
Reference:
https://confluence.atlassian.com/jirakb/how-to-update-all-user-profiles-for-the-notify-me-option-292126811.html
Question 13
All users should be able to transition issues in your project without restrictions.
However, some users complain that they cannot transition issues to the In Progress status. They can execute other transitions.
The workflow is shown below.
What should you request from the Jira administrator?
- A. Add a new transition from To Do to In Progress.
- B. Remove existing conditions from the global In Progress transition.
- C. Add all project users to the Transition Issues project permission.
- D. Remove existing triggers from the global In Progress transition.
- E. Add a new transition from Done to In Progress.
Answer : E
Explanation:
So we have a transition from "˜To Do"™ to "˜In Progress"™. A transition from "˜In Progress"™ to "˜Done"™. We even have a transition from "˜Done"™ to "˜To Do"™
Reference:
http://www.testmanagement.com/blog/2019/06/jira-basics-module-4-workflow-status
Question 14
You manage multiple projects which share a notification scheme.
For the Issue Moved event, you want to notify only a particular individual.
That individual needs to be selected by other users.
Which value should be used for the Issue Moved event?
- A. Single User
- B. Developers project role
- C. User Custom Field Value
- D. Current User
- E. Component Lead
- F. Single Email Address
Answer : A
Explanation:
For the issue move event, it will always notify the project which the issue is been moved to if you configure a single user in the notification,
Reference:
https://community.atlassian.com/t5/Jira-questions/Notifications-Issue-Moved/qaq-p/1042933
Question 15
A project has a single issue type named Task to manage Bugs and Feature Requests.
What requirement would result in the need to create an additional issue type to manage Bugs?
- A. Different fields should be displayed when creating a Bug based on the creator's project role.
- B. Different components should be selectable when creating Tasks versus Bugs.
- C. Different fields are needed when creating, editing or viewing Tasks versus Bugs.
- D. Different workflow transitions need to be available when Developers move a Bug through the workflow.
Answer : C