The correct answer is Company-managed Kanban board using a board sub-filter.

A Company-managed Kanban board using a board sub-filter can be based on a filter that pulls issues from multiple projects and can also apply a board sub-filter using JQL to automatically exclude issues. You can write a JQL sub-filter that omits issues with the resolution "Won't Fix" once their resolved date is older than 48 hours so the board hides them automatically. Kanban boards are appropriate here because they do not rely on sprint boundaries and they keep Done issues visible only when the filter allows them.

Company-managed Scrum board using quick filters is incorrect because quick filters are manual toggles that team members must enable or disable and they do not provide automatic hiding after a time period. Scrum boards are also sprint focused which makes automated removal of Done items by time less suitable.

Team-managed Kanban board with a board sub-filter is incorrect because team-managed boards have more limited filtering capabilities and they do not support the same cross-project board and sub-filter configuration that company-managed boards provide. That limitation prevents reliably combining three separate projects and applying an automated sub-filter across them.

Company-managed Scrum board with a board sub-filter is incorrect because Scrum boards are centered on sprints and the workflow for clearing Done issues is tied to sprint completion rather than continuous board filtering. While a company-managed Scrum board can use filters, the Kanban approach better supports continuously hiding Done items after a fixed time window.

Full AWS Practitioner Certification Question