A retired exam does not make a useful board less important
A team looks at its board and sees unrelated work mixed into the plan. Another team cannot find an important item at all. Rearranging the columns may make either board look better without changing the filter that produced the problem.
This retained practice course focuses on those board-level distinctions. Its value is in the skills the questions exercise, not a promise that you can still take the retired exam. The explanations help connect a configuration choice with what the team will actually see and do.
Start with the population, then make the flow readable
Saved filters define the intended work and project scope. Column mapping determines how workflow statuses appear to the board's audience. Swimlanes and quick filters provide additional ways to inspect the work without pretending every temporary view is the board's permanent scope.
Scrum topics include backlog, estimation, and sprint behavior. Kanban topics examine work-in-progress limits and continuous flow. These differences matter because a board used to select a sprint and a board used to manage an ongoing queue do not answer exactly the same questions.
The common thread is keeping the view honest. More cards do not necessarily mean a better population. Fewer columns do not necessarily mean a clearer workflow. The configuration should preserve the distinctions that change how the team plans, reviews, and finishes work.
Practice format
Six tests covering the retired ACA-905 board-configuration scope.
You get 6 practice tests, with 30 questions in each test (180 questions in total).
The course language is English, and the course level is Foundational.
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?
Set its saved filter to project = OPS AND labels = platform.Add an optional quick filter and keep the broad underlying board scope.
Unmap several statuses until fewer unrelated cards appear on the board.
Lower the work-in-progress limit so fewer cards can be shown.
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.
Illustrative public-page example, reworded for this edition; not a live examination item.
Check the underlying rule
For each missed item, identify whether it concerns selection, mapping, a temporary view, sprint behavior, or flow. Explain the rule before naming the setting. Use current Jira documentation to verify product behavior, and consult Atlassian's live catalog separately for an active credential. Keep the course's legacy status visible in your study plan instead of treating an old mock score as current examination readiness.



