Page 1 of 170
Jira Administrator Practice Exam
Questions with Correct Answers &
Explanations | Graded A+ Study Guide
Question 1
Your team is small, wants to administer its own project
independently, and prefers uncomplicated workflows with built-in
roles. Which project type should you recommend?
A) Company-managed project
B) Team-managed project
C) Business-managed project
D) Classic project
Correct Answer: B
Rationale: Team-managed projects are designed for small,
autonomous teams that need to manage their own project
,Page 2 of 170
configuration without relying on a central Jira administrator. They
have built-in roles and simplified workflows, making them ideal
for teams that prefer "uncomplicated workflows" as described in
the scenario.
Question 2
A large enterprise wants all projects to follow the same
standardized workflow, screen schemes, and field configurations.
Which project type should they use?
A) Team-managed projects
B) Company-managed projects
C) Personal projects
D) Next-gen projects
Correct Answer: B
,Page 3 of 170
Rationale: Company-managed projects (formerly "classic"
projects) are designed for centralized control where a Jira
administrator configures schemes (workflow schemes, screen
schemes, permission schemes) that can be shared across multiple
projects, ensuring consistency and standardization across the
enterprise.
Question 3
What is a key limitation of team-managed projects compared to
company-managed projects?
A) Team-managed projects cannot use Scrum boards
B) Team-managed projects cannot be shared across multiple
teams
C) Team-managed projects have built-in roles and cannot use
global permission schemes
D) Team-managed projects do not support custom fields
, Page 4 of 170
Correct Answer: C
Rationale: Team-managed projects have built-in, simplified roles
(Administrator, Member, Viewer) and cannot leverage global
permission schemes or custom role configurations. Company-
managed projects offer more granular permission control through
project roles and permission schemes.
Question 4
At NebulaOps, a small feature squad must independently
administer its project, and each project requires a distinct
configuration while the team prefers uncomplicated workflows.
Which Jira project type should they choose?
A) Company-managed project
B) Team-managed project
C) Classic project
D) Template-based project
Jira Administrator Practice Exam
Questions with Correct Answers &
Explanations | Graded A+ Study Guide
Question 1
Your team is small, wants to administer its own project
independently, and prefers uncomplicated workflows with built-in
roles. Which project type should you recommend?
A) Company-managed project
B) Team-managed project
C) Business-managed project
D) Classic project
Correct Answer: B
Rationale: Team-managed projects are designed for small,
autonomous teams that need to manage their own project
,Page 2 of 170
configuration without relying on a central Jira administrator. They
have built-in roles and simplified workflows, making them ideal
for teams that prefer "uncomplicated workflows" as described in
the scenario.
Question 2
A large enterprise wants all projects to follow the same
standardized workflow, screen schemes, and field configurations.
Which project type should they use?
A) Team-managed projects
B) Company-managed projects
C) Personal projects
D) Next-gen projects
Correct Answer: B
,Page 3 of 170
Rationale: Company-managed projects (formerly "classic"
projects) are designed for centralized control where a Jira
administrator configures schemes (workflow schemes, screen
schemes, permission schemes) that can be shared across multiple
projects, ensuring consistency and standardization across the
enterprise.
Question 3
What is a key limitation of team-managed projects compared to
company-managed projects?
A) Team-managed projects cannot use Scrum boards
B) Team-managed projects cannot be shared across multiple
teams
C) Team-managed projects have built-in roles and cannot use
global permission schemes
D) Team-managed projects do not support custom fields
, Page 4 of 170
Correct Answer: C
Rationale: Team-managed projects have built-in, simplified roles
(Administrator, Member, Viewer) and cannot leverage global
permission schemes or custom role configurations. Company-
managed projects offer more granular permission control through
project roles and permission schemes.
Question 4
At NebulaOps, a small feature squad must independently
administer its project, and each project requires a distinct
configuration while the team prefers uncomplicated workflows.
Which Jira project type should they choose?
A) Company-managed project
B) Team-managed project
C) Classic project
D) Template-based project
