ACA-900 Atlassian Certified Associate - Jira Essentials Practice Questions
Prepare for ACA-900 with more than an answer.
- Exam fee
- $100 USD
- Time limit
- 60 minutes
- Questions on the exam
- Up to 30
- Passing score
- 68%
- Level
- Atlassian Certified Associate (ACA)
- Valid for
- 24 months
Domains covered on the exam 5
- Basic Concepts21%
- Jira Navigation15%
- Rovo Basics3%
- Issue Lifecycle, Workflow, and Boards24%
- Working with Work Items37%
- 1
An organization has recently enabled Atlassian Rovo. A team member is assigned a complex Jira issue that contains a lengthy description and over 50 comments detailing a month-long discussion. The user wants to quickly understand the core problem and current status without reading the entire thread. Which Rovo capability is best suited for this specific task?
Show answer details
Correct answer: B
Rovo Chat is the conversational AI feature that excels at summarizing lengthy content, answering questions about specific Jira issues, and drafting text. Rovo Search is for finding information across connected apps, and Rovo Agents are specialized virtual teammates configured to automate specific tasks.
- 2
A Jira administrator is training new project leads on workflow concepts. They emphasize the difference between the actual stages of work and the actions required to move between those stages. In Jira workflow terminology, what represents the action a user takes that moves an issue from "To Do" to "In Progress"?
Show answer details
Correct answer: D
In Jira, a 'Status' represents the current state of an issue (e.g., To Do, In Progress). A 'Transition' is the link or action that connects two statuses, allowing an issue to move from one to the other. Status Categories are the broad groupings (To Do, In Progress, Done) that underlie individual statuses.
- 3
Company X has two distinct teams operating in Jira.
Team Alpha builds new software features. They plan their work in two-week iterations, committing to a specific scope of work at the start of the period and aiming to deliver a product increment by the end.
Team Beta handles IT support tickets. Their focus is on resolving issues as quickly as they arrive, maintaining a continuous flow of work. However, Team Beta frequently struggles with taking on too much work simultaneously, causing severe bottlenecks and delays.
Which board configurations are most appropriate for Team Alpha and Team Beta to address their respective working styles and challenges?
Show answer details
Correct answer: C
Team Alpha operates in time-boxed iterations (sprints), which requires a Scrum board. Team Beta requires continuous flow, which dictates a Kanban board. Because Team Beta struggles with taking on too much simultaneous work, configuring Work In Progress (WIP) limits on their Kanban board will visually restrict the number of issues allowed in specific columns, alleviating their bottleneck issue.
graph TD A[Team Alpha] -->|Time-boxed Iterations| B[Scrum Board] C[Team Beta] -->|Continuous Flow| D[Kanban Board] D -->|Bottleneck Issues| E[Apply WIP Limits] - 4
A technology firm has adopted the Atlassian suite to manage their operations. They need a tool specifically designed for the software development team to track bugs, manage agile sprints, and plan releases. Which Atlassian product is built primarily for these specific use cases?
Show answer details
Correct answer: C
Jira Software is specifically designed for agile software development teams. It includes features like Scrum and Kanban boards, backlog management, sprint planning, and release tracking. Jira Service Management is tailored for IT service desks, while Confluence is a wiki for documentation. Jira Work Management is designed for business teams like HR or Marketing.
- 5
A large enterprise is standardizing workflows across 15 different development teams. The Project Management Office (PMO) requires a single, rigid workflow scheme to be shared across all 15 teams to ensure consistent reporting.
Meanwhile, a newly acquired startup within the enterprise needs immediate autonomy. They want the freedom to modify their own project's workflow on the fly without affecting any other teams or requiring a Jira Administrator's intervention.
Based on these requirements, which project types should be provisioned for the enterprise PMO teams and the startup team respectively?
Show answer details
Correct answer: C
Company-managed projects are controlled by Jira administrators using shared schemes. This is perfect for the PMO that needs 15 teams to share a standardized workflow. Team-managed projects grant project leads autonomy to configure their own workflows without affecting other projects or requiring global admin rights, which perfectly suits the startup's needs.
graph TD A[Jira Instance] --> B[Company-Managed] A --> C[Team-Managed] B --> D[Shared Workflow Scheme] D --> E[PMO Team 1] D --> F[PMO Team 2] C --> G[Independent Workflow] G --> H[Startup Team] - 6
A product manager is planning a major new feature called 'User Authentication Redesign'. They need to break this large initiative down into smaller, actionable pieces of work that the development team can tackle over the next three sprints. Which TWO statements correctly describe the standard Jira issue hierarchy and usage for this scenario? (Select TWO)
flowchart TD E["Epic (Large Initiative) Spans Multiple Sprints"] S1["Story (Standard Issue) Sized for One Sprint"] S2["Task (Standard Issue) General Work"] S3["Bug (Standard Issue) Defect"] ST1["Sub-task (Lowest Level)"] ST2["Sub-task (Lowest Level)"] ST3["Sub-task (Lowest Level)"] E --> S1 E --> S2 E --> S3 S1 --> ST1 S2 --> ST2 S3 --> ST3 ST1 -->|Cannot have children| X["❌ Invalid Hierarchy"] style E fill:#fff3e0 style S1 fill:#f3e5f5 style S2 fill:#f3e5f5 style S3 fill:#f3e5f5 style ST1 fill:#e8f5e9 style ST2 fill:#e8f5e9 style ST3 fill:#e8f5e9Show answer details
Correct answer: A, D
In Jira's standard hierarchy, Epics sit at the top level and represent large initiatives that span multiple sprints. Sub-tasks are the lowest level and must be attached to standard issues (like Stories, Tasks, or Bugs). Sub-tasks cannot have their own child sub-tasks, and Stories cannot act as parents to Epics.
In Jira's standard hierarchy, Epics sit at the top level and represent large initiatives that span multiple sprints. Sub-tasks are the lowest level and must be attached to standard issues (like Stories, Tasks, or Bugs). Sub-tasks cannot have their own child sub-tasks, and Stories cannot act as parents to Epics.
