Free ACP-100 – Jira Administrator Exam Practice Test Question

Select all that apply, then click Submit answer.

• ○

  For the Fire issue type, the Description field should have a default value of “Termination”.
  

• ○

  For both issue types, the Employee Name custom field must be required upon creation and must never be
  
  blank.
  

• ○

  For the Hire issue type, the field description for the Due Date field should read “First day of work”.

• ○

  For both issue types, the Resolution should be set once the issues are being resolved.
  

• ○

  For both issue types, the Assignee field should be hidden when creating but not when viewing an issue.
  

• ○

  For the Fire issue type, the default value for the Priority field should be Blocker.
  
  
  

Select all that apply, then click Submit answer.

• ○

  Set Login Mode to Secure.

• ○

  Require character variety for the user name.
  

• ○

  Require that a password is not too similar to another user’s password.
  

• ○

  Require a certain length for passwords.
  

• ○

  Require that a password is not too similar to the user name or email address.
  
  
  

Select all that apply, then click Submit answer.

• ○

  security level
  

• ○

  project permission
  

• ○

  workflow condition
  

• ○

  project role
  

• ○

  global permission
  

• ○

  group
  
  
  

Select all that apply, then click Submit answer.

• ○

  Global Transitions
  

• ○

  Conditions
  

• ○

  Triggers
  

• ○

  Validators
  

• ○

  Common Transitions
  
  
  

Select all that apply, then click Submit answer.

• ○

  Implement an issue security scheme with three levels: (#1) Group (jira-patients), (#2) Reporter, and (#3) Group (medical-board).
  

• ○

  Implement an issue security scheme with two levels: (#1) Reporter and (#2) Group (medical-board).
  

• ○

  In the permission scheme, add Reporter and Group (anonymous) to Browse Projects and Create Issues.
  

• ○

  In the permission scheme, add Group (jira-patients) and Group (medical-board) to Browse Projects and Create Issues permissions.
  

• ○

  Implement an issue security scheme with one level: Reporter and Group (medical-board).
  
  
  

Select an option, then click Submit answer.

• ○

  Jon does not have the Browse Users global permission.
  

• ○

  Jon does not have the View Users project permission.
  

• ○

  Jon does not have the correct field security permission for the Comment field.
  

• ○

  The field configuration for the Comment field is not set to Autocomplete Renderer.
  
  
  

Select an option, then click Submit answer.

• ○

  The issue type’s field configuration for Component/s is not set to Required.
  

• ○

  The default assignee for the issues’ component is still set to Unassigned.
  

• ○

  The post function Assign to Lead Developer is missing in the create transition.

• ○

  Users creating this issue type do not have the Assign Issue permission.
  

• ○

  The assignee is being set to Unassigned in the first post-function of the create transition.
  
  
  

Select an option, then click Submit answer.

• ○

  Adjust the Day Format in the Jira look and Feel configuration.
  

• ○

  Adjust the jira.date.time.picker.java.format in the advanced settings configuration.
  

• ○

  Adjust the jira.date.picker.java.format in the advanced settings configuration.
  

• ○

  Adjust the Complete Date/Time Format in the Jira Look and Feel configuration.
  

• ○

  Adjust the language and time zone preferences in Max’s user profile.
  
  
  

Select an option, then click Submit answer.

• ○

  There is a workflow step property configured.
  

• ○

  He is not a member of a security level.
  

• ○

  There is a workflow condition configured.
  

• ○

  The Attachment field is missing from the screen for that issue type.
  

• ○

  He does not have the correct project permission.
  
  
  

Select an option, then click Submit answer.

• ○

  Configure individual screens for each issue type and update the priority scheme.
  

• ○

  Configure individual field configuration for each custom field and update the priority scheme.
  

• ○

  Create unique field contexts for each issue type for the desired fields.
  

• ○

  Configure individual field configurations for each issue type.
  

• ○

  Configure individual field contexts for each custom field and update the priority scheme.
  

• ○

  Configure individual screens for any combination of issue operation and issue type.