WHY JIRA BOARD CONFIGURATION?
Make the board reflect the work.
A board looks empty after a workflow change, yet the missing work still appears in search. Repairing the view starts with understanding how filters, statuses and columns combine to display it.
Learning board configuration helps you create views that support planning and reveal work in progress. You can diagnose misleading signals, distinguish presentation from underlying work and adapt a board to the team’s actual process.
The former ACA-905 assessment offered a structured way to test this knowledge. Its retirement does not remove the practical value of configuring boards that help teams understand and manage their work.
Investigate work missing from a board
Check filters and status mappings before changing work items so you can locate the source of an omission.
Make blocked work easier to discuss
Present the workflow clearly so people can spot work waiting for attention and agree who should respond.
Keep planning views consistent with reality
Connect backlog and sprint behavior to configuration so the team understands which work is available for planning.
Adapt views without changing shared work
Distinguish display adjustments from data or workflow changes that could affect people using other boards and reports.
FOUNDATIONS & PRACTICE
Review ACA-905 board skills.
The questions retain the former ACA-905 scope for configuring and troubleshooting Jira boards. Scenarios ask you to follow how selected work becomes a visual planning view and to identify which setting explains unexpected behavior.
Treat attempts as a prompt for practical investigation in current Jira. Compare explanations with official board documentation, especially where product terminology has changed; the value here is stronger operational understanding rather than preparation for an available examination.
- Practice tests
- 6
- Total questions
- 180
- Questions per test
- 30
- Time per test
- Not specified
What you’ll practice
Retained coverage spans board filters, status and column mappings, swimlanes, quick filters, Scrum backlogs, estimation and Kanban flow. Check current product guidance when applying an older scenario to a live configuration.
Is this the right fit?
For Scrum Masters, team leads, and Jira users or administrators who already know the basics and want retained board-configuration practice. It is not for someone seeking an active ACA-905 appointment. It also does not replace deeper Jira administration study for shared workflow schemes, global controls, or organization-wide access.
A sample of the reasoning
A board should include only work from project OPS carrying the label platform. Its current view contains unrelated projects, and the work items themselves should not change. Which fix best expresses the intended board scope?
Choose an option to reveal the reasoning.
Answer and distractor analysis
Best answer: A. A defines the intended population directly. A quick filter can narrow a temporary view but leaves the underlying scope broad. Status mapping and WIP limits answer different questions; neither expresses the required project-and-label condition. The test is whether the right records are selected, not whether the board happens to look less crowded.
Field Notes
Explore related Field Notes
Practical perspectives on the ideas behind your course and how they apply at work.
Continue exploring
More Jira project administration practice tests.
ACP-620 Exam: 6 Mock Tests Managing Jira Projects for Cloud
Project-administration practice across roles, components, versions, workflows, boards, releases, and reports. For learners who want to connect Jira configuration with how a team plans and delivers.
ACP-120 Exam: 6 Practice Tests Jira Administrator for Cloud
Advanced Jira Cloud administration practice focused on configuration relationships and shared impact. Work through permissions, schemes, fields, screens, workflows, and cross-project diagnosis.
ACA-900 - Jira Software Essentials 6 Practice Tests
Foundational Jira practice in work items, boards, backlogs, workflows, search, and reports. Retained Jira Software Essentials material; review current terminology and Rovo expectations separately.