The correct options are Board saved filter, Project permissions, Board quick filters, and Issue security levels.

Board saved filter controls which issues are included on the board by applying the board's underlying JQL. If the saved filter excludes certain projects, issue types, or specific criteria then those issues will not show up on the Active sprints board or in the Backlog even though their statuses are mapped to columns.

Project permissions determine who can browse and view issues in a project. If a user or the board context does not have the Browse Projects permission for a given project then those project issues will be invisible on the board and in the backlog regardless of status mapping.

Board quick filters are applied interactively on top of the board filter when a user enables them. An active quick filter can hide issues from both the Active sprints view and the Backlog until the filter is cleared, so a visible quick filter is a common cause of missing issues.

Issue security levels restrict visibility at the individual issue level. If an issue is assigned a security level that the viewer is not part of then that issue will not appear on the board or in the backlog even though it exists and has a mapped status.

Hide completed issues older than setting only affects how long resolved or completed issues remain visible after they are done. It does not hide active or backlog items and would not explain missing non completed issues.

Board sub filters are not the primary mechanism for items disappearing from a Scrum board that spans multiple projects. The saved filter and quick filters are the typical culprits for global exclusions.

Global permissions govern site wide capabilities and administration rights. They do not hide specific issues from a board in the way a saved filter, project permission or issue security level would.

Unmapped statuses would hide issues if statuses were not mapped to board columns, but Jordan has mapped every workflow status to a column so unmapped statuses cannot be the cause in this scenario.

Full AWS Practitioner Certification Question